GDM Freeze right after login

Hi all,

I’ve been out of country for over 6 Month and when I returned home I couldn’t login. When I left last year the system was on F36 up to date but I hadn’t yet upgraded to F37, so I thought let’s do some updates first… I logged in from SSH and ran:

  • sudo dnf upgrade --refresh
  • sudo dnf distro-sync --refresh

After the reboot my Sys is now like that:

─mircsicz@xw8200 ~  
╰─➤  sudo inxi -Fzxx               
System:
  Kernel: 6.2.15-100.fc36.x86_64 arch: x86_64 bits: 64 compiler: gcc v: 2.37-37.fc36
    Console: pty pts/0 DM: GDM Distro: Fedora release 36 (Thirty Six)
Machine:
  Type: Desktop Mobo: ASUSTeK model: PRIME X299-A v: Rev 1.xx serial: <filter>
    UEFI: American Megatrends v: 3701 date: 05/23/2022
Battery:
  Device-1: hidpp_battery_0 model: Logitech Wireless Touch Keyboard K400 Plus serial: <filter>
    charge: 50% (should be ignored) status: N/A
CPU:
  Info: 6-core model: Intel Core i7-7800X bits: 64 type: MT MCP arch: Skylake rev: 4 cache:
    L1: 384 KiB L2: 6 MiB L3: 8.2 MiB
  Speed (MHz): avg: 3308 high: 3500 min/max: 1200/4000 cores: 1: 1200 2: 3500 3: 3500 4: 3500
    5: 3500 6: 3500 7: 3500 8: 3500 9: 3500 10: 3500 11: 3500 12: 3500 bogomips: 83997
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: AMD Lexa PRO [Radeon 540/540X/550/550X / RX 540X/550/550X] vendor: Gigabyte
    driver: amdgpu v: kernel arch: GCN-4 pcie: speed: 2.5 GT/s lanes: 8 ports: active: DP-1
    empty: DVI-D-1,HDMI-A-1 bus-ID: c1:00.0 chip-ID: 1002:699f temp: 38.0 C
  Display: x11 server: X.org v: 1.20.14 with: Xwayland v: 22.1.9 compositor: gnome-shell driver:
    gpu: amdgpu note: X driver n/a tty: 197x84
  Monitor-1: DP-1 model: Sun Microsystems 0x058f res: 1920x1200 dpi: 96 diag: 602mm (23.7")
  API: OpenGL Message: GL data unavailable in console for root.
Audio:
  Device-1: Intel 200 Series PCH HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel
    bus-ID: 00:1f.3 chip-ID: 8086:a2f0
  Device-2: AMD Baffin HDMI/DP Audio [Radeon RX 550 640SP / 560/560X] vendor: Gigabyte
    driver: snd_hda_intel v: kernel pcie: speed: 2.5 GT/s lanes: 8 bus-ID: c1:00.1
    chip-ID: 1002:aae0
  API: ALSA v: k6.2.15-100.fc36.x86_64 status: kernel-api
  Server-1: PipeWire v: 0.3.70 status: n/a (root, process) with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack
    type: plugin
Network:
  Device-1: Intel Ethernet I219-V vendor: ASUSTeK driver: e1000e v: kernel port: N/A
    bus-ID: 00:1f.6 chip-ID: 8086:15b8
  IF: eno1 state: up speed: 1000 Mbps duplex: full mac: <filter>
Bluetooth:
  Device-1: TP-Link UB500 Adapter type: USB driver: btusb v: 0.8 bus-ID: 1-9:2 chip-ID: 2357:0604
  Report: rfkill ID: hci0 rfk-id: 0 state: up address: see --recommends
Drives:
  Local Storage: total: 848.33 GiB used: 21.1 GiB (2.5%)
  ID-1: /dev/nvme0n1 vendor: Lenovo model: LENSE20256GMSP34MEAT2TA size: 238.47 GiB
    speed: 31.6 Gb/s lanes: 4 serial: <filter> temp: 41.9 C
  ID-2: /dev/sda vendor: Intel model: SSDSCKKW256G8 size: 238.47 GiB speed: 6.0 Gb/s
    serial: <filter> temp: 38 C
  ID-3: /dev/sdb vendor: Western Digital model: WD740GD-50FLC0 size: 69.25 GiB speed: 1.5 Gb/s
    serial: <filter> temp: 32 C
  ID-4: /dev/sdc vendor: Western Digital model: WD740GD-50FLC0 size: 69.25 GiB speed: 1.5 Gb/s
    serial: <filter> temp: 31 C
  ID-5: /dev/sdd vendor: Samsung model: SSD 850 EVO 250GB size: 232.89 GiB speed: 6.0 Gb/s
    serial: <filter> temp: 28 C
Partition:
  ID-1: / size: 236.89 GiB used: 20.81 GiB (8.8%) fs: btrfs dev: /dev/nvme0n1p3
  ID-2: /boot size: 973.4 MiB used: 251.9 MiB (25.9%) fs: ext4 dev: /dev/nvme0n1p2
  ID-3: /boot/efi size: 598.8 MiB used: 42.7 MiB (7.1%) fs: vfat dev: /dev/nvme0n1p1
  ID-4: /home size: 236.89 GiB used: 20.81 GiB (8.8%) fs: btrfs dev: /dev/nvme0n1p3
Swap:
  ID-1: swap-1 type: zram size: 8 GiB used: 0 KiB (0.0%) priority: 100 dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 24.0 C mobo: N/A gpu: amdgpu temp: 38.0 C
  Fan Speeds (RPM): N/A gpu: amdgpu fan: 1965
Info:
  Processes: 402 Uptime: 1d 22h 36m Memory: 15.29 GiB used: 2.07 GiB (13.5%) Init: systemd v: 250
  target: graphical (5) default: graphical Compilers: gcc: 12.2.1 Packages: pm: rpm pkgs: N/A
  note: see --rpm Shell: Zsh v: 5.8.1 running-in: pty pts/0 inxi: 3.3.26

And still I can’t login from gdm so I checked journalctl…

Jun 08 11:53:33 xw8200 gdm-password][12895]: gkr-pam: unable to locate daemon control file
Jun 08 11:53:33 xw8200 gdm-password][12895]: gkr-pam: stashed password to try later in open session
Jun 11 11:05:57 xw8200 gdm[1155]: Gdm: GdmDisplay: Session never registered, failing
Jun 11 11:05:57 xw8200 systemd[1]: Stopping gdm.service - GNOME Display Manager…
░░ Subject: A stop job for unit gdm.service has begun execution
░░ Defined-By: systemd
░░ Support: systemd-devel Info Page
░░
░░ A stop job for unit gdm.service has begun execution.
░░
░░ The job identifier is 20386.
Jun 11 11:05:57 xw8200 gdm[1155]: Gdm: Failed to list cached users: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not activate remote peer: activation request failed: a concurrent d>
Jun 11 11:05:57 xw8200 systemd[1]: gdm.service: Main process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: systemd-devel Info Page
░░
░░ An ExecStart= process belonging to unit gdm.service has exited.
░░
░░ The process’ exit code is ‘exited’ and its exit status is 1.
Jun 11 11:05:57 xw8200 systemd[1]: gdm.service: Failed with result ‘exit-code’.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: systemd-devel Info Page
░░
░░ The unit gdm.service has entered the ‘failed’ state with result ‘exit-code’.
Jun 11 11:05:57 xw8200 systemd[1]: Stopped gdm.service - GNOME Display Manager.
░░ Subject: A stop job for unit gdm.service has finished
░░ Defined-By: systemd
░░ Support: systemd-devel Info Page
░░
░░ A stop job for unit gdm.service has finished.
░░
░░ The job identifier is 20386 and the job result is done.
Jun 11 11:05:57 xw8200 systemd[1]: gdm.service: Triggering OnFailure= dependencies.
Jun 11 11:05:57 xw8200 systemd[1]: gdm.service: Failed to enqueue OnFailure= job, ignoring: Transaction for plymouth-quit.service/start is destructive (boot-efi.mount has ‘stop’ job queued, but 's>
– Boot b380404d11f747e6928ff5a1f6d5f1ce –
Jun 11 11:07:05 xw8200 systemd[1]: Starting gdm.service - GNOME Display Manager…
░░ Subject: A start job for unit gdm.service has begun execution
░░ Defined-By: systemd
░░ Support: systemd-devel Info Page
░░
░░ A start job for unit gdm.service has begun execution.
░░
░░ The job identifier is 354.
Jun 11 11:07:05 xw8200 systemd[1]: Started gdm.service - GNOME Display Manager.
░░ Subject: A start job for unit gdm.service has finished successfully
░░ Defined-By: systemd
░░ Support: systemd-devel Info Page
░░
░░ A start job for unit gdm.service has finished successfully.
░░
░░ The job identifier is 354.
Jun 11 11:07:14 xw8200 gdm-password][2612]: gkr-pam: unable to locate daemon control file
Jun 11 11:07:14 xw8200 gdm-password][2612]: gkr-pam: stashed password to try later in open session

So how/where do I get more logs about the issue?

I’ve now found a way to work around GDM by running:

dbus-run-session -- gnome-shell --display-server --wayland

which starts my session as expected.

I’m now running the F38 upgrade, let’s see what that leads to :face_with_raised_eyebrow:

3 Likes

Sadly the upgrade didn’t fix my issue…

Open for any hint on how to get this fixed :upside_down_face: