Bug 958388

Summary: Incomplete shell profile in gnome-terminal on GNOME wayland
Product: [openSUSE] openSUSE Tumbleweed Reporter: Takashi Iwai <tiwai>
Component: GNOMEAssignee: E-mail List <gnome-bugs>
Status: RESOLVED FIXED QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P5 - None CC: dimstar, gp
Version: Current   
Target Milestone: ---   
Hardware: Other   
OS: Other   
See Also: https://bugzilla.gnome.org/show_bug.cgi?id=736660
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Bug Depends on:    
Bug Blocks: 975831    

Description Takashi Iwai 2015-12-08 16:59:17 UTC 
I noticed that a gnome-terminal opened on GNOME wayland doesn't have $HOME/bin in its path.  This must be some flaw in the evaluation of shell profile.

This reminds me of similar bugs on SLE12 (e.g. bug 869677).

The problem isn't seen when GNOME X11 mode.  It seems happening only in Wayland mode.
Comment 1 Dominique Leuenberger 2016-01-25 14:03:55 UTC 
The underlying issue is that gnome-session does not process the profiles:

https://bugzilla.gnome.org/show_bug.cgi?id=736660
Comment 2 Dominique Leuenberger 2016-01-25 14:04:30 UTC 
(as a workaround on my system for now I added 

. ~/.profile

as last line in ~/.bashrc
)
Comment 3 Gerald Pfeifer 2016-12-19 23:16:00 UTC 
I still ran into this not long ago, but am using a fallback to X.org
now since Wayland support simply introduced too many regressions.

Is this one that could be addressed easily?
Comment 4 Dominique Leuenberger 2016-12-20 12:34:58 UTC 
(In reply to Gerald Pfeifer from comment #3)
> I still ran into this not long ago, but am using a fallback to X.org
> now since Wayland support simply introduced too many regressions.
> 
> Is this one that could be addressed easily?

Discussion is ongoing upstream - there is a good chance the upstream position is shifting in favor of sourcing the files again.

Until then, the workaround in comment#2 can be used on local systems.
Comment 5 Dominique Leuenberger 2017-01-18 17:17:35 UTC 
GNOME 3.24 will finally bring the fix here - GNOME:Next (dev branch) already has been updated.

Upstream might backport it into GNOME 3.22 (as is currently provided in TW) - if they do and make new stable releases, we will follow this of course.

Other than that: I consider this FIXED (in the devel prj)