Bug#962224: lightdm does not source ~/.profile
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Control: forcemerge 636108 -1
On Thu, 2020-06-04 at 19:27 +0100, Graeme Vetterlein wrote:
> Having switched to lightdm from GDM3 (due to another bug in gdm3) I now find
> ~/.profile does
> not run.
>
> In order to debug this I created a clean user (new) called guest (pid=1001)
> I modified ~/.profile and ~/.bash_profile to log their use (see attached
> log)
>
> In summary the behaviour was:
>
> gdm3 + cinnamon = Runs ~/.profile only
> gdm3 + xfce = Runs ~/.profile only
> gdm3 + gnome3 = Runs ~/.profile only
>
> Switch to lioghtdm & reboot system
>
> lightdm + cinnamon = Runs neither
> lightdm + xfce = Runs neither
> lightdm + gnome = Runs neither
> lightdm + gnome(2nd version) = Runs neither
>
> The doc @ https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/794315 poin
> ts
> to where this has been fixed in the past.
Hi Graeme,
this is a duplicate of #636108 so I'm merging the bugs. Note that .profile (et
al) are explicitely a configuration file of *bourne shells:
# /etc/profile: system-wide .profile file for the Bourne shell (sh(1))
# and Bourne compatible shells (bash(1), ksh(1), ash(1), ...).
lightdm is *definitely not* a bourne or bourne-compatible shell and thus doesn't source any profile file.
If you want to set something to the desktop environment, use ~/.xsessionrc.
Regards,
- --
Yves-Alexis
-----BEGIN PGP SIGNATURE-----
iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAl7c8eEACgkQ3rYcyPpX
RFtVkgf6A5m9CXSC6E9X6a3qhXrOazblQ7iqeKqVEqMZ+/kOtyAS53CNt0G7DyqZ
rY99OIdaWKZdoqahTF4fXCqBhlTf/XaBLeh55K3J+WPIatEPSebHD/hvwKaqvfFM
8yWoGpy1eMuWlcQSkAiZrnxgZomlEFNMLPlZQK1+4sZ8RJ0qvYdApgtb4dllfVaP
K++E0XqVhf8OjQNodF9SXdJ3vFlYzlBaKHZH76h+wZpIBpoEsRD05FYkxBmAYH/L
Dz3YcVGBcoCSTk+UgQfLFK6EurmzCMo4i+jlKC7jZm1dG7m91KJDWQv4BxHjjyqc
gwwt80voUnk3F2G8xHAPX3unzjkNdA==
=ZpEp
-----END PGP SIGNATURE-----
Reply to: