You are not logged in.
I am on an HP Victus 15.
I usually use startx.
Here is my ~/.xinitrc:
xmodmap .xmodmaprc
xrdb -load ~/.Xdefaults
xset -b
ratpoisonI have no /etc/X11/xorg.conf; I have an /etx/X11/xorg.conf.d and it is empty.
A while ago I tried to start Brave [from within an X11/ratpoison session] and it hanged with error messages relating to video drivers [sorry that's not more helpful, I don't remember more detail]. Fearing it might be breaking, I restarted.
Now running startx gives me
Current Operating System: Linux <hostname> 6.14.6-arch1-1 #1 SMP PREEMPT_DYNAMIC Fri, 09 May 2025 17:36:18 +0000 x86_64
Kernel command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=c90689f0-dd63-469e-9abd-708706dfdcfe rw loglevel-3 quiet
Current version of pixman: 0.46.0
Before reporting problens, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (-) probed,
(*) from config file, (==) default setting, (+) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "home/ <user> /.local/share/xorg/Xorg.0.log", Time: Thu May 22 20:30:13 2025
(==) Using system config directory "/usr/share/X11/xorg.conf.d"and an interrupt does nothing, I have to power off using the power button.
Running xinit fails with
Fatal server error:
(EE) parse_vt_settings: Cannot open /dev/tty0 (Permission denied)lspci | grep VGA:
01:00.0 VGA compatible controller: NVIDIA Corporation GA107
06:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Rembrandt [Radeon 680M] (rev 0b)I tried commenting out lines 2 and 4 in my xinitrc [
xrdb -load ~/.Xdefaultsand
ratpoison] fearing they might be offending, but startx hangs just the same.
I upgraded my system [full upgrade] during the session before startx failed, and upgraded again after and retested.
I am pretty lost here, does anyone have any ideas?
Edit: pajamaman18 tracing a similar issue with Sway to today's mesa update prompted me to downgrade mesa, which fixes the issue. Brave too. Obviously not a permanent solution but a shim. Hopefully mesa fixes whatever the bug is.
Edit 2: xinit still fails with the same error even now that startx works again. Wasn't sure I'd been configured to use xinit in the first place. I hadn't.
Last edited by Lorec (2025-05-23 03:48:24)
Offline
https://bbs.archlinux.org/viewtopic.php?id=305727
Some posts there revovle around vmware, ignore those - but please post your (failing) Xorg log, https://wiki.archlinux.org/title/Xorg#General
Online
I'm on Wayland (sway, Lenovo Legion 5), after latest mesa update (1:25.0.5-1 -> 1:25.1.1-1) starting sway also hangs. I can SSH into the host, but the console is frozen. Reverting to previous mesa version, I can start sway.
Last edited by Galicarnax (2025-05-25 12:42:24)
Offline
I also got same the issue. Had to hold mesa update. Ryzen 7 with RTX 3050.
root@Coral /home/antonio $ lspci | grep 'VGA'
01:00.0 VGA compatible controller: NVIDIA Corporation GA106 [Geforce RTX 3050] (rev a1)
Last edited by antonioleal (2025-05-30 22:03:43)
Offline
I also got this, froze also text consoles in my box, had to hard reset it to get forward. I only use startx
Downgrading mesa to April version from repo snapshot [1] and using pacman -U ./mesa.... instead of pacman -U file:///mesa... as suggested in downgrade Wiki [1] made the trick this time.
[1] https://archive.archlinux.org/repos/202 … kg.tar.zst
[2] https://wiki.archlinux.org/title/Downgrading_packages
Offline
I ended up downloading the mesa source files from arch and compiling the PKGBUILD with "makepkg -s --skippgpcheck" then manually installing the resulting zsts
That fixed the problem.
Offline
Probably not, starting with arch not shipping any mesa sources - and unless you used some older PKGBUILD, building the buggy mesa version locally will not cause different behavior.
pacman -Qs mesaOnline
By "downloading" I mean of course through arch's own package build system. This indeed fixed the problem in my box.
Offline
unless you used some older PKGBUILD, building the buggy mesa version locally will not cause different behavior
but if you effectively re-installed mesa there's no way to figure what was wrong before.
Online
I can timeshift to the problematic versions and collect some logs from there, but someone must tell me what they want because I just started on Arch a few months ago (nice intro for me eh?). I can already say that disabling ssdm ( in my case I use kde) the machine boots normally... of course then only startx broke it.
Offline
pacman -Qikk mesaAnd after failing
system journal for the boot:
sudo journalctl -b | curl -F 'file=@-' 0x0.stXorg log, https://wiki.archlinux.org/title/Xorg#General
The system journal can likely be reached w/o timeshifting, ("…-b -δ…", δ >= 1 allows you to access journals of previous boots) but will at best tell "what" but not "why" things failed.
Online