| Summary: | offline updates are not installed on restart | ||
|---|---|---|---|
| Product: | [KDE Neon] neon | Reporter: | kinghat <madLyfe> |
| Component: | general | Assignee: | Neon Bugs <neon-bugs> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | aleixpol, dngrsone, jr, leviatan1, makosol, makspletiuk, mark, michele.kipiel, mjhopkins82, nate, neon-bugs, p.r.worrall, postix, sayan, shostak93, sitter, tagwerk19 |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Attachments: | Press to cancel??? | ||
|
Description
kinghat
2021-06-17 15:45:03 UTC
I wonder. do you get a "press 'c' to cancel" message? If so, what happens when you press 'c'? (In reply to Harald Sitter from comment #1) > I wonder. do you get a "press 'c' to cancel" message? If so, what happens > when you press 'c'? iirc i do remember seeing that. ill have to to that on the next update that rolls through. same since after 5.22.1 update Also seen this behaviour (in a KVM guest, not involving encrypted discs)
https://bugs.kde.org/show_bug.cgi?id=438600#c1
I think this is getting "muddled" ('tis a technical term) with the update pop-up when there's no updates to do.
Here it is there are updates, they get downloaded, you get prompted to restart, you don't get a long wait while the updates are applied and when you log back in again and run discover you still have the updates to apply.
Sometimes, but not always, if you then "Update all" the updates are applied on the second reboot.
Tried "pkcon offline-trigger", the same thing happens. Occasionally have to resort to a "pkcon update" to apply the patches there and then.
Feel this is enough to flag "Confirmed"
I have the same behavior on my system. KDE Neon 5.22 KDE Plasma 5.22.1 Created attachment 139486 [details]
Press to cancel???
When you press c to cancel... the updates install without problem! Doesn't make sense. There was a brief window of time where a bug had the logic inverted. Doing nothing canceled, 'c' continued 🙄 So to recap: If discover actually shows updates, you can apply updates, and upon reboot the updates screen appears but seemingly nothing gets updated: hit 'c' when the screen offers to cancel. This should install the updates. If it still does nothing then your problem has nothing to do with this bug. After having updated to at least the state of 2021-06-18 'c' will behave correctly and cancel. *** Bug 438600 has been marked as a duplicate of this bug. *** (In reply to francisco_t from comment #6) > Created attachment 139486 [details] > Press to cancel??? Worth a mention here but should be a new bug... ... I don't think this screen appears with KVM guests. I'll try different video settings and see if I can get it to appear but at the moment I get get a black screen and an unpredictable pause (In reply to tagwerk19 from comment #10) > ... I'll try different video settings and see if I can get it to appear ... So, for Neon running as a KVM guest... Check the "Video" in the details of the VM. If it is QXL, change to Virtio. As far as I can tell, you don't get to see the install boot splash if you have QXL video. Close down the VM and run from cold (simply restarting doesn't change the video) Log in, run Discover, let it downloads all updates and ask for a restart Don't worry if the system reboots and you can login straight away without getting the updates Log in again, run Discover and "Update all" again. This time, everything has been downloaded to it will prompt to Restart immediately. You'll get the Boot splash screen saying Preparing system update, press "c" to cancel. Press "c" ... The offline updates will start installing. *** Bug 438943 has been marked as a duplicate of this bug. *** *** Bug 439077 has been marked as a duplicate of this bug. *** I do not have the option to press 'c' to skip, and when rebooting, I press c anyway and nothing changes. I have also tried sudo pkcon refresh, sudo pkcon update, with no change. I am stuck on 'System Upgrade' with the first package in the list being bluedevil 4:5.2.2.1 (In reply to Dngrsone from comment #14) > I do not have the option to press 'c' to skip, and when rebooting, I press c > anyway and nothing changes. > > I have also tried sudo pkcon refresh, sudo pkcon update, with no change. > > I am stuck on 'System Upgrade' with the first package in the list being > bluedevil 4:5.2.2.1 I am on KDE neon 5.22, Plasma v 5.22.1, KDE frameworks v5.83.0, kernel 5.8.0.59-generic (64-bit) I am triple-booting with Win 10 and Linux Mint xfce, so I can easily jump in on the neon root partition from xfce to do any editing of config files or whatever. I am facing this issue on Arch Linux where I don't have plymouth installed and so naturally I don't get any splash screen that says press C to cancel but it fails anyway because I get the same update notification after booting to plasma. How do I fix it without plymouth? I don't want to install and configure plymouth because my system doesn't like it and causes plymouth to hang for more than 10 seconds on reboot or shutdown. Just took three reboots before the changes were applied Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.22.80 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.3 Kernel Version: 5.11.0-25-generic (64-bit) Graphics Platform: Wayland Processors: 2 × AMD A6-6400K APU with Radeon(tm) HD Graphics Memory: 7.7 GiB of RAM Graphics Processor: AMD CEDAR Same problem here, I have no encrypted disk. Sometimes it works, sometimes it need two or three reboots to actually activate update installation. (In reply to makosol from comment #18) > Same problem here, I have no encrypted disk. Sometimes it works, sometimes > it need two or three reboots to actually activate update installation. Still see it as well, Neon Testing in a KVM guest. Often after installing patches and rebooting, the system comes back "as was" without applying the patches. If I rerun Discover, I see the patches are still listed, I run update again (where it does not need to download the patches but jumps immediately to the "restart"). As far as I remember, this "second" update has always worked. Can you still reproduce it with a more recent Plasma version? 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! |