You are not logged in.
I am having a strange problem on my computer. I am using the NVIDIA driver and for some reason x.org randomly freezes, though it seams to be connected to the switch between 2D and 3D acceleration/engine usage but not fully as it can still happen without a switch, my entire systems graphics will lock up except my mouse and the lock can be fixed by moving my mouse between cursors or tabbing out to another window, which seams to fix the problem by switching 2D and 3D again. But the problem is intermittent and I cant find anything that looks broken in the logs.
This is most noticeable in games when going in menus and when watching web video in my Firefox based browser. Though it also happens a lot in games even if I dont go to a menu. It is very random, sometimes it is like ten times in five minutes and other times it wont happen for an hour. I am on AwesomeWM using the latest kernel and xorg release with the latest DKMS version of the driver.
If you need any logs to help please ask, I dont know what ones would be useful.
Offline
There're multiple reports concerning the 545xx drivers, you could test the behavior of the 535xx dkms driver from the ALA
Do you run a compositor next to awesomewm? (picom, xcompmgr, etc)
Online
> Do you run a compositor next to awesomewm? (picom, xcompmgr, etc)
Yes I use picom, but I have not had a change in my config since the problem started and picom has not hand an update since the problem started. So nothing has changed in picom to cause this. Unless maybe it is an interaction between the new drivers and picom?
I can test the last drivers. Will take to time to see if that fixes the issue.
Offline
Next time things stall, kill picom and see whether that has any impact (it'd explain the behavior, but the cause is most likely the 545xx drivers)
Online
but the cause is most likely the 545xx drivers)
Sadly I just downgraded them and the bug still happens.
I dont know how to try killing picom as the second I open another app or change focus it fixes itself.
Offline
shortcut for "killall picom"?
Online
shortcut for "killall picom"?
Forgot I could do that. But I did end up just doing pkill picom even though it was not frozen now I just have to wait to see.
If it is picom do you think it is fixable? I can give my config, I have no clue what would make picom freeze the screen.
Also thanks for taking help me with this.
Offline
Here is my picom conf:
backend = "glx";
glx-no-stencil = true;
glx-copy-from-front = false;
glx-swap-method = 2;
# Opacity
active-opacity = 1;
inactive-opacity = 1;
frame-opacity = 1;
inactive-opacity-override = false;
blur-background = true;
blur-method = "dual_kawase";
blur-strength = 6;
# Fading
fading = true;
fade-delta = 4;
no-fading-openclose = false;
fade-exclude = [ ];
# Window type settings
wintypes:
{
dock = {
shadow = false;
};
};
opacity-rule = [
"70:class_g = 'Alacritty' && !focused",
"70:class_g = 'Pcmanfm' && !focused",
"70:class_g = 'Mousepad' && !focused",
"90:class_g = 'discord' && !focused"
];
xrender-sync-fence = true;
corner-radius = 15
rounded-corners-exclude = [
"class_g = 'awesome'",
]
If it is important I also have "Force Full Composition Pipeline" enabled in the NVIDIA Settings. If that is impacting picom somehow.
Offline
It seams to relate to this github issue for picom: https://github.com/yshui/picom/issues/540 which was "solved" in this comment: https://github.com/yshui/picom/issues/5 … -728915236 and talked about in this post: https://bbs.archlinux.org/viewtopic.php?id=260131
But the only thing it said was to wait for a driver update for NVIDIA to fix it. But since I downgraded the driver to a version that worked for me in the past to no effect it cant just be a driver thing.
Offline
Do you have an xorg log from the downgraded driver run?
blur-method = "dual_kawase";
Do you run picom w/ "--experimental-backends" ?
Edit: the picom bug is 3 years old, it's probably not related.
Last edited by seth (2023-12-06 18:48:00)
Online
Do you run picom w/ "--experimental-backends" ?
No as it does still blurs without it, but I can try to see if that helps.
Edit 1: --experimental-backends does not seam to be an option anymore
Edit 2: this bug https://github.com/yshui/picom/issues/1145 seams to be it.
Last edited by picoman (2023-12-06 19:38:29)
Offline
Inverted into "--legacy-backends", sorry.
Do you get the freezes if you disable all blurring?
Online
Do you get the freezes if you disable all blurring?
Did not test, I just moved over to compfy as it is picom based but with animations and more active support/bug fixes. I am going to see if the problem still exists on compfy, if it does I will make an issue there.
I will mark this solved if changing to compfy fixes it. I just have to test if it did first.
Offline
Problem still happens on compfy, will have to send a report.
Offline
Did you confirm that it does not happen w/o any compositor?
Online
Did you confirm that it does not happen w/o any compositor?
No I have not. Though apart from picom and its derivatives I dont really know of any others that still get updates and have the features I crave (blur being the main one).
Offline
The point is more to establish whether the compositor plays a role in your situation at all - if the clients freeze w/o any compositor, you don't have to look there.
Depending on how frequent the issue is, you'll have to overcome your cravings for a short while
Online
Well I am looking at the wiki and I dont really see what one to test. The steam one is archived, gamescope is for games, and xcompmgr has not been touched in a year.
Are there some outside of that list that are standalone?
Offline
No compositor at all.
Like "none". Nada. Uncomposited. No fancy shadows, transparency, animations, blurring.
No redirection of anything.
Online
No compositor at all.
In that case I did actually test that for like 2 hours on a stream and no freezes that time in a game that used to do it all the time.
Offline
Ok, so the it's a picom issue - and likely the one you've identified.
You might try the xrender backend (which doesn't support any blurring) or to disable the blurring in the glx backend to hopefully narrow down the cause which could help upstream to fix the bug.
Online
You might try the xrender backend (which doesn't support any blurring) or to disable the blurring in the glx backend to hopefully narrow down the cause which could help upstream to fix the bug.
I will mess with it and talk to the devs of picom and compfy to see how it can be fixed. I will keep this open until I find out how to fix it while still having a compositor.
Thank your for your help and time.
Offline