Re: [X2Go-Dev] Different behavior of X2Go Client from Desktop and TCE

Am 18.05.2018 um 00:39 schrieb Nable: > On Fri, May 18, 2018 at 1:18 AM, Stefan Baur > wrote: > > [...] > The problem arises on systems that have a Window Manager (like OpenBox), > but no task bar, so no way to un-minimize the

Re: [X2Go-Dev] Different behavior of X2Go Client from Desktop and TCE

On Fri, May 18, 2018 at 1:18 AM, Stefan Baur wrote: > [...] > The problem arises on systems that have a Window Manager (like OpenBox), > but no task bar, so no way to un-minimize the X2Go/NX-window once the > user hits the magic pixel. Are you sure that task bar is

Re: [X2Go-Dev] Different behavior of X2Go Client from Desktop and TCE

Am 17.05.2018 um 23:21 schrieb Ulrich Sibiller: > Also I suppose we should automatically disable the magic pixel when > there's no window manager running. What do you think? Wait, no. Let's not get confused here. Magic Pixel *is* effectively disabled when there is no Window Manager running,

Re: [X2Go-Dev] Different behavior of X2Go Client from Desktop and TCE

Am 17.05.2018 um 23:46 schrieb Ulrich Sibiller: >>> Also I suppose we should automatically disable the magic pixel when >>> there's no window manager running. What do you think? >> I'd say your thinking is a bit too Linux-centric here. >> Or would your code also detect a running MS Windows / macOS

Re: [X2Go-Dev] Different behavior of X2Go Client from Desktop and TCE

Am 17.05.2018 um 23:46 schrieb Ulrich Sibiller: >> Because the magic pixel is useful on those platforms, too - especially >> Windows, where pressing Ctrl+Alt+F regularly crashes the X server, >> instead of toggling fullscreen mode. > We could file vcxsrv bug for that. We "just" need to track it

Re: [X2Go-Dev] Different behavior of X2Go Client from Desktop and TCE

Am 17.05.2018 um 23:21 schrieb Ulrich Sibiller: > Also I suppose we should automatically disable the magic pixel when > there's no window manager running. What do you think? I'd say your thinking is a bit too Linux-centric here. Or would your code also detect a running MS Windows / macOS

Re: [X2Go-Dev] Different behavior of X2Go Client from Desktop and TCE

On Thu, May 17, 2018 at 3:40 PM, Stefan Baur wrote: > Am 17.05.2018 um 15:32 schrieb Walid MOGHRABI: >> Anyway, having to install a WM in a TCE is not dumb stuff, it makes TCE acts >> much more like a real desktop than without it (and thus, easier to debug and >> a more

Re: [X2Go-Dev] Different behavior of X2Go Client from Desktop and TCE

Am 17.05.2018 um 15:32 schrieb Walid MOGHRABI: > Anyway, having to install a WM in a TCE is not dumb stuff, it makes TCE acts > much more like a real desktop than without it (and thus, easier to debug and > a more uniform setup than with local fat client). And that's why we added OpenBox to

Re: [X2Go-Dev] Different behavior of X2Go Client from Desktop and TCE

Anyway, having to install a WM in a TCE is not dumb stuff, it makes TCE acts much more like a real desktop than without it (and thus, easier to debug and a more uniform setup than with local fat client). The real problem was this was not part of the x2gothinclient-displaymanager install and so,

Re: [X2Go-Dev] Different behavior of X2Go Client from Desktop and TCE

Am 17.05.2018 um 14:33 schrieb Ulrich Sibiller: > On Thu, May 17, 2018 at 2:13 PM, Oleksandr Shneyder > wrote: >> Nope, it looks for me, that nxproxy window get information about screens >> from WM. If WM is not started, nxproxy get just the window geometry. >> With

Re: [X2Go-Dev] Different behavior of X2Go Client from Desktop and TCE

On Thu, May 17, 2018 at 2:13 PM, Oleksandr Shneyder wrote: > Nope, it looks for me, that nxproxy window get information about screens > from WM. If WM is not started, nxproxy get just the window geometry. > With started WM we have correct display information on server

Re: [X2Go-Dev] Different behavior of X2Go Client from Desktop and TCE

Am 17.05.2018 um 13:59 schrieb Ulrich Sibiller: > I am suspecting this has to do with the fact that openbox is the first > client to TCEs X server. Can someone try and run an > xterm/xclock/xlogo/whatever (and no WM) prior to x2goclient? What would you expect to happen when another application is

Re: [X2Go-Dev] Different behavior of X2Go Client from Desktop and TCE

On Thu, May 17, 2018 at 1:52 PM, Stefan Baur wrote: > Am 17.05.2018 um 13:02 schrieb Mike Gabriel: >> >> Same issue here with pyhoca-cli and Arctica Greeter's remote logon feature. >> >> I'll read the full scope of this mail thread and join in tomorrow... > > TL;DR: > No

Re: [X2Go-Dev] Different behavior of X2Go Client from Desktop and TCE

Am 17.05.2018 um 13:02 schrieb Mike Gabriel: > > Same issue here with pyhoca-cli and Arctica Greeter's remote logon feature. > > I'll read the full scope of this mail thread and join in tomorrow... TL;DR: No local Window Manager equals no working XINERAMA. TCE-NFS has none, so fails. TCE-Live

Re: [X2Go-Dev] Different behavior of X2Go Client from Desktop and TCE

Hi Stefan, Alex, On Mi 16 Mai 2018 15:00:33 CEST, Stefan Baur wrote: Hi Alex, Sorry, no solution yet, but we ran into the same issue yesterday/today (with TCE-Live, not NFS). What's worse is that it happens sometimes, but not always. At first we thought it depended on the Desktop