No password prompt on WiFi network selection

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?

Not without knowing what hardware you’re on. Please post the output of
inxi -Fazy

No idea. More information needed.

Try nmtui on the terminal.

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.

Since I could not connect to the Internet with my laptop, I couldn’t post the output of inxi -Fazy, but now that I’m back home I can:

    ~  inxi -Fazy                                                                                                                          ✔    jens 
System:
  Kernel: 6.2.16-2-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 13.1.1
    clocksource: tsc available: acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.2-x86_64
    root=UUID=c7140523-6434-4e7f-a044-4d22715d33b5 rw
    cryptdevice=UUID=dccc69d8-69ae-4728-8806-1a950897c316:luks-dccc69d8-69ae-4728-8806-1a950897c316
    root=/dev/mapper/luks-dccc69d8-69ae-4728-8806-1a950897c316 splash
    apparmor=1 security=apparmor
    resume=/dev/mapper/luks-b1fc9740-a686-47a4-b370-b07d695b9794
    udev.log_priority=3
  Desktop: GNOME v: 44.4 tk: GTK v: 3.24.38 wm: gnome-shell dm: startx
    Distro: Manjaro Linux base: Arch Linux
Machine:
  Type: Laptop System: LG product: TigerLake Platform v: 0.1
    serial: <superuser required> Chassis: type: 10 v: 0.1
    serial: <superuser required>
  Mobo: LG model: 17Z90P v: FAB1 serial: <superuser required> UEFI: Phoenix
    v: T2ZF0320 X64 date: 04/23/2021
Battery:
  ID-1: CMB0 charge: 69.8 Wh (98.9%) condition: 70.6/80.0 Wh (88.2%) volts: 8.6
    min: 7.7 model: LG LGC-LGC type: Li-ion serial: <filter> status: not charging
    cycles: 67
  Device-1: hidpp_battery_1 model: Logitech MX Master 3S serial: <filter>
    charge: 75% rechargeable: yes status: discharging
CPU:
  Info: model: 11th Gen Intel Core i7-1165G7 bits: 64 type: MT MCP
    arch: Tiger Lake gen: core 11 level: v4 note: check built: 2020
    process: Intel 10nm family: 6 model-id: 0x8C (140) stepping: 1
    microcode: 0xAC
  Topology: cpus: 1x cores: 4 tpc: 2 threads: 8 smt: enabled cache:
    L1: 320 KiB desc: d-4x48 KiB; i-4x32 KiB L2: 5 MiB desc: 4x1.2 MiB L3: 12 MiB
    desc: 1x12 MiB
  Speed (MHz): avg: 1825 high: 2800 min/max: 400/4700 scaling:
    driver: intel_pstate governor: powersave cores: 1: 1155 2: 2800 3: 2800
    4: 850 5: 612 6: 787 7: 2800 8: 2800 bogomips: 44864
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: retbleed status: Not affected
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
    prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
    sanitization
  Type: spectre_v2 mitigation: Enhanced IBRS, IBPB: conditional, RSB
    filling, PBRSB-eIBRS: SW sequence
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: Intel TigerLake-LP GT2 [Iris Xe Graphics] vendor: LG driver: i915
    v: kernel arch: Gen-12.1 process: Intel 10nm built: 2020-21 ports:
    active: HDMI-A-1 off: eDP-1 empty: DP-1,DP-2 bus-ID: 00:02.0
    chip-ID: 8086:9a49 class-ID: 0300
  Device-2: Realtek LG Camera driver: uvcvideo type: USB rev: 2.0
    speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-2:2 chip-ID: 0bda:5641
    class-ID: 0e02 serial: <filter>
  Display: server: X.org v: 1.21.1.8 with: Xwayland v: 23.2.0
    compositor: gnome-shell driver: X: loaded: modesetting alternate: fbdev,vesa
    dri: iris gpu: i915 display-ID: :0 screens: 1
  Screen-1: 0 s-res: 3840x2160 s-size: <missing: xdpyinfo>
  Monitor-1: HDMI-A-1 mapped: HDMI-1 pos: primary
    model: LG (GoldStar) Ultra HD serial: <filter> built: 2017 res: 3840x2160
    hz: 30 dpi: 163 gamma: 1.2 size: 600x340mm (23.62x13.39")
    diag: 690mm (27.2") ratio: 16:9 modes: max: 3840x2160 min: 640x480
  Monitor-2: eDP-1 note: disabled model: LG Display 0x0695 built: 2020
    res: 3840x2160 dpi: 178 gamma: 1.2 size: 366x229mm (14.41x9.02")
    diag: 432mm (17") ratio: 16:10 modes: 2560x1600
  API: OpenGL Message: Unable to show GL data. Required tool glxinfo missing.
Audio:
  Device-1: Intel Tiger Lake-LP Smart Sound Audio vendor: LG
    driver: sof-audio-pci-intel-tgl
    alternate: snd_hda_intel,snd_sof_pci_intel_tgl bus-ID: 00:1f.3
    chip-ID: 8086:a0c8 class-ID: 0401
  API: ALSA v: k6.2.16-2-MANJARO status: kernel-api with: aoss
    type: oss-emulator tools: alsactl,alsamixer,amixer
  Server-1: JACK v: 1.9.22 status: off tools: N/A
  Server-2: PipeWire v: 0.3.78 status: off with: pipewire-media-session
    status: active tools: pw-cli
  Server-3: PulseAudio v: 16.1 status: active with: 1: pulseaudio-alsa
    type: plugin 2: pulseaudio-jack type: module tools: pacat,pactl
Network:
  Device-1: Intel Wi-Fi 6 AX201 driver: iwlwifi v: kernel bus-ID: 00:14.3
    chip-ID: 8086:a0f0 class-ID: 0280
  IF: wlp0s20f3 state: up mac: <filter>
  IF-ID-1: docker0 state: down mac: <filter>
Bluetooth:
  Device-1: Intel AX201 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
    speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 3-10:4 chip-ID: 8087:0026
    class-ID: e001
  Report: hciconfig ID: hci0 rfk-id: 1 state: up address: <filter> bt-v: 5.2
    lmp-v: 11 sub-v: 20ce hci-v: 11 rev: 20ce class-ID: 6c010c
  Info: acl-mtu: 1021:4 sco-mtu: 96:6 link-policy: rswitch sniff
    link-mode: peripheral accept service-classes: rendering, capturing, audio,
    telephony
Drives:
  Local Storage: total: 953.87 GiB used: 242.77 GiB (25.5%)
  SMART Message: Required tool smartctl not installed. Check --recommends
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: SK Hynix
    model: HFS001TD9TNG-L2A0A size: 953.87 GiB block-size: physical: 512 B
    logical: 512 B speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter>
    fw-rev: 80001C10 temp: 41.9 C scheme: GPT
Partition:
  ID-1: / raw-size: 936.67 GiB size: 936.67 GiB (100.00%)
    used: 242.77 GiB (25.9%) fs: f2fs dev: /dev/dm-0 maj-min: 254:0
    mapped: luks-dccc69d8-69ae-4728-8806-1a950897c316
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
    used: 440 KiB (0.1%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default) zswap: yes
    compressor: zstd max-pool: 20%
  ID-1: swap-1 type: partition size: 16.9 GiB used: 0 KiB (0.0%) priority: -2
    dev: /dev/dm-1 maj-min: 254:1
    mapped: luks-b1fc9740-a686-47a4-b370-b07d695b9794
Sensors:
  System Temperatures: cpu: 49.0 C mobo: N/A
  Fan Speeds (rpm): N/A
Info:
  Processes: 425 Uptime: 15h 31m wakeups: 21716 Memory: total: 16 GiB
  note: est. available: 15.35 GiB used: 7.6 GiB (49.5%) Init: systemd v: 253
  default: graphical tool: systemctl Compilers: gcc: 13.2.1 clang: 15.0.7
  Packages: 1730 pm: pacman pkgs: 1701 libs: 417 tools: gnome-software,pamac
  pm: flatpak pkgs: 17 pm: snap pkgs: 12 Shell: Zsh v: 5.9 running-in: python
  inxi: 3.3.29

It’s an LG gram 17" from 2022

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.

Alright, then provide the output of:

G_MESSAGES_DEBUG=all gnome-control-center

use it as usual: connect to network.

It is also possible that gnome-keyring is not working, since there is the Wifi-Password saved usually:

systemctl --user --no-pager status gnome-keyring-daemon.service

seahorse is a GUI for the keyring. Try to look there.

@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.

I really don’t get it.

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?