https://bugs.kde.org/show_bug.cgi?id=443099
Bug ID: 443099
Summary: Neon restarts twice to apply updates
Product: neon
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity: wishlist
Priority: NOR
Component: general
Assignee: [email protected]
Reporter: [email protected]
CC: [email protected], [email protected], [email protected]
Target Milestone: ---
SUMMARY
This is not technically a bug but a design decision that makes it annoying for
users to update their systems. Neon applies offline updates by default now, but
the way it applies them is one of the reasons people get so upset about that
feature.
On Windows, when the user is prompted to restart their system to update, part
of the updates are applied on shutdown and the final steps are applied when
booting up the next time. When the system finishes installing updates it goes
straight into the desktop.
On Neon, when the user is prompted to restart, updates are applied on the next
start-up, and after it finishes it restarts again and then boots up normally,
thus adding additional time until the computer is ready to use. That's an
additional reboot for something that already bothers so many users on Windows,
a platform where the update process already requires fewer restarts and where
updates are way less frequent. Since Neon is a distro that gets updated
frequently, this can become quite frustrating.
It would be prudent to reconsider the use of offline updates by default until
that behavior is changed upstream (I don't know exactly what part of the system
is responsible for offline updates. Maybe systemd? If so let me know so I can
open a bug report upstream).
A temporary solution would be to:
1. Temporarily disable offline updates by default until the issue is fixed (in
systemd?). Maybe Neon developers could share their opinions in the bug report
upstream so it's more likely to be fixed quickly.
2. Apply updates while the system is still running and maybe warn the user
about the consequences of not restarting (like the increased possibility of
bugs). That warning could maybe be put here on KDE's bug tracker, with
something like: "Please restart your system and check if you can still
reproduce the issue before reporting a bug".
3. After the online updates are applied, show a notification telling the user
to restart (but don't enforce it). The point of showing a notification is to
make users more likely to restart before bugs caused by the online update
process have a chance to appear.
--
You are receiving this mail because:
You are watching all bug changes.
