Summary: | Restart required notification at every login | ||
---|---|---|---|
Product: | [Applications] Discover | Reporter: | Marco Ambu <marco.ambu> |
Component: | Notifier | Assignee: | Aleix Pol <aleixpol> |
Status: | RESOLVED NOT A BUG | ||
Severity: | normal | CC: | nate, null, plasma-bugs-null |
Priority: | NOR | ||
Version First Reported In: | 5.20.5 | ||
Target Milestone: | --- | ||
Platform: | Debian testing | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: |
Screenshot of notification
attachment-14004-0.html |
Description
Marco Ambu
2021-02-24 08:31:43 UTC
This comes from Discover; moving there. That's weird, can you tell us what's the contents of the following file? /var/lib/PackageKit/offline-update-competed Also can you please show us a screenshot of the notification you see? Created attachment 136184 [details]
Screenshot of notification
$ cat /var/lib/PackageKit/offline-update-action
power-off
Discover never set this, this must be coming from another tool as we only ever set it to "reboot". Would you know what that could be? Maybe you can check the date it was created (with ls -l) and we can infer where it's coming from. Ultimately, if it's very old maybe you can consider just removing the file, it might have been a past bug in PackageKit. Created attachment 136275 [details]
attachment-14004-0.html
The file looks to be old. Not sure if we can guess which package created it
from the info below.
Anyway, I removed it manually and the notification has now gone.
$ ll /var/lib/PackageKit/offline-update-action
-rw-r--r-- 1 root root 9 Nov 6 16:36
/var/lib/PackageKit/offline-update-action
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! |