Plasma 6.5 : plasma-discover: discover-notifier : no more icon in systray

Debian Testing and Debian Sid.
There is no icon in systray showing when updates are available.
No pop-up message.
I noticed the problem since version 6.5.0 and it has not been resolved in 6.5.1.
/usr/lib/x86_64-linux-gnu/libexec/DiscoverNotifier --check-delay 20 is running.

Best, Luca.

I dual-boot Debian 13 (stable) and 14 (testing), and neither have this problem. Maybe you can try re-installing plasma-discover package concerned if you haven’t done already?

Thanks for the reply. I’m waiting for version 6.5.1 in testing. if it doesn’t work I proceed with more in-depth investigations. in the meantime I made myself a bash/py script :wink:

I’ve seen the same issue on KDE Neon with 6.5.0

I managed to get it to work by copying an old PlasmaDiscoverUpdates file into ~/.config with this content:

[Global] 
LastNotificationTime=2024,12,24,18,51,40.263 

The icon appears in the systray, but after that the PlasmaDiscoverUpdates file is empty. I’ll try removing write permissions from the file…..

I have this file, owned by me with read/write permissions restricted to me only, which shouldn’t be a problem, and it appears to have been last modified on 30th October, i.e. when there were some software package updates last. It’s empty now because there are no updates. I’ll keep an eye on it to see if a similar problem also occurs here. :wink:

Here seems working only if it is not empty and with an old LastNotificationTime.

Preventing it from being overwritten it works.

it’s a bad workaround :wink:

This is not the first time there are problems with notifier in Debian.

Problem persists after update to 6.5.1 on KDE Neon.

I have now removed the empty file and restarted the service but obviously there currently no updates yet.

Added an upstream bug ticket

I noticed that LastNotificationTime is now set in the ~/.local/state/discovernotifierstaterc file. Maybe it’s having trouble determining the TriggerTime. I set the update notification frequency to daily. If I manually change the LastNotificationTime to more than a day ago, it seems to work. I’ll update and wait until tomorrow afternoon :wink:

1 Like

Aha!

If the setting migrated then this would (somewhat) explain the empty file.

The other files has last Monday as the LastNotificationTime value but my settings are to check daily.

with debug enabled:

org.kde.plasma.discover.notifier: Not triggering, earliestNextTriggerTime is DateTime(2025-11-03 13:24:38.999 UTC Qt::TimeZone UTC )

It’s probably insensitive to everything that happens until tomorrow :wink: