GNOME session sometimes fails to load after login unless wifi is disabled from login screen

I am on NixOS 24.05pre574351.612f97239e2c and often GNOME would fail to boot (without logging any seemingly related error) when wifi is on. That is, the cursor can still be moved but the entire screen remains grey.

The only workaround I could find was to disable wifi from the login screen. When this is done the GNOME session never fails to load.

Any idea why this is so? Or how to troubleshoot further? Any hint would be greatly appreciated – I am not super knowledge in GNOME things.

Logs for good measure:

journalctl -b -1 -r -p 0..3
=>
jan 25 10:49:53 nixos gdm-password][1862]: gkr-pam: unable to locate daemon control file
jan 25 10:49:51 nixos bluetoothd[977]: Failed to add UUID: Failed (0x03)
jan 25 10:49:51 nixos bluetoothd[977]: Failed to add UUID: Failed (0x03)
jan 25 10:49:51 nixos bluetoothd[977]: Failed to add UUID: Failed (0x03)
jan 25 10:49:51 nixos bluetoothd[977]: Failed to add UUID: Failed (0x03)
jan 25 10:49:48 nixos .libvirtd-wrapp[1363]: internal error: Failed to autostart storage pool 'pool': cannot open directory '/run/media/hades/nixos-home': No such file or directory
jan 25 10:49:48 nixos .libvirtd-wrapp[1363]: cannot open directory '/run/media/hades/nixos-home': No such file or directory
jan 25 10:49:48 nixos .libvirtd-wrapp[1363]: internal error: Failed to autostart storage pool 'pool-external': cannot open directory '/run/media/hades/vms': No such file or directory
jan 25 10:49:48 nixos .libvirtd-wrapp[1363]: cannot open directory '/run/media/hades/vms': No such file or directory
jan 25 10:49:48 nixos .libvirtd-wrapp[1363]: internal error: Failed to autostart storage pool 'pool-2': cannot open directory '/run/media/hades/nixos-home/vms': No such file or directory
jan 25 10:49:48 nixos .libvirtd-wrapp[1363]: cannot open directory '/run/media/hades/nixos-home/vms': No such file or directory
jan 25 10:49:48 nixos bluetoothd[977]: Failed to add UUID: Failed (0x03)
jan 25 10:49:48 nixos bluetoothd[977]: Failed to add UUID: Failed (0x03)
jan 25 10:49:48 nixos bluetoothd[977]: Failed to add UUID: Failed (0x03)
jan 25 10:49:48 nixos bluetoothd[977]: Failed to set mode: Failed (0x03)
jan 25 10:49:48 nixos bluetoothd[977]: Failed to add UUID: Failed (0x03)
jan 25 10:49:48 nixos bluetoothd[977]: Failed to add UUID: Failed (0x03)
jan 25 10:49:48 nixos bluetoothd[977]: Failed to add UUID: Failed (0x03)
jan 25 10:49:48 nixos bluetoothd[977]: Failed to clear UUIDs: Failed (0x03)
jan 25 10:49:48 nixos bluetoothd[977]: src/adapter.c:reset_adv_monitors_complete() Failed to reset Adv Monitors: Failed (0x03)
jan 25 10:49:46 nixos kernel: tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does not cover the entire command/response buffer. [mem 0xfed40000-0xfed4087f flags 0x200] vs fed40080 f80
jan 25 10:49:46 nixos kernel: tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does not cover the entire command/response buffer. [mem 0xfed40000-0xfed4087f flags 0x200] vs fed40080 f80
jan 25 10:49:45 nixos kernel: x86/cpu: SGX disabled by BIOS.
jan 25 10:49:45 nixos kernel: DMAR: [Firmware Bug]: No firmware reserved region can cover this RMRR [0x0000000078800000-0x000000007affffff], contact BIOS vendor for fixes

Did you ever figure out what was wrong? I am having the exact same issue. Didn’t know it was related to WiFI so that helps a ton.

I didn’t figure that out, the problem disappeared a few updates ago.

I still occasionally suffer from WiFi issues, always fixed by manually reconnecting to the WiFi network from GNOME. I wish I knew more.

That said I suspect a faulty interaction with tlp, which I also happen to use. So I will be testing with: services.tlp.setting.DEVICES_TO_DISABLE_ON_STARTUP = "bluetooth"; from now on.

updated: I can confirm that this solved all my issues!