You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running any variant of a MATE session (local, remote, nested), the XDG_CURRENT_DESKTOP env var contains "MATE" as set in mate-session's main.c file:
if (g_getenv ("XDG_CURRENT_DESKTOP") == NULL)
gsm_util_setenv ("XDG_CURRENT_DESKTOP", "MATE");
Actual behaviour
The XDG_CURRENT_DESKTOP env var does not get set with MATE when running in nested Xsessions. When run in nested mode, I get the desktop name of my local/native desktop (which is i3 most of the time).
This behaviour is expectable when looking at the above code snippet. Does anyone know what the reason for the above if clause really was? Does it make sense these days? A MATE session is a MATE session and should be reported as such, shouldn't it?
Steps to reproduce the behaviour
Log into a non-MATE desktop env locally...
terminal-1:$ nxagent -ac :1 (or Xephyr, or Xnest, or, ...)
There is a comment in the GNOME session that seems to explain this problem.
/* From 3.14 GDM sets XDG_CURRENT_DESKTOP. For compatibility with
* older versions of GDM, other display managers, and startx,
* set a fallback value if we don't find it set.
*/
if (g_getenv ("XDG_CURRENT_DESKTOP") == NULL) {
g_setenv("XDG_CURRENT_DESKTOP", "GNOME", TRUE);
gsm_util_setenv ("XDG_CURRENT_DESKTOP", "GNOME");
}
Expected behaviour
When running any variant of a MATE session (local, remote, nested), the XDG_CURRENT_DESKTOP env var contains "MATE" as set in mate-session's main.c file:
Actual behaviour
The XDG_CURRENT_DESKTOP env var does not get set with MATE when running in nested Xsessions. When run in nested mode, I get the desktop name of my local/native desktop (which is i3 most of the time).
This behaviour is expectable when looking at the above code snippet. Does anyone know what the reason for the above if clause really was? Does it make sense these days? A MATE session is a MATE session and should be reported as such, shouldn't it?
Steps to reproduce the behaviour
Log into a non-MATE desktop env locally...
Inside MATE:
echo $XDG_CURRENT_DESKTOP
MATE general version
1.20
Package version
1.20.0-1
Linux Distribution
Debian testing/unstable
The text was updated successfully, but these errors were encountered: