GNOME Bugzilla – Bug 738665
GDM doesn't source ~/.profile and friends with GNOME on Wayland session
Last modified: 2015-10-27 21:16:57 UTC
I just updated to GNOME 3.14.1 on Arch. With this release, the GNOME on Wayland session works pretty well so I'd like to use that for day-to-day use. However, in a GNOME on Wayland session my environment isn't set correctly. I think the problem is that with a normal GNOME session GDM would run /etc/gdm/Xsession which (next to many other things) sources ${HOME}/.profile where I have my general (non-shell specific) environment setup, e.g., I prepend ~/bin to PATH, etc. With the GNOME on Wayland session the /etc/gdm/Xsession doesn't seem to be run. At least my ~/.profile isn't sourced. So I guess there should probably be some /etc/gdm/Waylandsession which does the same as Xsession (without the X-specific stuff).
I can confirm that this is still an issue in 3.16.
Hi, I'm also experiencing this bug. Not only ${HOME}/.profile is not source, but neither /etc/profile .
I also can confirm this, using 3.16 on Manjaro 0.8.13rc1 .
Still visibile, and still pretty annoying (no PATH, no EDITOR) in 3.18.0 It would be nice to have a clear design on how to solve this. Indeed, I'm quite surprised it ever worked under X, as .profile was only sourced for gnome-session and its descendants, not for dbus and dbus activated services/apps.
Yeah, we should probably run a login shell on our own in gdm.
*** This bug has been marked as a duplicate of bug 736660 ***
see the discussion on bug 736660 . i think the environment variable problem can be solved in a different way than introducing a tower of shell scripts in the login path in wayland. wayland is our chance to break away from that, and some distros never ran a login shell at login time. Also, doing it in GDM isn't going to help with systemd user sessions going forward either.
*** Bug 757216 has been marked as a duplicate of this bug. ***