Hi, I just upgraded to 24.04 and am trying to add the included Nvidia driver, but after clicking Install, I am presented with a popup indicating error 303 about no authentication; I also entered the List Nvidia drivers in the terminal, which gives me some message I don't understand (screenshot provided).
anthony@anthony-OptiPlex-9010:~$ sudo ubuntu-drivers list
[sudo] password for anthony:
udevadm hwdb is deprecated. Use systemd-hwdb instead.
udevadm hwdb is deprecated. Use systemd-hwdb instead.
udevadm hwdb is deprecated. Use systemd-hwdb instead.
udevadm hwdb is deprecated. Use systemd-hwdb instead.
udevadm hwdb is deprecated. Use systemd-hwdb instead.
udevadm hwdb is deprecated. Use systemd-hwdb instead.
udevadm hwdb is deprecated. Use systemd-hwdb instead.
udevadm hwdb is deprecated. Use systemd-hwdb instead.
udevadm hwdb is deprecated. Use systemd-hwdb instead.
udevadm hwdb is deprecated. Use systemd-hwdb instead.
anthony@anthony-OptiPlex-9010:~$
Can I suggest that you close that "Software & Updates" window and run first the "Software Updater " in your "Ubuntu MATE 24.04"? I'm suggesting that because I fear that you may then find / get a "Partial Upgrade " window like the following screenshot and, IF that's the case, you should then click the "Partial Upgrade" button in that window and let it complete the partial upgrade:
Hi. I guess I should explain how my OS got to where it is now because it's probably causing some error that you can diagnose quickly; I tried running the Software Updater--the program was just going to remove some 6.8.0 kernels and didn't say anything about a partial upgrade.
I tried to upgrade last night then was told about the system not being able to disable screen lock (I have Caffeine installed--wouldn't that program make the screen not able to lock?). When I saw the message about the OS not being able to turn off screen-locking, I went to Firefox to see if there was something I needed to do. At this point, the Upgrade utility had downloaded the new packages, but I couldn't close Firefox, and FF being a program, I was told by the Upgrade utility to close all programs. I wanted the Upgrader to have the best chance of completing, so I needed to close FF, but couldn't; all that happened with the Upgrader is that it downloaded some packages at this point and I figured the Upgrader would just download them again if I turned off the system, and the requirement of not having an open program would be met. When the machine booted back up and I tried to upgrade, there indeed was a message about a partial Upgrade, but at some point the Wifi quit working, to where the computer saw nothing wifi--lsusb listed the Qgoo, though.
Earlier with this computer, the Qgoo stopped due to an upgraded kernel and I learned that I could get Wifi again if I just went to an earlier kernel (5.8) by pressing Esc at boot. So since I had no Wifi, this is what I did. Since I couldn't fix the Wifi situation for the 6.8 kernel, but 5.8 worked, I ran the Dist Upgrade command from the CLI. So now I have Wifi on 6.8-57 and the upgraded system shown by Profiler and Benchmark--24.04, but I have these authentication issues; Software Updater won't proceed to ask password after showing the window of what it's going to do (remove 6.8-*). I have some home stuff backed up, but the better option, I think, would be moving my entire Home directory to its own partition, then reinstall Noble, if I need to reinstall the OS. The terminal still asks for authentication, unlike the Software Updater, so I might be able to migrate the Home directory; is there something else I can do but reinstall? I had problems with authentication recently and discovered I had Policy Kit and the other keys not ticked to turn on at Startup--I checked, and they're ticked, so not sure about this authentication issue by Software Updater quitting before asking for the password to remove kernels.
The Software Updater not being able to disable screen lock might be a permission issue (perhaps there's some problem with the gnome keyring? I'm not an expert). Caffeine merely prevents screen locking by simulating input - but it's not disabling it.
Why not?
Is this something that happens normally? Or do you think it was disabled during some part of the upgrade process?
This last part suggests that you are able to get wifi working with the 6.8 kernel - is that correct?
Overall, it sounds like something is going wrong with the GNOME keyring on your setup; but I'm not an expert. There might be some clues if you look at the GNOME keyring and polkit services:
# check services like GNOME keyring and polkit:
systemctl status polkit.service
systemctl status --user gnome-keyring-daemon.service
# also see if "gkr" pops up elsewhere in the log for the current boot:
journalctl -b 0 | grep gkr-
With respect to your original post:
udevadm hwdb is deprecated. Use systemd-hwdb instead.
That's benign. However, when I run the command, I see a list of NV drivers, too, e.g.
udevadm hwdb is deprecated. Use systemd-hwdb instead.
...
nvidia-driver-550, (kernel modules provided by linux-modules-nvidia-550-generic)
nvidia-driver-535, (kernel modules provided by linux-modules-nvidia-535-generic)
...
Can you confirm that you have proprietary (restricted) drivers selected in Software & Updates?
I could be wrong about GNOME keyring, it looks like the issue is more likely with polkit (which PackageKit uses, which I believe 'pk-client-error' refers to).
Thanks for the info. After I opened Firefox to see about disabling Screen Lock, I think I minimized it and couldn't get the icon to clear from the dock (I was using Mutiny).
I think the wifi quiting had to do with me just turning off the computer--I didn't think the action would do anything since Upgrade just downloaded packages and could just re-download them; I don't have a problem usually with wifi. The wifi issue is indeed fine now (6.8 is okay)--I guess upgrading to 24.04 from a recovery kernel (5.8) reconfigured/replaced the main version so that I don't have to use a recovery kernel for wifi.
In Ubuntu Software and Updates, all are ticked except for the listing of Source Code.
● polkit.service - Authorization Manager
Loaded: loaded (/usr/lib/systemd/system/polkit.service; static)
Active: active (running) since Wed 2025-04-09 19:40:35 CDT; 3h 46min ago
Docs: man:polkit(8)
Main PID: 1065 (polkitd)
Tasks: 4 (limit: 28614)
Memory: 13.7M (peak: 14.4M)
CPU: 811ms
CGroup: /system.slice/polkit.service
└─1065 /usr/lib/polkit-1/polkitd --no-debug
Apr 09 19:40:21 anthony-OptiPlex-9010 systemd[1]: Starting polkit.service - Authorization Manager...
Apr 09 19:40:24 anthony-OptiPlex-9010 polkitd[1065]: Started polkitd version 124
Apr 09 19:40:32 anthony-OptiPlex-9010 polkitd[1065]: Loading rules from directory /etc/polkit-1/rules.d
Apr 09 19:40:32 anthony-OptiPlex-9010 polkitd[1065]: Loading rules from directory /usr/share/polkit-1/ru>
Apr 09 19:40:35 anthony-OptiPlex-9010 polkitd[1065]: Finished loading, compiling and executing 23 rules
Apr 09 19:40:35 anthony-OptiPlex-9010 systemd[1]: Started polkit.service - Authorization Manager.
Apr 09 19:40:35 anthony-OptiPlex-9010 polkitd[1065]: Acquired the name org.freedesktop.PolicyKit1 on the>
~
anthony@anthony-OptiPlex-9010:~$ systemctl status --user gnome-keyring-daemon.service
● gnome-keyring-daemon.service - GNOME Keyring daemon
Loaded: loaded (/usr/lib/systemd/user/gnome-keyring-daemon.service; enabled; preset: enabled)
Active: active (running) since Wed 2025-04-09 19:41:05 CDT; 3h 48min ago
TriggeredBy: ● gnome-keyring-daemon.socket
Main PID: 1840 (gnome-keyring-d)
Tasks: 5 (limit: 28614)
Memory: 2.3M (peak: 2.8M)
CPU: 786ms
CGroup: /user.slice/user-1000.slice/[email protected]/app.slice/gnome-keyring-daemon.service
└─1840 /usr/bin/gnome-keyring-daemon --foreground --components=pkcs11,secrets --control-dir>
Apr 09 19:41:05 anthony-OptiPlex-9010 gnome-keyring-daemon[1840]: The PKCS#11 component was already init>
Apr 09 19:41:05 anthony-OptiPlex-9010 gnome-keyring-d[1840]: The PKCS#11 component was already initializ>
Apr 09 19:41:12 anthony-OptiPlex-9010 gnome-keyring-daemon[1840]: The PKCS#11 component was already init>
Apr 09 19:41:12 anthony-OptiPlex-9010 gnome-keyring-d[1840]: The PKCS#11 component was already initializ>
Apr 09 19:41:14 anthony-OptiPlex-9010 gnome-keyring-daemon[1840]: The SSH agent was already initialized
Apr 09 19:41:14 anthony-OptiPlex-9010 gnome-keyring-d[1840]: The SSH agent was already initialized
Apr 09 19:41:17 anthony-OptiPlex-9010 gnome-keyring-daemon[1840]: The Secret Service was already initial>
Apr 09 19:41:17 anthony-OptiPlex-9010 gnome-keyring-d[1840]: The Secret Service was already initialized
Apr 09 19:41:53 anthony-OptiPlex-9010 gnome-keyring-daemon[1840]: asked to register item /org/freedeskto>
Apr 09 19:41:53 anthony-OptiPlex-9010 gnome-keyring-d[1840]: asked to register item /org/freedesktop/sec>
lines 1-21/21 (END)
The Nvidia driver is okay now. I have the screen-flicker issue I read about--I'll deal with that tomorrow. Still can't use the Additional Drivers method--with the message about pk-clieny-error-quark.
Sunaptic, probably due to the Authentication problem, is still not appearing.
I'm not sure why lightdm is not able to unlock the GNOME keyring when you log in - that must be something that you've set up (because it isn't the default behaviour).
As far as I remember, @Anthony_Craig had the autologin option enabled for lightdm. When autologin is enabled, the login.keyring is not unlocked automatically.
Hi all. I went back to 22.04, deciding to give Noble more time to work out kinks. One external drive had almost a free terabyte, so I backed up my entire home directory, only taking about 200GB. So right now, just waiting for the restore to finish.
I would keep expectations low for noble if you aren't willing to start from a clean slate; otherwise, you might want to wait until the next LTS and try a fresh install then.
Upgrades just aren't as clean and settings get carried over that trip things up - as probably happened in your system.
