Looks like a recent release of picom has new defaults for transparency when using "picom -CGb" (run from i3's config if that matters). Now all inactive windows and menus are transparent.
"picom -CGb -i 1" fixes inactive windows but context menus are still transparent. Is there a way to make everything non-transparent, including context menus without using a conf file (not that I know how to do that either atm, after a quick look through the file)
kleshas
All 12 comments
What version of picom are you running (before and after)? And please provide at least the output of picom --diagnostics.
Please run picom with --config /dev/null to make sure there is no default config file interfering.
tryone144
on 11 Sep 2020
I've had the same issue, it seems the arch maintainers changed the default config file which ships with the package in https://github.com/archlinux/svntogit-community/commit/1bad31a46ef9edb98fb380f98a77a770afb35dd1#diff-8d0411b338c83cd8cd8ad9d9db127101 , which enabled transparency along with some other settings.
Romern
on 11 Sep 2020
Related note: The -C, --no-dock-shadow and -G, --no-dnd-shadow options have been deprecated and will be removed in the next major release of picom. Instead use the wintypes option for dock and dnd as shown in the sample config.
tryone144
on 11 Sep 2020
What version of picom are you running (before and after)? And please provide at least the output of
picom --diagnostics.
Please run picom with--config /dev/nullto make sure there is no default config file interfering.
picom -CGb --config /dev/null fixes the problem. I had always assumed -CGb meant no config was loaded.
kleshas
on 11 Sep 2020
I've had the same issue, it seems the arch maintainers changed the default config file which ships with the package in archlinux/svntogit-community@1bad31a#diff-8d0411b338c83cd8cd8ad9d9db127101 , which enabled transparency along with some other settings.
Ah, ok. Thanks for the info.
kleshas
on 11 Sep 2020
@kleshas If you look at the output of picom --diagnostics, you can see that picom uses the config file at /home/kleshas/.config/picom/picom.conf unless specified otherwise. Maybe some option in there is causing this issue.
This might be related to a bug that surfaced recently after a glibc update on Arch which will be fixed in v8.1.
tryone144
on 11 Sep 2020
How does one disable the transparency fading when switching between workspaces? I seem to have set --fading=false in the past but now that's an invalid option?
devsnek
on 13 Sep 2020
How does one disable the transparency fading when switching between workspaces? I seem to have set
--fading=falsein the past but now that's an invalid option?
fading = false in the cfg file works for me
KrasimirZahariev
on 13 Sep 2020
@kleshas did you manage to fix context menus being translucent? Following the advice here regarding the config file fixed the issue with inactive windows, but my context menus are still translucent.
MarkusG
on 20 Sep 2020
@MarkusG I used picom -CGb --config /dev/null
kleshas
on 20 Sep 2020
The default system-wide config was changed in arch linux, in my case I didn't have a user config. sudoedit /etc/xdg/picom.conf and you will see transparency options commented out and replaced. You can leave exec_always compton or exec_always picom in your i3 config or wherever you have that spawn. In this way, you don't lose all of the other default configuration options.
tzcrawford
on 24 Sep 2020
I simply copied the old config file to ~/.config/picom.conf, as I found it to be working nicely.
jendrikw
on 24 Sep 2020
Related issues
Ropid
路
10Comments
arielnmz
路
3Comments
Ygarr
路
10Comments
arvl130
路
9Comments
aufkrawall
路
7Comments
Most helpful comment
I've had the same issue, it seems the arch maintainers changed the default config file which ships with the package in https://github.com/archlinux/svntogit-community/commit/1bad31a46ef9edb98fb380f98a77a770afb35dd1#diff-8d0411b338c83cd8cd8ad9d9db127101 , which enabled transparency along with some other settings.