-
-
Notifications
You must be signed in to change notification settings - Fork 584
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Drawing "grey" with Compton enabled after sleep with multiple monitors and i3 WM #134
Comments
Does compton print anything when this happens? |
I have rebooted, so I can't print logs right now. If the logs are written historically, I can paste those. From what I recall though, it prints the same warnings as the other calls to |
@freeqaz I have heard about similar multimonitor issues here and there, but I have never been able to reproduce this problem myself (I have intel cards too). I don't really think this is a driver bug from what I see. Can you run |
Finally got this again. Not sure what caused it, but I did the following and noticed it happening:
Output from logs, as requested:
|
Does this log you attached captured while this bug is happening? |
Yep, that log is while the bug is happening (as requested previously). Nothing seemed crazy suspicious to me there, but I am not an expert on Compton either. If there is anything else I can do to help reproduce this, please let me know. Thank you! |
@freeqaz But the log only captures 2 seconds. Does this bug happen immediately after you start compton? |
Hey @yshui, yeah this bug happens as soon as I open compton. And when I close + reopen compton, it persists. Pretty sure it's a driver issue but not sure if that's because of Intel drivers or because of compton's interactions with the Intel driver. Any thoughts would be appreciated. :) |
@freeqaz Do you mind record a trace with |
@yshui I have a similar problem. (i3, some windows transparent/not drawn after sleep) |
@g0t00 apitrace records your screen. So be sure to only record things relevant to the bug, and keep it as short as possible so the file size won't be too big. |
Not sure if this is relevant, but this could be caused by See @Airblader 's comment here:
My personal workaround is: exec_always for id in $(xprop -root _NET_CLIENT_LIST_STACKING | cut -d "#" -f2 | tr -d " " | sed "s/,/ /g"); do xprop -id "$id" -remove _NET_WM_WINDOW_OPACITY; done Note that this fortunately doesn't mess with any |
@SicariusNoctis Thanks a lot for the information. That gives me some ideas: @freeqaz Does setting |
@freeqaz @SicariusNoctis You have this problem because you have rules like this:
Compton set the opacity to 0 because it's told to. Also cc @Airblader |
So compton is working as intended here. compton set the opacity prop based on the rules, and when i3 restarts, compton have no way of knowing where the prop came from, so it just accepts it. One solution is to not set the opacity prop. But compton has been working this way for a long time, and changing it might break things. |
I'm not too sure why they're there, but I believe those rules were copied from Airblader's dotfiles. |
@SicariusNoctis they are there to make only the top window of the stack visible. So if you have a transparent window on the top, the windows below won't be visible. I think this is a valid use case. |
I'm glad to see this root-caused properly. Thank you for the help! I will test this fix out next time I experience the bug. Awesome to see this be solvable. :) |
In the Can you check if this fixes your problem? |
Looks like this bug is related. kovidgoyal/kitty#1681 |
Summary
When I "wake" my computer from sleep and/or attach multiple monitors, occasionally I get this issue where certain apps that are "collapsed" in i3 won't draw while Compton is running. This issue persists after I kill Compton and start it again.
Went through all of the issues I could find in the issues section here, as well as searched through online to find anything about this. Not sure what the issue is though. Guessing it's an Intel graphics driver bug. Could use some help debugging though. Thank you!
Platform
GPU, drivers, and screen setup
I'm running my laptop display alone often times (XPS 13 9370) and I also use my dock to connect 2 DisplayPort monitors.
These are the recommended settings in the Arch wiki for the i915 driver. https://wiki.archlinux.org/index.php/intel_graphics
Some extra info potentially on the driver version
Environment
I'm running i3 from the Arch repos. When I "stack" windows in i3, this is when the issue seems to happen. The window that was in the "foreground" works fine. The window behind renders as solid grey. I'm still able to interact with the window that is grey (my mouse cursor changes when hovering over a button, etc). Restarting the application fixes the issue.
Like I said before, if I kill Compton I can see the application again. When I start Compton again, the issue persists.
Compton version
I checked out the "next" repo and ran the install steps for that. In both versions, I see this issue
Compton configuration:
Steps of reproduction
exec compton
mod+s
killall compton
and windows work again, run compton and issue persistsExpected behavior
All items should render correctly.
Current Behavior
Collapsed tabs render grey after sleep and/or attaching of monitors.
Stack trace
No crash, as far as I can tell. If I can offer logs or anything, let me know.
Other details
Busted (compton running):
Expected (compton closed):
The text was updated successfully, but these errors were encountered: