Hi all,
Running x2go server on ubuntu (12.04), and my terminal is a mac running XQuartz (with quartz-wm) and the Qt x2go client.
I used the Published apps rootless and spawn a few windows from the server. Things run pretty smoothly and Im happy with the performance.
The thing that hurts is related to window management. Heres a relevant output: $ echo $DISPLAY :50 $ wmctrl -l Cannot get client list properties. (_NET_CLIENT_LIST or _WIN_CLIENT_LIST) $ wmctrl -m Cannot get window manager info properties. (_NET_SUPPORTING_WM_CHECK or _WIN_SUPPORTING_WM_CHECK)
Whereas if I run the same commands natively on the mac, XQuartz responds correctly to wmctrl.
So the problem affects pretty much all tools related to window management I tried.
I am no X11 expert, but I am a developer and very familiar with linux systems. Right now I just need a few pointers, any thoughts?
Thanks in advance! /jfd
Hi Jeff,
On Do 14 Nov 2013 19:58:14 CET, Jean-Francois Dagenais wrote:
Hi all,
Running x2go server on ubuntu (12.04), and my terminal is a mac
running XQuartz (with quartz-wm) and the Qt x2go client.I used the Published apps rootless and spawn a few windows from the server. Things run pretty smoothly and Im happy with the performance.
The thing that hurts is related to window management. Heres a
relevant output: $ echo $DISPLAY :50 $ wmctrl -l Cannot get client list properties. (_NET_CLIENT_LIST or _WIN_CLIENT_LIST) $ wmctrl -m Cannot get window manager info properties. (_NET_SUPPORTING_WM_CHECK or _WIN_SUPPORTING_WM_CHECK)Whereas if I run the same commands natively on the mac, XQuartz responds correctly to wmctrl.
So the problem affects pretty much all tools related to window management I tried.
I am no X11 expert, but I am a developer and very familiar with
linux systems. Right now I just need a few pointers, any thoughts?
With published applications you have to use wmctrl on your local
display (:0) not on the X2Go display (:50 or above...).
Mike
--
DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976 148
GnuPG Key ID 0x25771B31 mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...
On Nov 16, 2013, at 4:17, Mike Gabriel <mike.gabriel@das-netzwerkteam.de> wrote:
With published applications you have to use wmctrl on your local display (:0) not on the X2Go display (:50 or above...).
Mike
Thanks for the answer Mike, is there any way around that? I.e. a nxagent option or something? The reason is it would be nice to implement the window management trickery part on the server side, and not have to redo the setup on all my client terminals. Plus, the server is ubuntu, which has all the required packages readily available, whereas on mac, I have to use macports which has some quirks here and there.
Thanks again for the help guys! Cheers. /jfd
Hi jfd,
On Sa 16 Nov 2013 19:08:10 CET, Jean-Francois Dagenais wrote:
On Nov 16, 2013, at 4:17, Mike Gabriel
<mike.gabriel@das-netzwerkteam.de> wrote:With published applications you have to use wmctrl on your local
display (:0) not on the X2Go display (:50 or above...).Mike
Thanks for the answer Mike, is there any way around that? I.e. a
nxagent option or something? The reason is it would be nice to implement the window
nxagent is a display manager, not a window manager. So, if you you
want to apply some magic to X windows running on top of nxagent, you
have to use display manager tools like ,,xprop''.
management trickery part on the server side, and not have to redo the setup on all my client terminals. Plus, the server is ubuntu, which has all the required packages readily available, whereas on mac, I have to use macports which has some quirks here and there.
I'd be interested in the trickery you want to apply to the published
applications.
greets, Mike
DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976 148
GnuPG Key ID 0x25771B31 mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...
Hi, just following up on this old thread…
On Nov 17, 2013, at 3:13, Mike Gabriel <mike.gabriel@das-netzwerkteam.de> wrote:
Hi jfd,
On Sa 16 Nov 2013 19:08:10 CET, Jean-Francois Dagenais wrote:
On Nov 16, 2013, at 4:17, Mike Gabriel <mike.gabriel@das-netzwerkteam.de> wrote:
With published applications you have to use wmctrl on your local display (:0) not on the X2Go display (:50 or above...).
Mike
Thanks for the answer Mike, is there any way around that? I.e. a nxagent option or something? The reason is it would be nice to implement the window
nxagent is a display manager, not a window manager.
I understand that. Here’s what I meant. If I run ‘xprop’ from a linux gnome-terminal which displays through nxagent -> nxproxy -> Local X server, I get a very output than when I run xprop locally on my mac from the local terminal app (straight local connection to XQuartz). So the nxagent/nxproxy tunnel somehow breaks a few pieces of information and control paths. I was just wondering if this could be worked around somehow.
So, if you you want to apply some magic to X windows running on top of nxagent, you have to use display manager tools like ,,xprop''.
management trickery part on the server side, and not have to redo the setup on all my client terminals. Plus, the server is ubuntu, which has all the required packages readily available, whereas on mac, I have to use macports which has some quirks here and there.
I'd be interested in the trickery you want to apply to the published applications.
‘Trickery’ is a bad choice of words. To keep it simple, let’s just say I would like to use the ‘wmctrl’ program, but it should run from the remote machine (my ubuntu box that runs nxagent). Right now, I get: $ wmctrl -l Cannot get client list properties. (_NET_CLIENT_LIST or _WIN_CLIENT_LIST)
Why is that?
-
Jean-Francois Dagenais -
Mike Gabriel