After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 766819 - XDG_CURRENT_DESKTOP and maybe other env variables not set when starting wayland session
XDG_CURRENT_DESKTOP and maybe other env variables not set when starting wayla...
Status: RESOLVED DUPLICATE of bug 766176
Product: gnome-session
Classification: Core
Component: general
3.20.x
Other Linux
: Normal normal
: ---
Assigned To: Session Maintainers
Session Maintainers
Depends on:
Blocks:
 
 
Reported: 2016-05-23 19:02 UTC by Laurent Bigonville
Modified: 2016-05-24 11:18 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Laurent Bigonville 2016-05-23 19:02:13 UTC 
Hi,

With gnome-shell as a wayland compositor, if I'm starting nautilus using the launcher icon, it seems that the default application are not properly set (/usr/share/applications/gnome-mimeapps.list is apparently not read)

If I'm starting from gnome-terminal, the default applications settings are properly applied.

I feel this is an issue with the XDG_DATA_DIRS env variable

I'm also using systemd user session, but that doesn't seems to do a difference

I'm not exactly sure this is an issue directly related to nautilus
Comment 1 Laurent Bigonville 2016-05-23 20:33:42 UTC 
The problem seems to happen when the XDG_CURRENT_DESKTOP="GNOME" environment variable is not set.

So the question is what is not setting the environment variable when starting the wayland session
Comment 2 Laurent Bigonville 2016-05-23 21:00:11 UTC 
So to recap, when starting a wayland session it seems that the applications like nautilus (probably all the applications that are dbus activated) lack of some environment variables (like XDG_CURRENT_DESKTOP) when started.
Comment 3 Laurent Bigonville 2016-05-24 11:18:39 UTC 

*** This bug has been marked as a duplicate of bug 766176 ***