Bug 438943 - Update not recognised and re-performed
Summary: Update not recognised and re-performed
Status: RESOLVED FIXED
Alias: None
Product: Discover
Classification: Applications
Component: Updates (offline) (show other bugs)
Version: 5.21.5
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Dan Leinir Turthra Jensen
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-06-20 10:29 UTC by Mark Stanton
Modified: 2023-01-13 16:17 UTC (History)
4 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 Mark Stanton 2021-06-20 10:29:45 UTC 
SUMMARY

Today's update (218 packages, including kernel 5.12.11(-300.fc34.x86_64) a 420Mb download. It ran, I performed the restart that it now always wants and, on re-starting, the system has not loaded the new kernel and has re-run the whole download and is now waiting for the re-start.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora 34
(available in About System)
KDE Plasma Version: Can't find this anywhere.
KDE Frameworks Version: 5.82.0
Qt Version: 5.12.2

ADDITIONAL INFORMATION
Comment 1 Paul Worrall 2021-06-20 22:42:33 UTC 
Duplicate of bug 438809. See comment 8 of that bug for solution

*** This bug has been marked as a duplicate of bug 438809 ***
Comment 2 Harald Sitter 2021-06-20 22:50:55 UTC 
Are we sure this can be a duplicate? The other bug is about neon specific tooling that I'm not aware is used by Fedora.
Comment 3 Nate Graham 2021-07-28 20:50:48 UTC 
Haven't seen this on Fedora 34 FWIW.
Comment 4 Nate Graham 2023-01-12 18:12:48 UTC 
Is this still happening to you with Fedora 37? If so we can do a deep-dive investigation. Sorry for not doing so before.
Comment 5 Mark Stanton 2023-01-13 11:16:22 UTC 
(In reply to Nate Graham from comment #4)
> Is this still happening to you with Fedora 37? If so we can do a deep-dive
> investigation. Sorry for not doing so before.

I haven't seen it on F37, nor in fact F36 before that, so I think it would be a fair assumption that it's no longer an issue.
Comment 6 Nate Graham 2023-01-13 16:17:28 UTC 
Great!