Neon makes the system upgrade like windows. Is it a virus or some new procedure. Upgrade, restart, neon logo and countdown as in windows

And if you do that on CMD:

Code: Select all

sudo pkcon refresh && sudo pkcon update

Thanks for reporting, I know those commands, but I used the GUI because it reported a notification in the panel that there was an update. It was easier for me to click on the notification in the panel than to start the terminal and type the commands. What I am writing is irrelevant because your writing does not give any answer to my dilemma and none of the developers are advertising on that issue. I am using a legal update and a legal program that is built into Neon.If commands must be used then the GUI program should be removed from the installation. GUI is a severe and long disease that plagues the Linux system.

https://blog.neon.kde.org/index.php/202 ... re-coming/
https://blog.neon.kde.org/index.php/202 ... -are-here/

Thanks for the links, the right answer to my dilemma

I have one question about the new update system. Does it not ask for a password to apply updates now, or is something off with my install now?

Mace68 wrote:I have one question about the new update system. Does it not ask for a password to apply updates now, or is something off with my install now?

This is correct and as expected. The system reboots and installs the updates with a very minimal boot environment so password is needed - think of it being a bit similar to the recovery mode in a sense, where you don't need a passwor.

A more descriptive documentation of the process:
https://www.freedesktop.org/software/sy ... dates.html

I came here today because of this exact issue. I REALLY don't like this new upgrade system. All of this rebooting? 5 minutes of updating when booting up? It feels like I'm using windows again. I feel icky and gross, like I need to shower.

I don't look to Linux for the windows experience. Or look to desktops for a smartphone experience. Or look to FireFox for the Chrome experience. Why is everything trying to be something else? This is insanity.

That said, it's good news I can still update without having to reboot or update at boot up, which also triggers its own reboot. I would love to see offline updates optional in Discover though.

Mace68 wrote:I have one question about the new update system. Does it not ask for a password to apply updates now, or is something off with my install now?

I think that's because the new updates are some kind of flatpak/snap/appimage thing? I think? Which is just more smartphone mimicking, since Androids function in a similar fashion. And it's extra weird here because, sure it's more secure, but this is Linux we're talking about. Software/updates are still coming from the repos, there are no active Linux viruses in the wild, and you can't remotely execute code without special permissions anyways, so why are system updates/core files now flatpak/snap/appimages? Sure, such things work for userspace but as part of the core OS? It's just more insanity. So they're not a flatpak/snap/appimage thing?

I would love a way to opt out of flatpak/snap/appimage installs in Discover if it's coming from the repos.

mouse wrote:...
I would love a way to opt out of flatpak/snap/appimage installs in Discover if it's coming from the repos.

You should be able to uncheck those repos (Flatpack & Snap anyway) in Discover's Settings near the bottom of the list.

claydoh wrote:This is correct and as expected...

Thanks much for the confirmation!

What a really unthinking idea this new Discover update process is. I've put up with having to reboot for some large updates, but this morning there was a Firefox locale update of a few bytes in size, and now I have to reboot. The developers need their heads read. Really, a reboot for a minor locale update? Seriously? If I wanted this sort of tripe I'd use Windows.

Do any of the developers actually think about the user experience?

All those questions are rhetorical so they don't need answers.

Geeze.

catweazel wrote:What a really unthinking idea this new Discover update process is. I've put up with having to reboot for some large updates, but this morning there was a Firefox locale update of a few bytes in size, and now I have to reboot...

I imagine the command

Code: Select all

sudo pkcon refresh && sudo pkcon update

will still work like it used to.

Mace68 wrote:I imagine the command

Code: Select all

sudo pkcon refresh && sudo pkcon update

will still work like it used to.

Congratulations on completely missing the point.

catweazel wrote:Congratulations on completely missing the point.

Your main point was having to reboot, which can be avoided using pkcon.

Mace68 wrote:

catweazel wrote:Congratulations on completely missing the point.

Your main point was having to reboot, which can be avoided using pkcon.

Er, no. My point point was stated at least five times in different words.

1) "What a really unthinking idea this new Discover update process is." -> It sucks.
2) "Really, a reboot for a minor locale update? Seriously?" -> It sucks.
3) "The developers need their heads read." -> It sucks.
4) "If I wanted this sort of tripe I'd use Windows." -> It sucks.
5) "Do any of the developers actually think about the user experience?" -> It sucks.

In case you miss the point yet again, that means it sucks. As does the suggestion to use pkcon, which will not work at all when packages have been put on hold. The current correct solution is:

Code: Select all

kwriteconfig5 --file discoverrc --group Software --key UseOfflineUpdates --type bool false

That will do until the GUI option to disable it arrives.

QED