@mrjj said in Win toast / balloon notifications stopped working recently on windows 10 with Qt: Hi tried your code (Qt 5.12.6) in winVer1803 which is rather old now. I didnt update to 1903 as had many issues at work with it. No toast was shown using your code. ( I did assign valid icon) So in what version did you actually see that code work ? I saw the code work on Windows 10 Enterprise winVer1803 in August. Now still on winVer1803 (with hotfixes KB4512576, KB4516115, KB4521861, KB4523203, KB4525237 installed in the meantime) it's not working as I said. But recently I tested the code on Windows 10 winVer1903, and it worked on Qt 5.7 and Qt 5.12, the test notification was showing up! It doesn't make any sense to me. I might have to try using the new Windows 10 api to post the notifications, which is ugly or maybe impossible with using Visual Studio 2015.

Like @kshegunov already wrote using singleton should be avoided when possible and your use case really does't need any singleton. It sounds that you are rather creating tight coupling between your different classes rather that have a lean path to use system tray. So what are all these classes doing with the system tray icon and that menu ?

I have the same issue with updating the context menu with Qt 5.6 on Ubuntu 16.04 KDE Neo.

I tested in Ubuntu 14.04 up to 15.10 and the tray icon is still not shown. The systray whitelist is not available any more in those distributions though, and I'd rather not have to install packages that bring back the tray icon like https://launchpad.net/~gurqn/+archive/ubuntu/systray-trusty. I thought Qt 5.4.2 already supported app indicators?

OK, we found how to use -bundle... https://developer.apple.com/library/mac/documentation/Porting/Conceptual/PortingUnix/compiling/compiling.html

By reading the documentation I linked to and the examples also available from Qt. The "System Tray Icon" example is a good start.

Good, glad ya got it sorted out. Sorry I've been super busy lately and haven't lurked the forums here. :)

@Wieland Thanks for the reply. I'll verify with Ubuntu GNOME to see if the fix has been backported to Ubuntu. For future reference: I'm using the libraries provided by the official Ubuntu repositories.