-
-
Notifications
You must be signed in to change notification settings - Fork 31
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
Screen tearing due to no Picom config being loaded on boot #1024
Comments
I've never done Linux development before. If someone tells me which project of Regolith this is in I'd be apt to try to fix it myself |
Hi @TimVanDyke , sorry it's not clear to me if the issue is screen tearing or that your config isn't loading as expected. Here is the code that looks for a user-staged picom config file and loads it, or the default if doesn't exist: https://github.com/regolith-linux/regolith-compositor-picom-glx/blob/master/init#L12 Does that provide any help? |
The issue is neither config is loading on boot. I konw this is the case because when I kill Picom and run it pointing to a config it fixes my screen tearing. When I changed the default regolith config AND when I tried overriding it in Looking closer I see that I have a "residual config" from compton:
I'll purge that and reboot real quick |
Post reboot here is what's installed:
My screen is currently tearing.
Now running fixes my screen tearing This leads me to believe that it isn't loading the config correctly. |
Running that script you linked is working, what calls that? I modified it and added it to my scripts directory (just added print output) and it is working as I'd expect and loading the config: cat picom-restart
#!/bin/bash
compositor_PID=$(pidof picom)
while [ ! -z "$compositor_PID" ]; do
echo "Killing Picom"
kill $compositor_PID
sleep .1
compositor_PID=$(pidof picom)
done
echo "Picom Killed"
if [[ -f "$HOME/.config/regolith3/picom/config" ]]; then
echo "starting with home directory thing"
/usr/bin/picom --config "$HOME/.config/regolith3/picom/config" --daemon
else
echo "starting with else path"
CONFIG_PATH=$(xrescat regolith.compositor.picom.config /etc/regolith/picom/config)
/usr/bin/picom --config "$CONFIG_PATH" --daemon
fi output:
|
It's |
I do have both of those installed:
For good measure here is everything I have installed with "regolith" in the name:
|
Not sure why |
I get no output from that:
What should the output be? |
For what it's worth I upgraded from Regolith 2 and have had screen tearing for a long time, possibly even during the regolith 2 days. This doesn't return anything either (and I wouldn't expect it to)
|
Empty means "default" in this case, which is what I would expect. If you had set that to some other path, that would explain why the i3 isn't loading the compositor for you, but since you didn't set it, it's not the cause. |
Describe the bug
Screen tearing despite updating the picom config to enable V sync (this fixes it see below)
These config changes only actually load after running
I tried updating
/etc/regolith/picom/config
and also~/.config/regolith3/picom/config
running picom manually after boot and pointing to my config file is fixing my issue and is my workaround for now.
To Reproduce
use the default picom settings, and try to override them according to the docs here: https://regolith-desktop.com/docs/howtos/customize-compositor/
I test screen tearing with this video. It's immediately apparent if it's broken or fixed while viewing it: https://www.youtube.com/watch?v=MfL_JkcEFbE
Expected behavior
regolith loads my custom config (updating the default path
/etc/regolith/picom/config
doesn't work either as mentioned)Configuration file(s)
Please attach or mention any customization you've done to configuration files which might have an impact on the bug you are describing. It'll help us determine the root cause of your issue.
I don't think it makes a difference but here's my config that fixes the screen tearing:
Installation Details
The text was updated successfully, but these errors were encountered: