DESCRIPTION I'm having issues with Discover's notifier on one of my two Fedora 41 computers. This seemed to start within the last few months (I hadn't really noticed that it wasn't showing up so I don't know exactly when this started). I see the service for the Discover notifier running: ~> systemctl status --user app-org.kde.discover.notifier@autostart.service ● app-org.kde.discover.notifier@autostart.service - Discover Loaded: loaded (/etc/xdg/autostart/org.kde.discover.notifier.desktop; generated) Drop-In: /usr/lib/systemd/user/service.d └─10-timeout-abort.conf Active: active (running) since Fri 2024-12-27 22:43:07 EST; 2min 36s ago Invocation: e13b0d4d9a514509ae743609bf15203c Docs: man:systemd-xdg-autostart-generator(8) Process: 255559 ExecCondition=/usr/lib/systemd/systemd-xdg-autostart-condition KDE (code=exited, status=0/SUCCESS) Main PID: 255614 (DiscoverNotifie) Tasks: 14 (limit: 75898) Memory: 315.1M (peak: 316.4M) CPU: 2.371s CGroup: /user.slice/user-1000.slice/user@1000.service/app.slice/app-org.kde.discover.notifier@autostart.service └─255614 /usr/libexec/DiscoverNotifier Dec 27 22:43:07 systemd[3064]: Starting app-org.kde.discover.notifier@autostart.service - Discover... Dec 27 22:43:07 systemd[3064]: Started app-org.kde.discover.notifier@autostart.service - Discover. I do not however see the discover notifier on this computer. I also don't see any mention of it in the system tray settings. Directly running /usr/libexec/DiscoverNotifier in a terminal also yields no visible discover notifier. This seems vaguely like Bug 495651, however, I don't even see the icon when there _are_ updates. I also don't recall getting the notifications from Discover that updates have been found that need installed despite having my settings set to check things daily. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 41 KDE Plasma Version: 6.2.4 KDE Frameworks Version: 6.9.0 Qt Version: 6.8.1 Kernel Version: 6.12.5-200.fc41.x86_64 (64-bit) Graphics Platform: Wayland Processors: 32 × AMD Ryzen 9 7950X 16-Core Processor Memory: 61.9 GiB of RAM Graphics Processor: AMD Radeon RX 7900 XTX Manufacturer: ASUS
Please open two terminals In one run: systemctl --user stop app-org.kde.discover.notifier@autostart.service killall -9 DiscoverNotifier QT_LOGGING_RULES="org.kde.*=true" /usr/libexec/DiscoverNotifier In the other: busctl --user emit / org.kde.discover NotifyNotifier Then wait a bit and get the output from the first terminal to attach to this bug report.
(In reply to Harald Sitter from comment #1) > Please open two terminals > > In one run: > > systemctl --user stop app-org.kde.discover.notifier@autostart.service > killall -9 DiscoverNotifier > QT_LOGGING_RULES="org.kde.*=true" /usr/libexec/DiscoverNotifier > > In the other: > > busctl --user emit / org.kde.discover NotifyNotifier > > Then wait a bit and get the output from the first terminal to attach to this > bug report. Not much to report: > DiscoverNotifier: no process found > org.kde.plasma.libdiscover.backend.packagekit: using... PackageKit::Transaction(0x5564fcd70a20) "/31449_dcdaeebd" > org.kde.plasma.libdiscover.backend.packagekit: using... PackageKit::Transaction(0x5564fce750f0) "/31450_bdabbdeb"
Well that at least suggests it tries to talk to packagekit. what's the output of pkcon get-updates
Created attachment 177528 [details] pkcon get-updates output while tray icon is working At this particular moment it's working (but wasn't last night). I'll make a mental note to grab this output when it's not working.
Created attachment 177563 [details] pkcon get-updates output while tray icon is NOT working So, the tray icon isn't appearing. The output looks pretty much the same. Basically, I opened discover, it fetched updates and it reports there are updates to be installed but no tray icon appeared.
Has enough time passed as well? Note that we only notify about updates after a day or so ( I believe we have a setting for that).
(In reply to Harald Sitter from comment #6) > Has enough time passed as well? Note that we only notify about updates after > a day or so ( I believe we have a setting for that). So, I saw updates earlier in the week and I've waited and waited. My computer is now sitting at 5+ days of uptime, at least the last 3 there have been 25 updates available, now there's 100+. I think in general it's a downgrade as well that the discover tray no longer notifies immediately after discover notes there are updates (via manual check or not).
Created attachment 177891 [details] Another not working pkcon get-updates output log Here's a fresh copy of those 100 updates and the command output requested before: systemctl --user stop app-org.kde.discover.notifier@autostart.service killall -9 DiscoverNotifier QT_LOGGING_RULES="org.kde.*=true" /usr/libexec/DiscoverNotifier DiscoverNotifier: no process found org.kde.plasma.libdiscover.backend.packagekit: using... PackageKit::Transaction(0x5562e514d9a0) "/31743_eedbaaab" org.kde.plasma.libdiscover.backend.packagekit: using... PackageKit::Transaction(0x5562db4a6bb0) "/31744_bceeaaed"
Wyatt, are you still seeing this issue in Plasma 6.3.0 or later?
(In reply to Nate Graham from comment #9) > Wyatt, are you still seeing this issue in Plasma 6.3.0 or later? Yes, I saw it today even. Operating System: Fedora Linux 41 KDE Plasma Version: 6.3.2 KDE Frameworks Version: 6.11.0 Qt Version: 6.8.2 Kernel Version: 6.13.5-200.fc41.x86_64 (64-bit) Graphics Platform: Wayland Processors: 32 × AMD Ryzen 9 7950X 16-Core Processor Memory: 61.9 GiB of RAM Graphics Processor 1: AMD Radeon RX 7900 XTX Graphics Processor 2: AMD Radeon Graphics Manufacturer: ASUS
During a moment when this is reproducing (i.e. there are updates but the notifier hasn't appeared), can you paste the contents of the `~/.config/PlasmaDiscoverUpdates` file?
(In reply to Nate Graham from comment #11) > During a moment when this is reproducing (i.e. there are updates but the > notifier hasn't appeared), can you paste the contents of the > `~/.config/PlasmaDiscoverUpdates` file? [Global] LastNotificationTime=2025,3,3,17,26,16.665
So basically, that's a timestamp, and it's there to make sure we don't show too many notifications. If you delete that file and reboot, do you see the Notifier in your System Tray d get a notification about available updates?
(In reply to Nate Graham from comment #13) > So basically, that's a timestamp, and it's there to make sure we don't show > too many notifications. > > If you delete that file and reboot, do you see the Notifier in your System > Tray d get a notification about available updates? I didn't realize I didn't say this ... but rebooting always seems to resolve the issue. It's really an issue involving computers that have been running for an extended period (the desktop does not do power saving, so it's unrelated to sleep mode).
So if reboot fixes the issue, can you clarify what the issue is and when it happens? Is the tray icon disappearing on its own, or is it failing to re-appear as you expect after you install available updates but don't reboot yet? Or something else?
(In reply to Nate Graham from comment #15) > So if reboot fixes the issue, can you clarify what the issue is and when it > happens? > > Is the tray icon disappearing on its own, or is it failing to re-appear as > you expect after you install available updates but don't reboot yet? Or > something else? The computer boots after an update, there are no updates, some days go by, updates are released, the tray icon never comes back to tell me about those new updates. It only consistently appears to notify of updates after a reboot.
So in other words: 1. Turn on computer and log in 2. Updates are available, tray icon appears 3. Install updates 4. Reboot and log in 5. Updates are available, tray icon never appears <--------- bug appears 6. Reboot and log in 7. Updates are available, tray icon appears <--------- bug has stopped happening Is that accurate?
(In reply to Nate Graham from comment #17) > So in other words: > 1. Turn on computer and log in > 2. Updates are available, tray icon appears > 3. Install updates > 4. Reboot and log in > 5. Updates are available, tray icon never appears <--------- bug appears > 6. Reboot and log in > 7. Updates are available, tray icon appears <--------- bug has stopped > happening > > Is that accurate? More or less. Another way to phrase it is that: > A computer that boots, and at the time of boot is fully patched, does not get alerted that it's out of date until a reboot occurs. This is a problem primarily for people that do not reboot their systems frequently as they will not be notified of new updates in a timely fashion. e.g. if you install a security update on Monday, reboot and are fully patched, but a subsequent security update is released Wednesday, and you don't reboot until Sunday, you will not be notified about the security update from Wednesday until Sunday ... which is really *not* great.
Gotcha. Unfortunately I'm not able to reproduce this on git master: I see the notifier, install updates, reboot after a day or so, and then after I log in again, I see the notifier and get an update about even more updates.
(In reply to Nate Graham from comment #19) > Gotcha. > > Unfortunately I'm not able to reproduce this on git master: I see the > notifier, install updates, reboot after a day or so, and then after I log in > again, I see the notifier and get an update about even more updates. I'm not sure that's quite the reproduction; you don't need to wait to install updates if you've been notified of the updates. You should get your computer to a totally patched state, then just leave it on, and see if the tray notification ever shows up. Using a distro that moves quickly like Fedora is likely to have a higher rate of reproduction just because there are faster update cycles. It also doesn't even seem to be an "every time" thing ... but it does appear to be very frequent. Even right now, I have no notification of any updates, and here's the file contents you asked for earlier (again): [Global] LastNotificationTime=2025,3,9,21,55,31.674 I just opened Discover and there are 84 updates available (a mix of flatpaks and rpms). The update for Discord currently sitting in my Discover app has been available for 3 days: https://flathub.org/apps/com.discordapp.Discord and there's no indication that I'm ever going to be notified about it. I'm sure if I went and tracked down some of these RPMs I'd see similar build history. Even though you can't reproduce it personally I still think this should be a high priority issue. The non-technical folks that use KDE can be severely impacted by failure to notify of updates. A lot of folks simply do not reboot their computers and could potentially go weeks or even months without being told about a critical security update or update to fix a severe bug (e.g., one that can cause hardware damage to their system). Like this is really really bad ... and the only reason I can think of that more people aren't reporting it is that they just don't know they're missing updates. One of the strengths of Linux is managing critical updates in a centralized place and this bug completely undermines that.
> You should get your computer to a totally patched state, then just leave it on, and see if the tray > notification ever shows up. Using a distro that moves quickly like Fedora is likely to have a higher > rate of reproduction just because there are faster update cycles. That's what I do all the time, and indeed, I do use Fedora KDE 41. I update in Discover (with offline updates) reboot to apply the update, log in again, and more often than not, there's a new update waiting for me and Discover notifies me shortly after login. Non-technical folks generally never manually install updates. For such people, a trusted friend or family member should probably turn on auto-updates. Regardless, we need a clearly reproducible case for the bug report to be actionable. Once it is, it'll likely be fixed quickly.
(In reply to Nate Graham from comment #21) > > You should get your computer to a totally patched state, then just leave it on, and see if the tray > > notification ever shows up. Using a distro that moves quickly like Fedora is likely to have a higher > > rate of reproduction just because there are faster update cycles. > > That's what I do all the time, and indeed, I do use Fedora KDE 41. I update > in Discover (with offline updates) reboot to apply the update, log in again, > and more often than not, there's a new update waiting for me and Discover > notifies me shortly after login. It kind of sounds like you may be waiting too long to reboot. If you download updates in the morning, apply the offline update in the next morning, and then have updates shortly after your computer turns on, you probably are avoiding the issue by rebooting into a new set of updates that need to be applied. This will only "fail" if you have a completely patched system when KDE does its initial update check after boot. > Non-technical folks generally never manually install updates. I know several non-technical people that understand they need to install updates and do so when notified (especially about security updates). In fact they prefer Linux in no small part because they can choose when to install those updates; they still need to be aware that there are updates though. > For such people, a trusted friend or family member should probably turn on > auto-updates. I would also expect that auto-updates may not work ... if the notification system isn't triggering for the user, I don't know how the user would know to reboot to install their automatic updates (assuming they even get installed in the first place).
$ cat ~/.config/PlasmaDiscoverUpdates [Global] LastNotificationTime=2025,3,12,16,57,23.278 $ su - Password: # dnf check-update Updating and loading repositories: Fedora 41 - x86_64 - Updates 100% | 47.1 KiB/s | 25.8 KiB | 00m01s Fedora 41 - x86_64 - Updates 100% | 3.6 MiB/s | 2.9 MiB | 00m01s Repositories loaded. ImageMagick.x86_64 1:7.1.1.45-1.fc41 updates ... spectacle.x86_64 1:6.3.3-1.fc41 updates xdg-desktop-portal-kde.x86_64 6.3.3-1.fc41 updates There are 178 updates pending, but I haven't had a notification in over 24h. I did get a notification earlier this week, and I did install some updates using Discover. I think I did *not* reboot to apply those offline updates. Maybe Discover is not notifying me again until I reboot?
While the system is in needs-reboot state it will indeed not notify again.
Aha, so that explains what I'm seeing, which might be different from Wyatt's problem. Should there be a periodic "you didn't reboot yet" reminder instead?
I have also noticed - from time to time - that some "updates" do not make the notification icon show. So far i can't tell if it's flatpak updates or some other... (In reply to Nate Graham from comment #21) > Non-technical folks generally never manually install updates. > For such people, a trusted friend or family member should probably turn on > auto-updates. That would be great!!! If only Auto-updates would work... they still aren't triggered ( bug 447245 ) !!! with all the bug reports around discover and the notifier i'm starting to thing there is something really messed up with plasma/discover update system... These are important "basic things" for normal users which expect it to just work out of the box
(In reply to Jonathan Wakely from comment #25) > Aha, so that explains what I'm seeing, which might be different from Wyatt's > problem. > > Should there be a periodic "you didn't reboot yet" reminder instead? I seem to remember that we explicitly don't do that so people don't get annoyed by it. Certainly not ideal if you then run the system for days on end without rebooting.
(In reply to Harald Sitter from comment #24) > While the system is in needs-reboot state it will indeed not notify again. This does give me an idea... Occasionally, I install the flatpak updates (since they don't require a reboot) but I don't install the rpm updates (because there are none or I just don't want to reboot). I wonder if that could be making the part of Discover that checks for updates and notifies about them think that it's waiting on a reboot (and thus no longer notifying about new updates). (In reply to Harald Sitter from comment #27) > (In reply to Jonathan Wakely from comment #25) > > Aha, so that explains what I'm seeing, which might be different from Wyatt's > > problem. > > > > Should there be a periodic "you didn't reboot yet" reminder instead? > > I seem to remember that we explicitly don't do that so people don't get > annoyed by it. Certainly not ideal if you then run the system for days on > end without rebooting. I think it would be ideal if Discover could notify you that there are updates in addition to the ones it's already prepared to be installed. For instance if you have 10 updates, install them, and they're pending for reboot, then 10 more updates come in, it actually notifies and offers to stage those updates for offline install as well on the next reboot. As it stands you currently need 2 reboots to get the 20 packages installed.
I'm going to try a different reproduction strategy... I installed flatpak updates via Discover yesterday, I'm pretty sure I had a tray icon informing me there were updates. I did NOT install the RPM packages via Discover, I let those sit. I now no longer have a tray icon informing me there were updates. That implies a different sort of bug than I originally was thinking (i.e. you have the notification to start with, but then it goes away after installing only part of the updates).
Also very curiously, if I go to the command line flatpak reports there are updates available. However, Discover does not report those flatpak updates even when refreshed. It seems "stuck" in yesterday's state.
Okay, I've now observed this again, and I think (what I've updated the title to) is the problem. On day 1, you: - Have updates for flatpaks and RPMS - Have a tray icon telling you there are updates available - Install updates for flatpaks ONLY (tray icon does immediately go away as the updates for the RPMs are still available) Roughly 24-hours later / the next notification time: - Have updates for RPMS - No longer have a tray icon telling you there are updates available - May or may not have new flatpak updates Effectively, you install flatpaks and then lose your reminder about any future updates (to flatpaks or otherwise).