https://bugzilla.suse.com/show_bug.cgi?id=1181392 https://bugzilla.suse.com/show_bug.cgi?id=1181392#c3 --- Comment #3 from Matej Cepl <mcepl@suse.com> --- (In reply to Denys Kondratenko from comment #2)
How do you login ? What login manager do you use?
gdm (I was using Gnome until then, just installed sway package, logged out of the Gnome session, and logged in with Sway selected from the option button in the login menu).
`/etc/profile*` looks to be used for bash interactive login. If you start sway from bash, env should be there.
No, /etc/profile is used only with --login bash (and then ~/.bashrc is not used). And I would like to have environmental variables set for ALL applications started from Sway, including graphical ones (e.g., my own $PATH and many other ones), not only applications run from terminal application.
openSUSEway uses greetd to login, and `sway-run.sh` script to init some of the variables for apps to run under Wayland.
Is it a good idea to put all customization in special package. Users (like me) expect sway package just work, not being half baked. And apparently there are SOME customizations, but not all of them.
Also there is `environment.d` method for systemd services.
You mean /etc/environment file? Hmm, it starts with the comment: # This file is parsed by pam_env module So, it is even more complicated.
I don't really know how GDM and others are initializing and if it is correct to source `profile` files for sway.
Hmm, https://src.fedoraproject.org/rpms/sway/blob/master/f/sway.spec does even less than us. And Debian is similarly minimalistic https://sources.debian.org/patches/sway/1.5-7/0002-Modify-default-configurat... . -- You are receiving this mail because: You are on the CC list for the bug.