| Summary: | Auto updates do not work | ||
|---|---|---|---|
| Product: | [Applications] Discover | Reporter: | Elias <supgesu> |
| Component: | Notifier | Assignee: | Dan Leinir Turthra Jensen <leinir> |
| Status: | RESOLVED FIXED | ||
| Severity: | major | CC: | aleixpol, dap78, dofficialgman, fleisch.johannes, gigaoxygen28, johnmaverick74, kde.cope348, kde, nate, nutzloserwerbemuell, pieterkristensen, postix, ruawhitepaw, tombrown9501, Torkin, travier, yvan |
| Priority: | NOR | ||
| Version: | 5.23.4 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| URL: | https://invent.kde.org/plasma/discover/-/merge_requests/369 | ||
| See Also: | https://bugs.kde.org/show_bug.cgi?id=471548 | ||
| Latest Commit: | https://invent.kde.org/plasma/discover/-/commit/000772d959fb7b51ed29cd18dcc9bdb435d6e8fe | Version Fixed In: | 6.3.0 |
| Sentry Crash Report: | |||
| Attachments: | Offline updates config | ||
|
Description
Elias
2021-12-19 22:40:25 UTC
Btw. on Debian+Ubuntu there is an addational bug wich prevents auto updates from working. Not Discovers fault, but wanted to note that, for anyone testing. The deb/ubuntu package for packagekit currently contains a patch which disallows offline updates for non admin users and without a password prompt. This makes offline updates never get triggered. You have to change `/usr/share/polkit-1/actions/org.freedesktop.packagekit.policy` to get it working. See: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1955489 --- Also, adding to this I wrote before: > If my assumption is true, this could be fixed by changing from 15 minutes of idle to for example just 15 minutes after boot. Instead of 'xx minutes after boot' maybe 'xx minutes after updates were found' would be the better choice here. I can confirm this! I'm on: Operating System: KDE neon 5.24 KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 Kernel Version: 5.13.0-39-generic (64-bit) Graphics Platform: X11 I have Discover configured to auto-update. I was expecting Discover to check on updates (All kinds of updates that do not fit OS Upgrades) and that it would silently install them in the background. That never happens! I Always have to fire up discover and order it to "update all/everything" manually (In reply to John from comment #2) > That never happens! > I Always have to fire up discover and order it to "update all/everything" > manually let me just scratch that!!! It apparently works, but only after 15min in idle, as Elias pointed out. I do agree we should be able to set it to auto-update after 15min of boot, however! You mean to get the updates happen even while you're using the system? Yes. Has long as they only get installed on ShutDown or at BootUp, i don't understand why they can't be downloaded while i'm using the system. Even if i have to manually set it to do that, i should be able to say "i want my system to download the updates as soon as it can" A possibly relevant merge request was started @ https://invent.kde.org/plasma/discover/-/merge_requests/369 For me, the automatic updates start just as little often, so i don`t use it. But for casual users who never update themselves, it is important that there is a well-functioning automatic update system. But I don't think that more setting options are necessary for the update process. In my opinion, only the automatic update process should be adjusted. I totally agree with Johannes in comment 7. I recently installed Plasma on a laptop from plm. 2014. Windows (10) is really becoming too heavy on such a laptop so Plasma seemed a sensible choice. I was pleasantly surprised that it was love at first site with Plasma, especially after I showed Kpat! But I have no hope at all that the owner of this laptop will periodically update her machine. For her, automatic update would be a great option. I really don't see why automatic update should wait for anything at all! In my opinion it should grab every opportunity to do it's job. I also face this issue with the Fedora 38 (now 39) machines of parents. Despite having auto update enabled, they remain at the same state when I last time manually updated them. Automatically checking for updates and installing them on shutdown (bug #436928) - maybe once in a week at least - would greatly enhance the situation imo. I face the same issue currently on fedora 39. I have it running on two different computers but on both the auto updates don't work. It stays the same unless you update manually. I am also facing this issue on fedora 39, manually starting the update in discover works perfectly, however auto updates are never done by themselves. I also would like this feature to work! Updates will never install automatically. The importance of this bug needs to be updated to Major to reflect the severity based on KDE guidelines. Major Like Normal, but with no known workaround, or the workaround is painful and difficult Normal Something isn't working the way it was designed to work, with a known workaround that isn't too painful Thanks! I do agree as well, this bug should get a higher priority and be fixed soon - epecially since the KDE team does actively promote offline updates ( https://discuss.kde.org/t/why-doesnt-discover-notifier-enable-offline-updates-by-default-if-theyre-recommended/3336/14?u=rokejulianlockhart ). The average user sees the option to enable automatic updated right next to offline updates in KDE system settings, is happy about it, activates it - and never looks for updates again. This menas then the bug noted here causes updates to be effectively disabled... (edit: I just noted the bug already got a higher priority. Sorry for that...) I've been thinking about this... I think Plasma is misleading users if they set update settings to Apply System Updates: Immediately And it only does so "after 15 minutes of idle" (which may never occur!). When set to "Immediately" it should indeed apply them "Immediately" and not after XX Minutes of Idle. Having it "delayed" misleads the user. So either the idle time is removed or, ideally, a solution like Elias said: allowing user to set it manually (to, e.g.: 0min, 15min, 30 min) - where the 15min could be the default value... BTW, i think the option to apply updates as soon as possible (e.g.: after 0min) is an important option! This is likely a duplicate of https://bugs.kde.org/show_bug.cgi?id=471548 *** This bug has been marked as a duplicate of bug 471548 *** (In reply to Nate Graham from comment #19) > > *** This bug has been marked as a duplicate of bug 471548 *** Nate, i don't think this should be marked as duplicate of 471548. The issue here is regarding all updates and not just flatpaks. I also ended up here, again, because the 15 min idle does not appear to be working anymore. After the 6.2 update, i configured the system to finally use the offline updates - along with the new option to "install updates and shut down" - but after waiting more an hour (not touching the PC!) no updates were ready to be installed on shut down as expected... The only way to get them available to install and shutdown was to manually open Discover and press Install All. I think this should be reopened... Created attachment 174942 [details]
Offline updates config
i would like to present my expectations over this feature (because others may share this...)
With offline updates configured like the attached screenshot i was expecting that:
- as soon as we get notified there are updates available the System would immediately start downloading them in the background all by itself, without requiring any user intervention! (E.g.: the user does not need to "open Discover > go to Updates and > press Update All" or any other kind of action)
- when we go to shutdown the computer - on the logout screen - we would be offered the option to "Install Updates and Shutdown"
(In reply to John from comment #21) > Created attachment 174942 [details] > Offline updates config > > i would like to present my expectations over this feature (because others > may share this...) > > With offline updates configured like the attached screenshot i was expecting > that: > > - as soon as we get notified there are updates available the System would > immediately start downloading them in the background all by itself, without > requiring any user intervention! (E.g.: the user does not need to "open > Discover > go to Updates and > press Update All" or any other kind of action) > > - when we go to shutdown the computer - on the logout screen - we would be > offered the option to "Install Updates and Shutdown" I'm running into the same problem. The update settings are the same as in the provided screenshot, and I would expect things to behave as you describe. But nothing happens. I get a notification that there are updates, but Discover just sits there for days until I manually install them. Once I do manually install them, I get a prompt to restart, and all of that stuff works totally fine. Computer reboots, updates get installed, etc. It's only the process of initiating it automatically that does not work. It only does anything if I manually open Discover and tell it to. A possibly relevant merge request was started @ https://invent.kde.org/plasma/discover/-/merge_requests/975 Git commit 000772d959fb7b51ed29cd18dcc9bdb435d6e8fe by Harald Sitter. Committed on 16/12/2024 at 15:33. Pushed by sitter into branch 'master'. notifier: reduce the idle time to 1 minute the motivation here was to not have the update run while the user is using the system so as to not disturb workflows. alas, the problem is that idle time is a poor measure because the system may never be idle for long enough or the user returns before the update is complete rendering the idle timeout pointless to begin with. accepting defeat here, we are bring this value way down. should this become a problem we may need to investigate better solutions depending on what the actual problem is (e.g. cgroup constraints could help with load issues). remains to be seen if there will be problems though. M +6 -2 notifier/UnattendedUpdates.cpp https://invent.kde.org/plasma/discover/-/commit/000772d959fb7b51ed29cd18dcc9bdb435d6e8fe Will the system hold the automatic update process the moment you touch anything? In that case I think it would be useful if there was the possibility to make the automatic update process go on once it started. Imho than it would be almost guarantied that a lot of users would work with up to date systems. (In reply to PK from comment #25) > Imho than it would be almost guarantied that a lot of users would work with > up to date systems. That's what i expect as well: once it starts, it does not stop and continues to run on the background! if that's not the case, an option to make it behave like this would be more than welcome. I want to be sure my system is always up-to-date and i really don't want to have to babysit it everyday, like i have to now!!! I want it to download what it has to and get the updates ready for offline installation when i shut it down! So that it be ready for work the next morning... I think making the idle wait time optional entirely is the most sensible. There are probably some users who use their computer from the moment it's booted, to the moment it's shut down. There are also presumably users (like me) who would not mind updates going on in the background while they're doing things. Maybe the disruptiveness of the background updates is overstated? It depends on whether stuff is appearing on the screen (progress bars, notifications). I would definitely like it to update even if I'm doing things, but not show anything on the screen except maybe a quick notification when it's finished. Then I can restart the machine later whenever I want. |