Arch Linux

Nubco

Member

Registered: 2022-09-28

Posts: 37

StartX Fails - Log below - Began w/ Could not resolve keysym errors...

Please help! After today's update the computer just never booted again.

StartX is failing... it started off doing this...

Link to Pic of the earlier screen with xkbcomp errors... https://ibb.co/pZtVGxP

It is still failing but it is no longer displaying the xkbcomp related errors.

Xorg.0.log - http://0x0.st/H5AO.txt

Any ideas?

Last edited by Nubco (2024-02-22 04:42:03)

Scimmia

Fellow

Registered: 2012-09-01

Posts: 13,694

Re: StartX Fails - Log below - Began w/ Could not resolve keysym errors...

[  1311.271] (II) modeset(0): glamor X acceleration enabled on KABINI (radeonsi, , LLVM 16.0.6, DRM 2.50, 6.7.5-arch1-1)

bug in mesa. See https://bbs.archlinux.org/viewtopic.php?id=292952 among others.

Nubco

Member

Registered: 2022-09-28

Posts: 37

Re: StartX Fails - Log below - Began w/ Could not resolve keysym errors...

[  1311.271] (II) modeset(0): glamor X acceleration enabled on KABINI (radeonsi, , LLVM 16.0.6, DRM 2.50, 6.7.5-arch1-1)

bug in mesa. See https://bbs.archlinux.org/viewtopic.php?id=292952 among others.

Thank you. I rolled back to Mesa 23.3.5 and am functional again.

I greatly appreciate your speedy reply!

By the way, how did you know that from the logs?

Scimmia

Fellow

Registered: 2012-09-01

Posts: 13,694

Re: StartX Fails - Log below - Began w/ Could not resolve keysym errors...

The part of the log showed shows that you're using radeonsi, which is where the bug is. It's been all over the forums for the past couple of days so knowing what to look for is straightforward for someone that follows what's going on (and no, I'm not saying you should have, most people aren't going to be reading thread after thread, and that's fine). There's a patch pending, so the next release of mesa should take care of it.

Nubco

Member

Registered: 2022-09-28

Posts: 37

Re: StartX Fails - Log below - Began w/ Could not resolve keysym errors...

The part of the log showed shows that you're using radeonsi, which is where the bug is. It's been all over the forums for the past couple of days so knowing what to look for is straightforward for someone that follows what's going on (and no, I'm not saying you should have, most people aren't going to be reading thread after thread, and that's fine). There's a patch pending, so the next release of mesa should take care of it.

Sweet! Thank you greatly!