Hi all,
with Ubuntu precise launching an X2Go session named ,,GNOME'' results
in a UNITY-2D desktop session.
First thing: it is nice to have Unity available via X2Go.
Second thing: it is a PITA that starting ,,gnome-session'' ends up
with the UNITY shell. If we say GNOME in the client we should end up
with GNOME(3).
@devs:
Currently, the client-side translates the session profile <command>
(GNOME, KDE, ...) into the server-side command (gnome-session,
startkde). For single applications this translation is done within
x2goruncommand.
I would like to suggest to move this translation into x2goruncommand
completely. Allowing the server-side to detect what actual command has
to be executed for ,,GNOME'' or ,,KDE'' or <OTHER> will be much more
handy than making the client-side aware of the server's operating
system, shell, Xsession files, etc.
Your opinions, please!!!
Greets, Mike
--
DAS-NETZWERKTEAM mike gabriel, dorfstr. 27, 24245 barmissen fon: +49 (4302) 281418, fax: +49 (4302) 281419
GnuPG Key ID 0xB588399B mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
On 04/29/2012 12:22 AM, Mike Gabriel wrote:
Hi all,
with Ubuntu precise launching an X2Go session named ,,GNOME'' results in a UNITY-2D desktop session.
First thing: it is nice to have Unity available via X2Go.
Second thing: it is a PITA that starting ,,gnome-session'' ends up with the UNITY shell. If we say GNOME in the client we should end up with GNOME(3).
@devs: ------ Currently, the client-side translates the session profile <command> (GNOME, KDE, ...) into the server-side command (gnome-session, startkde). For single applications this translation is done within x2goruncommand.
I would like to suggest to move this translation into x2goruncommand completely. Allowing the server-side to detect what actual command has to be executed for ,,GNOME'' or ,,KDE'' or <OTHER> will be much more handy than making the client-side aware of the server's operating system, shell, Xsession files, etc.
Your opinions, please!!!
Greets, Mike
To solve the problem properly, you'd need something that understands gnome-session and uses it as it's expected.
Here are some example calls of gnome-session:
- gnome-session => starts the default session, on Ubuntu, unity-3d
- gnome-session --session=ubuntu => starts unity-3d
- gnome-session --session=ubuntu-2d => starts unity-2d
- gnome-session --session=gnome => starts Gnome3 (shell)
- gnome-session --session=gnome-fallback => starts the gnome 3.x fallback session
The names match entries in /usr/share/gnome-session/sessions/
It's also generally recommended to start these sessions through /etc/X11/Xsession or some things won't be set properly (gconf/dconf profile being the most annoying one).
I'm usually using: export DESKTOP_SESSION=gnome-fallback /etc/X11/Xsession "gnome-session --session=$DESKTOP_SESSION"
This simulates what gdm/lightdm do and make all the Xsessions script do the right thing and finally calling gnome-session with the right session. (DESKTOP_SESSION is used by gconf to change the default settings depending on the session).
Hope that helps you get a clear picture of how that all works and let you get good support for that in x2go. I had to dig into that lately when fixing some bugs in LTSP and in Weblive (with both x2go and NX).
Stéphane Graber Ubuntu developer http://www.ubuntu.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQIcBAEBCgAGBQJPnUebAAoJEMY4l01keS1nNx4QAISKX1vw/Ciuz3JLyF2lhLwP BM5dHtOo3LUowbvBao9DK8HYa44C+DPuZdq+E788vei5NRI1DW+qaLaT2LIhPstl BXhQjj8pPf4uhP5y/LDb434m09bJGrsWou3YS2rMwkcx8wQ14HtDBfB2WnqiNTmW UsoEmYJcgHfnDFEsU5oy8S+VyXi2wp56vTKfiO0YsyPZIkhApUdpqKkKq2qCbFBE jNxh8uot2D3UjZCsT3+9IuJp1igFapkS7PfJbTpAjldc+sP/+JaKO9Od05ySYCt4 000/RpmbG5qFLM+XNLZRGbWXtCNKLK4MF3j8AYja94ayVT9VrdBLwGnfCqWLmbFI L87TlyPB1T6CMy8J6qeWM0LZ1ZGzjGE00t7mfQqL0HKBgWrXJoPtJ4zBdoqRhepY dUZBUgC5DxOgdPY9VaeGrmMjpDUBjFNs+l2F2ACLqUsrktnQYLp86LkfNLehYuye KnE65tSi5jY/SOPPDmOiRTV2OU04cqIgmIVDgoNc/3iGxyYcM//l3rUC4TBRv7Ht gOmdINTLhXzEmadTLXgnGhXZRGVUhGzoZG3s18q3135TGPb38tWN4+6vmUbWyBHB +yla9b3YkB6UPk5VocTZDDadDTxTRdHGb2Bb6JHakBRDrqswsXkUVgNknhwNBLsQ 5YLNmaPLKp5BjxF88gWg =S0F0 -----END PGP SIGNATURE-----
Hi Stéphane,
thanks for clarifying all this!!!
On So 29 Apr 2012 15:52:32 CEST Stéphane Graber wrote:
To solve the problem properly, you'd need something that understands gnome-session and uses it as it's expected.
Here are some example calls of gnome-session:
- gnome-session => starts the default session, on Ubuntu, unity-3d
- gnome-session --session=ubuntu => starts unity-3d
- gnome-session --session=ubuntu-2d => starts unity-2d
- gnome-session --session=gnome => starts Gnome3 (shell)
- gnome-session --session=gnome-fallback => starts the gnome 3.x fallback session
I have just committed a set of patches for x2goruncommand that does
the following:
cmd in ('unity', 'UNITY') and Ubuntu is precise or later -> rewrite cmd to ,,gnome-session''
cmd in ('gnome-session, 'GNOME') and Ubuntu is precise or later -> rewrite cmd to ,,gnome-session-fallback''
This seems to work.
However, I have troubles with X2Go window resizing, esp. when running
a Unity session (I use pyhoca-gui as client).
Maybe my approach given above is not as clean as your ruleset, but we
can ignore GNOME3 (compiz shell) and Unity (compiz shell) for X2Go
anyway (IMHO). We rely on the fallback sessions to be supported in
future and to become more and more stable.
Greets, Mike
--
DAS-NETZWERKTEAM mike gabriel, dorfstr. 27, 24245 barmissen fon: +49 (4302) 281418, fax: +49 (4302) 281419
GnuPG Key ID 0xB588399B mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
On 04/29/2012 04:31 PM, Mike Gabriel wrote:
Hi Stéphane,
thanks for clarifying all this!!!
On So 29 Apr 2012 15:52:32 CEST Stéphane Graber wrote:
To solve the problem properly, you'd need something that understands gnome-session and uses it as it's expected.
Here are some example calls of gnome-session: - gnome-session => starts the default session, on Ubuntu, unity-3d - gnome-session --session=ubuntu => starts unity-3d - gnome-session --session=ubuntu-2d => starts unity-2d - gnome-session --session=gnome => starts Gnome3 (shell) - gnome-session --session=gnome-fallback => starts the gnome 3.x fallback session
I have just committed a set of patches for x2goruncommand that does the following:
cmd in ('unity', 'UNITY') and Ubuntu is precise or later -> rewrite cmd to ,,gnome-session''
cmd in ('gnome-session, 'GNOME') and Ubuntu is precise or later -> rewrite cmd to ,,gnome-session-fallback''
This seems to work.
However, I have troubles with X2Go window resizing, esp. when running a Unity session (I use pyhoca-gui as client).
Maybe my approach given above is not as clean as your ruleset, but we can ignore GNOME3 (compiz shell) and Unity (compiz shell) for X2Go anyway (IMHO). We rely on the fallback sessions to be supported in future and to become more and more stable.
Greets, Mike
Using gnome-session instead of '/etc/X11/Xsession "gnome-session
- --session=ubuntu-2d"' and gnome-session-fallback instead of '/etc/X11/Xsession "gnome-session --session=gnome-fallback"' isn't a good idea as any script in /etc/X11/Xsession.d will be bypassed.
Looking at the current scripts in there, this will mostly affect accessibility, gconf, translated xdg directories, ibus and probably some others. I'd strongly recommend always starting a full desktop session through /etc/X11/Xsession unless you're trying to debug a very specific part of the session.
Stéphane Graber Ubuntu developer http://www.ubuntu.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQIcBAEBCgAGBQJPnVHXAAoJEMY4l01keS1nGYAQANiq8fN+Q5o3mY1o9LdFqG+g ksKk6CKiy/vq2madgxumjxNXbkrEpVvQqwKlJga6N3q+9bhgDaGiRDDi5mbmRUva ucNaW40Ijp81+5SGZqjzQo54jn9zf8FjNEiKGNJ+vw6zdRnz2+HIiIURtKNMu9dY VmZL0pDb+oMGeUDxu8aADGWhRUEy+IdHPUCerBa3U6f6hhAiPxhcubF1mXc82Ovk VtIbGEVxALF20roWVIKiTtAZvMRI5pFu4O8qNg0sbfxPGrmbIg+T05B2kSERAqLU ZvasGnReUEBG8+Yh7o6m9msSv4jctFjno9r37aOz38+iQVIql+IhMeZ36UwLCWi+ eoqsFz0fe5Q7A1pA6n9ZkQ4pHEOaaKI2KgAi/B3K5MAHy5flNNQyTyh5bLjc+3qa 3mTya6ze1totv13g1fOvRyOVeZ4KayV2j7c8J7suSz2aRclftTHm2MmJLLmPBhuD QRkyE/xKiS5UuvBg/UfAPWm7L9baO4s5j9RbwPuNlVCC5Q6mYBLBQIV4pugA5lES OiCcHyI6dDqdyX6tVmovLcQO1SRNMMd2TkuVmfs67Fg+wY4fpRhlCPhDjGHcoFr0 7JOTiJeY59UtIYFAjx4SAaslkimjK4VVGgQmBuS4bPKlD3vYiKe3dqDBBNIaRcK0 lUzO4maJczoP6uOhsM9P =HKb9 -----END PGP SIGNATURE-----
-
Mike Gabriel -
Stéphane Graber