Ok, this is a weird bug report, but anyway... SUMMARY When discover shows that there are updates, and I manually run "pkcon update", the notification disappears. But when I actually click "apply all" in discover, it will download the updates and show me a restart notification. If I then do "pkcon update", the notification will not disappear, but no updates will be installed on reboot. STEPS TO REPRODUCE 1. Open discover - updates. Click on "apply all". Wait until the "reboot" notification appears. Close discover. 2. open konsole and run "pkcon update" 3. Restart OBSERVED RESULT Nothing EXPECTED RESULT Either the notification should disappear, or updates should be installed SOFTWARE/OS VERSIONS Operating System: KDE neon 6.0 KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.5.0-26-generic (64-bit) Graphics Platform: Wayland Processors: 6 × AMD Ryzen 5 4500U with Radeon Graphics Memory: 15,0 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: Acer Product Name: Aspire A515-44G System Version: V1.12 ADDITIONAL INFORMATION Yes, I know it's a weird and (possibly) stupid thing to do... ;-)
I am confused. The reboot notification tells you that you need to restart to complete the update, not to restart to apply the update. -- "The system needs to be restarted for the updates to take effect." Are you saying you get a reboot notification despite using offline updates?
I have set the system to do offline updates (apply system updates at the next restart). So, from my limited understanding, discover would download the updates and install them at the next reboot, then reboot again with the updates installed, right? The above behavior shows in that environment. It's not a big deal, just an inconsistency.
Maybe you could get me a screenshot of the notification we are talking about here.
Created attachment 169301 [details] discover update reboot notification inconsistency
this was after I 1) opened discover updates 2) clicked on "update all" 3) let it finish and the "reboot" notification appears 4) run "sudo pkcon update" in konsole
Oh, and it wouldn't go away even after closing and reopening discover (which then refreshes the update search)
Aha! Yeah, that's a status or tray icon, not a notification :) I wonder if we really want to try and get this to update. Depending on which "out of band" method was used to force an upgrade we may have no way of knowing about it. e.g. if you apt dist-upgrade rather than pkcon update, the relevant marker files wouldn't get cleared and the status would be inconsistent even if we fixed it for the packagekit scenario. So I have to wonder if we should bother at all.
Sorry for not expressing myself clearly, I'm neither a native English speaker nor a programmer... ;-) And I also thought it's a very minor thing, but still should get reported so someone more knowledgeable than I can decide whether and what to do. ;-)
It could make sense to see why that's not happening already. We are already tracking the reboot signal in the notifier, see PackageKitNotifier.cpp:363.
Well, it's a one way road. The only ever switches into reboot mode, it has no concept of reverting back to not needing reboot.