Bug 491755

Summary:	Feature Request: move the online/offline updates toggle from Ksettings to discover update page.
Product:	[Applications] Discover	Reporter:	Shad Young <foxwolfen>
Component:	Updates	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	RESOLVED NOT A BUG
Severity:	wishlist	CC:	aleixpol, sitter
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Shad Young 2024-08-15 15:50:44 UTC

Given I regularly have to switch between online and offline updates depending on the type of update, it would be welcome to have the online/offline update toggle normally found in Ksettings to be moved (or added) to the discover update page that launches when you click the notification.  It would save a lot of time not having to: 

1. open the update page in discover, 
2. check the update, 
3. close discover,  
4. open ksettings to toggle the type from whatever its on, 
5. close ksettings,  
6. restart discover updates again, 
7. click update. 

I basically have to do this with every single update. 

Ideally I would simply open the update page from the notifier, check the kind of update (app vs system), toggle the the kind I want, and click update.

TIA

Comment 1 Harald Sitter 2024-08-15 20:50:39 UTC

Switching back and forth defeats the purpose of offline updating. It's not about app versus system, it's about self-contained versus not. To that end self-contained updates aren't being applied offline.

Comment 2 Shad Young 2024-08-16 16:36:25 UTC

I do not understand what you mean by "self contained". I also fail to see how it defeats the purpose? Doing a reboot for something like Firefox is not required. Doing a reboot for the kernel or drivers is. Are you are saying that offline update is irrelevant? What is the purpose of the toggle in ksettings then? I fail to see how mirroring the toggle from the Ksettings page to the update page changes anything other than making it simpler to manage.

On another note, I was told to use the bug tracker for feature requests, was that in error?

Comment 3 Harald Sitter 2024-08-18 23:05:37 UTC

I am saying that when you update firefox that may pull in an update on libssl and that may break the already running plasmashell because of how plugins and lazy loading works in modern systems. That is why all updates coming out of packagekit are performed offline. Conversely all updates to flatpak or snaps are performed online as those can at most break the app itself - they are self-contained applications.

The use cases here are:
A) You can enable offline updates to perform safe updates without side effects (since they are performed in a minimally safe environment)
B) You can disable offline updates and operate in YOLO mode but get away without reboot (things may randomly break in all sorts of fun ways until reboot)

Switching between the two is really just option B) since you won't know that your not-self-contained firefox upgrade isn't going to break things.