Artix Linux => System => Topic started by: VectorSpiral on 19 February 2025, 16:50:24
Title: Display randomly freezes forcing hard restart
Post by: VectorSpiral on 19 February 2025, 16:50:24
Hello, I've been using Artix for a while now and after a recent update I'm having an issue where seemingly at random my computer will simply freeze and become completely unresponsive, I'm not sure what's causing this but it has never done this before. I suspect it has something to do with the new graphics driver packages such as mesa as others have reported display issues with those as well, but I'm not sure. Other things to note is that audio continues to play when the screen freezes but I don't believe that the computer still gets input, so far I haven't found a way out of this freeze other than to force a hard reset with the power button, even after trying to ctrl+alt+delete out or use ctrl+alt+F1-8 to switch displays, neither works, and the screen just remains stuck. I'm using OpenRC as well if that helps.
lsusb Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 048d:c985 Integrated Technology Express, Inc. ITE Device(8295) Bus 001 Device 003: ID 258a:002a BY Tech Usb Gaming Keyboard Bus 001 Device 004: ID 048d:c103 Integrated Technology Express, Inc. ITE Device(8910) Bus 001 Device 005: ID 30c9:00ac Luxvisions Innotech Limited Integrated Camera Bus 001 Device 006: ID 1532:006e Razer USA, Ltd DeathAdder Essential Bus 001 Device 007: ID 8087:0033 Intel Corp. AX211 Bluetooth Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Hello, I've been using Artix for a while now and after a recent update I'm having an issue where seemingly at random my computer will simply freeze and become completely unresponsive,
I have the same problem. But I found a simple solution. I disabled compositing (I use Mate DE). And the problem disappeared. On another computer with identical specifications, I use Kde plasma (wayland session) and I never had such a problem.
Title: Re: Display randomly freezes forcing hard restart
Post by: VectorSpiral on 19 February 2025, 18:24:51
Hello, I've been using Artix for a while now and after a recent update I'm having an issue where seemingly at random my computer will simply freeze and become completely unresponsive,
I have the same problem. But I found a simple solution. I disabled compositing (I use Mate DE). And the problem disappeared. On another computer with identical specifications, I use Kde plasma (wayland session) and I never had such a problem.
I actually am using Kde plasma with wayland, I tried disabling compositing like you said but that doesn't seem like an option when using wayland.
Title: Re: Display randomly freezes forcing hard restart
Post by: clappingsnowdrop on 19 February 2025, 23:26:02
This maybe related to the mesa problems or the Xorg problems in also related to desktop/window manager freezing.
1.) Problem from others: (Mesa) Downgrading Mesa to 24.2.7.x might work (see https://forum.artixlinux.org/index.php/topic,7564.0.html)
2.) My problem: (Xorg) Any applications that runs on Xorg/xwayland would cause this freeze. (see https://forum.artixlinux.org/index.php/topic,7551.0.html)
Unfortunately I have no solution for this. Even now I still have to deal with this bullshit. And only have been avoiding Xorg to avoid the crash/freeze.
2 - a.) There are some applications that run on xwayland that you may not notice (like launching gvim on the terminal unless launched with the DISPLAY= variable) or tor not launched with MOZ_ENABLE_WAYLAND=1 variable. Wine(not using the DISPLAY= variable), Steam client, proton launched applications, etc.
Title: Re: Display randomly freezes forcing hard restart
Post by: VectorSpiral on 03 March 2025, 05:50:45
This maybe related to the mesa problems or the Xorg problems in also related to desktop/window manager freezing.
1.) Problem from others: (Mesa) Downgrading Mesa to 24.2.7.x might work (see https://forum.artixlinux.org/index.php/topic,7564.0.html)
2.) My problem: (Xorg) Any applications that runs on Xorg/xwayland would cause this freeze. (see https://forum.artixlinux.org/index.php/topic,7551.0.html)
Unfortunately I have no solution for this. Even now I still have to deal with this bullshit. And only have been avoiding Xorg to avoid the crash/freeze.
2 - a.) There are some applications that run on xwayland that you may not notice (like launching gvim on the terminal unless launched with the DISPLAY= variable) or tor not launched with MOZ_ENABLE_WAYLAND=1 variable. Wine(not using the DISPLAY= variable), Steam client, proton launched applications, etc.
Sorry for the late reply, but I also had issues with my system booting after an update like some others here, but that's fixed now. Anyways, some more info I've notices since 1. It isn't a mesa issue, I've downgraded it, upgraded it, tried out the git version somone posted earlier, none of it works. So I'm pretty sure it's something to do with KDE or at least the display manager in some way. 2 It's only the display, the computer is actually running fine in the background, if I'm watching a video the audio will keep playing throughout the whole thing, and I've been able to use my mouse to shut windows or turn off the computer using shortcuts, so it isn't a full freeze, it's just the display, as I've mentioned before swapping desktops using ctl+alt+F5/F6/Fwhatever, won't work, nor will turning off the display by shutting the lid, once it's stuck it's stuck for good. 2. It tends to happen more when I'm using browsers, I don't know why, but with what you outlined about how it's probably with xorg/xwayland makes a lot of sense, oddly enough I've never had it happen when doing something like running a game, even when it runs my GPU fairly hard, so it's not something based just on how much that's being used, I think chromium is what causes it to happen the most, but I've had it happen just when browsing steam (but not in-game) even before running chromium that session, obviously while it's an issue with chromium to some extent the entire display shouldn't crash. However I do have chromium set to use wayland as it's ozone platform, so I'm not sure if it's still using xorg somehow.
Also does anyone know what logs I should be looking at for this? I've tried to go through some of them, but being new to this don't really know which ones I should be looking at or even really what I should be looking for, but I'm sure it's something to do with the display.
Title: Re: Display randomly freezes forcing hard restart
Post by: clappingsnowdrop on 05 March 2025, 12:02:01
I don't know why, but with what you outlined about how it's probably with xorg/xwayland makes a lot of sense, oddly enough I've never had it happen when doing something like running a game, even when it runs my GPU fairly hard, so it's not something based just on how much that's being used, I think chromium is what causes it to happen the most, but I've had it happen just when browsing steam (but not in-game) even before running chromium that session, obviously while it's an issue with chromium to some extent the entire display shouldn't crash. However I do have chromium set to use wayland as it's ozone platform, so I'm not sure if it's still using xorg somehow.
Also does anyone know what logs I should be looking at for this? I've tried to go through some of them, but being new to this don't really know which ones I should be looking at or even really what I should be looking for, but I'm sure it's something to do with the display.
1.) xorg/xwayland I emulated on what I noticed on what freezes the PC (looping 2 xorg/xwayland apps to keep on swapping positions/focus(window manager feature)). Mine does a full freeze, even audio repeats like a broken record. If I play a game and it uses wine's xorg backend (wine wayland is still lacking) I experience no freeze so long as I don't multitask(like running a browser in some other workspace/tag).
I tried the same test using 2 native wayland apps and I get no crashes no matter how long the test lasts. Usually the testing will only last 30-60 seconds before I get a freeze.
I hope the devs at wine can make it so that wine's wayland backend will have full parity if not better than it's xorg's backend counterpart.
1 - a.) To check if the apps are still running on xwayland I just check the processes if xwayland is running after opening the said app. Though sometimes even if it isn't used, sometimes it's still opens one so I terminate the xwayland process. If the app crashes then it's still using it, otherwise no.
2.) logs I tried some tools but got no luck on pinpointing the issue. I've ran them on a loop script while doing the crash/freeze test until it freezes: