Bug 438448

Summary: EVERY Login Discover-Notifier tells me to restart
Product: [Applications] Discover Reporter: Posi <posi1981>
Component: NotifierAssignee: Aleix Pol <aleixpol>
Status: RESOLVED FIXED    
Severity: normal CC: cedjo7, charlieivermee, imasuffix, jschroed, kde, nate, r.kunschke, smurtaza.53, v.n.suadicani
Priority: HI    
Version First Reported In: 5.22.0   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Posi 2021-06-11 05:28:53 UTC
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
Comment 1 Posi 2021-06-11 05:32:23 UTC
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.
Comment 2 Nate Graham 2021-06-15 22:27:39 UTC
Are you using offline updates (the kind that are applied on a reboot) or interactive updates?
Comment 3 Bug Janitor Service 2021-06-30 04:33:49 UTC
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!
Comment 4 r.kunschke 2021-07-01 12:06:32 UTC
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
Comment 5 r.kunschke 2021-07-01 12:40:06 UTC
(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.
Comment 6 Bug Janitor Service 2021-07-16 04:33:38 UTC
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!
Comment 7 notrealname 2021-07-24 09:25:22 UTC
I am getting the same bug. Turned on and off offline updates no change. On Manjaro
Comment 8 Nate Graham 2021-07-30 15:41:01 UTC
*** Bug 439421 has been marked as a duplicate of this bug. ***
Comment 9 Nate Graham 2021-07-30 15:41:29 UTC
*** Bug 439193 has been marked as a duplicate of this bug. ***
Comment 10 Nate Graham 2021-07-30 15:42:11 UTC
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.
Comment 11 Nate Graham 2021-10-07 16:15:58 UTC
*** Bug 443423 has been marked as a duplicate of this bug. ***
Comment 12 notrealname 2021-10-07 22:30:08 UTC
removing /var/lib/PackageKit/offline-update-action fixed it for me
Comment 13 Nate Graham 2021-10-08 14:21:49 UTC
For anyone experiencing this, can you attach the contents of that file with `cat /var/lib/PackageKit/offline-update-action`?
Comment 14 Cedjo 2021-10-08 14:24:30 UTC
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
Comment 15 Nate Graham 2021-10-08 14:26:32 UTC
Thanks. So I guess this file didn't get removed automatically, either because of a bug in PackageKit, or a bug in Discover.
Comment 16 notrealname 2021-10-08 14:29:29 UTC
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
Comment 17 John Schroeder 2022-01-02 21:43:41 UTC
(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.
Comment 18 Aleix Pol 2022-01-03 03:00:54 UTC
Let's close it as fixed. We can always reopen the bug report or create a new one.
Comment 19 v.n.suadicani 2024-06-11 16:48:45 UTC
> 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).