I have exactly the same problem described in this issue, but in the current Gnome edition.
I don‘t know since when the issue exists, since at home the WiFi connection works, and in trains I get to the captive portal, but when I select a new network in the Gnome settings, there is a hint that authentication is required, but now password prompt pops up, and I am pretty lost because I needed to do something fory my work which requires Internet.
Do you have an idea what’s wrong and how I can fix it? Is the at least a quick workaround with using CLI tools?
you should create different connections for home-use and outside that you can switch. there are settings like wpa-personal and wpa-enterprise wpa-2 , wpa-3 and so forth… .without knowing what connections you need in your country is almost impossible to give more detailed information.
sounds a little bit pitty, but if you ask a network-service-shop local in your country and pay them ~1 hour of work to give you detailed advice and will set up your mobile laptop (with you) to your needs might be a good idea that will pay off the money very soon.
Thanks, with nmtui I could connect to the Wifi network. But getting the Gnome system setting work properly again would be better of course. I have just posted the output of `inxi -Fazy’ here.
@megavolt So here is the output of the Gnome Control Center, a bit shortened, I deleted the repetitive lines with getting security from and DEBUG: key management is wpa-psk:
$ G_MESSAGES_DEBUG=all gnome-control-center ✔ 6s
00:05:38.3649 cc-object-storage[119640]: DEBUG: Initializing object storage
00:05:38.3654 GLib-GIO[119640]: DEBUG: Using cross-namespace EXTERNAL authentication (this will deadlock if server is GDBus < 2.73.3)
00:05:38.4251 Gtk[119640]: DEBUG: Connecting to session manager
00:05:38.4273 GLib-GIO[119640]: DEBUG: _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for ‘gio-vfs’
00:05:38.4669 GLib-GIO[119640]: DEBUG: _g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for ‘gsettings-backend’
00:05:38.4669 dconf[119640]: DEBUG: watch_fast: "/org/gnome/control-center/" (establishing: 0, active: 0)
00:05:38.4674 dconf[119640]: DEBUG: watch_established: "/org/gnome/control-center/" (establishing: 1)
00:05:38.4705 GLib-GIO[119640]: DEBUG: Using cross-namespace EXTERNAL authentication (this will deadlock if server is GDBus < 2.73.3)
00:05:38.5759 cc-firmware-security-panel[119640]: DEBUG: Firmware Security panel visible: yes as chassis was laptop
00:05:38.5760 cc-network-panel[119640]: DEBUG: Monitoring NetworkManager for Wi-Fi devices
00:05:38.5941 cc-object-storage[119640]: DEBUG: Adding object NMClient (CcObjectStorage::nm-client → 0x55c7624ce060) to the storage
00:05:38.5941 cc-network-panel[119640]: DEBUG: Wi-Fi panel visible: yes
00:05:38.6015 cc-wacom-panel[119640]: DEBUG: Wacom panel visible: no
00:05:38.6028 cc-object-storage[119640]: DEBUG: Adding object MMManager (CcObjectStorage::mm-manager → 0x55c7621aff30) to the storage
00:05:38.6028 cc-wwan-panel[119640]: DEBUG: Monitoring ModemManager for WWAN devices
00:05:38.6028 cc-wwan-panel[119640]: DEBUG: WWAN panel visible: no
00:05:38.6062 dconf[119640]: DEBUG: change_fast
00:05:38.6101 cc-network-panel[119640]: DEBUG: getting security from 0x55c7625705a0
00:05:38.6101 cc-network-panel[119640]: DEBUG: key management is wpa-psk
00:05:38.6103 cc-network-panel[119640]: DEBUG: getting security from 0x55c7625705a0
00:05:38.6103 cc-network-panel[119640]: DEBUG: key management is wpa-psk
[…]
00:05:38.6317 cc-network-panel[119640]: DEBUG: key management is wpa-psk
00:05:38.6318 cc-network-panel[119640]: DEBUG: getting security from 0x55c762421f80
00:05:38.6318 cc-network-panel[119640]: DEBUG: key management is wpa-psk
00:05:38.6372 cc-network-panel[119640]: DEBUG: Periodic Wi-Fi scan requested
00:05:38.6380 cc-object-storage[119640]: DEBUG: Asynchronously creating D-Bus proxy for CcObjectStorage::dbus-proxy(org.gnome.SettingsDaemon.Rfkill,/org/gnome/SettingsDaemon/Rfkill,org.gnome.SettingsDaemon.Rfkill)
00:05:38.6386 cc-window[119640]: DEBUG: Time to open panel 'WLAN': 0,032399s
00:05:38.7119 cc-object-storage[119640]: DEBUG: Finished creating D-Bus proxy for CcObjectStorage::dbus-proxy(org.gnome.SettingsDaemon.Rfkill,/org/gnome/SettingsDaemon/Rfkill,org.gnome.SettingsDaemon.Rfkill)
00:05:38.7119 cc-object-storage[119640]: DEBUG: Adding object GDBusProxy (CcObjectStorage::dbus-proxy(org.gnome.SettingsDaemon.Rfkill,/org/gnome/SettingsDaemon/Rfkill,org.gnome.SettingsDaemon.Rfkill) → 0x7f082000d7b0) to the storage
00:05:38.7128 cc-diagnostics-panel[119640]: DEBUG: ABRT vanished
00:05:38.7148 cc-thunderbolt-panel[119640]: DEBUG: Thunderbolt panel visible: yes
00:05:41.1726 cc-network-panel[119640]: DEBUG: getting security from 0x55c7625705a0
00:05:41.1727 cc-network-panel[119640]: DEBUG: key management is wpa-psk
00:05:41.1731 cc-network-panel[119640]: DEBUG: getting security from 0x55c7625705a0
[…]
00:05:41.1797 cc-network-panel[119640]: DEBUG: getting security from 0x55c762421f80
00:05:41.1797 cc-network-panel[119640]: DEBUG: key management is wpa-psk
00:05:44.6008 cc-network-panel[119640]: DEBUG: try to connect to WIFI network DIRECT-gd-FireTV_1562 [/org/freedesktop/NetworkManager/AccessPoint/1019]
00:05:44.6121 cc-network-panel[119640]: DEBUG: no existing connection found for DIRECT-gd-FireTV_1562, creating and activating one
00:05:44.6308 cc-network-panel[119640]: DEBUG: getting security from 0x55c7625705a0
00:05:44.6309 cc-network-panel[119640]: DEBUG: key management is wpa-psk
00:05:44.6389 cc-network-panel[119640]: DEBUG: getting security from 0x55c7625705a0
00:05:44.6390 cc-network-panel[119640]: DEBUG: key management is wpa-psk
[…]
00:05:45.0845 cc-network-panel[119640]: DEBUG: Simulating add/remove for active AP change
00:05:45.0845 cc-network-panel[119640]: DEBUG: getting security from 0x55c764e0ac90
00:05:45.0846 cc-network-panel[119640]: DEBUG: key management is wpa-psk
00:05:48.6411 cc-network-panel[119640]: DEBUG: getting security from 0x55c7625705a0
00:05:48.6411 cc-network-panel[119640]: DEBUG: key management is wpa-psk
00:05:48.6745 cc-network-panel[119640]: DEBUG: Simulating add/remove for active AP change
00:05:48.6745 cc-network-panel[119640]: DEBUG: getting security from 0x55c7625705a0
00:05:48.6746 cc-network-panel[119640]: DEBUG: key management is wpa-psk
[…]
00:05:48.8991 cc-network-panel[119640]: DEBUG: getting security from 0x55c762743230
00:05:48.8991 cc-network-panel[119640]: DEBUG: key management is wpa-psk
00:05:48.9002 cc-network-panel[119640]: DEBUG: getting security from 0x55c762743230
00:05:48.9002 cc-network-panel[119640]: DEBUG: key management is wpa-psk
00:05:54.2485 cc-network-panel[119640]: DEBUG: Periodic Wi-Fi scan requested
00:05:54.8751 dconf[119640]: DEBUG: change_fast
00:05:54.8871 cc-network-panel[119640]: DEBUG: Disabling periodic Wi-Fi scan
00:05:54.8897 dconf[119640]: DEBUG: unwatch_fast: "/org/gnome/control-center/" (active: 1, establishing: 0)
00:05:54.8899 dconf[119640]: DEBUG: sync
00:05:54.8900 cc-object-storage[119640]: DEBUG: Destroying cached objects
The moment I clicked on a new network (i.e. never connected before) was at the timestamp 00:05:44.6008. Like always no password dialogue popped up.
If the password is saved in the Gnome keyring, it must at least somehow work, because the system connects to my home WiFi network without any problem. That’s why I was not suspecting any malfunction until I travelled and wanted to connect to new WiFi networks. But I also noted that calling my password manager pass, which is based on GPG encrypting, takes about half a minute until a password prompt for my private GPG key pops up. But after entering the password it works: the saved password is being shown.
And here’s another output
systemctl --user --no-pager status gnome-keyring-daemon.service ✔ 57s
● gnome-keyring-daemon.service - GNOME Keyring daemon
Loaded: loaded (/usr/lib/systemd/user/gnome-keyring-daemon.service; disabled; preset: enabled)
Active: active (running) since Sun 2023-09-10 21:04:26 CEST; 1 day 3h ago
TriggeredBy: ● gnome-keyring-daemon.socket
Main PID: 1963 (gnome-keyring-d)
Tasks: 5 (limit: 18827)
Memory: 1008.0K
CPU: 35ms
CGroup: /user.slice/user-1000.slice/user@1000.service/app.slice/gnome-keyring-daemon.service
└─1963 /usr/bin/gnome-keyring-daemon --foreground --components=pkcs11,secrets --control-directory=/run/user/1000/keyring
Sep 12 00:01:47 gram gnome-keyring-daemon[1963]: The Secret Service was already initialized
Sep 12 00:01:47 gram gnome-keyring-d[1963]: The Secret Service was already initialized
Sep 12 00:03:47 gram gnome-keyring-daemon[1963]: The Secret Service was already initialized
Sep 12 00:03:47 gram gnome-keyring-d[1963]: The Secret Service was already initialized
Sep 12 00:05:47 gram gnome-keyring-daemon[1963]: The Secret Service was already initialized
Sep 12 00:05:47 gram gnome-keyring-d[1963]: The Secret Service was already initialized
Sep 12 00:07:47 gram gnome-keyring-daemon[1963]: The Secret Service was already initialized
Sep 12 00:07:47 gram gnome-keyring-d[1963]: The Secret Service was already initialized
Sep 12 00:15:55 gram gnome-keyring-daemon[1963]: The Secret Service was already initialized
Sep 12 00:15:55 gram gnome-keyring-d[1963]: The Secret Service was already initialized
seahorse shows a lot of gpg keys and some ssh keys. I can’t see any problems, but I also don’t know which key is used for the network passwords.
@Olli Thanks, but I don’t really get your point. I just want to add normal WiFi connections in the 2.5 GHz and 5 GHz band which is pretty much the same in all countries I have been travelling so far. I live in ermany and lst weekend I was in Belgium.
And I don’t know why and how I should use different WPA settings. And why should I hire a “network-service-shop local”, whatever that is for just connecting to standard WiFi networks.
Well, most likely there is already a password saved with that SSID, but wrong? Therefore it doesn’t prompt for a password? Just puzzling.
I see it is create/activates it… but you don’t see that refuses to login. TRy again and watch this log meanwhile:
journalctl --unit=NetworkManager.service --follow
Anyway… there should be a way to delete the wifi password in seahorse, but I don’t have laptop with Gnome installed. So sorry, cannot reproduce it. I always use nmtui.
Check also this path:
sudo ls /etc/NetworkManager/system-connections
Usually there are the plain connections (and passwords) saved with nmtui.
Or try to use nm-connection-editor to correct the password?