A bug with Gnome?

When Garuda was put on my laptop it was set to automatically log into the desktop when booting, and this it does.

If I then open [for example] a browser or the mail client the password required box appears. If I enter the correct password then everything subsequently works without issue. If, on the other hand, I click cancel a couple of times in the password box then it disappears and he browser / mail client or whatever opens, but when the software is used the password box will subsequently appear again.

As far as I am aware the password box shouldn't appear. Is this a bug with Gnome?

```text
System:
  Kernel: 6.0.6-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen root=UUID=e0aa6bf1-e32d-48b2-a659-01e4322f83f8
    rw [email protected] quiet quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0
    resume=UUID=31f5f81c-4fb3-4a39-893a-3e7c25a0feb6 loglevel=3
  Desktop: GNOME v: 43.0 tk: GTK v: 3.24.34 wm: gnome-shell dm: GDM v: 43.0 Distro: Garuda Linux
    base: Arch Linux
Machine:
  Type: Laptop System: ASUSTeK product: VivoBook_ASUSLaptop X513UA_M513UA v: 1.0
    serial: <superuser required>
  Mobo: ASUSTeK model: X513UA v: 1.0 serial: <superuser required> UEFI: American Megatrends LLC.
    v: X513UA.312 date: 04/26/2022
Battery:
  ID-1: BAT0 charge: 41.8 Wh (100.0%) condition: 41.8/42.1 Wh (99.5%) volts: 11.8 min: 11.8
    model: ASUSTeK ASUS Battery type: Li-ion serial: N/A status: not charging cycles: 11
CPU:
  Info: model: AMD Ryzen 5 5500U with Radeon Graphics bits: 64 type: MT MCP arch: Zen 2 gen: 3
    level: v3 note: check built: 2020-22 process: TSMC n7 (7nm) family: 0x17 (23)
    model-id: 0x68 (104) stepping: 1 microcode: 0x8608103
  Topology: cpus: 1x cores: 6 tpc: 2 threads: 12 smt: enabled cache: L1: 384 KiB desc: d-6x32
    KiB; i-6x32 KiB L2: 3 MiB desc: 6x512 KiB L3: 8 MiB desc: 2x4 MiB
  Speed (MHz): avg: 1399 high: 1400 min/max: 1400/4056 boost: enabled scaling:
    driver: acpi-cpufreq governor: powersave cores: 1: 1398 2: 1400 3: 1400 4: 1400 5: 1397 6: 1400
    7: 1397 8: 1400 9: 1400 10: 1400 11: 1400 12: 1400 bogomips: 50308
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  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 mitigation: untrained return thunk; SMT enabled with STIBP protection
  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: Retpolines, IBPB: conditional, STIBP: always-on, RSB filling,
    PBRSB-eIBRS: Not affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: AMD Lucienne vendor: ASUSTeK driver: amdgpu v: kernel arch: GCN-5.1 code: Vega-2
    process: TSMC n7 (7nm) built: 2018-21 pcie: gen: 3 speed: 8 GT/s lanes: 16 link-max: gen: 4
    speed: 16 GT/s ports: active: eDP-1 empty: HDMI-A-1 bus-ID: 03:00.0 chip-ID: 1002:164c
    class-ID: 0300 temp: 39.0 C
  Device-2: Quanta USB2.0 HD UVC WebCam type: USB driver: uvcvideo bus-ID: 3-3:3
    chip-ID: 0408:30d4 class-ID: 0e02 serial: <filter>
  Display: x11 server: X.Org v: 21.1.4 with: Xwayland v: 22.1.5 compositor: gnome-shell driver:
    X: loaded: amdgpu unloaded: modesetting,radeon alternate: fbdev,vesa dri: radeonsi gpu: amdgpu
    display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22") s-diag: 582mm (22.93")
  Monitor-1: eDP-1 mapped: eDP model: Samsung 0x4161 built: 2020 res: 1920x1080 hz: 60 dpi: 142
    gamma: 1.2 size: 344x194mm (13.54x7.64") diag: 395mm (15.5") ratio: 16:9 modes: max: 1920x1080
    min: 640x480
  Message: Unable to show GL data. Required tool glxinfo missing.
Audio:
  Device-1: AMD Renoir Radeon High Definition Audio driver: snd_hda_intel v: kernel pcie: gen: 3
    speed: 8 GT/s lanes: 16 link-max: gen: 4 speed: 16 GT/s bus-ID: 03:00.1 chip-ID: 1002:1637
    class-ID: 0403
  Device-2: AMD ACP/ACP3X/ACP6x Audio Coprocessor vendor: ASUSTeK driver: N/A
    alternate: snd_pci_acp3x, snd_rn_pci_acp3x, snd_pci_acp5x, snd_pci_acp6x, snd_acp_pci,
    snd_rpl_pci_acp6x, snd_sof_amd_renoir pcie: gen: 3 speed: 8 GT/s lanes: 16 link-max: gen: 4
    speed: 16 GT/s bus-ID: 03:00.5 chip-ID: 1022:15e2 class-ID: 0480
  Device-3: AMD Family 17h/19h HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel pcie:
    gen: 3 speed: 8 GT/s lanes: 16 link-max: gen: 4 speed: 16 GT/s bus-ID: 03:00.6
    chip-ID: 1022:15e3 class-ID: 0403
  Sound API: ALSA v: k6.0.6-zen1-1-zen running: yes
  Sound Server-1: PulseAudio v: 16.1 running: no
  Sound Server-2: PipeWire v: 0.3.59 running: yes
Network:
  Device-1: Intel Wi-Fi 6 AX210/AX211/AX411 160MHz driver: iwlwifi v: kernel pcie: gen: 2
    speed: 5 GT/s lanes: 1 bus-ID: 01:00.0 chip-ID: 8086:2725 class-ID: 0280
  IF: wlp1s0 state: down mac: <filter>
  Device-2: ZTE WCDMA MSM DEMO Mobile Boardband type: USB driver: cdc_ether,usb-storage
    bus-ID: 1-3:2 chip-ID: 19d2:1405 class-ID: 0806 serial: <filter>
  IF: enp3s0f3u3 state: up speed: 150 Mbps duplex: half mac: <filter>
Bluetooth:
  Device-1: Intel AX210 Bluetooth type: USB driver: btusb v: 0.8 bus-ID: 3-2:2 chip-ID: 8087:0032
    class-ID: e001
  Report: bt-adapter ID: hci0 rfk-id: 2 state: up address: <filter>
Drives:
  Local Storage: total: 476.94 GiB used: 9.11 GiB (1.9%)
  SMART Message: Required tool smartctl not installed. Check --recommends
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: MZVLQ512HALU-00000 size: 476.94 GiB
    block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter>
    rev: FXV7101Q temp: 30.9 C scheme: GPT
Partition:
  ID-1: / raw-size: 146.49 GiB size: 146.49 GiB (100.00%) used: 8.16 GiB (5.6%) fs: btrfs
    dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-2: /boot/efi raw-size: 1024 MiB size: 1022 MiB (99.80%) used: 608 KiB (0.1%) fs: vfat
    dev: /dev/nvme0n1p1 maj-min: 259:1
  ID-3: /home raw-size: 321.45 GiB size: 321.45 GiB (100.00%) used: 972.7 MiB (0.3%) fs: btrfs
    dev: /dev/nvme0n1p4 maj-min: 259:4
  ID-4: /var/log raw-size: 146.49 GiB size: 146.49 GiB (100.00%) used: 8.16 GiB (5.6%) fs: btrfs
    dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-5: /var/tmp raw-size: 146.49 GiB size: 146.49 GiB (100.00%) used: 8.16 GiB (5.6%) fs: btrfs
    dev: /dev/nvme0n1p2 maj-min: 259:2
Swap:
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: zram size: 7.15 GiB used: 0 KiB (0.0%) priority: 100 dev: /dev/zram0
  ID-2: swap-2 type: partition size: 8 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/nvme0n1p3
    maj-min: 259:3
Sensors:
  System Temperatures: cpu: 43.0 C mobo: N/A gpu: amdgpu temp: 39.0 C
  Fan Speeds (RPM): cpu: 0
Info:
  Processes: 376 Uptime: 2h 41m wakeups: 2 Memory: 7.15 GiB used: 3.66 GiB (51.1%) Init: systemd
  v: 251 default: graphical tool: systemctl Compilers: gcc: 12.2.0 Packages: pm: pacman pkgs: 1184
  libs: 328 tools: pamac,paru Client: shell wrapper v: 5.1.16-release inxi: 3.3.22
Garuda (2.6.9-1):
  System install date:     
  Last full system update: 2022-11-04
  Is partially upgraded:   No
  Relevant software:       NetworkManager
  Windows dual boot:       No/Undetected
  Snapshots:               Snapper
  Failed units:            
```

No, but installing gnome-keyring if it is not already present may help.

The 'cancellation' bug does sound like one. Have you checked for bug reports on that?

1 Like

I've had a look and the Gnome keyring is installed.

I have no idea where to look for bug reports.

I general starting point: https://bugs.archlinux.org/

1 Like

Not a bug...a feature. :wink:

The default behavior of Gnome keyring is to become unlocked when you log in (with your username and password). If you skip that step (with autologin, for example), the keyring does not become unlocked.

When an application requests verification that the keyring is unlocked (typically this would be an application where you log in with a profile, like a browser or mail client like you mentioned), Gnome says "no, no one unlocked the keyring--don't assume the session is secure". The application in turn insists the keyring be unlocked.

This is an intentional security feature; everything you have mentioned is working as intended.

If you would like to defeat this security feature so everything is automatically unlocked, the tried-and-true way to do that is to set a blank password for your Gnome keyring.

More here: GNOME/Keyring - ArchWiki

2 Likes

I'll leave everything as it is.

Many thanks for the explanation.

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.