The system must restart

[Beerislife]

Muon doesn't pick up software-properties-qt. It used to use software-properties-kde but the name got changed somewhere along the line.

[chimak111]

...
The "bug" that everything seems to be a "system update" persists, requiring a reboot for such mundane things as video editor packages. I switched my Openshot PPA to their 'daily' one, just to trigger an update over the weekend.

I tried with the quite small vim-daily ppa from here and got the same system update, restart required.

I don't mind the concept but everything being a system or security update will put off a lot of people.

But maybe, in this case, it was justified based on

vim-common/focal-updates,focal-security,now 2:8.1.2269-1ubuntu5.3 all [installed,automatic]
vim-gtk3/focal-updates,focal-security,now 2:8.1.2269-1ubuntu5.3 amd64 [installed,automatic]
vim-gui-common/focal-updates,focal-security,now 2:8.1.2269-1ubuntu5.3 all [installed]
vim-runtime/focal-updates,focal-security,now 2:8.1.2269-1ubuntu5.3 all [installed,automatic]
vim-tiny/focal-updates,focal-security,now 2:8.1.2269-1ubuntu5.3 amd64 [installed,automatic]

(I wonder if it's a Discover issue or whether the GNOME people see it as well.)

[claydoh]

(I wonder if it's a Discover issue or whether the GNOME people see it as well.)

I think that a package would need to be labeled as a Normal or System update and I don't think Debian has such a thing in its packaging, or they don't have such data attached to them yet. So Packagekit's Apt plugin would need a method to separate these out somehow.

The process itself is not distro or desktop specific.

Sent from my LM-V600 using Tapatalk

[chimak111]

Okay, tried with Unit193's inxi ppa. This isn't a security update but was regarded by the process as a "system" update.

The restart/reboot seems (much) longer than normal with even the GRUB screen appearing when there's just the one distro present. I can see why people may not go down this route

Also, the wording of the text that appears when "System Settings > Software Update > Update software" is toggled from Manually to Automatically could give users the wrong impression.

[GreyGeek]

KDE Neon does not include *buntu's Software Sources tool. Never has.

Install software-properties-qt, and Muon should pick it up and the option should be available there, at least it did last time I installed Muon on KDE Neon . Been a while. ....

That package was already installed. Retrying to access the sources tab I was presented with the same blocking dialog. This time, with more careful reading, Muon says it is looking for "software-properties-kde". I searched for that in the Neon repository but it wasn't listed. Another I went searching the web for a deb package of it but couldn't find one after a cursory ""software-properties-kde"package download".
Since I am not going to re-install Discover I am currently at a catch-22: can't open the sources tab, can't download the required package.
Got to go grocery shopping. Will retry the search later.

[claydoh]

Oh carp!

The package software-properties-kde no longer exists in Kubuntu, and was replaced with software-properties-qt - as now Lubuntu can have this as well.

Remember, Neon's repos include Ubuntu's. Neon's repo only add Plasma, KDE bits, and Qt, but would not include any *buntu-specific software. Anything like this comes directly from Ubuntu.

Problem is, I forgot that Muon has never been updated to look for the current tool. It is effectively unmaintained.
I *think* a simple symlink for software-properties-kde that points to software-properties-qt *might* make work with Muon.

Otherwise, it can be found in Discovers settings arera as "Software Sources", if software-properties-qt is installed.

[GreyGeek]

You are right, Claydoh! Deciding I wouldn't reinstall Discover to fix the problem, and after searching the web for a downloadable package which wasn't avaiable, I rubbed my two neurons together and thought of using the ln command. The simlink,
sudo ln /bin/software-properties-qt /bin/software-properties-kde
WORKED!
Problem solved!

[claydoh]

And apparently I am wrong about Muon:

$ apt policy muon
muon:
Installed: (none)
Candidate: 4:5.8.0-1xneon+20.04+focal+release+build4
Version table:
4:5.8.0-1xneon+20.04+focal+release+build4 500
500 http://archive.neon.kde.org/user focal/main amd64 Packages
4:5.8.0-1xneon+20.04+focal+build3 500
500 http://archive.neon.kde.org/user focal/main amd64 Packages
4:5.8.0-1xneon+20.04+focal+build2 500
500 http://archive.neon.kde.org/user focal/main amd64 Packages
4:5.8.0-1ubuntu5 500
500 http://archive.ubuntu.com/ubuntu focal/universe amd64 Packages

I'll wager Kubuntu's Muon version is patched to work with their software sources/driver tool

[chimak111]

I just got the Frameworks update, 368 packages. But, contrary to my expectations (because I chose Update software: Automatically), I got a notification to update. That done, the prompt to restart appeared and we're done.

[Beerislife]

Another niggle solved. Symlinking software-properties-qt to -kde worked great!

[chimak111]

Unless I'm looking in the wrong place Ubuntu 21.10 won't be offering "offline updates":

[claydoh]

Wrong spot.

Check System Settings. The offline updates are provided by Discover (ie Packagekit), so normal updating via Apt (including Synaptic and Muon) does not utilize the offline updates feature.


In other words, this is not a distro-specific action. This is present in Fedora, Suse (iirc), for example, but Arch and its kin have disable/removed it, as they don't promote automatic updates.
But they really should have put this in Discover, instead of System Settings, imnsho.