https://bugs.kde.org/show_bug.cgi?id=511499
Kevin Krammer <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #23 from Kevin Krammer <[email protected]> --- The easiest way to reproduce this is to restart the service (simulating session logout/login) once the status icon is shown. 1. Verify that the status icon is shown 2. Verify that the timestamp in `.local/state/discovernotifierstaterc` is less than your "update interval" old (in my case less than 24h) 3. systemctl --user restart [email protected] Expected: Status icon indicating that there are updates Observed: No icon As luca pointed out in https://bugs.kde.org/show_bug.cgi?id=511499#c10 the issue seems to have been introduced by a workaround for a bug report about checks happening too often. Given the multiple backends this is probably difficult to actually fix, so there was an attempt to hide this or mitigate the UI "noise" by remembering the last time the user was notified about updates. However, the check is accidentally applied against the status not the notification. I.e. the check is in `NotifierItem::shouldShowStatusNotifier()` when it should probably be in `DiscoverNotifier::notifyAboutUpdates()`, `DiscoverNotifier::showUpdatesNotification()` or `DiscoverNotifier::showDiscoverUpdates()` (these seem to be the places that deal with the actual notification, not the status/state) -- You are receiving this mail because: You are watching all bug changes.
