You are not logged in.
Since installing Arch, although most of it's worked fine, I guess I've failed to install certain graphics drivers, so that some UIs are simply unresponsive. Affected applications include kitty, Alacritty, Discord (the app; the website interface works fine), Steam, some GTK applications (e.g. gnome-mines 48.1-1), and Löve applications. xterm, Emacs, Firefox, Rhythmbox, gnome-mines 40.1-3, VLC work fine. In said affected applications, nothing happens when I hover over a button or when I click on it, but when I then move the window to another workspace to "refresh" it, it shows the menu or whatever that the button triggers. Similarly with typing text; what I typed is not visible until I "refresh". This is certainly not sustainable!
Relevant details: All my packages (with exception of those I've had to downgrade, which are just various GNOME games) are at their most recent. I run Arch on a laptop; my screen is 1366 x 768 (tantamount to 16:9). My CPU is a 12th Gen Intel i3-1215U (8) @ 4.400 GHz, and I have integrated graphics, so my GPU is an Intel Alder Lake-UP3 GT1 (not, say, Nvidia). This is vanilla Arch Linux, not Artix, Manjaro, etc. I use the i3 window manager (so X11, not Wayland), with mesa, vulkan-intel and xf86-video-intel. My current kernel is 6.14.4-arch1-2, not built from scratch, although I've been experiencing these issues for a while. I ignored them at first, since they're difficult to diagnose via Google, but I figured I ought to get around to them eventually.
Any help is appreciated. I don't know where any relevant logs are, but I can post them if a path is given.
Last edited by IDKWhatToPutHere (2025-05-08 15:29:40)
Offline
Have you had a look at the terminal outputs of the broken apps? (if there are any errors or warnings, post them here) It sounds like a configuration issue.
Next would be a journal: "journalctl -b | curl -F 'file=@-' 0x0.st" (preferably start up some apps to get some errors).
kitty uses opengl, that might be related?
The rest of the applications (other than alacritty) would rely on XWayland under Wayland, which is weird because you're running X11. Perhaps some missing environment variables or leftover Wayland configs?
Last edited by jl2 (2025-05-08 09:38:55)
Why I run Arch? To "BTW I run Arch" the guy one grade younger.
And to let my siblings and cousins laugh at Arsch Linux...
Offline
my GPU is an Intel Alder Lake-UP3 GT1 … I use the i3 window manager (so X11, not Wayland), with mesa, vulkan-intel and xf86-video-intel.
Lose xf86-video-intel - if that's not it (obviously restart X11), do you also run a compositor (picom) next to i3?
Offline
> Lose xf86-video-intel
Huh, that seems to fix it. Thank you!!
Offline
https://wiki.archlinux.org/title/Intel_ … ecent_GPUs - but don't.
The intel DDX driver doesn't really support newer IGPs all that well anyway. Using the modesetting driver is the proper solution, the kernel module does all the heavy lifting.
If you look at older Xorg logs, you'll also notice that you've been using the software rasterizer.
Offline