Focal Testing of Kubuntu 20.04 LTS

[kubicle]

Ok, things are still broken.

Let's try some apt housekeeping first:
"sudo dpkg --configure -a"
"sudo apt -f install"
"sudo apt clean"
Post errors if you get them

Then post the output of:
"apt list -a ubuntu-drivers-common"
"apt list -a software-properties-kde"

[GreyGeek]

I had previously commented out the line containing the "proposed" stuff, and re-ran Muon. That didn't help so I purged muon and software-properties-qt and it two dependencies, logged out and back in, and reinstalled them. That didn't help either.

I also tried to install ubuntu-drivers-common but was told it was a "virtual" application and could not be installed.

I searched every muon config file for any thing that might unlock the repository, of which locate listed many, directly or indirectly related. None except sources.list made any mention of "Proposed".

Here is what I got when I ran your suggestion.

jerry@Aspire-V3-771:~$ sudo apt update & sudo apt install ubuntu-drivers-common
[2] 72007
Hit:1 http://ca.archive.ubuntu.com/ubuntu focal InRelease
Hit:2 http://ca.archive.ubuntu.com/ubuntu focal-updates InRelease
Hit:3 http://archive.canonical.com/ubuntu focal InRelease
Hit:4 http://ca.archive.ubuntu.com/ubuntu focal-backports InRelease
Hit:5 http://security.ubuntu.com/ubuntu focal-security InRelease
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming.
The following information may help to resolve the situation:


The following packages have unmet dependencies:
ubuntu-drivers-common : Depends: alsa-utils
E: Unable to correct problems, you have held broken packages.
Reading package lists... Done
Building dependency tree
Reading state information... Done
2 packages can be upgraded. Run 'apt list --upgradable' to see them.

[2]- Done sudo apt update



jerry@Aspire-V3-771:~$ sudo apt install alsa-utils
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming.
The following information may help to resolve the situation:


The following packages have unmet dependencies:
alsa-utils : Depends: libasound2 (>= 1.1.1)
wine32:i386 : Depends: libwine:i386 (= 4.0.3-1) but it is not going to be installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.

The wine32 and libwine packages are necessary to run my wife's EKG analysis tool, and I have had them installed for a while and I had access to the repository settings before I checked the "Proposed" box in the software repository dialog.

And, I don't see the "Proposed" archive
## deb http://ca.archive.ubuntu.com/ubuntu/ focal-proposed multiverse universe restricted main


in the listings:

[B]jerry@Aspire-V3-771:~$ vdir /var/lib/apt/lists[/B]
total 149780
-rw-r--r-- 1 root root    10930 Dec 10 13:44 archive.canonical.com_ubuntu_dists_focal_InRelease
-rw-r--r-- 1 root root     3735 Dec 10 13:44 archive.canonical.com_ubuntu_dists_focal_partner_binary-amd64_Packages
-rw-r--r-- 1 root root     3994 Oct 18 06:49 archive.canonical.com_ubuntu_dists_focal_partner_binary-i386_Packages
-rw-r--r-- 1 root root     1981 Dec 10 13:44 archive.canonical.com_ubuntu_dists_focal_partner_i18n_Translation-en
drwxr-xr-x 1 _apt root        0 Jan  3 23:22 auxfiles
-rw-r--r-- 1 root root    79749 Oct 25 00:28 ca.archive.ubuntu.com_ubuntu_dists_focal-backports_InRelease
-rw-r--r-- 1 root root       53 Oct 25 00:23 ca.archive.ubuntu.com_ubuntu_dists_focal-backports_main_cnf_Commands-amd64
-rw-r--r-- 1 root root       59 Oct 25 00:23 ca.archive.ubuntu.com_ubuntu_dists_focal-backports_multiverse_cnf_Commands-amd64
-rw-r--r-- 1 root root       59 Oct 25 00:23 ca.archive.ubuntu.com_ubuntu_dists_focal-backports_restricted_cnf_Commands-amd64
-rw-r--r-- 1 root root       57 Oct 25 00:23 ca.archive.ubuntu.com_ubuntu_dists_focal-backports_universe_cnf_Commands-amd64
-rw-r--r-- 1 root root   255467 Jan 29 14:05 ca.archive.ubuntu.com_ubuntu_dists_focal_InRelease
-rw-r--r-- 1 root root  6321158 Jan 29 13:44 ca.archive.ubuntu.com_ubuntu_dists_focal_main_binary-amd64_Packages
-rw-r--r-- 1 root root  4363906 Jan 29 13:44 ca.archive.ubuntu.com_ubuntu_dists_focal_main_binary-i386_Packages
-rw-r--r-- 1 root root   110136 Nov 25 21:24 ca.archive.ubuntu.com_ubuntu_dists_focal_main_cnf_Commands-amd64
-rw-r--r-- 1 root root   734467 Jan 29 11:46 ca.archive.ubuntu.com_ubuntu_dists_focal_main_dep11_Components-amd64.yml.gz
-rw-r--r-- 1 root root   368016 Jan 29 11:46 ca.archive.ubuntu.com_ubuntu_dists_focal_main_dep11_icons-128x128.tar.gz
-rw-r--r-- 1 root root    90966 Jan 29 11:46 ca.archive.ubuntu.com_ubuntu_dists_focal_main_dep11_icons-48x48.tar.gz
-rw-r--r-- 1 root root     6234 Jan 15 14:47 ca.archive.ubuntu.com_ubuntu_dists_focal_main_dep11_icons-64x64%402.tar.gz
-rw-r--r-- 1 root root   161088 Jan 29 11:46 ca.archive.ubuntu.com_ubuntu_dists_focal_main_dep11_icons-64x64.tar.gz
-rw-r--r-- 1 root root  3010164 Jan 28 23:19 ca.archive.ubuntu.com_ubuntu_dists_focal_main_i18n_Translation-en
-rw-r--r-- 1 root root    11684 Jan 10 12:07 ca.archive.ubuntu.com_ubuntu_dists_focal_main_i18n_Translation-en%5fCA
-rw-r--r-- 1 root root   751106 Jan 28 08:59 ca.archive.ubuntu.com_ubuntu_dists_focal_multiverse_binary-amd64_Packages
-rw-r--r-- 1 root root   371071 Jan 27 20:54 ca.archive.ubuntu.com_ubuntu_dists_focal_multiverse_binary-i386_Packages
-rw-r--r-- 1 root root    32732 Nov 25 19:30 ca.archive.ubuntu.com_ubuntu_dists_focal_multiverse_cnf_Commands-amd64
-rw-r--r-- 1 root root    58756 Jan 29 11:56 ca.archive.ubuntu.com_ubuntu_dists_focal_multiverse_dep11_Components-amd64.yml.gz
-rw-r--r-- 1 root root   357871 Jan 29 11:56 ca.archive.ubuntu.com_ubuntu_dists_focal_multiverse_dep11_icons-128x128.tar.gz
-rw-r--r-- 1 root root    14943 Jan 29 11:56 ca.archive.ubuntu.com_ubuntu_dists_focal_multiverse_dep11_icons-48x48.tar.gz
-rw-r--r-- 1 root root     1062 Dec 10 14:58 ca.archive.ubuntu.com_ubuntu_dists_focal_multiverse_dep11_icons-64x64%402.tar.gz
-rw-r--r-- 1 root root   199916 Jan 29 11:56 ca.archive.ubuntu.com_ubuntu_dists_focal_multiverse_dep11_icons-64x64.tar.gz
-rw-r--r-- 1 root root   477743 Jan 28 08:59 ca.archive.ubuntu.com_ubuntu_dists_focal_multiverse_i18n_Translation-en
-rw-r--r-- 1 root root   263600 Jan 28 09:25 ca.archive.ubuntu.com_ubuntu_dists_focal_restricted_binary-amd64_Packages
-rw-r--r-- 1 root root    59755 Jan 24 06:29 ca.archive.ubuntu.com_ubuntu_dists_focal_restricted_binary-i386_Packages
-rw-r--r-- 1 root root     1357 Nov 15 08:25 ca.archive.ubuntu.com_ubuntu_dists_focal_restricted_cnf_Commands-amd64
-rw-r--r-- 1 root root    48071 Jan 28 08:59 ca.archive.ubuntu.com_ubuntu_dists_focal_restricted_i18n_Translation-en
-rw-r--r-- 1 root root 49726207 Jan 29 13:44 ca.archive.ubuntu.com_ubuntu_dists_focal_universe_binary-amd64_Packages
-rw-r--r-- 1 root root 25647543 Jan 29 13:44 ca.archive.ubuntu.com_ubuntu_dists_focal_universe_binary-i386_Packages
-rw-r--r-- 1 root root  1152791 Nov 25 21:26 ca.archive.ubuntu.com_ubuntu_dists_focal_universe_cnf_Commands-amd64
-rw-r--r-- 1 root root  5506574 Jan 29 11:51 ca.archive.ubuntu.com_ubuntu_dists_focal_universe_dep11_Components-amd64.yml.gz
-rw-r--r-- 1 root root 15204406 Jan 29 11:50 ca.archive.ubuntu.com_ubuntu_dists_focal_universe_dep11_icons-128x128.tar.gz
-rw-r--r-- 1 root root  2935737 Jan 29 11:50 ca.archive.ubuntu.com_ubuntu_dists_focal_universe_dep11_icons-48x48.tar.gz
-rw-r--r-- 1 root root    35700 Jan 28 07:53 ca.archive.ubuntu.com_ubuntu_dists_focal_universe_dep11_icons-64x64%402.tar.gz
-rw-r--r-- 1 root root  7923448 Jan 29 11:50 ca.archive.ubuntu.com_ubuntu_dists_focal_universe_dep11_icons-64x64.tar.gz
-rw-r--r-- 1 root root 26781141 Jan 29 13:44 ca.archive.ubuntu.com_ubuntu_dists_focal_universe_i18n_Translation-en
-rw-r--r-- 1 root root     1858 Jan 10 12:07 ca.archive.ubuntu.com_ubuntu_dists_focal_universe_i18n_Translation-en%5fCA
-rw-r--r-- 1 root root    79701 Oct 25 00:33 ca.archive.ubuntu.com_ubuntu_dists_focal-updates_InRelease
-rw-r--r-- 1 root root       51 Oct 25 00:29 ca.archive.ubuntu.com_ubuntu_dists_focal-updates_main_cnf_Commands-amd64
-rw-r--r-- 1 root root       57 Oct 25 00:29 ca.archive.ubuntu.com_ubuntu_dists_focal-updates_multiverse_cnf_Commands-amd64
-rw-r--r-- 1 root root       57 Oct 25 00:29 ca.archive.ubuntu.com_ubuntu_dists_focal-updates_restricted_cnf_Commands-amd64
-rw-r--r-- 1 root root       55 Oct 25 00:29 ca.archive.ubuntu.com_ubuntu_dists_focal-updates_universe_cnf_Commands-amd64
-rw-r----- 1 root root        0 Jan  3 23:22 lock
drwx------ 1 _apt root        0 Jan 29 14:41 partial
-rw-r--r-- 1 root root    79703 Oct 25 00:33 security.ubuntu.com_ubuntu_dists_focal-security_InRelease
-rw-r--r-- 1 root root       52 Oct 25 00:29 security.ubuntu.com_ubuntu_dists_focal-security_main_cnf_Commands-amd64
-rw-r--r-- 1 root root       58 Oct 25 00:29 security.ubuntu.com_ubuntu_dists_focal-security_multiverse_cnf_Commands-amd64
-rw-r--r-- 1 root root       58 Oct 25 00:29 security.ubuntu.com_ubuntu_dists_focal-security_restricted_cnf_Commands-amd64
-rw-r--r-- 1 root root       56 Oct 25 00:29 security.ubuntu.com_ubuntu_dists_focal-security_universe_cnf_Commands-amd64

Or,

[B]jerry@Aspire-V3-771:~$ ls -lh /var/lib/apt/lists/ | uniq[/B]
total 147M
-rw-r--r-- 1 root root  11K Dec 10 13:44 archive.canonical.com_ubuntu_dists_focal_InRelease
-rw-r--r-- 1 root root 3.7K Dec 10 13:44 archive.canonical.com_ubuntu_dists_focal_partner_binary-amd64_Packages
-rw-r--r-- 1 root root 4.0K Oct 18 06:49 archive.canonical.com_ubuntu_dists_focal_partner_binary-i386_Packages
-rw-r--r-- 1 root root 2.0K Dec 10 13:44 archive.canonical.com_ubuntu_dists_focal_partner_i18n_Translation-en
drwxr-xr-x 1 _apt root    0 Jan  3 23:22 auxfiles
-rw-r--r-- 1 root root  78K Oct 25 00:28 ca.archive.ubuntu.com_ubuntu_dists_focal-backports_InRelease
-rw-r--r-- 1 root root   53 Oct 25 00:23 ca.archive.ubuntu.com_ubuntu_dists_focal-backports_main_cnf_Commands-amd64
-rw-r--r-- 1 root root   59 Oct 25 00:23 ca.archive.ubuntu.com_ubuntu_dists_focal-backports_multiverse_cnf_Commands-amd64
-rw-r--r-- 1 root root   59 Oct 25 00:23 ca.archive.ubuntu.com_ubuntu_dists_focal-backports_restricted_cnf_Commands-amd64
-rw-r--r-- 1 root root   57 Oct 25 00:23 ca.archive.ubuntu.com_ubuntu_dists_focal-backports_universe_cnf_Commands-amd64
-rw-r--r-- 1 root root 250K Jan 29 14:05 ca.archive.ubuntu.com_ubuntu_dists_focal_InRelease
-rw-r--r-- 1 root root 6.1M Jan 29 13:44 ca.archive.ubuntu.com_ubuntu_dists_focal_main_binary-amd64_Packages
-rw-r--r-- 1 root root 4.2M Jan 29 13:44 ca.archive.ubuntu.com_ubuntu_dists_focal_main_binary-i386_Packages
-rw-r--r-- 1 root root 108K Nov 25 21:24 ca.archive.ubuntu.com_ubuntu_dists_focal_main_cnf_Commands-amd64
-rw-r--r-- 1 root root 718K Jan 29 11:46 ca.archive.ubuntu.com_ubuntu_dists_focal_main_dep11_Components-amd64.yml.gz
-rw-r--r-- 1 root root 360K Jan 29 11:46 ca.archive.ubuntu.com_ubuntu_dists_focal_main_dep11_icons-128x128.tar.gz
-rw-r--r-- 1 root root  89K Jan 29 11:46 ca.archive.ubuntu.com_ubuntu_dists_focal_main_dep11_icons-48x48.tar.gz
-rw-r--r-- 1 root root 6.1K Jan 15 14:47 ca.archive.ubuntu.com_ubuntu_dists_focal_main_dep11_icons-64x64%402.tar.gz
-rw-r--r-- 1 root root 158K Jan 29 11:46 ca.archive.ubuntu.com_ubuntu_dists_focal_main_dep11_icons-64x64.tar.gz
-rw-r--r-- 1 root root 2.9M Jan 28 23:19 ca.archive.ubuntu.com_ubuntu_dists_focal_main_i18n_Translation-en
-rw-r--r-- 1 root root  12K Jan 10 12:07 ca.archive.ubuntu.com_ubuntu_dists_focal_main_i18n_Translation-en%5fCA
-rw-r--r-- 1 root root 734K Jan 28 08:59 ca.archive.ubuntu.com_ubuntu_dists_focal_multiverse_binary-amd64_Packages
-rw-r--r-- 1 root root 363K Jan 27 20:54 ca.archive.ubuntu.com_ubuntu_dists_focal_multiverse_binary-i386_Packages
-rw-r--r-- 1 root root  32K Nov 25 19:30 ca.archive.ubuntu.com_ubuntu_dists_focal_multiverse_cnf_Commands-amd64
-rw-r--r-- 1 root root  58K Jan 29 11:56 ca.archive.ubuntu.com_ubuntu_dists_focal_multiverse_dep11_Components-amd64.yml.gz
-rw-r--r-- 1 root root 350K Jan 29 11:56 ca.archive.ubuntu.com_ubuntu_dists_focal_multiverse_dep11_icons-128x128.tar.gz
-rw-r--r-- 1 root root  15K Jan 29 11:56 ca.archive.ubuntu.com_ubuntu_dists_focal_multiverse_dep11_icons-48x48.tar.gz
-rw-r--r-- 1 root root 1.1K Dec 10 14:58 ca.archive.ubuntu.com_ubuntu_dists_focal_multiverse_dep11_icons-64x64%402.tar.gz
-rw-r--r-- 1 root root 196K Jan 29 11:56 ca.archive.ubuntu.com_ubuntu_dists_focal_multiverse_dep11_icons-64x64.tar.gz
-rw-r--r-- 1 root root 467K Jan 28 08:59 ca.archive.ubuntu.com_ubuntu_dists_focal_multiverse_i18n_Translation-en
-rw-r--r-- 1 root root 258K Jan 28 09:25 ca.archive.ubuntu.com_ubuntu_dists_focal_restricted_binary-amd64_Packages
-rw-r--r-- 1 root root  59K Jan 24 06:29 ca.archive.ubuntu.com_ubuntu_dists_focal_restricted_binary-i386_Packages
-rw-r--r-- 1 root root 1.4K Nov 15 08:25 ca.archive.ubuntu.com_ubuntu_dists_focal_restricted_cnf_Commands-amd64
-rw-r--r-- 1 root root  47K Jan 28 08:59 ca.archive.ubuntu.com_ubuntu_dists_focal_restricted_i18n_Translation-en
-rw-r--r-- 1 root root  48M Jan 29 13:44 ca.archive.ubuntu.com_ubuntu_dists_focal_universe_binary-amd64_Packages
-rw-r--r-- 1 root root  25M Jan 29 13:44 ca.archive.ubuntu.com_ubuntu_dists_focal_universe_binary-i386_Packages
-rw-r--r-- 1 root root 1.1M Nov 25 21:26 ca.archive.ubuntu.com_ubuntu_dists_focal_universe_cnf_Commands-amd64
-rw-r--r-- 1 root root 5.3M Jan 29 11:51 ca.archive.ubuntu.com_ubuntu_dists_focal_universe_dep11_Components-amd64.yml.gz
-rw-r--r-- 1 root root  15M Jan 29 11:50 ca.archive.ubuntu.com_ubuntu_dists_focal_universe_dep11_icons-128x128.tar.gz
-rw-r--r-- 1 root root 2.8M Jan 29 11:50 ca.archive.ubuntu.com_ubuntu_dists_focal_universe_dep11_icons-48x48.tar.gz
-rw-r--r-- 1 root root  35K Jan 28 07:53 ca.archive.ubuntu.com_ubuntu_dists_focal_universe_dep11_icons-64x64%402.tar.gz
-rw-r--r-- 1 root root 7.6M Jan 29 11:50 ca.archive.ubuntu.com_ubuntu_dists_focal_universe_dep11_icons-64x64.tar.gz
-rw-r--r-- 1 root root  26M Jan 29 13:44 ca.archive.ubuntu.com_ubuntu_dists_focal_universe_i18n_Translation-en
-rw-r--r-- 1 root root 1.9K Jan 10 12:07 ca.archive.ubuntu.com_ubuntu_dists_focal_universe_i18n_Translation-en%5fCA
-rw-r--r-- 1 root root  78K Oct 25 00:33 ca.archive.ubuntu.com_ubuntu_dists_focal-updates_InRelease
-rw-r--r-- 1 root root   51 Oct 25 00:29 ca.archive.ubuntu.com_ubuntu_dists_focal-updates_main_cnf_Commands-amd64
-rw-r--r-- 1 root root   57 Oct 25 00:29 ca.archive.ubuntu.com_ubuntu_dists_focal-updates_multiverse_cnf_Commands-amd64
-rw-r--r-- 1 root root   57 Oct 25 00:29 ca.archive.ubuntu.com_ubuntu_dists_focal-updates_restricted_cnf_Commands-amd64
-rw-r--r-- 1 root root   55 Oct 25 00:29 ca.archive.ubuntu.com_ubuntu_dists_focal-updates_universe_cnf_Commands-amd64
-rw-r----- 1 root root    0 Jan  3 23:22 lock
drwx------ 1 _apt root    0 Jan 29 14:41 partial
-rw-r--r-- 1 root root  78K Oct 25 00:33 security.ubuntu.com_ubuntu_dists_focal-security_InRelease
-rw-r--r-- 1 root root   52 Oct 25 00:29 security.ubuntu.com_ubuntu_dists_focal-security_main_cnf_Commands-amd64
-rw-r--r-- 1 root root   58 Oct 25 00:29 security.ubuntu.com_ubuntu_dists_focal-security_multiverse_cnf_Commands-amd64
-rw-r--r-- 1 root root   58 Oct 25 00:29 security.ubuntu.com_ubuntu_dists_focal-security_restricted_cnf_Commands-amd64
-rw-r--r-- 1 root root   56 Oct 25 00:29 security.ubuntu.com_ubuntu_dists_focal-security_universe_cnf_Commands-amd64

[kubicle]

Thanks for the heads-up!
Now, how do I re-enable my access to repository settings?

First disable your proposed repositories by commenting out the lines that have "proposed" in them in /etc/apt/sources.list.

Then run "sudo apt update & sudo apt install ubuntu-drivers-common"
If there are no errors, muon's repository management should work after that. If there are errors with the install, post them here (if you have already installed stuff from proposed, you may need to downgrade them to meet depencies)

[GreyGeek]

Thanks for the heads-up!
Now, how do I re-enable my access to repository settings?

[acheron]

ubuntu-drivers-common is a real package

The reason it is not installable is that ubuntu-drivers-common depends on alsa-utils which is not installable with proposed enabled, as it depends on alsa-libs which in proposed version breaks the version of alsa-utils that is available.

This sort of thing is why the proposed > release pocket separation exists. Packages do not migrate from the proposed to release pocket until such installability brokenness is fixed.

Even brave testers of the dev release should not routinely run with proposed enabled.

[GreyGeek]

Neither should be strictly speaking necessary (if you don't need the kubuntu-driver-manager, and nothing else you need depends on them). You can always install drivers manually and not use the driver-manager GUI. I thought you meant that ubuntu-drivers-common wasn't installed on one focal installation and kubuntu-driver-manager was (which would be quite strange).


The XDG message is normal, and results from muon running as root (XDG_RUNTIME_DIR is set for your user, but not for root, so it just uses /tmp/runtime-root which is the default)
The rest of the messages point to a python problem. Muon's repository management uses "software-properties-kde" which wants to load the UbuntuDrivers python module. Do you have ubuntu-drivers-common installed? (If not, try installing it...if yes, then it's a problem with the packages, something is lagging behind)

Kubuntu-drivers-manager was not installed and could not be marked for installation or upgrade.

Ubuntu-drivers-manager gave the same msg:


I'll poke around in the python packages and see what pops up.

[kubicle]

My ASUS does not have "kubuntu-driver-manager" installed or "ubuntu-driver-common" and has no problems with the Pre-release updates. Whereas my HP which is a UHD display has both "kubuntu-driver-manager" and "ubuntu-driver-common" installed

Neither should be strictly speaking necessary (if you don't need the kubuntu-driver-manager, and nothing else you need depends on them). You can always install drivers manually and not use the driver-manager GUI. I thought you meant that ubuntu-drivers-common wasn't installed on one focal installation and kubuntu-driver-manager was (which would be quite strange).

But, XDG_RUNTIME_DIR was set

The XDG message is normal, and results from muon running as root (XDG_RUNTIME_DIR is set for your user, but not for root, so it just uses /tmp/runtime-root which is the default)
The rest of the messages point to a python problem. Muon's repository management uses "software-properties-kde" which wants to load the UbuntuDrivers python module. Do you have ubuntu-drivers-common installed? (If not, try installing it...if yes, then it's a problem with the packages, something is lagging behind)

[NoWorries]

ubuntu-drivers-common is the driver check/install commands and backend used by the various DE specific GUI tools for driver install (like "kubuntu-driver-manager"), which depend on it...so it actually should be installed if you have "kubuntu-driver-manager" installed (i'm not on focal so I can't directly check if there are any changes to the dependency chain, but I doubt it). EDIT, checked, kubuntu-driver-manager still depends on ubuntu-drivers-common on focal.

I have two systems with Focal. One is an ASUS with an Nvidia video and the other is a HP with an AMD Radeon RX Vega video.

My ASUS does not have "kubuntu-driver-manager" installed or "ubuntu-driver-common" and has no problems with the Pre-release updates. Whereas my HP which is a UHD display has both "kubuntu-driver-manager" and "ubuntu-driver-common" installed.

I have with previous distributions encountered problems with Pre-release updated and waited for this problem to pass. In this case I found the difference a little odd and that is why I decided to seek a solution.

I will take your advice and wait out until the problem packaged is fixed. At least Muon gives me a good guide on what is going to be removed.

[GreyGeek]

I ran into that same problem yesterday. This morning I rolled back to 20200122.

After doing a 22 file upgrade earlier today, I opened Muon to check my repository settings and when I entered the password it took me back to the main GUI.
This was the error msg:

QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
Traceback (most recent call last):
File "/usr/bin/software-properties-kde", line 38, in <module>
from softwareproperties.qt.SoftwarePropertiesQt import SoftwarePropertiesQt
File "/usr/lib/python3/dist-packages/softwareproperties/qt/SoftwarePropertiesQt.py", line 56, in <module>
from UbuntuDrivers import detect
ModuleNotFoundError: No module named 'UbuntuDrivers'

But, XDG_RUNTIME_DIR was set:

:~$ env | grep XDG
XDG_CONFIG_DIRS=/etc/xdg/xdg-plasma:/etc/xdg:/usr/share/kubuntu-default-settings/kf5-settings
XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session1
XDG_SEAT=seat0
XDG_SESSION_DESKTOP=KDE
XDG_SESSION_TYPE=x11
XDG_CURRENT_DESKTOP=KDE
XDG_SEAT_PATH=/org/freedesktop/DisplayManager/Seat0
XDG_SESSION_CLASS=user
XDG_VTNR=1
XDG_SESSION_ID=3
XDG_RUNTIME_DIR=/run/user/1000
XDG_DATA_DIRS=/usr/share/plasma:/usr/local/share:/usr/share:/var/lib/snapd/desktop

I redid "sudo apt update & sudo apt full-upgrade" and got only two apps held back (libwin32 and wine32). So, out of curiosity, I opened Discover. It said I had 41 apps ready to update. So, I let it run. I still can't access my repository setting dialog, however.

Discover must bedrawing from the snap store. That means that either I abandon Muon and use Discover only, or I run apt from the command line and Discover from the menu.

I hope this is not the way Kubuntu is heading. And, if it is, how can Neon avoid it without re-engineering its Ubuntu base?

[kubicle]

When I enable muon updates with Pre-release updates

My best recommendation is, don't.
the "proposed" repository is where packages are built and tested, and dependency breakage is fairly common, it makes very little sense to enable it unless you specifically wish to find out what is broken (development). When packages are issue free, they get moved to the regular repos in a matter of hours or days. The dependency problems could be caused by the python changes in focal or a number of other things, but are generally not really solvable by user actions (that's why they are in proposed).

As far as I can tell the package ubuntu-drivers-common should not be installed. On my other system with Focal it is not install and it is treated as a virtual package which cannot be installed or upgraded. If I try to remove ubuntu-drivers-common it wants to remove:

• kubuntu-driver-manager
• kubuntu-desktop
• kubuntu-notifications-helper

I am wondering if I should remove ubuntu-drivers-common and then install the ones it has removed.

I am open to any suggestions to solve this problem.

ubuntu-drivers-common is the driver check/install commands and backend used by the various DE specific GUI tools for driver install (like "kubuntu-driver-manager"), which depend on it...so it actually should be installed if you have "kubuntu-driver-manager" installed (i'm not on focal so I can't directly check if there are any changes to the dependency chain, but I doubt it). EDIT, checked, kubuntu-driver-manager still depends on ubuntu-drivers-common on focal.

[NoWorries]

I have certainly enjoyed reading all the contributions to views on snap and its uncertain future. But I am seeking help on a problem that I have encountered which is not related to snap.

When I enable muon updates with Pre-release updates, it tries to remove 8 essential packages as shown in this image



As far as I can tell the package ubuntu-drivers-common should not be installed. On my other system with Focal it is not install and it is treated as a virtual package which cannot be installed or upgraded. If I try to remove ubuntu-drivers-common it wants to remove:

• kubuntu-driver-manager
• kubuntu-desktop
• kubuntu-notifications-helper

I am wondering if I should remove ubuntu-drivers-common and then install the ones it has removed.

I am open to any suggestions to solve this problem.

[kubicle]

Hmmm... could have fooled me. Here's the screen capture

That is certainly odd. It definitely shouldn't be there. So, the command 'plasmashell --version' reports 5.17.90 and the unlock widgets option is still there after restarting plasma (or logging out or rebooting)? It definitely shouldn't be, but I'd probably have to install the beta to dig any deeper.

Except that I deliberately removed snapd, and its sockets and its "plumbing" (squashfs mount points that chromium used), and chromium-browser. BTW, reinstalling snapd did not re-create the mount points. I had to do that manually.

I'd think that is probably because you manually disabled all that plumbing/mounts. While it can be considered somewhat unexpected that a user would purposefully disable things that are necessary for the snap to work, snapd *should* be able to handle such occurrences (and if it doesn't, it's just another example that the coding isn't technically up to par).

The "repository" version of chromium-browser (the deb package) is 47kb in size (it would obviously be quite a feat to fit a modern browser into it), the pre/postinstall scripts within the package just install the snap version from the snap store, and the /usr/bin/chromium-browser file installed by that deb is just this script (pasting only the important bits):

#!/bin/sh
if ! [ -x /snap/bin/chromium ]; then
echo "" >&2
echo "Command '$0' requires the chromium snap to be installed." >&2
echo "Please install it with:" >&2
echo "" >&2
echo "snap install chromium" >&2
echo "" >&2
exit 1
fi
...
[DESKTOP SPECIFIC CODE HERE]
...
[HL]exec /snap/bin/chromium "$@"[/HL]

Since that may take a few months or years, my next concern is what Canonical plans to do with the repository that has accompanied Ubuntu/Kubuntu since their inception?

Well, ubuntu basically copies the stuff they want from debian (with only small changes), and then put their crap on top of that. Obviously the base system will always come in debs, but my guess is that Canonical is planning to eventually replace the user facing apps in ubuntu with snaps, which reduces their maintenance efforts/costs (and shift that maintenance to upstream devs that will be responsible for maintaining the snaps). This will likely be a tough pill to swallow for many ubuntu users, but that's what you get with Canonical.

They are redundant sources of application but will the repository contain the best and the latest

The deb repositories of released versions will never contain "the latest" as *buntus aren't rolling releases. The snaps are probably also an attempt (a poor one) to remedy that (so you could get newer apps that are available in the repos...or apps that are unavailable in the repos).

Discover/Muon/Synaptic have no running daemons and are not active when the user is not actually removing, installing or updating their applications. Snapd is in our face all the time. Flatpak requires that you "add remotes" (repositories) despite the fact that we have a repository already. So, in affect, it becomes just another PPA.

While I dislike the snap infrastructure, the contained package formats do offer several advantages over the ppas (which really are problematic in many ways...compatibility and security issues are a real problem)...there are a few "official ppas" that can be considered quite secure, but even those suffer from many compatibility (and maintenance) issues.

[Don B. Cilly]

Just out of curiosity, why would you want to have Chromium even though it's snap-only?
Brave for example is basically Chromium, it's open-source and does not come as a snap.

[GreyGeek]

....
IMO the technical implementation is a mess (that can't easily be fixed) and how the whole snap infrastructure should be quickly placed to the same recycle bin where you find the rest of Canonical garbage (upstart, unity, mir) that all ended up there because Canonical stubbornly refuses to understand how the free software ecosystem works and how to work with it rather than trying to do their own thing and trying to coerce everyone else to accept their crappy excuse for software engineering.

It would be perfect if snapd were resting comfortable along side upstart, unity and mir in the trash bin. Something to hope for.

Since that may take a few months or years, my next concern is what Canonical plans to do with the repository that has accompanied Ubuntu/Kubuntu since their inception? They are redundant sources of application but will the repository contain the best and the latest, or will it shrivel on the vine and die? Discover/Muon/Synaptic have no running daemons and are not active when the user is not actually removing, installing or updating their applications. Snapd is in our face all the time. Flatpak requires that you "add remotes" (repositories) despite the fact that we have a repository already. So, in affect, it becomes just another PPA.

For years I've seen the packages in the repository grow in number from 35,000 to 85,000 and drop back to 65,000 only recently (dropping 32bit packages?). I can't imagine, at this point, that snapd or flatpak would have access to that many packages. All Canonical is doing is throwing mud into what was once a sparkling pool.

[GreyGeek]

Appimages don't really have a centralized store to find them, the format is basically meant for developer direct distribution. I'd probably use great care for picking them up on just any site that provides them en masse, the trustworthiness of such images is not easily determined, probably better to rely on appimages that are straight from the developer (this is what they are meant for).

It is obvious that AppImages don't have a "repository" in the regular sense, and the importance of site selection is also obvious.

With the discover backend installed by default, you can install them directly from Discover, not really complicated at all. Link: https://pointieststick.com/2018/01/1...t-in-discover/ (I am assuming the flatpak backend is installed by default on 20.04, but I'm not 100% sure, but in case it isn't, it's just one "apt install" away)


Due to the technical implementation of snaps, it's snapd's job to create the loop mounts (and other "plumbing") for the snap you run, so it's necessary to have the daemon running for running installed snap software (it's not just for installing, updating and removing snaps), terminology explained: https://askubuntu.com/questions/9634...nappy-refer-to


And that is a snap package, not a regular deb so it needs the snap "plumbing" to work. (https://snapcraft.io/blog/chromium-i...nap-transition)

Except that I deliberately removed snapd, and its sockets and its "plumbing" (squashfs mount points that chromium used), and chromium-browser. BTW, reinstalling snapd did not re-create the mount points. I had to do that manually. That's when I decided to forget the trench work and just roll back. Three minutes later I was running my 20200122 snapshots and 5 minutes later I had 202 updates installed.