-
-
Notifications
You must be signed in to change notification settings - Fork 589
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
Opacity randomly set to 1 #474
Comments
Probably a duplicate of #470. There seem to be some issues with rule parsing on Arch lately. |
#470 has been fixed in |
The issue no longer appears, thanks a lot! |
netbsd-srcmastr
pushed a commit
to NetBSD/pkgsrc
that referenced
this issue
Oct 3, 2020
Changes: Fixed yshui/picom#470 yshui/picom#471 yshui/picom#474 yshui/picom#465 Worked around yshui/picom#301 Fixed specifying a window id with the picom-trans script Fixed minor memory leaks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Platform
Arch Linux
GPU, drivers, and screen setup
T14s AMD 4750U Integrated GPU
Environment
i3-gaps
picom version
Configuration:
Steps of reproduction
Randomly reoading picom with
killall picom; picom --experimental-backends --log-level DEBUG
Expected behavior
Opacity is consistently set
Current Behavior
Sometimes correct opacity is applied and Sometimes opacity of 1 is set.
Other details
Success and Failure files represent the two cases; the differences as far as I can tell are:
Window mode changed to 0 (correct behaviour) vs Window mode changed to 2 (wrong opacity) and the presence of the line
win_update_opacity_target
below in the successful casepicom_failure.log
picom_success.log
Note: this also happens with latest version from
next
branchThe text was updated successfully, but these errors were encountered: