Skip to content
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

Compton no longer turns windows transparent on i3-gaps #571

Open
trophystitch opened this issue Apr 29, 2020 · 1 comment
Open

Compton no longer turns windows transparent on i3-gaps #571

trophystitch opened this issue Apr 29, 2020 · 1 comment

Comments

@trophystitch
Copy link

Platform: Ubuntu 18.04 LTS

GPU, drivers, and screen setup: Geforce GTX 1650, default drivers in ubuntu, one monitor configured with xrandr (I think?)

Compton version: v7 (installed from ubuntu repositories with apt)

Compton configuration: I haven't changed configuration file at all, but couldn't find anything at ~/.config/ or ~/.config/i3/ , so I don't know where the file is, sorry.

Steps of reproduction

Compton setup as autostart in i3wm config file, later removed to try and run from a terminal. I think the last time it worked was before I used lxappearance to change from the Raleigh theme to Adwaita Dark, but even after swapping it back it didn't change anything.

Expected behavior

I would like Compton to run the exact same way it did before, which was making my terminal windows partially transparent.

Current Behavior & Other details

When left in the config file for i3, Compton makes no changes to anything. When ran in a terminal, it outputs this error:

zach@sevastopol:~$ compton
[ 04/28/2020 11:06:33.739 x_fence_sync ERROR ] Failed to trigger the fence.
[ 04/28/2020 11:06:33.739 paint_all ERROR ] x_fence_sync failed, xrender-sync-fence will be disabled from now on.
@alalfakawma
Copy link

I had this same issue and when I ran compton it told me that it was now changed to picom and showed me several changes that I had to make in the config file. Doesn't look like it's the case in yours, but I will be putting this here just in case someone bumps into this looking for a solution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants