[SOLVED] Unable to launch any GUI (neither Wayland nor X11)

jacek_kotek · 2026-01-21 10:20:01

Since yesterday I am unable to launch any GUI, have tried SDDM and Hyprland (the two I have installed).

For reference, I have a Lenovo laptop with a i5-12500H (with integrated graphics, I use the i915 driver for it) and a Nvidia RTX3060 (I use the nvidia-open driver).

At the begginning I tought it was an X11 issue, since it sometimes crashed earlier, so I installed Ly and tried launching Hyprland through Ly, as well as from the tty. This still didnt work, Hyprland keeps core dumping.
This makes me think this is probably a graphics driver issue, but its weird that its unable to run on any of my 2 graphics cards (I tried disabling the nvidia graphics card from BIOS as well as to blacklist i915 driver in GRUB to force the computer to use only one of the graphic cards).

Here is my journalctl -b : https://0x0.st/PPru.log

Any help is very appreciated, I am forced back onto windows for now.

Last edited by jacek_kotek (2026-01-21 15:35:24)

seth · 2026-01-21 13:23:35

I am forced back onto windows for now.

3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.

Jan 21 11:11:12 koteczek systemd-coredump[5658]: Process 5640 (Hyprland) of user 1000 dumped core.
                                                 
                                                 Stack trace of thread 5640:
                                                 #0  0x00007ff5273a3eea n/a (ld-linux-x86-64.so.2 + 0x25eea)
                                                 #1  0x00007ff527386648 n/a (ld-linux-x86-64.so.2 + 0x8648)
                                                 #2  0x00007ff527387e19 n/a (ld-linux-x86-64.so.2 + 0x9e19)
                                                 #3  0x00007ff52738183d n/a (ld-linux-x86-64.so.2 + 0x383d)
                                                 #4  0x00007ff527380456 _dl_catch_exception (ld-linux-x86-64.so.2 + 0x2456)
                                                 #5  0x00007ff527381ca3 n/a (ld-linux-x86-64.so.2 + 0x3ca3)
                                                 #6  0x00007ff52738bc48 n/a (ld-linux-x86-64.so.2 + 0xdc48)
                                                 #7  0x00007ff527380456 _dl_catch_exception (ld-linux-x86-64.so.2 + 0x2456)
                                                 #8  0x00007ff52738b21c n/a (ld-linux-x86-64.so.2 + 0xd21c)
                                                 #9  0x00007ff527380456 _dl_catch_exception (ld-linux-x86-64.so.2 + 0x2456)
                                                 #10 0x00007ff52738b75a n/a (ld-linux-x86-64.so.2 + 0xd75a)
                                                 #11 0x00007ff526292cc4 n/a (libc.so.6 + 0x92cc4)
                                                 #12 0x00007ff527380456 _dl_catch_exception (ld-linux-x86-64.so.2 + 0x2456)
                                                 #13 0x00007ff5273805a9 n/a (ld-linux-x86-64.so.2 + 0x25a9)
                                                 #14 0x00007ff5262927b3 n/a (libc.so.6 + 0x927b3)
                                                 #15 0x00007ff526292d7b dlopen (libc.so.6 + 0x92d7b)
                                                 #16 0x00007ff526d30d33 n/a (libgbm.so.1 + 0x2d33)
                                                 #17 0x00007ff526d30176 n/a (libgbm.so.1 + 0x2176)
                                                 #18 0x00007ff526d30377 gbm_create_device (libgbm.so.1 + 0x2377)
                                                 #19 0x00007ff5272359a0 _ZN10Aquamarine13CGBMAllocatorC1EiN9Hyprutils6Memory12CWeakPointerINS_8CBackendEEE (libaquamarine.so.9 + 0x6f9a0)
                                                 #20 0x00007ff527235ca4 _ZN10Aquamarine13CGBMAllocator6createEiN9Hyprutils6Memory12CWeakPointerINS_8CBackendEEE (libaquamarine.so.9 + 0x6fca4)
                                                 #21 0x00007ff52723fb82 _ZN10Aquamarine8CBackend5startEv (libaquamarine.so.9 + 0x79b82)
                                                 #22 0x000056109377176c _ZN11CCompositor10initServerENSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEi (/usr/bin/Hyprland + 0x28076c)
                                                 #23 0x00005610936d3c2e main (/usr/bin/Hyprland + 0x1e2c2e)
                                                 #24 0x00007ff526227635 n/a (libc.so.6 + 0x27635)
                                                 #25 0x00007ff5262276e9 __libc_start_main (libc.so.6 + 0x276e9)
                                                 #26 0x0000561093734ca5 _start (/usr/bin/Hyprland + 0x243ca5)

sudo LC_ALL=C pacman -Qkk |& grep --line-buffered -v ', 0 altered files' | grep -v backup > /tmp/howbadisit.txt
cat /tmp/howbadisit.txt | curl -F 'file=@-' 0x0.st

Also

X11 issue, since it sometimes crashed earlier

Please post your Xorg log, https://wiki.archlinux.org/title/Xorg#General

Scimmia · 2026-01-21 13:31:43

And please, do all of that without "ibt=off initcall_blacklist=simpledrm_platform_driver_init i915.force_probe!=46a6" in the kernel command line. That last one especially is problematic on an Optimus setup.

Last edited by Scimmia (2026-01-21 14:11:39)

jacek_kotek · 2026-01-21 14:38:52

I have disabled the kernel command line modules Scimmia mentioned.
Disabled windows fast start, it was on.

Here is Xorg log: http://0x0.st/PPXp.txt

And here is the howbadisit.txt : http://0x0.st/PPXo.txt

I hope this helps

seth · 2026-01-21 14:44:29

warning: lib32-mesa: /usr/lib32/libgallium-25.3.3-arch1.3.so (Size mismatch)
warning: lib32-mesa: /usr/lib32/libgallium-25.3.3-arch1.3.so (SHA256 checksum mismatch)
lib32-mesa: 90 total files, 1 altered file
warning: mesa: /usr/lib/libgallium-25.3.3-arch1.3.so (Size mismatch)
warning: mesa: /usr/lib/libgallium-25.3.3-arch1.3.so (SHA256 checksum mismatch)
mesa: 104 total files, 1 altered file

re-install the mesa packages

Edit:

[  2146.076] (++) Using config file: "/home/jacek/xorg.conf.new"
[  2146.076] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[  2146.077] (==) ServerLayout "X.org Configured"
[  2146.077] (**) |-->Screen "Screen0" (0)
[  2146.077] (**) |   |-->Monitor "Monitor0"
[  2146.077] (**) |   |-->Device "Card0"
[  2146.077] (**) |-->Screen "Screen1" (1)
[  2146.077] (**) |   |-->Monitor "Monitor1"
[  2146.077] (**) |   |-->Device "Card1"
[  2146.077] (**) |-->Input Device "Mouse0"
[  2146.077] (**) |-->Input Device "Keyboard0"
[  2146.077] (**) Allowing byte-swapped clients

remove the static server config - it's (now) also wrong because w/o blacklisting the simplydumb device, your losing card0 to it.

[  2146.078] (EE) open /dev/dri/card0: No such file or directory
[  2146.078] (WW) Falling back to old probe method for modesetting
[  2146.078] (EE) open /dev/dri/card0: No such file or directory

Last edited by seth (2026-01-21 14:46:46)

Scimmia · 2026-01-21 14:46:02

[  2146.076] (++) Using config file: "/home/jacek/xorg.conf.new"

Don't do that, either. Remove all xorg configs.

jacek_kotek · 2026-01-21 15:20:53

Reinstalling the Mesa packages seems to have solved the problem, things launch now. Thank you very much for the help.

seth · 2026-01-21 15:23:47

\o/
Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

Fwwi, "Ibt=off" was a thing for a short while years ago and "i915.force_probe!=46a6" is syntactically wrong why the switch to xe never worked.

Arch Linux

#1 2026-01-21 10:20:01

[SOLVED] Unable to launch any GUI (neither Wayland nor X11)

#2 2026-01-21 13:23:35

Re: [SOLVED] Unable to launch any GUI (neither Wayland nor X11)

#3 2026-01-21 13:31:43

Re: [SOLVED] Unable to launch any GUI (neither Wayland nor X11)

#4 2026-01-21 14:38:52

Re: [SOLVED] Unable to launch any GUI (neither Wayland nor X11)

#5 2026-01-21 14:44:29

Re: [SOLVED] Unable to launch any GUI (neither Wayland nor X11)

#6 2026-01-21 14:46:02

Re: [SOLVED] Unable to launch any GUI (neither Wayland nor X11)

#7 2026-01-21 15:20:53

Re: [SOLVED] Unable to launch any GUI (neither Wayland nor X11)

#8 2026-01-21 15:23:47

Re: [SOLVED] Unable to launch any GUI (neither Wayland nor X11)

Board footer