Interesting observation in noble in contrary to jammy, the keyring runs
with two components secrets,pkcs11, instead only secrets

root@desktop-noble:~# ps aux|grep keyrin
gdm         5468  0.0  0.1 314312  9728 ?        Ssl  11:12   0:00 
/usr/bin/gnome-keyring-daemon --foreground --components=pkcs11,secrets 
--control-directory=/run/user/124/keyring
root        5544  0.0  0.0   7076  2048 pts/0    S+   11:16   0:00 grep 
--color=auto keyrin

If I create the override like below and reboot

root@desktop-noble:~# cat 
/etc/systemd/user/gnome-keyring-daemon.service.d/override.conf
[Service]
#ExecStart=/usr/bin/gnome-keyring-daemon --foreground 
--components="pkcs11,secrets" --control-directory=%t/keyring
ExecStart=/usr/bin/gnome-keyring-daemon --foreground --components="secrets" 
--control-directory=%t/keyring

Then the service is running like:
12:18 PM
root@desktop-noble:~# ps aux|grep keyrin
gdm         1748  0.0  0.1 314308  9472 tty1     Sl+  11:18   0:00 
/usr/bin/gnome-keyring-daemon --start --foreground --components=secrets
root        1763  0.0  0.0   7076  2048 pts/0    S+   11:18   0:00 grep 
--color=auto keyrin

and the org.freedesktop.secrets is successful

Feb 17 11:44:38 desktop-noble kernel: Lockdown: systemd-logind: hibernation is 
restricted; see man kernel_lockdown.7
Feb 17 11:44:43 desktop-noble NetworkManager[1779]: 
/etc/netplan/50-cloud-init.yaml: Error in network definition: wlp6s0f0: No 
access points defined
Feb 17 11:44:43 desktop-noble systemd[1]: Reloading requested from client PID 
1781 ('systemctl') (unit NetworkManager.service)...
Feb 17 11:44:43 desktop-noble systemd[1]: Reloading...
Feb 17 11:44:44 desktop-noble systemd[1]: Reloading finished in 116 ms.
Feb 17 11:44:44 desktop-noble NetworkManager[952]: <info>  [1739792684.0610] 
device (wlp6s0f0): Activation: starting connection 'coppernik-guest' 
(e69fb8d0-8ade-4196-9b1f-9d0e6d9ca6af)
Feb 17 11:44:44 desktop-noble NetworkManager[952]: <info>  [1739792684.0612] 
audit: op="connection-add-activate" uuid="e69fb8d0-8ade-4196-9b1f-9d0e6d9ca6af" 
name="coppernik-guest" pid=1337 uid=124 result="success"
Feb 17 11:44:44 desktop-noble NetworkManager[952]: <info>  [1739792684.0613] 
device (wlp6s0f0): state change: disconnected -> prepare (reason 'none', 
sys-iface-state: 'managed')
Feb 17 11:44:44 desktop-noble NetworkManager[952]: <info>  [1739792684.0614] 
device (wlp6s0f0): state change: prepare -> config (reason 'none', 
sys-iface-state: 'managed')
Feb 17 11:44:44 desktop-noble NetworkManager[952]: <info>  [1739792684.0616] 
device (wlp6s0f0): Activation: (wifi) access point 'coppernik-guest' has 
security, but secrets are required.
Feb 17 11:44:44 desktop-noble NetworkManager[952]: <info>  [1739792684.0616] 
device (wlp6s0f0): state change: config -> need-auth (reason 'none', 
sys-iface-state: 'managed')
Feb 17 11:44:44 desktop-noble /usr/libexec/gdm-wayland-session[1290]: 
dbus-daemon[1290]: [session uid=124 pid=1290] Activating service 
name='org.freedesktop.secrets' requested by ':1.3' (uid=124 pid=1337 
comm="/usr/bin/gnome-shell" label="unconfined")
Feb 17 11:44:44 desktop-noble gnome-keyring-daemon[1884]: couldn't access 
control socket: /run/user/124/keyring/control: No such file or directory
Feb 17 11:44:44 desktop-noble gnome-keyring-daemon[1884]: 
discover_other_daemon: 0
Feb 17 11:44:44 desktop-noble gnome-keyring-d[1884]: couldn't access control 
socket: /run/user/124/keyring/control: No such file or directory
Feb 17 11:44:44 desktop-noble /usr/libexec/gdm-wayland-session[1884]: 
discover_other_daemon: 0
Feb 17 11:44:44 desktop-noble /usr/libexec/gdm-wayland-session[1290]: 
dbus-daemon[1290]: [session uid=124 pid=1290] Successfully activated service 
'org.freedesktop.secrets'
Feb 17 11:44:45 desktop-noble systemd[1]: systemd-fsckd.service: Deactivated 
successfully.
Feb 17 11:44:48 desktop-noble systemd[1]: systemd-timedated.service: 
Deactivated successfully.
Feb 17 11:44:50 desktop-noble systemd-timesyncd[734]: Contacted time server 
185.125.190.58:123 (ntp.ubuntu.com).
Feb 17 11:44:50 desktop-noble systemd-timesyncd[734]: Initial clock 
synchronization to Mon 2025-02-17 11:44:51.128469 UTC.
Feb 17 11:44:54 desktop-noble systemd[1]: systemd-localed.service: Deactivated 
successfully.
Feb 17 11:44:54 desktop-noble systemd[1]: systemd-hostnamed.service: 
Deactivated successfully.
Feb 17 11:44:54 desktop-noble systemd[1]: fprintd.service: Deactivated 
successfully.



** Attachment added: "Screenshot from 2025-02-17 12-19-13.png"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2098016/+attachment/5858209/+files/Screenshot%20from%202025-02-17%2012-19-13.png

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2098016

Title:
  Ubuntu 24.04 WiFi from gdm3 login screen: cannot select new network

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2098016/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to