Gnome wayland session doesn't source ~/.profile
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu GNOME |
In Progress
|
Low
|
Unassigned | ||
gnome-session |
Fix Released
|
Medium
|
|||
gnome-session (Ubuntu) |
Fix Released
|
Low
|
Unassigned | ||
Xenial |
Triaged
|
Low
|
Unassigned | ||
Yakkety |
Triaged
|
Low
|
Unassigned |
Bug Description
Impact
======
Logging in with GDM3 and choosing GNOME on Wayland gives me a session where `$HOME/.profile` **hasn't** been sourced.
Where as logging on with standard GNOME gives me a session where `$HOME/.profile` **has** been sourced.
Test Case
=========
This test case assumes you haven't removed any lines from the default ~/.profile that is created for you.
mkdir ~/bin
Log out. Click your user name and choose GNOME on Wayland from the gear button and then Log in.
Open a terminal. Run
env | grep PATH
PATH will not contain /home/username/bin as the first entry
From Ubuntu GNOME, install the updated gnome-session packages
Log out. Log in to GNOME on Wayland
Open a terminal. Run
env | grep PATH
PATH will contain /home/username/bin as the first entry
When you're done testing, feel free to remove ~/bin if you haven't put any other files in that directory.
Regression Potential
=======
This update was pushed to Fedora 25, which uses Wayland by default although X is still available there.
Ubuntu GNOME still uses X by default although "GNOME on Wayland" is available as an included option in Ubuntu 16.04 and newer.
Other Info
==========
The reason this bug existed for so long was that GNOME developers would like to use a different way to let users set environment variables or whatever other common tasks used to be done by running profile scripts. However, that new way hasn't been implemented yet. Now that GNOME 3.22 uses Wayland by default (overridden currently in Ubuntu and Debian stretch), this bug has become more of a problem so developers backed down and provided this solution until the alternative is ready.
https:/
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: gnome-session-
ProcVersionSign
Uname: Linux 4.8.0-21-generic x86_64
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
CurrentDesktop: GNOME
Date: Sun Oct 9 14:52:08 2016
InstallationDate: Installed on 2013-04-11 (1277 days ago)
InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Alpha amd64 (20130410)
SourcePackage: gnome-session
UpgradeStatus: Upgraded to yakkety on 2016-10-02 (6 days ago)
Changed in gnome-session: | |
importance: | Unknown → Medium |
status: | Unknown → In Progress |
Changed in gnome-session (Ubuntu): | |
importance: | Undecided → Low |
Changed in gnome-session (Ubuntu Xenial): | |
importance: | Undecided → Low |
status: | New → Triaged |
Changed in gnome-session (Ubuntu Yakkety): | |
importance: | Undecided → Low |
status: | New → Triaged |
description: | updated |
Changed in ubuntu-gnome: | |
status: | New → In Progress |
importance: | Undecided → Low |
Changed in gnome-session (Ubuntu): | |
status: | Confirmed → In Progress |
Changed in gnome-session: | |
status: | In Progress → Fix Released |
description: | updated |
Status changed to 'Confirmed' because the bug affects multiple users.