FVWM: x2go fullscreen and fvwm?
I've just been experimenting with running x2go, and when I tell the client to run fullscreen, it apparently tells fvwm don't manage me, which works OK till I use the x2go hotkey Ctrl-Alt-M to minimize the fullscreen client and get back to my normal local desktop. There doesn't appear to be any way to restore this un-managed client now. Has anyone already figured out a way to best operate fullscreen x2go under fvwm? Tell it to grab the window anyway, but put the client window at 0,0 with the decorations off the screen perhaps? (Is there an easy way to refer to the position of the window inside the decorations in fvwm?)
Re: FVWM: x2go fullscreen and fvwm?
On 31 July 2015 at 13:36, Tom Horsley horsley1...@gmail.com wrote: I've just been experimenting with running x2go, and when I tell the client to run fullscreen, it apparently tells fvwm don't manage me, which works OK till I use the x2go hotkey Ctrl-Alt-M to minimize the fullscreen client and get back to my normal local desktop. Can you please run xprop(1) on this window before and after you've fullscreened this thing? It's not allowed to be unmanaged *after* it has mapped, so I suspect something else is going on. There doesn't appear to be any way to restore this un-managed client now. I doubt it's unmanaged. Get me some xprop(1) output, please. -- Thomas Adam
Re: FVWM: x2go fullscreen and fvwm?
On Fri, 31 Jul 2015 13:43:24 +0100
Thomas Adam wrote:
Can you please run xprop(1) on this window before and after you've
fullscreened this thing? It's not allowed to be unmanaged *after* it
has mapped, so I suspect something else is going on.
It isn't going unmanaged after mapping, it is (I think) a brand new window
starting out fullscreen and unmanaged. Certainly after I minimize
it with the hot key, it doesn't show up in the window list in
fvwm.
It is kinda difficult to run xprop because I can't get to my desktop
with the client program fullscreened :-). I'll see if I can ssh in
and dig up the windows that way. OK, I think I got it:
WM_COLORMAP_WINDOWS(WINDOW): window id # 0x240003c, 0x2400023
WM_PROTOCOLS(ATOM): protocols WM_DELETE_WINDOW
WM_HINTS(WM_HINTS):
bitmap id # to use for icon: 0x240001e
bitmap id # of mask for icon: 0x2400020
WM_NORMAL_HINTS(WM_SIZE_HINTS):
program specified location: 0, 0
program specified minimum size: 80 by 60
program specified maximum size: 1920 by 1080
WM_COMMAND(STRING) = { /usr/lib64/nx/../x2go/bin/x2goagent, -extension,
XFIXES, -nolisten, tcp, -nolisten, tcp, -dpi, 96, -D, -auth,
/home/tom/.Xauthority, -name, X2GO-tom-50-1438347898_stDxterm_dp24, :50
}
WM_ICON_NAME(STRING) = X2GO-tom-50-1438347898_stDxterm_dp24
WM_NAME(STRING) = X2GO-tom-50-1438347898_stDxterm_dp24
WM_CLASS(STRING) = X2GoAgent, X2GoAgent
Re: FVWM: x2go fullscreen and fvwm?
On Fri, 31 Jul 2015 09:14:28 -0400 Tom Horsley wrote: It isn't going unmanaged after mapping, it is (I think) a brand new window starting out fullscreen and unmanaged. Certainly after I minimize it with the hot key, it doesn't show up in the window list in fvwm. Actually I take it all back. I'm just blind. I could see the window in the window list for some reason. Sorry about the noise, everything is actually perfect :-).
Re: FVWM: x2go fullscreen and fvwm?
On 31 July 2015 at 14:33, Tom Horsley horsley1...@gmail.com wrote: On Fri, 31 Jul 2015 09:14:28 -0400 Tom Horsley wrote: It isn't going unmanaged after mapping, it is (I think) a brand new window starting out fullscreen and unmanaged. Certainly after I minimize it with the hot key, it doesn't show up in the window list in fvwm. Actually I take it all back. I'm just blind. I could see the window in the window list for some reason. Sorry about the noise, everything is actually perfect :-). Thanks; one less thing I need to respond to. Oh wait... ;P -- Thomas Adam
