Balloon notification keeps popping up and is driving me nuts

[theahadub]

having the same issue also

[knoa]

Update:
2025-11-22 (Nov 22) The pop-up appeared on 14.2. So I downgraded it to 1.12.4.

Since then, 1.12.4 works fine for me.

[crobin]

Originally Posted by knoa

Update:
2025-11-22 (Nov 22) The pop-up appeared on 14.2. So I downgraded it to 1.12.4.

Since then, 1.12.4 works fine for me.

This works with the smaller prompter. I have the new Prompter XL and you are unable to mirror the screen with the older version of DisplayLink which renders CameraHub useless.

Waiting for a fix...

[Szymon]

Thank you for your patience. A release with a fix for this issue is expected next week.

Regards,
Szymon

[Jamesface]

I see that driver version 15.0.0 is now live with the release notes including "Fixed DisplayLink App menu bar popping up automatically without user interaction. (VIFR-7107)"

[Szymon]

Hi Jamesface,

You've noticed more quickly than I shared the news 😊 Yes, the release is out now and everyone from this thread is encouraged to test it and share feedback 🤞

Link: https://www.synaptics.com/products/d...ownloads/macos


Regards,
Szymon

[JBB]

Originally Posted by Szymon

Hi Jamesface,

You've noticed more quickly than I shared the news 😊 Yes, the release is out now and everyone from this thread is encouraged to test it and share feedback 🤞

Link: https://www.synaptics.com/products/d...ownloads/macos


Regards,
Szymon

New version still has the pop up. Admittedly it is happening less often.

[Szymon]

Hi JBB,

Thank you for your feedback. It would be really helpful if you reported your case following this FAQ:
https://support.displaylink.com/know...to-displaylink

Thanks!
Szymon

[JBB]

I have done so.

[knoa]

Following up on my previous report: I’ve been using version 15.0 for three days now, and the menu bar issue seems to be fully resolved in my environment (macOS 15.7.2 with Duet Display). I haven't experienced the automatic pop-up even once since the update.

I noticed JBB reported that the issue still persists for them (though less frequently), but at least in my case, the fix (VIFR-7107) appears to be working perfectly.

I’ll keep an eye on it for a while longer and will post an update if the behavior returns, but for now, it looks like I won't need to roll back to 1.11.0. Thanks for the fix!