Bug 442833

Summary: offline update: plymouth installing update progress value jumps immediately to 100%
Product: [KDE Neon] neon Reporter: Achim Bohnet <ach>
Component: Packages User EditionAssignee: Neon Bugs <neon-bugs-null>
Status: RESOLVED WAITINGFORINFO    
Severity: normal CC: jr, nate, neon-bugs-null, sitter
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Neon   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Achim Bohnet 2021-09-23 09:05:30 UTC
SUMMARY


STEPS TO REPRODUCE
1. pkcon -only-download; pkcon offline-trigger # reboot

OBSERVED RESULT
Progress indicate jumps after a few seconds from 0% to 100%
100% is shows for (dozend) minutes depending on size of the update

EXPECTED RESULT
Progess indicator increments Percentage shown according to the pkg installation progress.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Neon User 5.22.5

KDE Frameworks 5.86.0
Qt 5.15.3 (built against 5.15.3)
The xcb windowing system
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

When the 100% is show by plymouth and I press 'ESC' to see the systemd boot messages I see
an progress indicatr like: [====     ] xx
Installing updates - nn %
Installing updates - yy %

I get this behaviour in my laptop and desktop (both latest kde neon user).
Comment 1 Achim Bohnet 2021-10-13 12:49:49 UTC
I've to correct myself: after ~ 20 - 30 seconds after the immediate jump from 0% to 100% the percentage  is replaced by a proper working incremented progess indicator.  (In my case 100% was then replaced with once 11% and once with 16% (AFAIR) counting up to 100% as one expects.
Comment 2 Carlos De Maine 2025-09-20 09:36:10 UTC
Thank you for your bug report! 
However this bug report was created/provided previous to 01/01/2023 and also has not received any updates since  before 01/01/2025. 
Unfortunately KDE neon no longer provides updates for anything older than noble 24.04 based edition's.
Please upgrade to KDE neon noble and if you can reproduce the issue after upgrading to an active version, feel free to re-open this bug report.
Thanks for understanding!