SUMMARY STEPS TO REPRODUCE 1. Restart with this notification 2. Restart by hand 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Arch Linux 5.12.9 (available in About System) KDE Plasma Version: 5.22.0 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION
If updates made or not... after Login to the GUI i receive the notification from Discover-Notifier, that a restart is required. If i restart with this button or via the normal reboot command or any other method, i receive the same result. After Login Discover-Notifier tells me to restart.
Are you using offline updates (the kind that are applied on a reboot) or interactive updates?
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
I have the same problem since i enabled offline updates I think the auto-update isn't working at all since then. Updating manually works in discover. I opened a thread in the arch-forum about this issue: https://bbs.archlinux.org/viewtopic.php?id=267644 i am not sure if this problem is related to KDE or to arch
(In reply to Nate Graham from comment #2) > Are you using offline updates (the kind that are applied on a reboot) or > interactive updates? for me it happened after i switched from manual to automatic offline updates. The installation did not started. But I got a additional reboot and i think it should have updated in that process. Since that automatic updates are not working regardless of offline or "normal" automatic update. But the notifications about rebooting is shown on every boot.
I am getting the same bug. Turned on and off offline updates no change. On Manjaro
*** Bug 439421 has been marked as a duplicate of this bug. ***
*** Bug 439193 has been marked as a duplicate of this bug. ***
From duplicate bug 439193, it seems like the file /var/lib/PackageKit/offline-update-action is not getting removed as expected? Removing it manually seems to fix the issue.
*** Bug 443423 has been marked as a duplicate of this bug. ***
removing /var/lib/PackageKit/offline-update-action fixed it for me
For anyone experiencing this, can you attach the contents of that file with `cat /var/lib/PackageKit/offline-update-action`?
the content of the (In reply to Nate Graham from comment #13) > For anyone experiencing this, can you attach the contents of that file with > `cat /var/lib/PackageKit/offline-update-action`? the content is: reboot
Thanks. So I guess this file didn't get removed automatically, either because of a bug in PackageKit, or a bug in Discover.
Got it from snapshot because I deleted the actual file. cat /home/timeshift/snapshots/2021-10-03_15-00-01/localhost/var/lib/PackageKit/offline-update-action reboot
(In reply to notrealname from comment #12) > removing /var/lib/PackageKit/offline-update-action fixed it for me This fixed it for me as well on my Arch Linux system. I have not had the issue since removing /var/lib/PackageKit/offline-update-action. I have run updates since then and the file has not been recreated. Would this bug be able to be closed then? It suspect that the issue has been fixed in a recent build of Discover (or other software). The only lingering issue is that /var/lib/PackageKit/offline-update-action needs to be removed manually if the file was created at the time that this was an issue. However, it might be correct to leave up to the user to remove.
Let's close it as fixed. We can always reopen the bug report or create a new one.
> Let's close it as fixed. We can always reopen the bug report or create a new one. Hi, I am in 2024 still experiencing this bug in a new recently installed Kubuntu 24.04, so I suspect this bug is not fixed (or has been re-introduced somehow).