-
-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
kernel updates require two reboots #94
Comments
Actually, now it seems that every update requires a reboot - the notification comes up even after updating a single app from flathub. |
updating with
|
This isn't an AppCenter specific issue. This is because updates are installed offline and affects pretty much all offline update mechanisms on Linux. Here's a relevant issue report in PackageKit: PackageKit/PackageKit#510 There's been some progress recently upstream about resolving this, I believe in systemd. I can't find the information at the moment but this is an underlying Linux architecture issue and not something that can be solved in AppCenter |
To clarify: this issue is about the current version of AppCenter included in OS 7 behaving differently then older versions of AppCenter, as well as all update mechanisms I know from Ubuntu in the past 10+ years. It all works as I'm used to, except the AppCenter in OS 7, which does things differently. PS: in the terminology of the linked issue, elementary OS 7 does three reboots to apply a kernel update. So there is still one more than there needs to be. I didn't count the short reboot after the progress bar as a real reboot in my original post. Actually, there may be four this way, not sure. PPS: One more example to illustrate - on my second laptop with Ubuntu MATE 22.04 (i.e. the same version as the base of elementary OS 7), applying kernel updates takes exactly one (visible) reboot, no matter if I use |
@janxkoci Yes, to clarify: AppCenter now installs all system updates offline so the behavior will be different than installing updates via apt while online. Offline updates require an extra reboot but the trade off is a more stable updates process with a lower chance of failure |
@danirabbit Ok, interesting, but the link still only talks about two reboots, while I experience 3-4 reboots (I need to count them properly next time using their definition). Also, online updates seem to be rock-solid - the same Ubuntu MATE laptop has only 32gb eMMC storage and with 9gb in Dropbox and a few apps I usually have only some 1.2 - 1.5gb of free disk space (below 1gb Dropbox stops syncing). I often observe that updates - especially kernel updates - regularly run out of space in the middle (as in |
Ah here we go, here's a talk about Soft Reboot: https://www.youtube.com/watch?v=5HO1PAcsM7g It looks like this landed in Systemd in July, so maybe in OS 8 we'll be able to have only a single reboot when installing updates |
Ok, I don't think that's the same issue. My issue is that I have to reboot twice all the way to the desktop to apply system updates, while the video and the linked PackageKit issue only talk about the short reboots during booting sequence (i.e. way before I even see login screen). I also noticed a reboot is sometimes required even without a kernel update. One such case was the five days ago, this is the log entry for 20th of September:
I don't see anything obvious that should require a reboot there (only one reboot to desktop was needed though). So to recap:
Did I miss anything? |
Yes, all system updates regardless of whether or not they contain kernel updates require a restart because they are installed offline. The only updates that install in the session are Flatpak updates. We only push out a set of updates about once a month, unless you're running early access, so you should plan to restart your system once a month to stay up to date. If you're saying you're rebooting all the way into the desktop multiple times then something there is wrong because what you should see is a reboot, installation of updates happening offline, another reboot, and then your updated desktop |
Well I see system updates definitely more often than once a month, but some of those will be Ubuntu updates.
And that's exactly what this issue is about. PS: see also "steps to reproduce" in the first post. |
What Happened?
For some reason - and unique in the Linux world - the new versions of Appcenter require two reboots when there are kernel updates in the queue. This is highly unusual.
Steps to Reproduce
Expected Behavior
Kernel updates have always required only one reboot. It's a nice tradition to keep.
OS Version
7.x (Horus)
Software Version
Latest release (I have run all updates)
Log Output
No response
Hardware Info
No response
The text was updated successfully, but these errors were encountered: