GDM fails to black screen after update?

Issues & Assistance GNOME
1

Garuda-inxi

╭─pekka@VIHAJUNA in ~ 
 ╰─λ garuda-inxi
System:
  Kernel: 6.0.10-zen2-1-zen arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
    root=UUID=d0eaf59a-d8bd-4ed6-a1a3-ad6a6ed2927d rw rootflags=subvol=@
    quiet
    cryptdevice=UUID=73f44a72-a7e1-4d0f-8abe-542272531d11:luks-73f44a72-a7e1-4d0f-8abe-542272531d11
    root=/dev/mapper/luks-73f44a72-a7e1-4d0f-8abe-542272531d11 quiet splash
    rd.udev.log_priority=3 vt.global_cursor_default=0
    resume=/dev/mapper/luks-4d4a3656-9348-4bd0-924f-b6367948f5ef loglevel=3
  Desktop: GNOME v: 43.1 tk: GTK v: 3.24.35 wm: gnome-shell dm: GDM v: 43.0
    Distro: Garuda Linux base: Arch Linux
Machine:
  Type: Laptop System: Dell product: XPS 13 9370 v: N/A
    serial: <superuser required> Chassis: type: 10 serial: <superuser required>
  Mobo: Dell model: 0XXY7V v: A00 serial: <superuser required> UEFI: Dell
    v: 1.19.0 date: 03/22/2022
Battery:
  ID-1: BAT0 charge: 37.9 Wh (89.8%) condition: 42.2/52.0 Wh (81.1%)
    volts: 8.1 min: 7.6 model: BYD DELL DGV24 type: Li-poly serial: <filter>
    status: discharging
CPU:
  Info: model: Intel Core i5-8350U bits: 64 type: MT MCP arch: Coffee Lake
    gen: core 8 level: v3 note: check built: 2017 process: Intel 14nm family: 6
    model-id: 0x8E (142) stepping: 0xA (10) microcode: 0xF0
  Topology: cpus: 1x cores: 4 tpc: 2 threads: 8 smt: enabled cache:
    L1: 256 KiB desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB desc: 4x256 KiB
    L3: 6 MiB desc: 1x6 MiB
  Speed (MHz): avg: 1525 high: 1900 min/max: 400/3600 scaling:
    driver: intel_pstate governor: powersave cores: 1: 900 2: 1900 3: 1900
    4: 900 5: 900 6: 1900 7: 1900 8: 1900 bogomips: 30399
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT
    vulnerable
  Type: mds mitigation: Clear CPU buffers; SMT vulnerable
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data mitigation: Clear CPU buffers; SMT vulnerable
  Type: retbleed mitigation: IBRS
  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: IBRS, IBPB: conditional, RSB filling,
    PBRSB-eIBRS: Not affected
  Type: srbds mitigation: Microcode
  Type: tsx_async_abort mitigation: TSX disabled
Graphics:
  Device-1: Intel UHD Graphics 620 vendor: Dell driver: i915 v: kernel
    arch: Gen-9.5 process: Intel 14nm built: 2016-20 ports: active: eDP-1
    empty: DP-1,DP-2 bus-ID: 00:02.0 chip-ID: 8086:5917 class-ID: 0300
  Device-2: Realtek Integrated_Webcam_HD type: USB driver: uvcvideo
    bus-ID: 1-5:3 chip-ID: 0bda:58f4 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: modesetting
    alternate: fbdev,intel,vesa dri: iris gpu: i915 display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x286mm (20.00x11.26")
    s-diag: 583mm (22.95")
  Monitor-1: eDP-1 model: Sharp 0x148b built: 2017 res: 1920x1080 hz: 60
    dpi: 166 gamma: 1.2 size: 294x165mm (11.57x6.5") diag: 337mm (13.3")
    ratio: 16:9 modes: 3840x2160
  API: OpenGL Message: Unable to show GL data. Required tool glxinfo
    missing.
Audio:
  Device-1: Intel Sunrise Point-LP HD Audio vendor: Dell driver: snd_hda_intel
    v: kernel alternate: snd_soc_skl,snd_soc_avs bus-ID: 00:1f.3
    chip-ID: 8086:9d71 class-ID: 0403
  Sound API: ALSA v: k6.0.10-zen2-1-zen running: yes
  Sound Server-1: PulseAudio v: 16.1 running: no
  Sound Server-2: PipeWire v: 0.3.61 running: yes
Network:
  Device-1: Intel Wireless 8265 / 8275 driver: iwlwifi v: kernel pcie: gen: 1
    speed: 2.5 GT/s lanes: 1 bus-ID: 02:00.0 chip-ID: 8086:24fd class-ID: 0280
  IF: wlp2s0 state: up mac: <filter>
  IF-ID-1: tailscale0 state: unknown speed: -1 duplex: full mac: N/A
Bluetooth:
  Device-1: Intel Bluetooth wireless interface type: USB driver: btusb v: 0.8
    bus-ID: 1-7:4 chip-ID: 8087:0a2b class-ID: e001
  Report: bt-adapter ID: hci0 rfk-id: 0 state: up address: <filter>
Drives:
  Local Storage: total: 931.51 GiB used: 360.66 GiB (38.7%)
  SMART Message: Required tool smartctl not installed. Check --recommends
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Kingston model: SA2000M81000G
    size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
    lanes: 4 type: SSD serial: <filter> rev: S5Z44106 temp: 33.9 C scheme: GPT
Partition:
  ID-1: / raw-size: 914.35 GiB size: 914.35 GiB (100.00%)
    used: 360.66 GiB (39.4%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0
    mapped: luks-73f44a72-a7e1-4d0f-8abe-542272531d11
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
    used: 752 KiB (0.2%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
  ID-3: /home raw-size: 914.35 GiB size: 914.35 GiB (100.00%)
    used: 360.66 GiB (39.4%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0
    mapped: luks-73f44a72-a7e1-4d0f-8abe-542272531d11
  ID-4: /var/log raw-size: 914.35 GiB size: 914.35 GiB (100.00%)
    used: 360.66 GiB (39.4%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0
    mapped: luks-73f44a72-a7e1-4d0f-8abe-542272531d11
  ID-5: /var/tmp raw-size: 914.35 GiB size: 914.35 GiB (100.00%)
    used: 360.66 GiB (39.4%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0
    mapped: luks-73f44a72-a7e1-4d0f-8abe-542272531d11
Swap:
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: zram size: 15.33 GiB used: 0 KiB (0.0%) priority: 100
    dev: /dev/zram0
  ID-2: swap-2 type: partition size: 16.86 GiB used: 0 KiB (0.0%)
    priority: -2 dev: /dev/dm-1 maj-min: 254:1
    mapped: luks-4d4a3656-9348-4bd0-924f-b6367948f5ef
Sensors:
  System Temperatures: cpu: 41.0 C pch: 37.5 C mobo: 33.0 C sodimm: SODIMM C
  Fan Speeds (RPM): cpu: 0
Info:
  Processes: 304 Uptime: 5m wakeups: 210 Memory: 15.33 GiB
  used: 3.01 GiB (19.6%) Init: systemd v: 252 default: graphical
  tool: systemctl Compilers: gcc: 12.2.0 clang: 14.0.6 Packages: pm: pacman
  pkgs: 1700 libs: 388 tools: pamac,paru Shell: fish v: 3.5.1 running-in: gjs
  inxi: 3.3.23
Garuda (2.6.10-1):
  System install date:     2022-10-30
  Last full system update: 2022-12-03
  Is partially upgraded:   No
  Relevant software:       NetworkManager
  Windows dual boot:       No/Undetected
  Snapshots:               Snapper
  Failed units:

Journal errors

On boot, everything works normally (luks opens and the splash screen displays), but the login screen never appears. The screen just stays blank. I can drop to console with ctrl-alt-F2 and do startx, then the login screen appears. But if I let the screen lock itself, I can’t log back in.

I can restore a week-old snapshot and that works, but after doing garuda-update the problem returns.

I checked pacman.log:

╰─λ sudo cat /var/log/pacman.log | grep gdm
[2022-10-30T22:33:15+0200] [ALPM-SCRIPTLET] gdm 42.0+r11+g4a52f026-1
[2022-10-30T22:33:15+0200] [ALPM-SCRIPTLET] libgdm 42.0+r11+g4a52f026-1
[2022-10-30T22:34:34+0200] [ALPM-SCRIPTLET] gdm 42.0+r11+g4a52f026-1
[2022-10-30T22:34:34+0200] [ALPM-SCRIPTLET] libgdm 42.0+r11+g4a52f026-1
[2022-10-30T22:40:48+0200] [ALPM] upgraded libgdm (42.0+r11+g4a52f026-1 → 43.0-1)
[2022-10-30T22:41:07+0200] [ALPM] upgraded gdm (42.0+r11+g4a52f026-1 → 43.0-1)

and it seems like gdm was updated around the time the problem started to occur.

What can I do to fix this?

Thanks.

2

I'm not a Gnome user, so take this only as an idea...
I can see in the journal 3 plugins failing before gdm. Maybe you could try disabling them and update again?

2 Likes
3

@RampantPanda I am not a Gnome user, but I had a similar issue a few days ago. You could try to restore the snapshot right after the update that caused the issue. It sounds paradox, but that did the trick for me. My system booted without problems after doing this.

I just randomly spotted that I have the same entrys in the journal:

Dez 03 17:52:08 PowerTower bluetoothd[727]: src/plugin.c:plugin_init() Failed to init vcp plugin
Dez 03 17:52:08 PowerTower bluetoothd[727]: src/plugin.c:plugin_init() Failed to init mcp plugin
Dez 03 17:52:08 PowerTower bluetoothd[727]: src/plugin.c:plugin_init() Failed to init bap plugin

grafik
grafik1818×140 53.4 KB

It seems to be something with Bluetooth, but my Bluetooth works without any issues. Maybe there is a general issue with these plugins?

Sorry for throwing in this off-topic question. No need to take care about. I have no issues with that, as long as everything works fine. But perhaps someone of the Garuda Team may have a look at it. :slight_smile:

2 Likes
4

Ah you're right, I didn't notice it's just bluetooth stuff... Forget about it...
You see, when text formatting makes the difference. It's so much evident in that way.

5

Tried that, didn't help.
Thanks for trying though :+1:

6

Do you mind posting some logs from GDM and Xorg?

1 Like
7

Please give some more explanation about this. What, how, when happens…
We need logs. IIRC GDM Xorg logs are included in journal.

8

You could try freezing the GDM package version before updating. If you can boot properly after upating you know it was the GDM update that was the cause.

2 Likes
9

I can't log back in because I can't enter the password: the password field doesn't accept input.

After rebooting, ctrl-alt-f2 and startx, I get this:

sudo journalctl -u gdm -b
[sudo] password for pekka:         
joulu 03 20:27:57 VIHAJUNA systemd[1]: Starting GNOME Display Manager...
joulu 03 20:27:57 VIHAJUNA systemd[1]: Started GNOME Display Manager.
joulu 03 20:27:58 VIHAJUNA gdm[626]: Gdm: GdmDisplay: Session never registered, failing
joulu 03 20:27:58 VIHAJUNA gdm[626]: Gdm: Child process -688 was already dead.
joulu 03 20:27:58 VIHAJUNA gdm[626]: Gdm: GdmDisplay: Session never registered, failing
joulu 03 20:27:58 VIHAJUNA gdm[626]: Gdm: Child process -688 was already dead.
joulu 03 20:27:58 VIHAJUNA gdm[626]: Gdm: GdmDisplay: Session never registered, failing
joulu 03 20:27:58 VIHAJUNA gdm[626]: Gdm: Child process -898 was already dead.
joulu 03 20:27:58 VIHAJUNA gdm[626]: Gdm: GdmDisplay: Session never registered, failing
joulu 03 20:27:58 VIHAJUNA gdm[626]: Gdm: Child process -898 was already dead.
joulu 03 20:27:58 VIHAJUNA gdm[626]: Gdm: GdmDisplay: Session never registered, failing
joulu 03 20:27:58 VIHAJUNA gdm[626]: Gdm: Child process -1126 was already dead.
joulu 03 20:27:58 VIHAJUNA gdm[626]: Gdm: GdmDisplay: Session never registered, failing
joulu 03 20:27:58 VIHAJUNA gdm[626]: Gdm: Child process -1126 was already dead.
joulu 03 20:27:58 VIHAJUNA gdm[626]: Gdm: GdmDisplay: Session never registered, failing
joulu 03 20:27:58 VIHAJUNA gdm[626]: Gdm: Child process -1217 was already dead.
joulu 03 20:27:58 VIHAJUNA gdm[626]: Gdm: GdmDisplay: Session never registered, failing
joulu 03 20:27:58 VIHAJUNA gdm[626]: Gdm: Child process -1217 was already dead.
joulu 03 20:27:58 VIHAJUNA gdm[626]: Gdm: GdmDisplay: Session never registered, failing
joulu 03 20:27:58 VIHAJUNA gdm[626]: Gdm: Child process -1237 was already dead.
joulu 03 20:27:58 VIHAJUNA gdm[626]: Gdm: GdmDisplay: Session never registered, failing
joulu 03 20:27:58 VIHAJUNA gdm[626]: Gdm: Child process -1237 was already dead.
joulu 03 20:27:58 VIHAJUNA gdm[626]: Gdm: GdmDisplay: Session never registered, failing
joulu 03 20:27:58 VIHAJUNA gdm[626]: Gdm: GdmLocalDisplayFactory: maximum number of X display failures reache>
joulu 03 20:27:58 VIHAJUNA gdm[626]: Gdm: Child process -1251 was already dead.

and this is the end of journalctl -b /usr/bin/Xorg:

joulu 03 20:27:58 VIHAJUNA /usr/lib/gdm-x-session[1253]: (II) modeset(0): Modeline "320x180"x118.6    8.88  320 344 360 400  180 181 184 187 doublescan +hsync -vsync (22.2 kHz d)
joulu 03 20:27:58 VIHAJUNA /usr/lib/gdm-x-session[1253]: (II) modeset(0): EDID for output DP-1
joulu 03 20:27:58 VIHAJUNA /usr/lib/gdm-x-session[1253]: (II) modeset(0): EDID for output DP-2
joulu 03 20:27:58 VIHAJUNA /usr/lib/gdm-x-session[1253]: (II) modeset(0): Output eDP-1 connected
joulu 03 20:27:58 VIHAJUNA /usr/lib/gdm-x-session[1253]: (II) modeset(0): Output DP-1 disconnected
joulu 03 20:27:58 VIHAJUNA /usr/lib/gdm-x-session[1253]: (II) modeset(0): Output DP-2 disconnected
joulu 03 20:27:58 VIHAJUNA /usr/lib/gdm-x-session[1253]: (II) modeset(0): Using exact sizes for initial modes
joulu 03 20:27:58 VIHAJUNA /usr/lib/gdm-x-session[1253]: (II) modeset(0): Output eDP-1 using initial mode 3840x2160 +0+0
joulu 03 20:27:58 VIHAJUNA /usr/lib/gdm-x-session[1253]: (==) modeset(0): Using gamma correction (1.0, 1.0, 1.0)
joulu 03 20:27:58 VIHAJUNA /usr/lib/gdm-x-session[1253]: (==) modeset(0): DPI set to (96, 96)
joulu 03 20:27:58 VIHAJUNA /usr/lib/gdm-x-session[1253]: (II) Loading sub module "fb"
joulu 03 20:27:58 VIHAJUNA /usr/lib/gdm-x-session[1253]: (II) LoadModule: "fb"
joulu 03 20:27:58 VIHAJUNA /usr/lib/gdm-x-session[1253]: (II) Module "fb" already built-in
joulu 03 20:27:58 VIHAJUNA /usr/lib/gdm-x-session[1253]: (EE) modeset(0): drmSetMaster failed: Permission denied
joulu 03 20:27:58 VIHAJUNA /usr/lib/gdm-x-session[1253]: (EE)
joulu 03 20:27:58 VIHAJUNA /usr/lib/gdm-x-session[1253]: Fatal server error:
joulu 03 20:27:58 VIHAJUNA /usr/lib/gdm-x-session[1253]: (EE) AddScreen/ScreenInit failed for driver 0
joulu 03 20:27:58 VIHAJUNA /usr/lib/gdm-x-session[1253]: (EE)
joulu 03 20:27:58 VIHAJUNA /usr/lib/gdm-x-session[1253]: (EE)
joulu 03 20:27:58 VIHAJUNA /usr/lib/gdm-x-session[1253]: Please consult the The X.Org Foundation support
joulu 03 20:27:58 VIHAJUNA /usr/lib/gdm-x-session[1253]:          at http://wiki.x.org
joulu 03 20:27:58 VIHAJUNA /usr/lib/gdm-x-session[1253]:  for help.
joulu 03 20:27:58 VIHAJUNA /usr/lib/gdm-x-session[1253]: (EE) Please also check the log file at "/var/lib/gdm/.local/share/xorg/Xorg.0.log" for additional information.
joulu 03 20:27:58 VIHAJUNA /usr/lib/gdm-x-session[1253]: (EE)
joulu 03 20:27:58 VIHAJUNA /usr/lib/gdm-x-session[1253]: (EE) Server terminated with error (1). Closing log file.

The entire Xorg log file is here.

10

I tried to add gdm and gdmlib to pacman ignore list earlier, but couldn't reboot after garuda-update even with those kept unupdated. So maybe that isn't the problem after all.

11

Recently there were troubles with plymouth-git.
Could you please try booting removing splash from the kernel boot parameters?
Even just once, pressing button E on the grub line.

2 Likes
12

Try adding i915 in MODULES section of mkinitcpio.conf. Rebuild images and reboot.