x2go-user May 2020

x2go-user@lists.x2go.org

22 participants
23 discussions

SSH compression
by Simon Reiter 17 May '20

17 May '20

Hi, I already read a few information about the compression used in x2go at https://github.com/ArcticaProject/nx-libs/issues/802. My naive assumption would be that using the compression in x2go makes any compression in the SSH config obsolete, because the compression is only a general one and the one in x2go should suite better for what to be transmitted. Since x2go reads my SSH config, I am now wondering, if the “Compression” option in the config file is ignored when establishing the connection or not. On my current setup, the x2go server requires a ProxyJump, which I set up in the x2go session settings. Does it provide better performance to do it like this or rather open manually a SSH connection to the target host with some local forwarding? And also here with or without compression? I am very happy for some recommendations. Best regards, Simon Reiter

1 0

x2go occasionally stops responding
by Andrew Munn 12 May '20

12 May '20

I can connect to my x2go session running XFCE on CentOS 8.1. The x2go client runs on Windows. Screen updates are still pushed to my client correctly (on-screen clock shows correct time), however sometimes my kb and mouse actions start being ignored. I can disconnect and reconnect to the same session from another windows PC and the results are the same. So something on the CentOS server appears to be the issue, The only way I know to recover is kill the x2go session on the server and reconnect.

1 0

Semi-Offtopic: The sorry state of Landline and Mobile Internet in Germany
by Stefan Baur 11 May '20

11 May '20

Hi List, in an adjacent thread, Alex made a statement that low-bandwidth internet connections are a thing of the past, and thus NX is basically obsolete. I have personal experience to share which proves him wrong. The following internet speeds were recorded in a suburb of a metropolitan area with more than 185 000 residents. And yes, I have the screenshots to prove it, I just don't want to burden the list with them. Residential DSL: Downstream: 5.435 MBit/s max, 5.233 MBit/s average Upstream: 0.465 MBit/s max, 0.427 MBit/s average Ping latency: 23.00 ms min, 28.94 ms average Residential Cable: Downstream: 35.14 MBit/s max, 28.06 MBit/s average Upstream: 2625 MBit/s max, 2.426 MBit/s average Ping latency: 32.00 ms min, 39,38 ms average (iow, higher throughput than DSL, but higher latency) -> This will, however, get worse, as Cable is a shared medium and people in the area are getting fed up with their DSL speeds and are switching over to Cable as their contracts expire. LTE, 1st of 2 providers: 3 out of 5 bars Downstream: 4.715 MBit/s max, 2.029 MBit/s average Upstream: 3.923 MBit/s max, 3.706 MBit/s average Ping latency: 48.00 ms min, 60.50 ms average LTE, 2nd of 2 providers: 2 out of 5 bars Downstream: 0.325 MBit/s max, 0.214 MBit/s average Upstream: 0.325 MBit/s max, 0.225 MBit/s average Ping latency: 64.00 ms min, 79.25 ms average Now step outside and move another 800 meters towards the city limits, and LTE provider 1 drops to UMTS/EDGE (and GSM on a bad day), while LTE provider 2 actually goes up to 3-4 bars and gets 3-7 MBit/s peak rates - but they are short peaks/bursts in an otherwise very mediocre reception. Nothing you want to rely on. Again, this isn't Mooville, West Virgina, with 100 inhabitants and 75 of them cattle, but a larger city in the self-proclaimed high-tech nation Germany. Even Finnish rural areas have better UMTS and LTE coverage than we in Germany have, at the outskirts of our cities. And no, I'm not making this up, I've been to such areas in Finland in the last two years, and I know what the reception there was like. So NX will be here for quite some time, there is a need for it, and for less fancy, but lightweight desktops that work well with it. -Stefan -- BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243

6 11

Re: [X2Go-User] Resizing bug
by Kees Bakker 09 May '20

09 May '20

On 07-05-2020 11:48, Ulrich Sibiller wrote: > 1. well, the current source is this one: > https://github.com/ArcticaProject/nx-libs > 2. go to nx-X11/programs/Xserver/hw/nxagent > 3. edit Screen.c and Window.c. find these lines right at the beginning: > #undef TEST > #undef DEBUG > and change them to > #define TEST > #define DEBUG > > If you want to have really much output that tends to get overwhelming > and unreadable you can do the same for Events.c > > 4. in the toplevel directory run debuild -uc -us > > (for other distros see README.NX-development in the toplevel directory) > > 5. Install the resulting packages > 6. run you session, replicate the issue > 7. post ~/.xg2o/<your session>/session.log (maybe strip it a bit) > > Please ask if you have questions/problems. > Thanks Uli Here is a first set of (stripped) logs. The procedure was simple, but is of course not 100% reproducible because the mouse movements can be different each time. But the import condition is that the window is only **moved** by clicking on the top bar and dragging it somewhat to the right and a bit down. After the move, keep the mouse down and keep it there for two or three seconds. Three remote desktops: (standard) Ubuntu, Gnome Classic, MATE. The remote session size is 800x600. The local desktop is 1440x900. To start I have only grepped the lines with "nxagentChangeScreenConfig:" In the case of MATE the bug does not show up, but in the other two cases it does. ===============MATE==================== nxagentChangeScreenConfig: called for screen [0], width [800] height [600] nxagentChangeScreenConfig: screenInfo.screens[0]->root [0x55aa1ec8be60] nxagentChangeScreenConfig: grabstate [SERVER_GRABBED], client [(nil)] nxagentChangeScreenConfig: Changing config to 800 x 600 nxagentChangeScreenConfig: Xinerama is disabled nxagentChangeScreenConfig: current geometry: 1,56 800x600 nxagentChangeScreenConfig: returning [1] nxagentChangeScreenConfig: called for screen [0], width [800] height [600] nxagentChangeScreenConfig: screenInfo.screens[0]->root [0x55aa1ec8be60] nxagentChangeScreenConfig: grabstate [SERVER_UNGRABBED], client [0x55aa1edd4bb0] nxagentChangeScreenConfig: Changing config to 800 x 600 nxagentChangeScreenConfig: Xinerama is disabled nxagentChangeScreenConfig: current geometry: 119,99 800x600 nxagentChangeScreenConfig: returning [1] nxagentChangeScreenConfig: called for screen [0], width [800] height [600] nxagentChangeScreenConfig: screenInfo.screens[0]->root [0x55aa1ec8be60] nxagentChangeScreenConfig: grabstate [SERVER_UNGRABBED], client [0x55aa1edd4bb0] nxagentChangeScreenConfig: Changing config to 800 x 600 nxagentChangeScreenConfig: Xinerama is disabled nxagentChangeScreenConfig: current geometry: 300,164 800x600 nxagentChangeScreenConfig: returning [1] ===============MATE==================== ===============Ubuntu=================== nxagentChangeScreenConfig: called for screen [0], width [800] height [600] nxagentChangeScreenConfig: screenInfo.screens[0]->root [0x563988763e40] nxagentChangeScreenConfig: grabstate [SERVER_GRABBED], client [(nil)] nxagentChangeScreenConfig: Changing config to 800 x 600 nxagentChangeScreenConfig: Xinerama is disabled nxagentChangeScreenConfig: current geometry: 67,57 800x600 nxagentChangeScreenConfig: returning [1] nxagentChangeScreenConfig: called for screen [0], width [800] height [600] nxagentChangeScreenConfig: screenInfo.screens[0]->root [0x563988763e40] nxagentChangeScreenConfig: grabstate [SERVER_UNGRABBED], client [0x5639888ab690] nxagentChangeScreenConfig: Changing config to 800 x 600 nxagentChangeScreenConfig: Xinerama is disabled nxagentChangeScreenConfig: current geometry: 439,159 800x600 nxagentChangeScreenConfig: returning [1] nxagentChangeScreenConfig: called for screen [0], width [800] height [630] nxagentChangeScreenConfig: screenInfo.screens[0]->root [0x563988763e40] nxagentChangeScreenConfig: grabstate [SERVER_UNGRABBED], client [0x5639888ab690] nxagentChangeScreenConfig: Changing config to 800 x 630 nxagentChangeScreenConfig: Xinerama is disabled nxagentChangeScreenConfig: current geometry: 439,159 800x630 nxagentChangeScreenConfig: returning [1] nxagentChangeScreenConfig: called for screen [0], width [800] height [660] nxagentChangeScreenConfig: screenInfo.screens[0]->root [0x563988763e40] nxagentChangeScreenConfig: grabstate [SERVER_UNGRABBED], client [0x5639888ab690] nxagentChangeScreenConfig: Changing config to 800 x 660 nxagentChangeScreenConfig: Xinerama is disabled nxagentChangeScreenConfig: current geometry: 439,159 800x660 nxagentChangeScreenConfig: returning [1] nxagentChangeScreenConfig: called for screen [0], width [800] height [690] nxagentChangeScreenConfig: screenInfo.screens[0]->root [0x563988763e40] nxagentChangeScreenConfig: grabstate [SERVER_UNGRABBED], client [0x5639888ab690] nxagentChangeScreenConfig: Changing config to 800 x 690 nxagentChangeScreenConfig: Xinerama is disabled nxagentChangeScreenConfig: current geometry: 439,159 800x690 nxagentChangeScreenConfig: returning [1] nxagentChangeScreenConfig: called for screen [0], width [800] height [720] nxagentChangeScreenConfig: screenInfo.screens[0]->root [0x563988763e40] nxagentChangeScreenConfig: grabstate [SERVER_UNGRABBED], client [0x5639888ab690] nxagentChangeScreenConfig: Changing config to 800 x 720 nxagentChangeScreenConfig: Xinerama is disabled nxagentChangeScreenConfig: current geometry: 439,159 800x720 nxagentChangeScreenConfig: returning [1] nxagentChangeScreenConfig: called for screen [0], width [800] height [750] nxagentChangeScreenConfig: screenInfo.screens[0]->root [0x563988763e40] nxagentChangeScreenConfig: grabstate [SERVER_UNGRABBED], client [0x5639888ab690] nxagentChangeScreenConfig: Changing config to 800 x 750 nxagentChangeScreenConfig: Xinerama is disabled nxagentChangeScreenConfig: current geometry: 439,159 800x750 nxagentChangeScreenConfig: returning [1] nxagentChangeScreenConfig: called for screen [0], width [800] height [780] nxagentChangeScreenConfig: screenInfo.screens[0]->root [0x563988763e40] nxagentChangeScreenConfig: grabstate [SERVER_UNGRABBED], client [0x56398886cef0] nxagentChangeScreenConfig: Changing config to 800 x 780 nxagentChangeScreenConfig: Xinerama is disabled nxagentChangeScreenConfig: current geometry: 439,159 800x780 nxagentChangeScreenConfig: returning [1] nxagentChangeScreenConfig: called for screen [0], width [800] height [843] nxagentChangeScreenConfig: screenInfo.screens[0]->root [0x563988763e40] nxagentChangeScreenConfig: grabstate [SERVER_UNGRABBED], client [0x56398886cef0] nxagentChangeScreenConfig: Changing config to 800 x 843 nxagentChangeScreenConfig: Xinerama is disabled nxagentChangeScreenConfig: current geometry: 439,159 800x843 nxagentChangeScreenConfig: returning [1] nxagentChangeScreenConfig: called for screen [0], width [800] height [843] nxagentChangeScreenConfig: screenInfo.screens[0]->root [0x563988763e40] nxagentChangeScreenConfig: grabstate [SERVER_UNGRABBED], client [0x56398886cef0] nxagentChangeScreenConfig: Changing config to 800 x 843 nxagentChangeScreenConfig: Xinerama is disabled nxagentChangeScreenConfig: current geometry: 439,57 800x843 nxagentChangeScreenConfig: returning [1] nxagentChangeScreenConfig: called for screen [0], width [800] height [843] nxagentChangeScreenConfig: screenInfo.screens[0]->root [0x563988763e40] nxagentChangeScreenConfig: grabstate [SERVER_UNGRABBED], client [0x5639888ab690] nxagentChangeScreenConfig: Changing config to 800 x 843 nxagentChangeScreenConfig: Xinerama is disabled nxagentChangeScreenConfig: current geometry: 439,159 800x843 nxagentChangeScreenConfig: returning [1] ===============Ubuntu=================== ===============Gnome Classic================ nxagentChangeScreenConfig: called for screen [0], width [800] height [600] nxagentChangeScreenConfig: screenInfo.screens[0]->root [0x55efc5939ee0] nxagentChangeScreenConfig: grabstate [SERVER_GRABBED], client [(nil)] nxagentChangeScreenConfig: Changing config to 800 x 600 nxagentChangeScreenConfig: Xinerama is disabled nxagentChangeScreenConfig: current geometry: 0,65 800x600 nxagentChangeScreenConfig: returning [1] nxagentChangeScreenConfig: called for screen [0], width [800] height [600] nxagentChangeScreenConfig: screenInfo.screens[0]->root [0x55efc5939ee0] nxagentChangeScreenConfig: grabstate [SERVER_UNGRABBED], client [0x55efc5a96170] nxagentChangeScreenConfig: Changing config to 800 x 600 nxagentChangeScreenConfig: Xinerama is disabled nxagentChangeScreenConfig: current geometry: 205,132 800x600 nxagentChangeScreenConfig: returning [1] nxagentChangeScreenConfig: called for screen [0], width [800] height [637] nxagentChangeScreenConfig: screenInfo.screens[0]->root [0x55efc5939ee0] nxagentChangeScreenConfig: grabstate [SERVER_UNGRABBED], client [0x55efc5a96170] nxagentChangeScreenConfig: Changing config to 800 x 637 nxagentChangeScreenConfig: Xinerama is disabled nxagentChangeScreenConfig: current geometry: 205,132 800x637 nxagentChangeScreenConfig: returning [1] nxagentChangeScreenConfig: called for screen [0], width [800] height [674] nxagentChangeScreenConfig: screenInfo.screens[0]->root [0x55efc5939ee0] nxagentChangeScreenConfig: grabstate [SERVER_UNGRABBED], client [0x55efc5a96170] nxagentChangeScreenConfig: Changing config to 800 x 674 nxagentChangeScreenConfig: Xinerama is disabled nxagentChangeScreenConfig: current geometry: 205,132 800x674 nxagentChangeScreenConfig: returning [1] nxagentChangeScreenConfig: called for screen [0], width [800] height [711] nxagentChangeScreenConfig: screenInfo.screens[0]->root [0x55efc5939ee0] nxagentChangeScreenConfig: grabstate [SERVER_UNGRABBED], client [0x55efc5a96170] nxagentChangeScreenConfig: Changing config to 800 x 711 nxagentChangeScreenConfig: Xinerama is disabled nxagentChangeScreenConfig: current geometry: 205,132 800x711 nxagentChangeScreenConfig: returning [1] nxagentChangeScreenConfig: called for screen [0], width [800] height [748] nxagentChangeScreenConfig: screenInfo.screens[0]->root [0x55efc5939ee0] nxagentChangeScreenConfig: grabstate [SERVER_UNGRABBED], client [0x55efc5a96170] nxagentChangeScreenConfig: Changing config to 800 x 748 nxagentChangeScreenConfig: Xinerama is disabled nxagentChangeScreenConfig: current geometry: 205,132 800x748 nxagentChangeScreenConfig: returning [1] nxagentChangeScreenConfig: called for screen [0], width [800] height [785] nxagentChangeScreenConfig: screenInfo.screens[0]->root [0x55efc5939ee0] nxagentChangeScreenConfig: grabstate [SERVER_UNGRABBED], client [0x55efc5a96170] nxagentChangeScreenConfig: Changing config to 800 x 785 nxagentChangeScreenConfig: Xinerama is disabled nxagentChangeScreenConfig: current geometry: 205,132 800x785 nxagentChangeScreenConfig: returning [1] nxagentChangeScreenConfig: called for screen [0], width [800] height [801] nxagentChangeScreenConfig: screenInfo.screens[0]->root [0x55efc5939ee0] nxagentChangeScreenConfig: grabstate [SERVER_UNGRABBED], client [0x55efc5a96170] nxagentChangeScreenConfig: Changing config to 800 x 801 nxagentChangeScreenConfig: Xinerama is disabled nxagentChangeScreenConfig: current geometry: 205,132 800x801 nxagentChangeScreenConfig: returning [1] nxagentChangeScreenConfig: called for screen [0], width [800] height [801] nxagentChangeScreenConfig: screenInfo.screens[0]->root [0x55efc5939ee0] nxagentChangeScreenConfig: grabstate [SERVER_UNGRABBED], client [0x55efc5a96170] nxagentChangeScreenConfig: Changing config to 800 x 801 nxagentChangeScreenConfig: Xinerama is disabled nxagentChangeScreenConfig: current geometry: 205,65 800x801 nxagentChangeScreenConfig: returning [1] nxagentChangeScreenConfig: called for screen [0], width [800] height [801] nxagentChangeScreenConfig: screenInfo.screens[0]->root [0x55efc5939ee0] nxagentChangeScreenConfig: grabstate [SERVER_UNGRABBED], client [0x55efc5a96170] nxagentChangeScreenConfig: Changing config to 800 x 801 nxagentChangeScreenConfig: Xinerama is disabled nxagentChangeScreenConfig: current geometry: 205,132 800x801 nxagentChangeScreenConfig: returning [1] ===============Gnome Classic================ -- Kees

2 1

Fwd: Resizing bug
by Ulrich Sibiller 09 May '20

09 May '20

Sorry, hit the wrong reply button... ---------- Forwarded message --------- From: Ulrich Sibiller <uli42(a)gmx.de> Date: Thu, May 7, 2020 at 11:48 AM Subject: Re: [X2Go-User] Resizing bug To: Kees Bakker <kees(a)ijzerbout.nl> 1. well, the current source is this one: https://github.com/ArcticaProject/nx-libs 2. go to nx-X11/programs/Xserver/hw/nxagent 3. edit Screen.c and Window.c. find these lines right at the beginning: #undef TEST #undef DEBUG and change them to #define TEST #define DEBUG If you want to have really much output that tends to get overwhelming and unreadable you can do the same for Events.c 4. in the toplevel directory run debuild -uc -us (for other distros see README.NX-development in the toplevel directory) 5. Install the resulting packages 6. run you session, replicate the issue 7. post ~/.xg2o/<your session>/session.log (maybe strip it a bit) Please ask if you have questions/problems. Uli BTW: I have not received your email with the "OK lets hear it", I also have checked the spam folder. On Thu, May 7, 2020 at 10:03 AM Kees Bakker <kees(a)ijzerbout.nl> wrote: > > On 04-05-2020 18:00, Kees Bakker wrote: > > On 03-05-2020 21:28, Ulrich Sibiller wrote: > >> I can instruct you how to build a debugging version of > >> nxagent/x2goagent to get more information in the logs. > >> > > OK. Let's hear it. > > Hey, > > I really need some guidance, please. > > I'm familiar how to build things. But I need to know what program(s) to > debug, how to enable more logging, etc. Especially, what are the things > to be looking for? > > I have two virtualbox VMs that I can use, one as the server and one as > the client. I have cloned git://code.x2go.org/nx-libs.git. Is that the one? > -- > Kees > _______________________________________________ > x2go-user mailing list > x2go-user(a)lists.x2go.org > https://lists.x2go.org/listinfo/x2go-user

1 0

new x2go client for windows
by Paul Borowicz 08 May '20

08 May '20

I've been using the 4.1.2.0 windows client with no issues aside from the clipboard occasionally getting messed up. I usually restart the client and it fixes the problem. I just tried the 4.1.2.2 client, hoping it fixed this. It works fine when I access my OpenSuse server, but when I try to access my Red Hat 7 server it drops with no error output. I tried using the debug console and it also crashes. I can't seem to find a way to output the debug info somewhere I can capture it. Can you point me at the files necessary for to submit a bug report? I see this on the server: Session: Resuming session at 'Wed May 6 08:56:15 2020'. Info: Proxy running in client mode with pid '105652'. Info: Using errors file '/tmp/.x2go-e93313t/C-e93313t-53-1588625310_stDKDE_dp32/session.log'. Info: Using stats file '/tmp/.x2go-e93313t/C-e93313t-53-1588625310_stDKDE_dp32/C-e93313t-53-1588625310_stDKDE_dp32/stats'. Loop: WARNING! Unrecognized session type 'unix-kde-depth_32'. Assuming agent session. Warning: Unrecognized session type 'unix-kde-depth_32'. Assuming agent session. Info: Waiting for connection from 'localhost' on socket 'tcp:*:33747'. Info: Aborting the procedure due to signal '1'. Session: Display failure detected at 'Wed May 6 08:57:15 2020'. Session: Suspending session at 'Wed May 6 08:57:15 2020'. Session: Session suspended at 'Wed May 6 08:57:15 2020'. Session: Resuming session at 'Wed May 6 09:01:22 2020'. Info: Proxy running in client mode with pid '105652'. Info: Using errors file '/tmp/.x2go-e93313t/C-e93313t-53-1588625310_stDKDE_dp32/session.log'. Info: Using stats file '/tmp/.x2go-e93313t/C-e93313t-53-1588625310_stDKDE_dp32/C-e93313t-53-1588625310_stDKDE_dp32/stats'. Loop: WARNING! Unrecognized session type 'unix-kde-depth_32'. Assuming agent session. Warning: Unrecognized session type 'unix-kde-depth_32'. Assuming agent session. Info: Waiting for connection from 'localhost' on socket 'tcp:*:33747'. : Paul Borowicz

3 9

Re: [X2Go-User] Semi-Offtopic: The sorry state of Landline and Mobile Internet in Germany
by J.Witvliet＠mindef.nl 07 May '20

07 May '20

From: "Михайло Падалка" <misha.cn.ua(a)gmail.com<mailto:misha.cn.ua@gmail.com>> Date: Thursday, 7 May 2020 at 20:56:45 To: "Stefan Baur" <X2Go-ML-1(a)baur-itcs.de<mailto:X2Go-ML-1@baur-itcs.de>> Cc: "x2go users" <x2go-user(a)lists.x2go.org<mailto:x2go-user@lists.x2go.org>> Subject: Re: [X2Go-User] Semi-Offtopic: The sorry state of Landline and Mobile Internet in Germany Hmm... Just tested connection from my home (city with ~300 000 people), Ukraine: 1) Cable connection, the cheapest plan I can get here: Downstream: 24.72 Mbps Upstream: 24.27 Mbps Ping: 6 ms Btw, I can easily get symmetrical 90 Mbps if I need that - just need to switch plan. 2) LTE (3 bars): Downstream: 10.96 Mbps Upstream: 11.89 Mbps Ping: 36 ms DSL gives lower speeds of course, due to old cables most of which are >30 years old. But it's not used much nowadays. Tested with speedtest.net<http://speedtest.net> You need to see it slightly broader. Nice that some lucky ones have Mega bit connections up/down and few ms latency; but tháts not standard. Some have to cope with satellite connection, gprs. And even those with *dsl, cable or fibre, one individual might have 8Mb download. But at the other end, it also has to be uploaded. One single connection is no problem, neither 10, or 100. But when dealing with 10,000 parallel connections you ARE aware of excessive bandwidth usage. Dit bericht kan informatie bevatten die niet voor u is bestemd. Indien u niet de geadresseerde bent of dit bericht abusievelijk aan u is toegezonden, wordt u verzocht dat aan de afzender te melden en het bericht te verwijderen. De Staat aanvaardt geen aansprakelijkheid voor schade, van welke aard ook, die verband houdt met risico's verbonden aan het elektronisch verzenden van berichten. This message may contain information that is not intended for you. If you are not the addressee or if this message was sent to you by mistake, you are requested to inform the sender and delete the message. The State accepts no liability for damage of any kind resulting from the risks inherent in the electronic transmission of messages.

1 0

The future of x2gokdrive
by Oleksandr Shneyder 07 May '20

07 May '20

Hello guys, this is for those of you how is wondering in which direction development of x2gokdrive is going. As you may know, I mostly working now on the development of x2go kdrive, which will be used parallel to NX. The client part of x2go kdrive is quite simple and not depends on Xorg, which makes possible to create the clients for mobile and web platforms. I made some proof of concept and quickly developed a simple HTML5 client which is connecting to x2gokdrive over websockets. I used websockify to connect ws to tcp socket. The client has limited support for mouse and keyboard events, no support for cursors, but it's enough to create the image how it'll work. I attached the screenshot of plasma5 session running in browser tab with libreoffice and youtube video running in browser. regards, Alex -- ----------------------------------------------------------- Oleksandr Shneyder | Email: o.shneyder(a)phoca-gmbh.de phoca GmbH | Tel. : 0911 - 14870374 0 Schleiermacherstr. 2 | Fax. : 0911 - 14870374 9 D-90491 Nürnberg | Mobil: 0163 - 49 64 461 Geschäftsführung: Dipl.-Inf. Oleksandr Shneyder Amtsgericht München | http://www.phoca-gmbh.de HRB 196 658 | http://www.x2go.org USt-IdNr.: DE281977973 -----------------------------------------------------------

4 24

Resizing bug
by Kees Bakker 07 May '20

07 May '20

Hi, The client shows a weird resizing bug. I want to know what I can do to analyse this further and report it as a bug. I've mentioned this already earlier on the [X2Go-User] mailing list [1]. I'm surprised that I'm the only one seeing this, because I see it on all the environments that I work on. That is, on all PCs where I am logged in with the standard Ubuntu desktop. My client is Ubuntu (with Ubuntu desktop) and the server side is Ubuntu with a Mate (or Openbox or XFCE) session. Also worthwhile to mention that I don't have my x2go client full screen. When I move(!) the X2GO window, it resizes(!). And when I keep the mouse clicked on the top bar for the move, (and even if I don't move anymore) it keeps resizing until it reaches the maximum height of my local monitor. BTW. That maximum monitor height is not(!) the maximum height of my local window manager. The maximum height for the X2GO client window is the monitor height minus the height of the top bar. What I also noticed is that the height increments in steps of 37 pixels. I'm not sure, but I think the the height of the top bar in the Ubuntu desktop is 37. Here are the last few lines of the remote session.log. I start with a session of 800x600 Info: Screen [0] resized to geometry [799x600] fullscreen [0]. Info: Screen [0] resized to geometry [799x674] fullscreen [0]. Info: Screen [0] resized to geometry [798x674] fullscreen [0]. Info: Screen [0] resized to geometry [798x711] fullscreen [0]. Info: Screen [0] resized to geometry [797x711] fullscreen [0]. Info: Screen [0] resized to geometry [797x748] fullscreen [0]. Info: Screen [0] resized to geometry [796x748] fullscreen [0]. Info: Screen [0] resized to geometry [796x748] fullscreen [0]. Kind regards, Kees Bakker [1] https://lists.x2go.org/pipermail/x2go-user/2020-April/005936.html

2 6

Re: [X2Go-User] multiple instances of x2go server appearing in tray
by brian 05 May '20

05 May '20

Stefan: Well you are correct in that it doesn't seem to be needed. I disabled it as a start-up application and it makes no difference on my ability to log in to the remote machine. Thinking about it now, I'm not sure of it's intended use; if I'm logging into an unattended remote machine and starting a new session, then desktop sharing is not required. If I'm logging in to a remote machine to share a desktop with someone local to it at the other end, they can always start the desktop sharing service manually. Either way it's not an issue. Never the less, thank you for your informative responses. brian > Message: 3 > Date: Mon, 4 May 2020 19:17:15 +0200 > From: Stefan Baur <X2Go-ML-1(a)baur-itcs.de> > To: x2go-user(a)lists.x2go.org > Subject: Re: [X2Go-User] multiple instances of x2go server appearing > in tray > Message-ID: <78d6d9c8-83c6-adba-c4cf-45197237add2(a)baur-itcs.de> > Content-Type: text/plain; charset=utf-8 > > Am 04.05.20 um 19:03 schrieb b salzano: > > Stephan: Abject apologies - I misstated the issue. The tray icon is > indeed > > for x2go desktopsharing, and that is exactly the function that I > need to > > use. So the question I meant to ask, then, is whether there is a > config > > file somewhere that will prevent more than one instance of > desktopsharing > > to run in a particular account. > > I must admit, I've never really used desktopsharing that much. So my > memory may be hazy. > > But if I remember correctly, desktopsharing consists of two packages > - > one for actually handling desktopsharing, and one for letting the > user > know when desktopsharing is active (and providing users with a way to > toggle it on and off). > > So if you could live with it being permanently enabled with no visual > indication, it would still suffice to uninstall this particular > package. > > x2godesktopsharing is the one for the GUI applet, while > x2goserver-desktopsharing does all the heavy lifting in the > background, > if I'm not mistaken. > > > > Xfce (what I normally use) doesn't provide any options to manage > that > > aspect. Perhaps someone knows what config file to look at? > > Sorry, someone else will have to answer that part. As I said I'm not > really a user of desktopsharing myself - plus not a user of Xfce. > > I do wonder, though, do you really need desktopsharing? > > I mean, yes, obviously, if you're trying to support a remote user > somewhere, you will need it. > > But if you're trying to take over your own desktop at work so you can > work from home, using a native X2Go session from the very start > (connecting to localhost:22 while at work, and connecting to > your-companys-external-ip:port while at home) will make things both > easier and faster for you. The only thing to remember is that when > logging in to start your X2Go-Xfce session at work, you need to pick > a > different desktop environment (a minimalistic Openbox with X2GoClient > will suffice, maybe throw in tint2 as a task bar if you really need > one) > - because running the same Desktop Environment twice, under the same > user account, may cause issues. > > -Stefan > > -- > BAUR-ITCS UG (haftungsbeschränkt) > Geschäftsführer: Stefan Baur > Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 > Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243

2 1

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

x2go-user May 2020