Bug 441157 - Keep getting repair system
Summary: Keep getting repair system
Status: RESOLVED UPSTREAM
Alias: None
Product: Discover
Classification: Applications
Component: discover (show other bugs)
Version: 5.22.4
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Dan Leinir Turthra Jensen
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-08-19 07:13 UTC by Jarl Gjessing
Modified: 2021-08-31 22:34 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Jarl Gjessing 2021-08-19 07:13:19 UTC 
I accidentially restarted while offline updates were installing (not to fond of these though)
So something when wrong of course. And on boot I got the repair system popup.
And it keeps popping up

STEPS TO REPRODUCE
1. Start let discover download updates
2. While updating on boot, and while it is installing kernel packages reboot the PC
3. Now the error keeps popping up


I did expect the popup not to appear after pressing repair and letting it do it's job.
I've also tried: sudo dpkg --configure -a

SOFTWARE/OS VERSIONS
KDE neon
KDE FW 5.85.0
Discover 5.22.4
Comment 1 wincak 2021-08-25 15:00:39 UTC 
I'm getting the repair system popup as well, after failed update (/boot ran out of space while installing new kernel).
Clicking on "Repair system" just asks for admin password, nothing happens after.
Since the failed update I've also tried "sudo dpkg --configure -a", installed a couple of updates successfully, including kernel. The popup still appears on every startup.
Is there at least a way to get rid of it manually?

Operating System: KDE neon 5.22
KDE Plasma Version: 5.22.4
KDE Frameworks Version: 5.85.0
Qt Version: 5.15.3
Kernel Version: 5.11.0-27-generic (64-bit)
Graphics Platform: X11
Comment 2 Aleix Pol 2021-08-31 22:33:20 UTC 
I've seen this as well, sometimes PackageKit "forgets" to clean the offline updates file. (you can try removing it by hand if you're sure it's all up to date)

This would be an issue in PackageKit upstream as far as I know.
Comment 3 Nate Graham 2021-08-31 22:34:23 UTC 
Has it been reported to packageKit?