Am 21.12.2017 um 13:13 schrieb Robert Dinse:

Now it does not and I do not see any way of reverting to the previous version.

Restore from backup? Keep a local, archiving mirror (would probably make your hosting customers happy, too, as downloads would be faster and not count against their traffic, since it would be all internal)?

Seems like Ubuntu doesn't have a snapshot server (Debian does) that would allow you to go back in time with the entire repository (<trump>SAD!</trump>). However, the answer provided here: <https://askubuntu.com/questions/499871/is-there-ubuntus-analogue-of-snapshot-debian-org/792264#792264> might help you.

Kind Regards, Stefan Baur

-- 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

  Is there any place one can find instructions for building from source?

It appears there are about 25 projects rather than some consolidated whole.

-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting. Knowledgeable human assistance, not telephone trees or script readers. See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.

On Thu, 21 Dec 2017, Robert Dinse wrote:

Date: Thu, 21 Dec 2017 05:19:17 -0800 (PST) From: Robert Dinse <nanook@eskimo.com> To: Stefan Baur <X2Go-ML-1@baur-itcs.de> Cc: x2go-user@lists.x2go.org Subject: Re: [X2Go-User] New x2go broken on Ubuntu 17.10

If I knew what file(s) to pull as opposed to what packages, then I could

retrieve it from a backup.

-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting. Knowledgeable human assistance, not telephone trees or script readers. See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.

On Thu, 21 Dec 2017, Stefan Baur wrote:

...

Date: Thu, 21 Dec 2017 13:33:31 +0100 From: Stefan Baur <X2Go-ML-1@baur-itcs.de> To: x2go-user@lists.x2go.org Subject: Re: [X2Go-User] New x2go broken on Ubuntu 17.10

Am 21.12.2017 um 13:13 schrieb Robert Dinse:

...

Now it does not and I do not see any way of reverting to the previous version.

Restore from backup? Keep a local, archiving mirror (would probably make your hosting customers happy, too, as downloads would be faster and not count against their traffic, since it would be all internal)?

Seems like Ubuntu doesn't have a snapshot server (Debian does) that would allow you to go back in time with the entire repository (<trump>SAD!</trump>). However, the answer provided here: <https://askubuntu.com/questions/499871/is-there-ubuntus-analogue-of-snapshot-debian-org/792264#792264> might help you.

Kind Regards, Stefan Baur

-- 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

• On 12/21/2017 01:13 PM, Robert Dinse wrote:

  I have four machines running 17.10 as servers and a work station running

Ubuntu 17.10. I have the client set for display 1, so it gives me a full screen but I can switch to other things. My monitor is 1920x1080. My client version is 4.1.1.1 (Qt - 4.8.7). I have tried it both with the libs supplied from launchpad and I've also tried it with the latest nx-libs compiled from source. Same results either way. The server version that is not working properly for me is 4.1.0.0-0~1453~ubuntu17.10.1.

The X2Go Server version is irrelevant in this case.

  An update I applied on December 19th at 23:20 broke it.  Prior to that

it worked peroperly. Two days ago it worked properly for me too. Now it does not and I do not see any way of reverting to the previous version.

Yep, about three days ago, I switched Launchpad to the new Arctica version of nx-libs, which seems to trigger your issues.

This version has been used by only a few people during the last two years, but we have to switch to it ASAP as part of X2Go as well for our server components to be able to land into the official Ubuntu repositories for 18.04 LTS.

The change should have been carried out more than a week ago, but due to some unforeseen bug within launchpad itself (and my lack of looking at the repository import status), this was delayed until I switched the repository to a native git import about three days ago.

Unfortunately, launchpad doesn't provide snapshots of older packages. Once a new version was uploaded to the repository, older versions are deleted. This deletions happens roughly every few hours or once a day.

Even though, we cnanot switch back to the old version. It's crucial to carry out this migration - in doubt even with remaining problems.

Testing of course is always welcome. I haven't heard about the problems you described yet, but of course that doesn't have to mean anything.

What does "but I can't use the bottom half or approximately right third of my desktop now" mean exactly? Are these regions not drawn at all? Or are they drawn but insensitive to clicks? Is the window big enough to cover the whole screen, or is local desktop stuff visible within these regions (which would indicate that the window is too small)?

Mihai

  I only know that before the last updates from the nightly build repository 

it was working properly with Ubuntu 17.10 and Mate. And if instead of using display 1, I use full screen, it also works properly. I will give it a try with xfce or lxde to see if the problem is window manager specific.

-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting. Knowledgeable human assistance, not telephone trees or script readers. See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.

On Sat, 23 Dec 2017, Mihai Moldovan wrote:

Date: Sat, 23 Dec 2017 06:52:57 +0100 From: Mihai Moldovan <ionic@ionic.de> To: Robert Dinse <nanook@eskimo.com> Cc: x2go-user@lists.x2go.org Subject: Re: [X2Go-User] New x2go broken on Ubuntu 17.10

• On 12/22/2017 08:08 PM, Mihai Moldovan wrote:

...

What does "but I can't use the bottom half or approximately right third of my desktop now" mean exactly? Are these regions not drawn at all? Or are they drawn but insensitive to clicks? Is the window big enough to cover the whole screen, or is local desktop stuff visible within these regions (which would indicate that the window is too small)?

I've played around with a 17.10 VM with Ubuntu MATE (not pure MATE) and noticed that:

• with the legacy nx-libs version: o the remote session had an 800x600 window within the proxy window (that was correctly sized according to the fake fullscreen mode) o I got an xrandr error message upon session startup (version too old)
• with the new nx-libs version: o everything looked huge, like you said o in MATE's appearance dialog, the "DPI" was set to 200 for some reason o xpyinfo reported a (more correct) value of 95 o xrandr reported a *current* resolution of 800x600 and I haven't been able to change it to a saner value

My current suspicion is that

• MATE needs a newer version of the XRANDR extension to resize itself properly
• nxagent for some reason passes through a wrong resolution value
• MATE tries to cope with the weird should-be-high-resolution-but-is-low-instead by situation by raising the DPI value

I guess I'll have to figure out where this discrepancy is coming from.

Mihai

xfce also works, kde does not work at all, get the plasma by kde at the bottom right then all black screen except mouse cursor.

-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting. Knowledgeable human assistance, not telephone trees or script readers. See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.

On Sat, 23 Dec 2017, Robert Dinse wrote:

Date: Sat, 23 Dec 2017 00:04:56 -0800 (PST) From: Robert Dinse <nanook@eskimo.com> To: Mihai Moldovan <ionic@ionic.de> Cc: x2go-user@lists.x2go.org Subject: Re: [X2Go-User] New x2go broken on Ubuntu 17.10

Ok, I just tried it with lxde, and with lxde display 1 works properly. 

With the new libs the nightly build worked properly until a few days ago when there were updates to many of the x2go components. So there is an aspect specific to Mate. But Mate worked properly with the previous version and works properly locally. I'm running Mate on my local workstation as well, which is also Ubuntu 17.10.

-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting. Knowledgeable human assistance, not telephone trees or script readers. See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.

On Sat, 23 Dec 2017, Mihai Moldovan wrote:

...

Date: Sat, 23 Dec 2017 06:52:57 +0100 From: Mihai Moldovan <ionic@ionic.de> To: Robert Dinse <nanook@eskimo.com> Cc: x2go-user@lists.x2go.org Subject: Re: [X2Go-User] New x2go broken on Ubuntu 17.10

• On 12/22/2017 08:08 PM, Mihai Moldovan wrote:

...

What does "but I can't use the bottom half or approximately right third of my desktop now" mean exactly? Are these regions not drawn at all? Or are they drawn but insensitive to clicks? Is the window big enough to cover the whole screen, or is local desktop stuff visible within these regions (which would indicate that the window is too small)?

I've played around with a 17.10 VM with Ubuntu MATE (not pure MATE) and noticed that:

• with the legacy nx-libs version: o the remote session had an 800x600 window within the proxy window (that was correctly sized according to the fake fullscreen mode) o I got an xrandr error message upon session startup (version too old)
• with the new nx-libs version: o everything looked huge, like you said o in MATE's appearance dialog, the "DPI" was set to 200 for some reason o xpyinfo reported a (more correct) value of 95 o xrandr reported a *current* resolution of 800x600 and I haven't been able to change it to a saner value

My current suspicion is that properly

• MATE needs a newer version of the XRANDR extension to resize itself

• nxagent for some reason passes through a wrong resolution value
• MATE tries to cope with the weird should-be-high-resolution-but-is-low-instead by situation by raising the DPI value

I guess I'll have to figure out where this discrepancy is coming from.

Mihai

---

x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user

  But this went from working to not working after an upgrade of x2go, I

did not recompile the libs until after it broke in an attempt to fix it.

-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting. Knowledgeable human assistance, not telephone trees or script readers. See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.

On Sun, 24 Dec 2017, Mihai Moldovan wrote:

Date: Sun, 24 Dec 2017 00:50:38 +0100 From: Mihai Moldovan <ionic@ionic.de> To: Robert Dinse <nanook@eskimo.com> Cc: x2go-user@lists.x2go.org Subject: Re: [X2Go-User] New x2go broken on Ubuntu 17.10

• On 12/23/2017 09:04 AM, Robert Dinse wrote:

...

  Ok, I just tried it with lxde, and with lxde display 1 works properly.

With the new libs the nightly build worked properly until a few days ago when there were updates to many of the x2go components. So there is an aspect specific to Mate. But Mate worked properly with the previous version and works properly locally. I'm running Mate on my local workstation as well, which is also Ubuntu 17.10.

There's definitely something amiss. My results differ from yours, but I think I have found out why that is.

Running either XFCE or MATE with the *new* nx-libs version resulted in the following environment:

ionic@ubuntu:~$ cat /tmp/.x2go-ionic/C-ionic-50-1514044160_stDXFCE_dp24/options nx/nx,[...],geometry=800x600,resize=1,fullscreen=0,[...]:50 ionic@ubuntu:~$ xrandr Screen 0: minimum 320 x 240, current 800 x 600, maximum 1920 x 1200 NX1 connected 1920x1080+0+0 0mm x 0mm nx_1920x1080 60.00*

That just isn't right. The returned screen resolution should match the visual window dimensions (i.e., 1920x1080 or a bit lower iff window decorations are used on the local machine), not the initial geometry passed via options (i.e., 800x600).

MATE tries to make the best out of this situation and maps the 800x600 virtual screen size to a 1920x1080 physical display resolution, resulting in a very high DPI value (that, weirdly, will not show up in xdpyinfo or the like).

If you set the DPI value manually in MATE's font settings, this will override the workaround MATE employs to some degree, but not completely. The actual screen size is still limited in a non-trivial way and maximizing a window within the session will lead to very odd results.

XFCE behaves differently, but also faces the same problem. Here, instead of simulating a high DPI value, the screen is split into smaller 800x600 "sections". Applications can not be maximized to any bigger value than the first/top left 800x600 section, while, interestingly, the dock/bottom panel floats at the bottom of the screen as it should and is not confined to the first 800x600 section only. The top panel also stretches over all sections.

In all my tests, I have so far been unable to actually change the virtual screen size. That's probably what I need to look into next.

The situation is different for the old, legacy version of nx-libs: the session is opened seemingly in fullscreen (it's really just "fake fullscreen", but bear with me), but the viewport is only 800x600 in size.

Resizing is possible via XFCE's display utility (selecting a resolution of 1920x1080), which then sticks and is probably the reason for it working in your case - you must have done so some time ago. In a clean environment, this wasn't the case of course. For MATE, the situation is more bleak, since MATE's display utility depends upon XRANDR 1.3+, which the old nx-libs version does not provide. Hence, the only possibility to resize the session is to use the xrandr tool and the XRANDR 1.1/1.0 interface (i.e., -s). Xrandr 1.2 (--output ... --mode ...) fails in RRGetScreenResourcesCurrent. This change of course is only temporary and will not be saved upon session termination.

Example output of xrandr:

ionic@ubuntu:~$ xrandr xrandr: Failed to get size of gamma for output default Screen 0: minimum 320 x 240, current 800 x 600, maximum 1920 x 1200 default connected 800x600+0+0 0mm x 0mm [a lot of other modes I don't care about] 800x600 60.00* [a lot of other modes I don't care about]

Note, that, if you're testing on an unclean, upgraded system and already have set a custom resolution in MATE itself previously (I guess that older MATE versions didn't require XRANDR 1.3+ yet), then you probably side-stepped this issue.

Mihai

   What I am trying to say is the behavior changed from a working to

non-working state without my having changed nx-libs on this end, I only changed them after things broke.

-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting. Knowledgeable human assistance, not telephone trees or script readers. See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.

On Sun, 24 Dec 2017, Mihai Moldovan wrote:

Date: Sun, 24 Dec 2017 01:17:03 +0100 From: Mihai Moldovan <ionic@ionic.de> To: Robert Dinse <nanook@eskimo.com> Cc: x2go-user@lists.x2go.org Subject: Re: [X2Go-User] New x2go broken on Ubuntu 17.10

• On 12/24/2017 12:56 AM, Robert Dinse wrote:

...

  But this went from working to not working after an upgrade of x2go, I

did not recompile the libs until after it broke in an attempt to fix it.

Yes...? Where's the "but" coming from? Did I ever claim otherwise?

It's obvious that the new nx-libs version behaves differently and in this case not particularly well.

I'll have to figure out why that is and fix it.

Mihai

  I had built the libs from source but perhaps the repository version

overwrote them.

-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting. Knowledgeable human assistance, not telephone trees or script readers. See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.

On Sun, 24 Dec 2017, Mihai Moldovan wrote:

Date: Sun, 24 Dec 2017 03:16:19 +0100 From: Mihai Moldovan <ionic@ionic.de> To: Robert Dinse <nanook@eskimo.com> Cc: x2go-user@lists.x2go.org Subject: Re: [X2Go-User] New x2go broken on Ubuntu 17.10

• On 12/24/2017 02:02 AM, Robert Dinse wrote:

...

   What I am trying to say is the behavior changed from a working to

non-working state without my having changed nx-libs on this end, I only changed them after things broke.

Huh, that would be weird. nx-libs changed in the nightly repository on Dec 21, so that sounds close enough to the breakage date.

If you would have updated on Dec 19 exactly, you would have run into the upgrade issue that was brought up on the -dev mailing list a day later. Given that the repository was in an inconsistent state back then, upgrading wouldn't have worked in the first place.

Mihai

  It about 99.99% works, one behavior that is still off is if I have Window

Snapping enabled in Mate Tweak (I normally don't so this particular bug does not cause me any problems), when it's in a corner a Mate terminal only expands to have the screen horizontally but full screen vertically. This is the only thing I can find broke. With window snapping off, the way I normally have it configured, I can expand a mate terminal full screen and it uses the whole screen, I can move it anywhere, synaptic now works properly, drop down menus work properly, so it makes all the important things work :)

-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting. Knowledgeable human assistance, not telephone trees or script readers. See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.

On Sun, 24 Dec 2017, Mihai Moldovan wrote:

Date: Sun, 24 Dec 2017 03:26:30 +0100 From: Mihai Moldovan <ionic@ionic.de> To: Robert Dinse <nanook@eskimo.com> Cc: x2go-user@lists.x2go.org Subject: Re: [X2Go-User] New x2go broken on Ubuntu 17.10

• On 12/24/2017 03:18 AM, Robert Dinse wrote:

...

  I had built the libs from source but perhaps the repository version

overwrote them.

Maybe.

In any case, if you specify "-rrxinerama" (mind the spelling and single dash at the beginning) in /etc/x2go/x2goagent.options, can you confirm that it's working again regarding your use case?

Mihai

  That could be, can you shoot me that option one more time, I accidentally

deleted your e-mail, I found machines that are still broke and they have different versions of the libs than the ones that are working.

  libnx-x11-6 on the machine(s) that is working is version 

2:3.5.99.9-0.1+git20170830.2839+14.04.release 1.

  libnx-x11-6 on the machine(s) that are not working is version

2:3.5.99.12-0~201712191523~ubuntu17.10.1.

-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting. Knowledgeable human assistance, not telephone trees or script readers. See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.

On Sun, 24 Dec 2017, Mihai Moldovan wrote:

Date: Sun, 24 Dec 2017 04:07:09 +0100 From: Mihai Moldovan <ionic@ionic.de> To: Robert Dinse <nanook@eskimo.com> Cc: x2go-user@lists.x2go.org Subject: Re: [X2Go-User] New x2go broken on Ubuntu 17.10

• On 12/24/2017 03:45 AM, Robert Dinse wrote:

...

  It about 99.99% works, one behavior that is still off is if I have Window

Snapping enabled in Mate Tweak (I normally don't so this particular bug does not cause me any problems), when it's in a corner a Mate terminal only expands to have the screen horizontally but full screen vertically.

Hm, this doesn't sound like a bug. A window is only maximized both vertically and horizontally, if you move it to the top edge. Moving it to either the left or right edges maximizes a window vertically, but only half-way horizontally (depending on what edge you moved it to).

MATE always behaved like that and it's consistent with, i.e., the way Windows is maximizing windows when moving to edges.

Disabling rrxinerama is only a workaround, though. It will break client-side Xinerama setups and maybe other stuff, too. The nice part is that without rrxinerama, the fallback (read: old) code is being used.

Mihai

  I applied to a machine that was definitely broken, logged out and logged

back in and things work with that added argument.

-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting. Knowledgeable human assistance, not telephone trees or script readers. See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.

On Sun, 24 Dec 2017, Mihai Moldovan wrote:

Date: Sun, 24 Dec 2017 04:22:45 +0100 From: Mihai Moldovan <ionic@ionic.de> To: Robert Dinse <nanook@eskimo.com> Cc: x2go-user@lists.x2go.org Subject: Re: [X2Go-User] New x2go broken on Ubuntu 17.10

• On 12/24/2017 04:19 AM, Robert Dinse wrote:

...

  That could be, can you shoot me that option one more time, I accidentally

deleted your e-mail, I found machines that are still broke and they have different versions of the libs than the ones that are working.

-rrxinerama to disable Xinerama handling through RandR.

...

  libnx-x11-6 on the machine(s) that is working is version

2:3.5.99.9-0.1+git20170830.2839+14.04.release 1.

Maybe Ulis changes were not part of this release yet (and, by extension, the code still used the old Xinerama faking mechanism without relying on RandR).

Mihai

Ok will do, headed out to get fuel now, should be about an hour when I get back.

-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting. Knowledgeable human assistance, not telephone trees or script readers. See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.

On Sun, 24 Dec 2017, Mihai Moldovan wrote:

Date: Sun, 24 Dec 2017 05:35:22 +0100 From: Mihai Moldovan <ionic@ionic.de> To: Robert Dinse <nanook@eskimo.com> Cc: x2go-user@lists.x2go.org Subject: Re: [X2Go-User] New x2go broken on Ubuntu 17.10

• On 12/24/2017 04:38 AM, Robert Dinse wrote:

...

  I applied to a machine that was definitely broken, logged out and logged

back in and things work with that added argument.

If you're still doing stuff in, say, an hour from now, go for a sync and update the system at that time. Remove the -rrxinerama workaround and create a new session without it.

I've pushed a fix for the wrong screen size with RRXinerama. Packages are currently building on launchpad. Upload ETA ~30 minutes.

Mihai

• On 12/24/2017 06:42 AM, Robert Dinse wrote:

  Just installed the updates and that did fix the issue.  Thank you!

Great, at least we've got that.

The new architecture still is a bit weird in that it deletes all RandR modes but the one that was detected on the remote (i.e., client-side) screens, so changing the resolution within the session itself won't be possible.

This shouldn't be a huge problem in general since resizing is still possible in windowed mode and irrelevant in whole display or fullscreen modes.

Other than that, be aware that the new version still has other unresolved bugs, which include a huge memory footprint within nxproxy (server/client mode), slowdowns for no apparent reason (though only one user so far has reproduced this), random application crashes for software that uses a lot of X resources (e.g., Firefox/Pale Moon, Audacity, KDE Plasma, fvwm2, ...) and sudden connection drops (which may be related to the previous slowdowns and have so far only been experienced by one user).

Mihai

• On 12/26/2017 02:06 AM, Robert Dinse wrote:

  I see that you pushed another update today on Christmas.  Things still

seem work but I am curious about arguments to nxagent:

root 13298 6.0 0.0 282796 81308 ? S 17:02 0:02 nxagent -nolisten tcp -nolisten tcp -dpi 96 -D -auth /root/.Xauthority -geometry 800x600 -name X2GO-root-50-1514250167_stDMATE_dp24 :50

  In particular the -geometry 800x600 even though I'm set at a screen

resolution of 1920x1080 (and it is displaying at the correct resolution in spite of that).

We're always starting whole display sessions with a geometry of 800x600 (which corresponds to the default width and height). You're right that this is probably a bit weird, but the window is resized to the correct size later on and nxagent adjusts to that.

This is pretty much also true for rootless sessions (in which case the window is also immediately resized to spawn the whole display).

Real fullscreen sessions get a geometry value of "fullscreen" instead.

It doesn't really matter to much if resizing is working properly. We could avoid a useless resize operation by pre-determining the display size and passing that as the initial geometry, but there isn't all that much to gain.

  Memory usage of nxagent does not seem unreasonable to me, 282k of which

81k is in core. FIrefox is around 4GB at times.

That's good to hear! I hope to have squashed most memory hog situations, that mostly boiled down to bugs in the new logging code during the last few days and weeks.

The issue I talked about in my last mail boiled down to using the new -d parameter with nxproxy and enabling info or debug output. Staying on the default warning log level didn't lead to it eating memory quickly, but even so that issue should also be gone now.

This update cost me a few hairs lately.

Mihai

  Ok, strangeness now.  I just tried another box that was broken yesterday,

I did not add this option, but it is working today anyway.

-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting. Knowledgeable human assistance, not telephone trees or script readers. See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.

On Sun, 24 Dec 2017, Mihai Moldovan wrote:

Date: Sun, 24 Dec 2017 03:26:30 +0100 From: Mihai Moldovan <ionic@ionic.de> To: Robert Dinse <nanook@eskimo.com> Cc: x2go-user@lists.x2go.org Subject: Re: [X2Go-User] New x2go broken on Ubuntu 17.10

• On 12/24/2017 03:18 AM, Robert Dinse wrote:

...

  I had built the libs from source but perhaps the repository version

overwrote them.

Maybe.

In any case, if you specify "-rrxinerama" (mind the spelling and single dash at the beginning) in /etc/x2go/x2goagent.options, can you confirm that it's working again regarding your use case?

Mihai

  I may have gotten confused about what machine(s) were broken though I

could swear ubuntu and ftp which is a user shell server and web server respectively were broke. Probably just losing my mind.

-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting. Knowledgeable human assistance, not telephone trees or script readers. See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.

On Sat, 23 Dec 2017, Robert Dinse wrote:

Date: Sat, 23 Dec 2017 19:07:24 -0800 (PST) From: Robert Dinse <nanook@eskimo.com> To: Mihai Moldovan <ionic@ionic.de> Cc: x2go-user@lists.x2go.org Subject: Re: [X2Go-User] New x2go broken on Ubuntu 17.10

Ok, even weirder, I just took that option back out and the other box is

also working without it. I have no idea what changed overnight but something "unbroke".

-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting. Knowledgeable human assistance, not telephone trees or script readers. See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.

On Sat, 23 Dec 2017, Robert Dinse wrote:

...

Date: Sat, 23 Dec 2017 19:00:32 -0800 (PST) From: Robert Dinse <nanook@eskimo.com> To: Mihai Moldovan <ionic@ionic.de> Cc: x2go-user@lists.x2go.org Subject: Re: [X2Go-User] New x2go broken on Ubuntu 17.10

Ok, strangeness now.  I just tried another box that was broken 

yesterday, I did not add this option, but it is working today anyway.

-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting. Knowledgeable human assistance, not telephone trees or script readers. See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.

On Sun, 24 Dec 2017, Mihai Moldovan wrote:

...

Date: Sun, 24 Dec 2017 03:26:30 +0100 From: Mihai Moldovan <ionic@ionic.de> To: Robert Dinse <nanook@eskimo.com> Cc: x2go-user@lists.x2go.org Subject: Re: [X2Go-User] New x2go broken on Ubuntu 17.10

• On 12/24/2017 03:18 AM, Robert Dinse wrote:

...

  I had built the libs from source but perhaps the repository version

overwrote them.

Maybe.

In any case, if you specify "-rrxinerama" (mind the spelling and single dash at the beginning) in /etc/x2go/x2goagent.options, can you confirm that it's working again regarding your use case?

Mihai

---

x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user

---

x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user