Hi, On Tue, Feb 04, 2025 at 02:48:49PM +0100, Birger Schacht wrote: > On 2/3/25 12:10 PM, Sebastian Reichel wrote: > > The new config drop-in from sway-backgrounds has higher priority than > > the user configuration in $HOME/.config/sway/config. > > The drop-in from sway-backgrounds should not be used unless there is some > `include /etc/sway/config.d` somewhere in the main config file. This is the > case for the one installed in /etc/sway/config and it might also be the case > for some configs in $HOME/.config/sway/config.
Ah, I should have checked how the config.d files are handled. I see /etc/sway/config has the include at the very end and the manpage suggests to copy /etc/sway/config to the user's config directory and continue from there. So it is easy to run into that trap :) Maybe a sentence could be added: Note that the default configuration ends with including config files from /etc/sway/config.d, which might need to be removed or relocated to avoid overriding the user configuration. > > As a workaround > > I deinstalled sway-backgrounds, since I don't really need it. But this > > is quite unexpected and recommended packages are installed by default. > > Yes, sway-backgrounds being a recommended package of sway is definitely a > bug, now that the default configuration of sway on Debian does not use the > sway-backgrounds background by default. I'll fix that. Sounds good to me. Greetings, -- Sebastian
