Re: [X2Go-User] Dependency error

[Mihai Moldovan]

* On 6/10/23 17:37, Buddy Butterfly wrote:
> also tested it on a Ubuntu Trusty (18.04) system.
> It does not work there yet!

Thanks for testing. Oh, that's right. For Ubuntu, I've only built release/stable
KDrive packages for Jammy (20.04), Kinetic, Lunar and Mantic.

Unfortunately, X2Go Server always hard-depends upon KDrive, so any older version
that will not get KDrive packages will be broken.

I can fix that (by removing KDrive support for old deb-based distro versions),
but will only be able to make a new X2Go Server release next week.


On a related note, I'm pretty sure that KDrive at least compiles on 18.04, but
given that 18.04 is freshly out of mainstream support, I'd rather rely on
commercial support requests for providing binaries for older distros such as
18.04, if there's even any interest.



Mihai


OpenPGP_signature
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] Dependency error

[Mihai Moldovan]

* On 6/6/23 15:52, Buddy Butterfly wrote:
> just revert to the previous version for the time being with pinning it:
> 
> Create file pin-x2go in /etc/apt/preferences.d/ with content:

Please try unpinning.


Now that we have X2Go KDrive builds, and I have fixed up the brokenness in the
Debian build metadata of X2Go Server, a normal upgrade should work just fine.



Mihai


OpenPGP_signature
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] x2go upgrade issues (packages with unmet dependencies)

[Mihai Moldovan]

* On 5/31/23 10:39, Enrico Baravoglia | Fucine.IT wrote:
> Hello everyone.
> 
> We have this remote desktop (with x2go-server running there):
> 
>   * Operating System: Kubuntu 20.04
>   * KDE Plasma Version: 5.18.8
>   * KDE Frameworks Version: 5.68.0
>   * Qt Version: 5.12.8
>   * Kernel Version: 5.4.0-147-generic
>   * OS Type: 64-bit
>   * Processors: 12 × AMD Ryzen 5 3600 6-Core Processor
>   * Memory: 62,8 GiB
> 
> During package update we got:
> 
>> E:
>> /var/cache/apt/archives/libx2go-server-perl_4.1.0.4-0~1975~ubuntu20.04.1_all.deb:
>> trying to overwrite '/usr/share/man/man3/X2Go::Utils.3pm.gz', which is also 
>> in
>> package libx2go-utils-perl 4.1.0.3-5
> In particular:

Thanks for the report.


You won't be able to upgrade X2Go packages just yet. The new version of X2Go
Server depends upon KDrive components that are currently unreleased, so you'll
have X2Go Server subpackages that won't be upgradeable. I have to throw out a
barrage of other releases to bring this into an consistent state, but that will
probably not be finished until the end of this week or next week (just because
it's a lot of work and requires a lot of testing and building).



Mihai


OpenPGP_signature
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] [Debian repository] stable link points to buster instead of bullseye

[Mihai Moldovan]

* On 5/19/22 9:22 AM, richard lucassen wrote:
> @ the Debian repository admin:
> 
> When running "apt update" I get this warning:
> 
> W: Conflicting distribution: http://packages.x2go.org/debian stable
> InRelease (expected stable but got buster)
> 
> In /etc/apt/sources.list.d/x2go.list I have: 
> 
> deb http://packages.x2go.org/debian stable main
> 
> I think there the "stable" link points to buster:
> 
> http://packages.x2go.org/debian/dists/

Ah, I forgot to change the symlinks when changing the configuration file.


This said, the links and configs are often outdated.

Please don't *ever* use keywords such as stable, oldstable or testing. Always
use the proper codename, like buster, bullseye or the like. Unstable and sid are
not moving targets, so both are fine, but everything else can vary in a bad way.
Codenames are guaranteed to be stable, while keywords are moving targets.



Mihai



OpenPGP_signature
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] x2goserver Requires: base64

[Mihai Moldovan]

* On 5/10/21 11:38 PM, Mike Gabriel wrote:
>> Just looking to upgrade to nightly on a CentOS7 system.  I have the  
>> repo file installed.  I disabled the default and enabled the nightly  
>> and gave it the old "yum update "x2go*"
>>
>>
>> There is no package in standard repos that I could find names  
>> base64.  Any tips?
>>
>> Cheers!
> 
> I encountered the same with the DEB packages. The base64 executable  
> normally is available in one of the distro's core packages (in  
> general, there might be exceptions).

Yep, sorry, that was my fault. base64 is almost always part of coreutils. I
assumed that the coreutils RPM package might have a "Provides" tag for each
binary, but that wasn't the case, so the packages were broken for a bit.

This should have been fixed in the deb and RPM packaging long ago (21 days ago),
though.



Mihai



OpenPGP_signature
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] [EXT] Re: Sticky (repeated) arrows using x

[Mihai Moldovan]

* On 8/16/20 8:42 AM, Tamir Einy wrote:
> I have installed latest nightly build (4.1.2.3) that you provided, the
> connection to the server failed, 
> 
> Here is the debug output to the command: 
> 
> x2go-INFO-1> "Starting X2Go Client 4.1.2.3..."
> x2go-WARNING-1> English language requested, not loading translator.
> x2go-WARNING-1> English language requested, not loading translator.
> [...]
> x2go-INFO-8> "Starting connection to server: dcilda927:22"
> x2go-DEBUG-../src/onmainwindow.cpp:2931> Starting new ssh connection to
> server:"dcilda927":"22" krbLogin: false
> x2go-DEBUG-../src/sshmasterconnection.cpp:168> SshMasterConnection, host
> "dcilda927"; port 22; user "e171950"; useproxy false; proxyserver ""; 
> proxyport 22
> x2go-DEBUG-../src/sshmasterconnection.cpp:248> Starting SSH connection without
> Kerberos authentication.
> x2go-DEBUG-../src/sshmasterconnection.cpp:250> SshMasterConnection, instance
> SshMasterConnection(0x3cf9ad8)  created.
> x2go-DEBUG-../src/sshmasterconnection.cpp:492> SshMasterConnection, instance
> SshMasterConnection(0x3cf9ad8)  entering thread.
> x2go-DEBUG-../src/sshmasterconnection.cpp:573> Setting SSH directory to
> C:/Users/teiny171950/ssh
> x2go-DEBUG-../src/sshmasterconnection.cpp:795> Session port before config file
> parse: 22
> x2go-DEBUG-../src/sshmasterconnection.cpp:805> Session port after config file
> parse: 22
> x2go-DEBUG-../src/sshmasterconnection.cpp:869> Session port before config file
> parse (part 2): 22
> x2go-DEBUG-../src/sshmasterconnection.cpp:879> Session port after config file
> parse (part 2): 22
> x2go-DEBUG-../src/sshmasterconnection.cpp:903> cserverAuth
> x2go-DEBUG-../src/sshmasterconnection.cpp:942> state: 1
> 
> x2go-DEBUG-../src/sshmasterconnection.cpp:674> Setting SSH directory to
> C:/Users/teiny171950/ssh


Unfortunately, that's not very helpful. There's no connection attempt visible
(other than a really generic setup).

Stefan's call has been "wrong" in that the order of redirections do matter, and,
wwith his listing, stderr-data will continue to get printed out to the console.

Rather try:

x2goclient.debug.exe --debug >%TEMP%\x2godebug.log 2>&1

instead. %TEMP%\x2godebug.log should include text after that.

Also, if possible, please make sure to wait until the connection attempt
actually errors out.


Additionally, do you have a file located at "C:\Users\teiny171950\ssh\config"?

If so, what does it contain?



Mihai



signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] x2go kdrive & windows client

[Mihai Moldovan]

* On 4/23/20 6:16 PM, Oleksandr Shneyder wrote:
> yes, the community installer of Windows X2Go Client doesn't contain
> x2gokdriveclient binary yet. I can't tell you why, apparently Mike
> didn't have time to build it or maybe he just forgot about it. Looks
> like x2gokdrive isn't really important for community yet, but some of my
> "enterprise" customers are using it productively with Gnome 3 and plasma
> since 2019.

I haven't had time to package it yet.

So far, I've packaged the x2gokdrive server part for some RPM variants, but
haven't touched the client yet.

It's mostly low-priority, given all the other things that need attention (and
fixing).



Mihai




signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] Windows client release

[Mihai Moldovan]

* On 2/10/20 2:47 AM, Ingo Brückl wrote:
> Are there plans for a new release of the Windows client
> (with current VcXsrv)?

Yes, very soon™.

I'm working on it. Desperately need it for other operating systems as well.
Hopefully done tomorrow or at least very soonish.



Mihai



signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] x2go quits unexpectedly

[Mihai Moldovan]

* On 8/8/19 2:16 PM, vijaya raj wrote:
> Recently, the x2go client in mac started quitting unexpectedly on first try.
Can you please be more specific? Does X2Go Client itself quit unexpectedly? Does
the client itself work, but does starting a session not work? When does what
exactly quit?

I know that the client often crashes when starting it for the first time on
macOS. I tried debugging this years ago but never managed to find the root
cause. It's also not easily reproducible, since subsequent launches don't crash.


> On the second try, x2go starts, but ends up with a blank dotted screen 
> (screenshot
> attached).

That mostly sounds okay - you may be seeing random VRAM content instead of the
nxagent/x2go logos within the nxproxy window, which is a bug, but also a
difficult one to reproduce. It doesn't actually cause any problems, neither,
since the image will be updated later on by a window manager or the like.


> I am using the latest (August 6, 2019) x2go server version, running mac 
> 10.14.6. 

We don't provide official builds for 10.14 as of now... but I highly suspect
that even a client build targeting 10.14 wouldn't change the situation.

> I also have the latest xquartz installed.
> If I start a session in a PC and then join the session from mac, it works.

Sounds like the session startup itself doesn't work correctly when called from
the macOS client, but it's difficult to tell what exactly is happening.

> The server is running ubuntu 18.

18.04, I figure?


> image.png

The image was not attached correctly, only the file name made it into the
message as plain text.


> x2go client starting details;
> 
> NXPROXY - Version 3.5.99.14
> 
> Copyright (c) 2001, 2011 NoMachine (http://www.nomachine.com
> <http://www.nomachine.com/>)
> Copyright (c) 2008-2014 Oleksandr Shneyder  <mailto:o.shney...@phoca-gmbh.de>>
> Copyright (c) 2014-2016 Ulrich Sibiller mailto:ul...@gmx.de>>
> Copyright (c) 2014-2016 Mihai Moldovan  <mailto:io...@ionic.de>>
> Copyright (c) 2011-2016 Mike Gabriel  <mailto:mike.gabr...@das-netzwerkteam.de>>
> Copyright (c) 2015-2016 Qindel Group (http://www.qindel.com
> <http://www.qindel.com/>)
> 
> NXCOMP, NX protocol compression and NX extensions to this software
> are copyright of the aforementioned persons and companies.
> 
> Redistribution and use of the present software is allowed according
> to terms specified in the file LICENSE.nxcomp which comes in the
> source distribution.
> 
> All rights reserved.
> 
> NOTE: This software has received contributions from various other
> contributors, only the core maintainers and supporters are listed as
> copyright holders. Please contact us, if you feel you should be listed
> as copyright holder, as well.
> 
> NX protocol compression is derived from DXPC project.
> 
> Copyright (c) 1995,1996 Brian Pane
> Copyright (c) 1996,1997 Zachary Vonler and Brian Pane
> Copyright (c) 1999 Kevin Vigor and Brian Pane
> Copyright (c) 2000,2003 Gian Filippo Pinzari and Brian Pane
> 
> All rights reserved.
> 
> See ArcticaProject/nx-libs <https://github.com/ArcticaProject/nx-libs> for 
> more
> information.
> 
> Info: Proxy running in server mode with pid '31769'.
> Session: Starting session at 'Tue Aug 6 19:50:00 2019'.
> Info: Using errors file
> '/Users/nag/.x2go/S-ubuntu-55-1565135376_stDMATE_dp32/sessions'.
> Info: Using stats file '/Users/nag.x2go/S-55/stats'.
> Loop: WARNING! Overriding auxiliary X11 port with new value '1'.
> Warning: Overriding auxiliary X11 port with new value '1'.
> Info: Connecting to remote host 'localhost:49082'.
> Info: Connected to remote proxy on FD#11.
> Info: Connection with remote proxy completed.
> Loop: WARNING! Unrecognized session type 'unix-kde-depth_32'. Assuming agent
> session.
> Warning: Unrecognized session type 'unix-kde-depth_32'. Assuming agent 
> session.
> Info: Using ADSL link parameters 1408/24/1/0.
> Info: Using cache parameters 4/4096KB/8192KB/8192KB.
> Info: Using pack method '16m-jpeg-9' with session 'unix-kde-depth_32'.
> Info: Using ZLIB data compression 1/1/32.
> Info: Using ZLIB stream compression 4/4.
> Info: No suitable cache file found.
> Info: Forwarding X11 connections to display
> '/private/tmp/com.apple.launchd.8b6SbCKo0f/org.macosforge.xquartz:0'.
> Info: Forwarding auxiliary X11 connections to display
> '/private/tmp/com.apple.launchd.8b6SbCKo0f/org.macosforge.xquartz:0'.
> Session: Session started at 'Tue Aug 6 19:50:00 2019'.
> Info: Established X server connection.
> Info: Using shared memory parameters 0/0K.

Nothing interesting in here. Looks all normal so far.



Mihai



signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] X2GoBroker Python3 CentOS 7 issue

[Mihai Moldovan]

* On 6/1/19 2:44 AM, Spenser Gilliland wrote:
> I'm having an issue installing the x2gobroker-agent package on CentOS 7.  It
> looks like CentOS 7 has a python36 package but not a python3 (and various 
> python
> packages).

Yeah, x2gobroker is broken on CentOS/EPEL since the Python 3 port. Unfortunately
it's not just a simple packaging issue, which would have been easy to fix.

EPEL is missing quite a lot of Python(3) packages the new broker version needs
in order to work. Porting them through the extras repo would be possible, but
not a good idea since I know that I won't be keeping track of foreign packages
well enough.



Mihai



signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] [X2Go-Dev] Fedora X2Go repos down?

[Mihai Moldovan]

* On 6/6/19 7:52 PM, Robert Kudyba wrote:
> We're still seeing:
> 
> Failed to synchronize cache for repo 'x2go-nightly-fedora'
> Failed to synchronize cache for repo 'x2go-extras-fedora'
> Ignoring repositories: x2go-nightly-fedora, x2go-extras-fedora
> 
> Does that mean we have to import the new certificate?

Likely not. What Fedora version are you referring to? If it's 30, we don't have
packages for that yet.



Mihai




signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] [X2Go-Dev] Fedora X2Go repos down?

[Mihai Moldovan]

* On 5/31/19 4:15 AM, Robert Kudyba wrote:
> Been seeing these errors from def update for the past few nights:
> 
> Failed to synchronize cache for repo 'x2go-nightly-fedora'
> Failed to synchronize cache for repo 'x2go-extras-fedora'
> Ignoring repositories: x2go-nightly-fedora, x2go-extras-fedora

Turns out it was a bash issue. Older versions (for instance 4.3 as used on
Ubunto 16.04 LTS) of bash don't support quotes in arithmetic expressions (or at
least not very well), while newer versions (4.4 on Debian Stretch) don't seem to
have any problem with that.

The newest, working certificate should valid from 06/02/2019 and have the
SHA256/SHA1 fingerprints
E4:48:B2:AD:8A:D1:D4:B7:35:D3:93:88:DE:93:C2:A1:0B:D2:24:93:3C:03:2F:6D:BA:23:9A:AC:14:89:21:A6
/ 64:D4:B9:8F:04:0A:51:D8:DD:F6:15:2D:09:F0:ED:2F:9B:68:4F:4E.

That *doesn't* apply to wiki.x2go.org (and friends), which does have a different
certificate.



Mihai





signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] PulseAudio understanding problem (Windows client)

[Mihai Moldovan]

* On 3/28/19 10:40 PM, Ingo Brückl wrote:
> I tried "custom desktop" and simply gave "sh /home/me/.xinitrc" as an
> experiment. Everything shows up like my local desktop with two exceptions.
> Xterm is a very small window with small font in it (as if my X resource
> XTerm.VT100.font: 10x18 would be ignored or 10x18 is some other font) and
> xdosemu.
> 
> The above holds for starting without VcXsrv's font directory. When I enable
> the directory and put my 10x18 font into fonts/misc, I get the same small
> size window, but now with my (too big) font in it. Glyphs overlay.
> 
> It seems that the wrong size font is used to calculate xterm's window size at
> start-up.

Try to copy your ~/.Xresources file to ~/.Xresources-x2go . There's a good
reason why we decided not to use the "normal" ~/.Xresources file, but an
X2Go-specific one. Users set weird things in ~/.Xresources (that were fine for
their local X sessions, though), but ran into that when spawning X2Go sessions.
Hence we're just using a custom file and don't even make use of the more general
~/.Xresources file.


There are multiple caveats, though. Firstly, this file is only
read/executed/whatever for full desktop sessions. Secondly, the actual method of
how this is done differs from OS to OS. On Debian (and derivates), we just set a
variable that is handled by the usual X11 scripts (/etc/X11/Xsession and
friends), while on RHEL (and derivates) and *SUSE (and derivates) we merge both
the system file and the user file manually.

Since you're using a completely different OS... well, full desktop sessions
might just fail to start up to begin with because our Xsession script will
probably not find a release/version file to determine what your OS is based on.


> (BTW, how could VcXsrv run when I removed its font directory as an
> experiment? Where do fonts come from?)

Good question. Generally VcXsrv should still run mostly correctly. Maybe some
fonts will be substituted with a default, ugly, built-in font. If I don't
remember correctly we don't have fonts installed by default, so users would
probably have spoken up if that had caused a lot of breakage.

The whole fonts business has gotten pretty complicated anyway, since most
applications (unlike older ones like xterm etc.) rasterize fonts themselves via
cairo and output that as either bitmaps or other X primitives, which means that
the original X fonts mechanism aren't widely used any longer.



Mihai



signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] Typo with IceWM command?

[Mihai Moldovan]

* On 3/28/19 6:44 PM, Ingo Brückl wrote:
> Is x2goruncommand line 245 ("$dmd" == "IceWM") a typo (dmd instead of cmd)?

Yes, but it's not critical since X2Go Client has a bug (at least I would
categorize it as such) that maps names back into full commands.

I fixed that up in
https://code.x2go.org/gitweb?p=x2goserver.git;a=commitdiff;h=d00f3f081a59b58290b756a2b3ddec3036d77bc7



Mihai



signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] OpenSUSE Tumbleweed (et al) and OBS

[Mihai Moldovan]

* On 3/22/19 11:53 AM, Ulrich Sibiller wrote:
> Well, all I know is this (from
> https://wiki.x2go.org/doku.php/wiki:repositories:suse):
> "Currently, the OBS SUSE X2Go instance is stale. The packages are only
> being updated irregularly and support will likely not be provided.
> This note will be removed once the situation changes. You are
> encouraged to use the X2Go package repository only for the time being.
> "

The reason is that I planned to make the public OBS instance automatically track
our repositories instead of having to manually publish releases (which would
also bring nightly packages) years ago. In essence, both our upstream repository
and what is on the OBS public instance should be synchronized. It's a
non-trivial task, though, for instance because of the way we build packages
(using our custom build scripts).


The reason why this hasn't happened yet is time. There's always more important
stuff to do and I do try to maintain our upstream repositories as good as 
possible.



Mihai



signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

[X2Go-User] Upcoming Deprecation of EOL Distributions

[Mihai Moldovan]

Hi

In order to lower resource stress when building packages, I plan to deprecate
support for distributions that have reached End Of Life on December 31th 2018.


This includes the following distro versions:

- Fedora
  o 26
  o 27
- OpenSuSE
  o 42.1
  o 42.2
- SLES
  o 12.0

Ubuntu builds are ceased automatically after upstream deprecation (minus special
exceptions).


SLES 12.0 builds will be replaced by SLES 12.3 (12 SP3) builds, since SLE 12.0
has long been deprecated and newer versions include proper Qt5 support, which
the initial version lacked.


After deprecation, no new builds will be published and existing builds will be
moved to the archive repositories to discourage users from installing
unmaintained software.



Mihai



signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] Problem restoring connection on Ubuntu 18.04

[Mihai Moldovan]

* On 09/11/2018 08:02 PM, EI wrote:
> I have a very strange problem with x2goserver running on Ubuntu 18.04. I get 
> an
> error message on the client side when I try to suspend the connection. I also,
> can't reconnect to existing connections. I haven't had this problem with 
> 16.04.
> 
> I tried debugging the problem and I discovered that 
> /var/lib/x2go/x2go_sessions
> database is not getting updated when connection is created. I tried erasing 
> and
> re-creating the database, same problem. 
> 
> Even running perl script manually:
> /usr/lib/x2go/libx2go-server-db-sqlite3-wrapper.pl
> 
> insertsession,50,blah,blah-50-1536602027_stRkonsole_dp 
> doesn't change the database.

Likely caused because the server is running in an LXC (or other nom-du-jour)
container without necessary permissions.


Note that the database is supposed to be modified via a setuid root binary,
which then calls the actual perl script. The perl script is not supposed to work
correctly when called directly as an unprivileged user.

LXC is known to have problems with setuid binaries for unprivileged containers,
but that seems to be a design choice.



Mihai




signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

[X2Go-User] Looking for a Swedish Translator for X2Go Components

[Mihai Moldovan]

Hi


Our current active Swedish translator stepped down recently.

On behalf of the project, I am looking for someone to replace him and continue
the well-maintained Swedish translations.


If you are interested to help, please subscribe to the i18n mailing list[0].
More information regarding the translation process can be found on the i18n wiki
page[1]. Note that most projects also have a README.i18n file in the source code
repository, detailing how translations are done.

Since we already have Swedish translations, all steps for adding a new
translation can be skipped.


Mihai



[0] https://lists.x2go.org/listinfo/x2go-i18n
[1] https://wiki.x2go.org/doku.php/wiki:development:i18n



signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] Aborting session with 'Unable to , open display , 'nx/nx'

[Mihai Moldovan]

* On 04/15/2018 04:59 AM, Qianqian Fang wrote:
> thank you so much! the /usr/lib/x86_64-linux-gnu in the LD_LIBRARY_PATH
> was indeed the culprit! after removing it, I am now able to log in all my
> servers!
> 
> I checked my file modification history for .bashrc, I added this path for a
> subset of my machines on March 11. It was also the window when I
> applied the package updates throughout my cluster, so I mistook the
> issue to the new packages. my bad!

Actually, that makes sense - we've only started using DT_RUNPATH with nx-libs
3.5.99.14, starting with March when we also switched to using this new version.
Before that, we inserted the correct link through LD_LIBRARY_PATH as well, but I
cannot remember if it was prepended or appended. If it was prepended, your
modification would have worked, otherwise not.

So it's been a combination of both things.


Try to keep LD_LIBRARY_PATH trimmed down. I understand that you may need it for
the nVidia binary driver and CUDA to work, but this might become problematic in
the future. Currently, we're statically linking in a copy of MESA into nxagent
and don't use the system libGL version that is normally provided by MESA, but
this might change in the future. If the system libGL references the nVidia
binary version, you'll run into problems again. It's not something that will hit
you right away, but likely at an unspecific point in the future. Just as a 
heads-up.



Mihai



signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] Aborting session with 'Unable to , open display , 'nx/nx'

[Mihai Moldovan]

* On 04/15/2018 01:39 AM, Qianqian Fang wrote:
> ||<
> LD_LIBRARY_PATH=/usr/local/cuda/lib64:/usr/lib:/pub/lib:/pub/cuda-7.5/lib64:/space/hoyi/1/users/shared/mesa-10.1.3:/usr/lib/x86_64-linux-gnu/mesa:/usr/lib/nvidia-375:/usr/lib/nvidia-387:/usr/lib/nvidia-384||
> ||---||
> ||>
> LD_LIBRARY_PATH=/usr/local/cuda/lib64:/usr/lib:/pub/lib:/pub/cuda-7.5/lib64:/usr/lib/nvidia-375:/usr/lib/nvidia-387:/usr/lib/nvidia-384:/usr/lib/x86_64-linux-gnu||

I haven't had an idea how to help further, thus kept quiet.

This is interesting though - and could explain your problems.


First of all, you shouldn't set LD_LIBRARY_PATH at all. The new X2Go Server
versions don't do it and you shouldn't either. /usr/lib/x86_64-linux-gnu in
there should even be fully redundant and messes with the default linking order.
Not just that, but it means that our DT_RUNTIME trick in nxagent, which is
supposed to override libX11 linking against a compatibility symlink (libX11 ->
libNX11) installed in a specific directory, is not working - hence loading the
wrong libX11 library and thus leading to nxagent failing to open its internal
display.

Be careful when you mess with stuff with that.



Mihai



signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] Problem with X2Go 4.0.1.22-2 on Centos 7.3

[Mihai Moldovan]

* On 04/13/2018 11:30 PM, Roger Moye wrote:
> When we login to the server, the X2Go window appears as if the Linux desktop 
> is
> about to appear and then the session is terminated.
> 
> The only thing I see that is noteworthy in /var/log/messages on the server is:
> 
> /usr/bin/x2goruncommand: dbus wrapper not available
> 
>  
> 
> This error does NOT appear on servers where we are able to connect
> successfully.   However, those servers are running an older version of X2Go
> server.

This is because starting sessions wrapped in dbus-run-session is a new addition
in the latest X2Go Server versions only.


>  I have not been able to find any explanation for what this error means
> or how to avoid it.

This is not really an error. I mean, naturally it is, since you will miss
functionality (mostly concurrent sessions support for one user if the desktop
environment needs a special dbus instance for every session), but starting a
session should still work, provided there's not already a DE instance running
for the user that tries to start a session. Even then, some DEs are more or less
strict on the requirements for parallel sessions - XFCE for instance starts up
regardless, while MATE requires a private dbus instance.

Note that RH/EPEL/C7 does not feature the required binary in any package, so on
these platforms you'll always get the missing dbus wrapper notification.


> We have tried running different window managers like XFCE
> and GNOME and all produce the same result.

GNOME in RH/EPEL/C7 won't work. XFCE should.


You're actual problem is likely a different one, but I cannot tell what exactly.
You probably want to look into ~/.xsession-x2go-*-errors, maybe also enable the
debug loglevel in /etc/x2go/x2goserver.conf (no need to restart anything, just
spawn a new session) and on the client-side install the debug version of X2Go
Client (x2goclient.debug.exe; it's contained in the installer, if you don't have
that installed yet, just re-run the installer and make sure to select this
option since by default it's not installed automatically) and get a client log
via x2goclient.debug.exe > x2goclient-debug.log 2>&1 in a Windows cmd.exe
instance (yes, redirection works like that even on Windows).



Mihai



signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] X2Go Client suddenly failing to connect

[Mihai Moldovan]

* On 03/28/2018 02:58 PM, Ivan Gomez wrote:
> libNX_X11-3.5.0.32-3.el7.x86_64
> libNX_Xcomposite-3.5.0.32-3.el7.x86_64
> libNX_Xdamage-3.5.0.32-3.el7.x86_64
> libNX_Xdmcp-3.5.0.32-3.el7.x86_64
> libNX_Xext-3.5.0.32-3.el7.x86_64
> libNX_Xfixes-3.5.0.32-3.el7.x86_64
> libNX_Xinerama-3.5.0.32-3.el7.x86_64
> libNX_Xpm-3.5.0.32-3.el7.x86_64
> libNX_Xrandr-3.5.0.32-3.el7.x86_64
> libNX_Xrender-3.5.0.32-3.el7.x86_64
> libNX_Xtst-3.5.0.32-3.el7.x86_64
> nxagent-3.5.0.32-3.el7.x86_64
> nx-libs-3.5.0.32-3.el7.x86_64
> x2goagent-3.5.0.32-3.el7.x86_64
> x2goserver-4.0.1.20-1.el7.x86_64

That's the old, more or less unsupported version and additionally provided by
EPEL, not by our repositories.


> One new update on this issue:
> Updated x2gosever on one of the servers that was showing the issue to 
> x2goserver-4.0.1.22-2.el7.x86_64. After the update, access through that 
> server started working again.
> Any guidance to understand the root cause would still be greatly appreciated.

I'm afraid I can't offer a lot of help here.

You could look into ~/.x2go/C-/session.log to see what the
server-side process logged out.

At some point it must have failed to run correctly, otherwise the client-side
nxproxy would have been able to connect successfully.

Debugging such issues is always difficult.



Mihai



signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] X2Go Client suddenly failing to connect

[Mihai Moldovan]

* On 03/27/2018 03:09 PM, Ivan Gomez wrote:
> *Environment:*
> 
> *Server:*
> 
> Red Hat Enterprise Linux Server release 7.3 (Maipo)
> 
> x2goagent: 3.5.0.32
> 
> x2goserver: 4.0.1.20
> 
> x2goserver-extensions: 4.0.1.20
> 
> *Client:*
> 
> *    *Windows 7 & Windows 10
> 
>    
> 
>  
> 
> I have been using X2Go client in the current environment for quite a while now
> without issues. Seemingly all of sudden today an outage happened where X2Go 
> will
> no longer launch any applications.

rpm -qa | grep -iE '(nx|x2go)'



Mihai




signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] x2go stops working on some Ubuntu 14.04 boxes

[Mihai Moldovan]

* On 03/26/2018 11:11 PM, Qianqian Fang wrote:
> I confirm that the server giving the first error, i.e. "The remote proxy 
> closed
> the connection while negotiating..."
> has indeed installed an older version of libnx-x11 (3.5.0.33~710).

Hmm, mixing X2Go Server 4.1.0.0 and nx-libs 3.5.0.x is not really supported.

> after letting apt-get to upgrade the nx libraries and x2go packages,
> I saw the libnx-x11 was replaced by a new package named libnx-x11-6, and
> the version is now 3.5.99.16. However, now I start seeing the 2nd error
> message on those machines, i.e. "connection failed".

So, good that you upgraded.


> here is a dump of the session.log file under the failed session:
> 
> 
> |NXAGENT - Version 3.5.99.16||
> ||
> ||Copyright (c) 2001, 2011 NoMachine (http://www.nomachine.com)||
> ||||
> ||See https://github.com/ArcticaProject/nx-libs for more information.||
> ||
> ||Info: Agent running with pid '17844'.||
> ||Session: Starting session at 'Mon Mar 26 16:56:11 2018'.||
> ||Error: Aborting session with 'Unable to open display
> 'nx/nx,options=/tmp/.x2go-fangq/C-fangq-50-1522097770_stDXFCE_dp24/options:50''.||
> ||Session: Aborting session at 'Mon Mar 26 16:56:11 2018'.||
> ||Session: Session aborted at 'Mon Mar 26 16:56:11 2018'.||
> |

Hmm, strange. Being unable to open the internal display normally means there is
a libNX_X11 problem.

dpkg -l | grep -Ei '(x2go|nx)'
ls -ldh /usr/lib/*86*/nx/X11


> strangely, the x2go window reports something differently, it says (see 
> attached
> screenshot)
> 
> |"PANIC!" Failure negotiating the session in stage 7||
> ||...||
> ||Wrong version or invalid session authentication cookie.||
> ||||
> |
> 
> are these two error messages caused by a single issue or multiple?

They are different error messages, because the first one is from nxproxy in
client mode, while the second one is from nxproxy in server mode. This error
message is a pretty generic one - the server part (which ironically runs on the
client side for reasons) expected to read authentication data from the nxproxy
client, but it never got it. Instead, the connection was just terminates
unexpectedly.


> I've already restarted x2gosever, but no dice. any other files that I need to
> reset/clear?

No. Additionally, you do not need to restart the x2goserver service at all
(unless you're upgrading the x2goserver package or modifying
/etc/x2go/x2goserver.conf) - the x2goserver service is just a cleanup utility
that syncs content in the database with what is observed on the file system. It
has nothing to do (well, mostly...) with starting or running sessions (though
I've seen strange things happening leading to session suspension, but that's a
different story and mainly caused by nxagent trying to display a popup or such).



Mihai



signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] x2go stops working on some Ubuntu 14.04 boxes

[Mihai Moldovan]

* On 03/26/2018 03:45 PM, Qianqian Fang wrote:
> I run a small cluster for my lab, including about 12 Linux boxes running 
> Ubuntu
> 14.04 (1x with 16.04). We have been using x2go and ssh as the primary tool to
> access these computing resources.
> 
> Recently (started a month ago), I noticed there were package updates of x2go
> server (now 4.1.0.0-0-1517), client (now 4.1.1.1-0-1719) and the nx11 
> libraries,
> on the other hand, I started having difficulty log on to some of my servers, 
> and
> this list starts to grow. I am not sure if this was the result of the recent
> package upgrade, or the reason motivated the package updates, but I started
> seeing the below two types of messages:

Please make sure that nx-libs 3.5.99.16 is installed on the server side.


> For some of the machines, I saw the below message initially:
> 
> *The remote proxy closed the connection while negotiating*
> **
> *the session. This may be due to the wrong authentication*
> **
> *credentials passed to the server.*

This sounds like a typical incarnation of the DPMS bug, fixed with nx-libs
3.5.99.15.


> for some other servers, I am getting the below message:
> 
> *Connection failed.**Failed to start X2Go Agent session with ID
> account-xx_stDXFCE_dp24. X2Go Agent terminated unexpectedly. Aborting
> session startup. *
> 
> The 1st message appeared first, after I tried to restart x2goserver or 
> rebooting
> 
> the machine, or apply the updates, deleting the ~/.x2go folder, or a reboot, 
> those
> 
> machines typically display the 2nd message; none of those were fixed using the
> 
> above procedures.

However, this doesn't sound like it. Normally the DPMS bug only manifests after
a pretty long time (say, an hour or 1.5h, depending on DPMS settings), but not
right away after starting the session. I haven't yet seen such an error message
yet. It's possible that it's caused by the session repositioning on non-first
displays/nxagent crashing bug as fixed with nx-libs 3.5.99.16, but normally that
incarnates differently (i.e., nxagent is being started successfully, but then
dies quickly while starting the session without a client-side error message).



Mihai



signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] timeout connecting to new server

[Mihai Moldovan]

* On 03/23/2018 10:10 PM, Michael Stauffer wrote:
> CentOS 7.4
>
> However when I try to connect with x2go client (4.1.1.1 on windows 10), I get 
> a
> timeout. Connecting to our old x2go server works.
> 
> I've disabled the firewall for testing but it still times out.

Such issues come up every now and then and mostly relate to different address
families being used.

libssh doesn't pick a host to connect to at random, so it'll use the first entry
that is returned by your DNS system.

In some instances, this leads to libssh (and hence X2Go Client) always trying to
connect to the remote server via IPv6, while...


> I can successfully ssh using x-forwarding to the new x2go server.

OpenSSH's implementation seems to prefer IPv4 addresses some of the time (but
not always) - and may even try the next address in the list if connecting to the
current one failed. libssh doesn't seem to have this fallback.


Please check your IPv6 setup.


You can have X2Go Client connect to an IPv4 address directly, but that's
finicky. Essentially, to avoid having to do this for every session definition,
you could define a new shortname in ~/.ssh/config named host-v4, hardcode the
IPv4 address there and use that shortname in X2Go Client. That should work on
UNIX-based platforms and theoretically also on Windows, but I don't know the
correct path for the file on this platform.


As a quick test, try using the v4 address anyway.



Mihai



signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] Can we have some old rpms in the x2go.repo?

[Mihai Moldovan]

* On 03/15/2018 05:23 AM, Norman Gaywood wrote:
> If I connect, suspend the session, resume the session. I can then move my
> session across screens.
> Worked for me a few times so far.
Hmm, I just tried that right now and couldn't. nxagent crashes, even after
suspending and resuming the session before moving it to another display.


> Not sure I can in a useful manner, but:
> I keep changing my connection screen size to many different sizes.
> I'm not sure how to report my physical workstation screen sizes but:
> Dell 27" 2560x1440, Dell 29" 2560x1018

Okay, with configuration I meant something like that:

 ___  ___
| P || S |
| 2560x1440 || 2560x1018 |
|   | ---
 ---

Where P denotes a primary display and S a secondary one. Marking just the
primary would also be okay, since there can only be one™.

In this configuration, the secondary display is east of the other one and
aligned at the top.

Anyway, I am retracting my initial assessment, I can reproduce the crashing when
moving nxagent windows around display, but only iff the display sizes differ.

With two displays of the same size, this doesn't happen.


> The workstation x2goclient is x2goclient-4.1.1.0-1.fc27.x86_64
> 
> All desktop environments on the server(s) are
> XFCE, xfce4-session-4.12.1-12.fc27.x86_64
> The server(s) are running:
> libNX_X11-6-3.5.99.15-0.0build1.1.git20180308.2971.main.fc27.x86_64
> libXcompext3-3.5.0.33-0.0x2go1.1.git20180204.776.main.fc27.x86_64
> nxagent-3.5.99.15-0.0build1.1.git20180308.2971.main.fc27.x86_64
> nx-libs-3.5.99.15-0.0build1.1.git20180308.2971.main.fc27.x86_64
> nxproxy-3.5.99.15-0.0build1.1.git20180308.2971.main.fc27.x86_64
> perl-X2Go-Log-4.1.0.0-0.0x2go1.1.git20180302.1517.main.fc27.x86_64
> perl-X2Go-Server-4.1.0.0-0.0x2go1.1.git20180302.1517.main.fc27.x86_64
> perl-X2Go-Server-DB-4.1.0.0-0.0x2go1.1.git20180302.1517.main.fc27.x86_64
> x2goserver-4.1.0.0-0.0x2go1.1.git20180302.1517.main.fc27.x86_64
> x2goserver-common-4.1.0.0-0.0x2go1.1.git20180302.1517.main.fc27.x86_64
> x2goserver-extensions-4.1.0.0-0.0x2go1.1.git20180302.1517.main.fc27.x86_64
> x2goserver-x2goagent-4.1.0.0-0.0x2go1.1.git20180302.1517.main.fc27.x86_64
> x2goserver-xsession-4.1.0.0-0.0x2go1.1.git20180302.1517.main.fc27.x86_64
> 
> The prod server would have mostly Windows x2go clients connecting, but some 
> Mac
> and some Linux, all different versions.
> The dev server would only have x2goclient-4.1.1.0-1.fc27.x86_64 connecting.
>   
> The servers (dev and prod) are Fedora  27 running:
> libNX_X11-6-3.5.99.15-0.0build1.1.git20180308.2971.main.fc27.x86_64
> libXcompext3-3.5.0.33-0.0x2go1.1.git20180204.776.main.fc27.x86_64
> nxagent-3.5.99.15-0.0build1.1.git20180308.2971.main.fc27.x86_64
> nx-libs-3.5.99.15-0.0build1.1.git20180308.2971.main.fc27.x86_64
> nxproxy-3.5.99.15-0.0build1.1.git20180308.2971.main.fc27.x86_64
> perl-X2Go-Log-4.1.0.0-0.0x2go1.1.git20180302.1517.main.fc27.x86_64
> perl-X2Go-Server-4.1.0.0-0.0x2go1.1.git20180302.1517.main.fc27.x86_64
> perl-X2Go-Server-DB-4.1.0.0-0.0x2go1.1.git20180302.1517.main.fc27.x86_64
> x2goserver-4.1.0.0-0.0x2go1.1.git20180302.1517.main.fc27.x86_64
> x2goserver-common-4.1.0.0-0.0x2go1.1.git20180302.1517.main.fc27.x86_64
> x2goserver-extensions-4.1.0.0-0.0x2go1.1.git20180302.1517.main.fc27.x86_64
> x2goserver-x2goagent-4.1.0.0-0.0x2go1.1.git20180302.1517.main.fc27.x86_64
> x2goserver-xsession-4.1.0.0-0.0x2go1.1.git20180302.1517.main.fc27.x86_64

Everything's okay. You have an old version of libXcompext3 installed, but it's
an orphaned leaf and won't cause trouble since nothing links against it.

You may remove it manually if you wish.



Mihai



signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] Can we have some old rpms in the x2go.repo?

[Mihai Moldovan]

* On 03/15/2018 03:11 AM, Norman Gaywood wrote:
> So I've updated dev to the latest
> again 3.5.99.15-0.0build1.1.git20180308.2971.main.fc27
> 
> And I seem to get an nxagent segfault every time I move the session window 
> into
> another screen.
> 
> Same version in production and it was stable for a few days now. I could move 
> it
> across screens. I suspended and resumed several times.
> But, after logging out of production and logging back in again, I'm back to
> segfaulting when moving across screens.
> 
> It's a very strange problem :-(
> 
> Executive summary:
> 
> The segfault on connect I have not reproduced. But its been reported by 
> several
> of my users. I have around 50 logged in users at the moment. The login 
> segfault
> only happens to very few (5/6). Some of them seemed to be working now.

I've been unable to reproduce this on a 16.04 VM with two virtual heads, but
neither was the original reporter that tried connecting from a 16.04 with one
head to a 16.04 machine, that previously segfaulted on connect when using a
14.04 client box with dual head setup (with 21:9 displays or such).


> The move across the screen segfault has happened to 3 users (including me) and
> all have been linux clients (Fedora I think).
> The move across screen segfault seems to go away sometimes for undermined 
> reasons.

I personally wasn't able to reproduce that either, but it seems to be depending
on quite some factors.

Can you tell me the display configuration (size and positioning) you are seeing
this with and what window managers/desktop environments and operating systems
are used on the client and server side?



Mihai



signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] Update: Problems after upgrading to recent x2go-server and x2go client releases

[Mihai Moldovan]

* On 03/13/2018 02:41 PM, h i wrote:
> When using the ppa:x2go/stable repository, something seemed strange when I ran
> the update manager in Ubuntu 14.04 and Ubuntu 16.04. I received a message 
> about
> a partial upgrade I've never seen since using Ubuntu. I've attached the 
> message.
> After running this partial upgrade, I started experiencing the flickering
> problems. Removed x2goserver entirely, and did a fresh install of the most
> update to date version. Still experiencing the flickering problems.

Hm, I don't know what a partial update means. If you upgraded successfully there
should be no partial upgrades.

Switching from stable to saimaa directly is not possible, though.

You will need to uninstall all X2Go packages first, then add the Saimaa
repository and reinstall.


> I no longer experience the flickering when maximizing/minimizing or moving the
> window from side-to side. Everything is working fine like it was prior to the
> most recent update from the ppa:x2go/stable repository. I think I'm going to
> stick with the Saimaa repository for now until the bugs are fixed from
> the ppa:x2go/stable  repository.  

Fine, but please follow the release announcements to know when that happens.


> Also going to stick with x2goclient 4.1.0.0 where there is no issue with
> clicking the session panel. I can click where I'm accustomed to clicking 
> again.

Note that X2Go Client prior to 4.1.1.1 won't work correctly with the new stable
release of X2Go Server due to Xinerama changes.



Mihai



signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] Problems after upgrading to recent x2go-server and x2go client releases

[Mihai Moldovan]

* On 03/09/2018 10:23 PM, h i wrote:
> I think I might have to roll-back to the previous x2goserver version. At 
> least with our setup, we never had a flicker issue until this most recent  
> update.

I know, it's a new issue that only manifests with the new nx-libs 3.5.99.x 
release.

We currently do not know why it happens exactly, but it seems to only occur on
Windows 10 as the client platform (not Windows 7 for instance).

It looks like the window is constantly resizing to the same size - but we'll
have to figure out what generates so many resizing requests and why.


> Interesting. Yeah, I never had an issue with the sensitive area. 
> Understandable that others might have an issue.

You likely never tried changing settings within a tile using the drop-down
mechanism provided there. Others did... and were frustrated with the constant
starting of sessions even though they just wanted to change settings prior to
actually firing them off.


> What is Saimaa release, and why are there two separate releases for x2go now? 
>  
> 
> 
> Is the saimaa release from here:
> 
> https://launchpad.net/~x2go/+archive/ubuntu/saimaa

Yes, that's an Ubuntu repository for Saimaa.

Saimaa is an ESR release based on the earlier version of X2Go Server 4.0.1.x and
legacy nx-libs 3.5.0.x versions. It won't get normal bug fixes, only at most
security updates and doesn't contain all X2Go packages.

It's supposed to provide a fallback to the old state that was working for users
so that they can switch to something they know is working if they experience
problems with the new release.

More information also here: https://wiki.x2go.org/doku.php/download:saimaa

It's not meant to be used indefinitely, though. As problems in the new release
are fixed, users should migrate back to the stable version again.



Mihai



signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] Can't install X2goserver on Debian 9

[Mihai Moldovan]

* On 03/15/2018 01:16 AM, Nigra Truo wrote:
> [SOLVED]
> 
> I figured out what the culprit is. This is an older system and the intent to
> purge was based on the assumption that some old config or other depricated
> element might be still hanging around. So doing this here:
> 
> apt purge x2goserver x2goserver-common x2goserver-dbgsym x2goserver-extensions
> x2goserver-fmbindings x2goserver-printing x2goserver-pyhoca 
> x2goserver-x2goagent
> x2goserver-xsession libx2go-log-perl libx2go-server-db-perl 
> libx2go-server-perl
> 
> Fixes it. It removes all traces of x2go from the server, only when you
> especially mention each and every one package and purge it does it work, for
> example the users are contained in the x2goserver-common package, if you just 
> do
> a purge of x2goserver alone, that leaves most things still on the system.
> This gives you the possibility to wipe the slate clean and install it like it
> was a brand new linux install.

Oh, indeed, you should have purged both x2goserver and x2goserver-common...
maybe also the old db packages.

It looks like in your original message, apt-get only tried to purge these 
packages:

The following packages will be REMOVED:
  x2goserver* x2goserver-extensions* x2goserver-fmbindings* x2goserver-printing*
x2goserver-xsession*

So definitely not everything, for instance x2goserver-common is missing there.



Mihai



signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] Can't install X2goserver on Debian 9

[Mihai Moldovan]

* On 03/14/2018 02:48 PM, Mihai Moldovan wrote:
> Please create /etc/x2go/x2gosql/sql manually with a line containing
> 'backend=sqlite'. That should allow you to purge the packages.
> 
> Afterwards you should be able to reinstall them normally.

Oh, and if this still doesn't help for purging, you'll have to modify the
scriptlets apt saved in /var/lib/dpkg/info/, like Jason already pointed out.

Edit x2goserver.postrm, libx2go-server-db-perl.postrm and
x2goserver-common.postrm (if they exist) and put a [ -d '/etc/x2go' ] && before
the rmdir calls, like in
https://code.x2go.org/gitweb?p=x2goserver.git;a=commitdiff;h=561ee44138fa6bc02d1293539dac501a9dda1886

Purging should seriously work after that.



Mihai




signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] Can't install X2goserver on Debian 9

[Mihai Moldovan]

* On 03/14/2018 03:19 AM, Nigra Truo wrote:
> Thanks for the pointers. Yes, of course all apt commands are always executed
> as root. Right now it is not so much about the bug that prevents purging, it
> is more that I just can't reinstall x2goserver anymore. I see this message
> 
> "X2Go is configured to use a non-SQLite DB backend, leaving the database
> alone" and the server install fails.
> 
> and can't find any documentation and reference to it, it is a show stopper
> at this moment. Question: Where is x2go told to do that? Which config is
> still left on the system? I cleaned up EVERYTHING x2go related, erased all
> dirs and configs, I have never seen this message before. It is like apt /
> dpkg remembers some setting that it is not supposed to remember (as the
> package was purged)

It's determined in a {pre,post}{inst,rm} scripts... which are buggy in that 
regard.

We should ignore non-existing files instead of assuming a different SQL backend
being used.

Please create /etc/x2go/x2gosql/sql manually with a line containing
'backend=sqlite'. That should allow you to purge the packages.

Afterwards you should be able to reinstall them normally.


Mihai




signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] LinuxMint 18.3 upgrade fails

[Mihai Moldovan]

* On 03/11/2018 09:44 AM, Robert Dinse wrote:
>   Might be because of backports being enabled giving me a newer version of
> something:
> 
>   deb http://packages.linuxmint.com sylvia main upstream import backport 
> enabled giving me a newer version of something?  Or maybe my apt database is
> corrupted somehow.  This has been upgraded in place many times, not a fresh
> 18.3 install.
> 
> deb http://archive.ubuntu.com/ubuntu xenial main restricted universe 
> multiverse
> deb http://archive.ubuntu.com/ubuntu xenial-updates main restricted universe 
> multiverse
> deb http://archive.ubuntu.com/ubuntu xenial-backports main restricted 
> universe 
> multiverse
> 
> deb http://security.ubuntu.com/ubuntu/ xenial-security main restricted 
> universe 
> multiverse
> deb http://archive.canonical.com/ubuntu/ xenial partner
> deb http://ppa.launchpad.net/x2go/stable/ubuntu artful main
> #deb-src http://ppa.launchpad.net/x2go/stable/ubuntu xenial main

These, apart from the X2Go repositories, seem to be the default values in my
fresh VM (i.e., backport enabled).

So that's not it either.


Btw, to clear up some confusion here:

> The following packages have unmet dependencies:
>   x2goserver : Depends: x2goserver-x2goagent (>= 
> 4.1.0.0-0~1517~ubuntu16.04.1) 
> but it is not going to be installed
>Depends: x2goserver-x2goagent (< 
> 4.1.0.0-0~1517~ubuntu16.04.1.1~) 
> but it is not going to be installed
> E: Unable to correct problems, you have held broken packages.
> 
>   I do not undersatnd how it can depend upon a version both less than and
> greater than the current version available.

It's depending on a version greater or equal to 4.1.0.0-0~1517~ubuntu16.04.1 and
less than 4.1.0.0-0~1517~ubuntu16.04.1.1~ (the tilde in Debian packaging always
sorts before everything else, so any additional strings will make the version
higher.)

Anyway, the point here is the *additional* .1 at the end.

That's to make sure that version bumps, like 4.1.0.0-0~1517~ubuntu16.04.2 also
satisfy the dependency.

We're not really actively using that, but it's a pretty common versioning 
scheme.


Not explaining your error, though.

dpkg -l | grep -i x2go

from that machine please.



Mihai



signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] Can we have some old rpms in the x2go.repo?

[Mihai Moldovan]

* On 03/13/2018 10:25 AM, Norman Gaywood wrote:
> But all those links/folders on http://snapshots.packages.x2go.org/ seem to be 
> empty.
> 
> Or am I missing something?

Nope, they are not. See for instance
https://snapshots.packages.x2go.org/20180302/fedora/27/main/x86_64/rpms/nx-libs/

It's just the index page that is "blank", just like https://packages.x2go.org/ 
is.


> Fixing the bug could take weeks, so it would be good to roll back 1 version 
> that
> seemed to be more stable while we wait.

The other version has a different severe bug, related to Screen Savers and DPMS.
Make sure to disable them, if you really want to downgrade.



Mihai




signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] Can we have some old rpms in the x2go.repo?

[Mihai Moldovan]

* On 03/13/2018 07:34 AM, Norman Gaywood wrote:
> Last night after upgrading several Fedora 27 systems with the latest
> 
> http://packages.x2go.org/fedora/$releasever/main/$basearch
> 
> nxagent now segfaults sometimes on connection, sometimes when doing a move
> of the x2goclient screen.
> 
> Problem is, I can't roll back to the previous version (to test) as the repo 
> does not contain the older rpms?
> 
> Would it be possible to have a version or two to be able to do a "dnf 
> downgrade"?

You can switch to old versions using http://snapshots.packages.x2go.org/, but
these won't be available for a very long time. The retention policy is somewhat
complicated.

Even better would be to fix that problem, though...



Mihai



signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

[X2Go-User] Deprecation and removal of X2Go Plugin

[Mihai Moldovan]

Hi


Since most browsers either stopped supporting NPAPI (or will be dropping support
with the next ESR version) and Qt 5 does not feature a browser plugin
architecture any longer, I will be ripping out code related to the X2Go Plugin
in the development version of X2Go Client soonish.

Expect the next version to not supply X2Go Plugin binaries.



Mihai



signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] LinuxMint 18.3 upgrade fails

[Mihai Moldovan]

* On 03/11/2018 06:15 AM, Robert Dinse wrote:
>   With xenial:
> 
> apt install x2goserver x2gomatebindings x2golxdebindings --install-suggests 
> --install-recommends --fix-broken --fix-missing
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>   x2goserver : Depends: x2goserver-x2goagent (>= 
> 4.1.0.0-0~1517~ubuntu16.04.1) 
> but it is not going to be installed
>Depends: x2goserver-x2goagent (< 
> 4.1.0.0-0~1517~ubuntu16.04.1.1~) 
> but it is not going to be installed
> E: Unable to correct problems, you have held broken packages.

Cannot reproduce:

ionic-Standard-PC-i440FX-PIIX-1996 ~ # add-apt-repository ppa:x2go/stable
You are about to add the following PPA:
 Quick howto to turn your machine into an X2Go server:

sudo apt-add-repository ppa:x2go/stable
sudo apt-get update
sudo apt-get install x2goserver x2goserver-xsession
sudo apt-get install x2gomatebindings  # if you use MATE/mubuntu
sudo apt-get install x2golxdebindings  # if you use LXDE/lubuntu

Quick howto to install the x2goclient:

sudo apt-add-repository ppa:x2go/stable
sudo apt-get update
sudo apt-get install x2goclient

Enjoy!
 More info: https://launchpad.net/~x2go/+archive/ubuntu/stable
Press Enter to continue or Ctrl+C to cancel

Executing: /tmp/tmp.hDxxLtwHbD/gpg.1.sh --keyserver
hkp://keyserver.ubuntu.com:80
--recv-keys
0A53F9FD
gpg: requesting key 0A53F9FD from hkp server keyserver.ubuntu.com
gpg: key 0A53F9FD: public key "Launchpad PPA for x2go" imported
gpg: Total number processed: 1
gpg:   imported: 1  (RSA: 1)
ionic-Standard-PC-i440FX-PIIX-1996 ~ # apt-get update
Hit:1 http://archive.ubuntu.com/ubuntu xenial InRelease
Get:2 http://ppa.launchpad.net/x2go/stable/ubuntu xenial InRelease [23,8 kB]

Hit:3 http://archive.ubuntu.com/ubuntu xenial-updates InRelease

Hit:4 http://security.ubuntu.com/ubuntu xenial-security InRelease

Hit:5 http://archive.canonical.com/ubuntu xenial InRelease

Hit:6 http://archive.ubuntu.com/ubuntu xenial-backports InRelease

Ign:7 http://packages.linuxmint.com sylvia InRelease

Hit:8 http://packages.linuxmint.com sylvia Release
Get:9 http://ppa.launchpad.net/x2go/stable/ubuntu xenial/main Sources [5.148 B]
Get:11 http://ppa.launchpad.net/x2go/stable/ubuntu xenial/main amd64 Packages
[17,4 kB]
Get:12 http://ppa.launchpad.net/x2go/stable/ubuntu xenial/main i386 Packages
[17,4 kB]
Get:13 http://ppa.launchpad.net/x2go/stable/ubuntu xenial/main Translation-en
[9.256 B]
Fetched 72,9 kB in 0s (95,5 kB/s)
Reading package lists... Done
ionic-Standard-PC-i440FX-PIIX-1996 ~ # apt-get install x2goserver
x2goserver-xsession
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
  libcapture-tiny-perl libconfig-simple-perl libdbd-pg-perl libdbd-sqlite3-perl
libdbi-perl libfile-which-perl libnx-x11-6
  libpq5 libswitch-perl libtry-tiny-perl libx2go-log-perl libx2go-server-db-perl
libx2go-server-perl libxcomp3 libxcompshad3
  libxfont2 nx-x11-common nxagent openssh-server openssh-sftp-server pwgen
x2goserver-common x2goserver-x2goagent
Suggested packages:
  libmldbm-perl libnet-daemon-perl libsql-statement-perl rssh molly-guard
monkeysphere rdesktop
Recommended packages:
  ncurses-term ssh-import-id sshfs x2goserver-extensions x2goserver-fmbindings
x2goserver-printing
The following NEW packages will be installed:
  libcapture-tiny-perl libconfig-simple-perl libdbd-pg-perl libdbd-sqlite3-perl
libdbi-perl libfile-which-perl libnx-x11-6
  libpq5 libswitch-perl libtry-tiny-perl libx2go-log-perl libx2go-server-db-perl
libx2go-server-perl libxcomp3 libxcompshad3
  libxfont2 nx-x11-common nxagent openssh-server openssh-sftp-server pwgen
x2goserver x2goserver-common x2goserver-x2goagent
  x2goserver-xsession
0 upgraded, 25 newly installed, 0 to remove and 0 not upgraded.
Need to get 4.764 kB of archives.
After this operation, 14,1 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
[...]
ionic-Standard-PC-i440FX-PIIX-1996 ~ # x2goversion
x2goserver-common: 4.1.0.0
x2goserver-x2goagent: 3.5.99.15
x2goserver-xsession: 4.1.0.0


Working as expected for me.


I then went on to install x2goserver from the Saimaa repository to emulate an
upgrade test from the old packages to the current ones:

[install Saimaa X2Go Server]
ionic-Standard-PC-i440FX-PIIX-1996 ~ # add-apt-repository -r ppa:x2go/saimaa
You are about to remove the following PPA:
 Bundle release of X2Go named ,,Saimaa'' (based on X2Go Server / Client 4 /
nx-libs 3.5.0)
 More info: https://launchpad.net/~x2go/+archive/ubuntu/saimaa
Press 

Re: [X2Go-User] LinuxMint 18.3 upgrade fails

[Mihai Moldovan]

* On 03/11/2018 04:39 AM, Robert Dinse wrote:
>   Also, all repositories older than artful wanted to use the 3.5.0 libs
> but need 3.5.99 to get the proper version of xrandr for Mint 18.3.

Switching to packages for a newer system version than you have isn't a good 
idea...

I'll install a Mint 18.3 VM to figure out what might be wrong, if I can
reproduce the problem.



Mihai




signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] Problems after upgrading to recent x2go-server and x2go client releases

[Mihai Moldovan]

* On 03/08/2018 07:52 PM, Stefan Baur wrote:
> Could we change the mouse cursor over the sensitive area, maybe?  Or,
> undo the change and go back to a fully sensitive tile, but change the
> mouse cursor once it hovers over an editable field?

The problem isn't visual indication and changing the mouse cursor thus wouldn't
help. The fields are already highlighted when hovering over them, which gives
the same visual clue changing the cursor would.

The problem is human accuracy, as demonstrated by Fitts's Law. Pointing accuracy
decreases as the distance to or size of the target increase. Typically, the
distance is pretty high, so users often over- or undershoot the target box, even
if by just a few pixels.


Decreasing the sensitive area totally makes sense - I've had requests for this
from multiple users and my personal experience is also that it was frustrating
to change settings directly in the tiles before since every and now and then you
ended up starting the session instead of changing a setting.


I'd generally advise to trigger sessions by clicking a pointer near the session
icon (or in any area horizontally or vertically from it).


Mihai



signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] Problems after upgrading to recent x2go-server and x2go client releases

[Mihai Moldovan]

* On 03/07/2018 07:34 PM, h i wrote:
> I've been experiencing problems with opening applications and resizing my x2go
> client window after installing the newest version x2go-server.
> 
> 
> The issues occurs on Ubuntu 14.04 and 16.04.
> 
> 
> What happens now is that every time I maximize my x2go-client window, the 
> images
> on screen rapidly flicker and won't stop until I minimize the screen.

The flickering is a known problem, but as far as we can tell only appears on
Windows (and even then not with all X servers, but prominently with VcXsrv, that
we bundle). It's tracked here: 
https://github.com/ArcticaProject/nx-libs/issues/600


> Also, each time I move the window, a quick flicker occurs across the screen.
Probably related to the move being something alike to a resize and thus also
triggering the new xinerama code.


> This never occurred before this new release.

There is no known workaround currently, though it might be possible to just
ignore multiple resize events in nxagent if the requested size doesn't change.
We'll have to see how that goes.


> On the client side, I upgraded to the 4.1.1.1 from 4.1.0.0 and experienced 
> some
> issues. I have to click on the outside/top-right edge of the session panel for
> the login session window to appear. Any thing closer to the middle, and it 
> won't
> respond.

This is not an issue, but an often requested new feature. I've changed the
click-sensitive area to an upside-down L shape around the session settings that
can be modified within the tile. Actually like this, where "s" denotes a
click-sensitive area:

 ___
|sss|
|sss|
|sss|
|sss|
|sss|
|sss|
 ---

The problem so far has been that users can normally edit some exposed settings
within a tile, but doing so proved to be very difficult since an incorrect click
triggered a session startup instead of changing a setting, which was happening
quite often.

The sensitive area isn't small and figuring that out shouldn't take long
usually, so I guess you've just been unlucky to always click on the right hand
side which is typically insensitive but in the upper part.


> I also get a pop-up message about the sound that I had not experienced
> with previous versions.

What does the Popup say? Was it unable to start PulseAudio? Is there any way to
reproduce that?

If possible, a debug log would be good to have, including the PA server config
file that is left somewhere in your user's directory when starting the debug
version of the client.

You'd have to install the debug version and start it in a command line terminal,
redirecting output to a file, such as:

path\to\x2goclient.debug.exe --debug >
by\your\user\writeable\path\x2goclient-debug.log 2>&1


> Once logged into a session, the flickering resulting
> from moving/maximizing the window is much worse.
> 
> Fortunately, I was able to revert back to x2go-client 4.1.0.0.

Huh, the flickering should be always the same, whether a session has been
started with 4.1.1.1 or 4.1.0.0. Though, potentially there could be a
difference: versions prior to 4.1.1.1 won't be able to utilize the Xinerama
feature in X2Go Server 4.1.0.0, so when connecting with older client versions
Xinerama will always be disabled in nxagent.


> However,is there a way to revert back to this previous version/configuration
> of x2goserver. Right now, it is has been a lot of flickering while to trying 
> to
> do routine tasks with the current release.

That's what the Saimaa release is for. You'll have to switch repositories and
make sure to pin the release.

After doing so, you should be following issue reports that affect you and
eventually switch back to the stable server release, since Saimaa is not getting
any bug fixes or new features, apart from security-related issues.



Mihai



signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] nxagent

[Mihai Moldovan]

* On 03/04/2018 10:51 AM, Robert Dinse wrote:
>   It hasn't happened to me so I don't know what the people are doing 
> before
> it gets stuck, could be mate, kde, lxde, lfce, openbox, they're all on there.
> Next time it happens I'll trace it to see what it is doing.

Please follow https://github.com/ArcticaProject/nx-libs/issues/671



Mihai




signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] nxagent

[Mihai Moldovan]

* On 03/04/2018 01:54 AM, Robert Dinse wrote:
>   Yes consuming a large amount of CPU and not doing anything useful, 
> customer is disconnected.  Connection is still possible but doesn't get rid
> of the stuck processes, I have to kill -9 to get rid of them.

Uhm... "stuck" is pretty ambiguous in that context - I assume that you are
referring to the CPU usage, which doesn't go down to sane levels even after
reconnecting, but reconnecting to the session as such is possible?

Is there any reasonable way to trigger this behavior? Like starting a MATE
session, disconnecting and waiting for an hour to see the CPU usage spike? Or is
it triggered by other programs running inside of the session?

I'll need something to reproduce it, server OS information would also be great.

There is https://bugs.x2go.org/1260 which sounds like the same issue, but I
haven't had time to get into this yet. This issue is observable on Fedora 27,
but if it's even observable on Debian or Ubuntu or other distros it would also
be interesting information.



Mihai




signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] nxagent

[Mihai Moldovan]

* On 03/04/2018 01:35 AM, Robert Dinse wrote:
>   We are seeing nxagent processes stuck running in a loop when the 
> customer
> is no longer logged in.

Stuck in a loop, i.e., using a high amount of CPU resources and not doing
anything useful? Is connecting still possible? Does the usage return to normal
levels after that?


Mihai



signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] Upgrades

[Mihai Moldovan]

* On 03/03/2018 04:45 AM, Robert Dinse wrote:
> 
>   I have now had three different machines, a ubuntu server, a mint server,
> and a zorin server with the most recent builds installed display very strange
> behavior.
> 
>   Initially they work, I connect, and at some point during the session,
> it disconnects, tells me to check my network.
> 
>   I go to reconnect and in the main window it says:
> 
> Loop: PANIC! Failure negotiating the session in stage '7'.
> Error: Failure negotiating the session in stage '7'.
> Loop: PANIC! Wrong version or invalid session authentication cookie.
> Error: Wrong version or invalid session authentication cookie.
> Session: Terminating session at 'Fri Mar 2 19:06:40 2018'.
> Session: Session terminated at  'Fri Mar 2 19:06:40 2018'.
> 
>   I also get a POP UP that says:
> 
> The remote proxy closed teh connection while negotiating the session. This 
> may 
> be due to the wrong authentication credentials passed to the server.
> 
>   Once it enters this state I can not connect to the server again. 
> Rebooting both client and server does not fix the problem (and this wipes out
> everything in  /tmp and /var/tmp as I have both in tmpfs file systems).
> 
>   The only thing I've found that fixes it is completely purging the server
> x2go software and re-installing it.

Reinstalling shouldn't change any state, other than maybe reinitializing the
database.

When this happens, are there still x2goagent or nxagent processes around? Do
x2glistsessions_root, x2gogetports, x2gogetdisplays report sane values?


Maybe x2goagent is crashing or otherwise misbehaving.

Is there any known trigger for this?



Mihai



signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] LinuxMint 18.3 upgrade fails

[Mihai Moldovan]

* On 03/03/2018 01:49 AM, Robert Dinse wrote:
>   Trying to install x2go stable x2goserver on Ubuntu 17.10 I am getting:
> 
> The following packages have unmet dependencies:
>   x2goserver : Depends: x2goserver-x2goagent (>= 
> 4.1.0.0-0~1517~ubuntu17.10.1) 
> but it is not going to be installed
>Depends: x2goserver-x2goagent (< 
> 4.1.0.0-0~1517~ubuntu17.10.1.1~) 
> but it is not going to be installed
> 
>   ... However the Nightly Builds installed and functions fine.


I'll need the full output, I'm afraid.

x2goserver-x2goagent-4.1.0.0-0~1517~ubuntu17.10.1 is available in the repository
as far as I can tell, so I do not know what supposedly blocks its installation.



Mihai



signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] LinuxMint 18.3 upgrade fails

[Mihai Moldovan]

* On 03/03/2018 12:37 AM, Robert Dinse wrote:
>   Question: It appears that the various libs in lib-nx that used to be
> separate deb packages on Ubuntu/Debian, etc, have been replaces with a single
> nx-11-common package, is this correct?

Nope, wrong.

-common packages, as always in Ubuntu/Debian context, only contain shared,
architecture-independent data.

The libraries that have been removed from the new nx-libs package are really
gone. nx-libs (and in particular nxagent) now uses more system libraries instead
of bundling older versions itself.

So seeing less packages being installed is correct.



Mihai



signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] LinuxMint 18.3 upgrade fails

[Mihai Moldovan]

* On 03/02/2018 12:18 PM, Stefan Baur wrote:
>> -After the most resent update:
>>
>> x2goagent : Depends: nxagent (< 2:3.5.0.33-0~710~ubuntu16.04.1.1)
>>
>> -however,
>> nxagent is already the newest version (2:3.5.99.14-0~816~ubuntu16.04.1).
>
> Please wait until all the builds have completed, then try again.

Was caused by x2goserver release builds not being ready yet.

All supported platforms should now feature updated x2goserver packages.

The dependency problems should be gone by now.



Mihai




signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] Mint

[Mihai Moldovan]

* On 03/02/2018 07:37 AM, Robert Dinse wrote:
> 
>   The output of:
> 
>   dpkg -l | grep -iE '(x2go|nx)'?
> 
>   ... Was too large to post to the list so I've thrown it up on my ftp
> server, you can retrieve it from ftp.eskimo.com, username: anonymous,
> password: (your e-mail address).  It is x2go-mint.txt.

Naturally without the ? character at the end, but in any case, you're on the
release version.

Hmm, that error message is weird. It indicates that the remote proxy sent
garbage, while the other side expected a version number.

What's the client OS? What packages are used there?



Mihai



signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] Mint

[Mihai Moldovan]

* On 03/02/2018 07:04 AM, Robert Dinse wrote:
> 
>   I just did:
> 
>   apt purge *x2go* nx* libnx*
> 
>   Followed by:
> 
>   apt install x2goserver --install-suggests --install-recommends
> 
>   And still get that same pop-up.  This is on:

Hm, dpkg -l | grep -iE '(x2go|nx)'?



Mihai




signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] Mint

[Mihai Moldovan]

* On 03/02/2018 12:53 AM, Robert Dinse wrote:
>   The nightly builds won't install and the stable doesn't work.  When I
> try to login I get a pop-up:
> 
> The remote proxy closed the connection while negotiating
> the session. This may be due to the wrong authentication
> credentials passed to the server.

Is this still a problem?

I've fixed it up yesterday already for Debian, Fedora, CentOS, ... builds.

Launchpad reportedly built new packages 3 hours ago, I guess I should have
kicked that earlier but forgot.



Mihai



signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] Upcoming Deprecation of (Almost) EOL Distributions

[Mihai Moldovan]

The deprecation has been fully finished.



Mihai



signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] can't connect to session

[Mihai Moldovan]

* On 01/24/2018 08:36 AM, Robert Dinse wrote:
>   Yes, you gotta love systemd.  There is an upside though, it's about
> two seconds between the time my BIOS fires off the boot block and I've got a
> desktop login screen, under the old start up system it was more like 30 
> seconds.

... unless you suddenly find yourself in the never-ending cylon eye situation
(ask Stefan).


Anyway, new x2goserver builds (minus FC26, since there's a problem with
upstream's metadata it seems) now feature a /etc/tmpfiles.d/x2goserver.conf file
on systems using systemd.

Hope that will protect session data from now on.



Mihai



signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] can't connect to session

[Mihai Moldovan]

* On 01/22/2018 10:28 PM, Andrew Munn wrote:
> Thanks!
> I've added the following line to /usr/lib/tmpfiles.d/tmp.conf
> 
> x /tmp/.x2go-*
> 
> Hopefully that fixes it.

Then again, according to
https://developers.redhat.com/blog/2016/09/20/managing-temporary-files-with-systemd-tmpfiles-on-rhel7/
and the general file system hierarchy, /usr/lib is not a good place to make 
changes.

Thankfully you should be able to move this into /etc/tmpfiles.d/x2go.conf and
have that setting persist between system updates.


> Do you think there should be some automated 
> process to append that line during installation on a CentOS/RHEL system?

Yes, I should add this file to the general packaging! It's impressive how many
workarounds are necessary for systemd in order for it not to break everything...



Mihai



signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] can't connect to session

[Mihai Moldovan]

* On 01/16/2018 02:32 AM, Andrew Munn wrote:
> I get reasonable output from x2golistsessions_root.  I also see a matching 
> directory in /tmp/.x2go-$user/ containing 3 files:
> 
> [root@hercules C-andrew-51-1513021653_stDMATE_dp24]# ls
> total 12
> -rw-rw-r-- 1 andrew andrew  1 Jan 10 08:56 options
> -rw-rw-r-- 1 andrew andrew 12 Jan 10 08:56 sshd.pid
> -rw-rw-r-- 1 andrew andrew  8 Jan 10 08:56 state
> [root@hercules C-andrew-51-1513021653_stDMATE_dp24]#

Hm, that doesn't look right. A suspended session's directory should contain many
more files, like a spool symlink, a cache directory, a mimebox symlink, an
options file, a cmdoutput file, a state file and maybe others.

I really do believe that something is deleting files in /tmp/ without you
knowing it!

Did you really check for a cron job or the like that might clean up /tmp/? It
looks like CentOS 7 has this configurable in /usr/lib/tmpfiles.d/tmp.conf and
uses systemd for that purpose.



Mihai



signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] Ubuntu Nightly Builds Server Problem

[Mihai Moldovan]

* On 01/14/2018 04:22 AM, Robert Dinse wrote:
>   Unfortunately, it created a different error:

All this code is new, so I'm not surprised. :)

> Connection failed. /usr/lib/x2go/x2gogetfreeport: line 47: typeset: '65535':
syntax error: operand expected (error token is "'65535'")

Hmm, that line doesn't match up with the actual sources. I see what's going on.
That'll require some more work.

Please apply
https://code.x2go.org/gitweb?p=x2goserver.git;a=commitdiff;h=b1341c2d9aaac8e1383336a2bd2ce3e65f569c86



Mihai



signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] Ubuntu Nightly Builds Server Problem

[Mihai Moldovan]

* On 01/14/2018 03:28 AM, Robert Dinse wrote:
>   After installing updates today Ubuntu 17.10 server with x2gonightly
> builds now will not allow me to connect.  When I try I get a pop-up that says:
> 
>   Connection failed. /usr/lib/x2go/x2gogetrandomport: line 106:
>   get_random_port: command not found Unable to get
>   (pseudo-) randomized starting port value.
> 
>   The stable build still works except the xrandr version issue which was
> why I have been using the Nightly Builds on Ubuntu.

Did you merge /etc/x2go/x2goserver.conf correctly after the update?

What does the file look like right now?



Mihai



signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] can't connect to session

[Mihai Moldovan]

* On 01/10/2018 04:13 PM, Andrew Munn wrote:
> I'm seeing this situation again. I can see the session in the client as 
> usual by when I click on it nothing happens.  I think someone in another 
> thread mentioned running out of available ports as a possible cause.  Is 
> that right?  What's the solution here?  I want to reconnect to the session 
> without killing my running applications.

Running out of usable ports is possible, but shouldn't happen unless the session
database is not cleaned up properly or there are huge amounts of sessions 
running.

Does x2golistsessions_root output something reasonable?


I've recently worked on port detection. This probably will not really help if
there are no free ports left, but at least pass back a more or less useful
message to x2go client in such as case.

It's not part of any released code yet, so nothing you would care in the first
place anyway.


Are you positive that session data is still available either in ~user/.x2go or
/tmp/.x2go-$user/?


Note that some systems delete files out of /tmp regularly!



Mihai



signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] New x2go broken on Ubuntu 17.10

[Mihai Moldovan]

* 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 ?S17: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



signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] New x2go broken on Ubuntu 17.10

[Mihai Moldovan]

* 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



signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] New x2go broken on Ubuntu 17.10

[Mihai Moldovan]

* 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




signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] New x2go broken on Ubuntu 17.10

[Mihai Moldovan]

* 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



signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] New x2go broken on Ubuntu 17.10

[Mihai Moldovan]

* 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



signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] New x2go broken on Ubuntu 17.10

[Mihai Moldovan]

* 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



signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] New x2go broken on Ubuntu 17.10

[Mihai Moldovan]

* 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



signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] New x2go broken on Ubuntu 17.10

[Mihai Moldovan]

* 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



signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] New x2go broken on Ubuntu 17.10

[Mihai Moldovan]

* 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



signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] New x2go broken on Ubuntu 17.10

[Mihai Moldovan]

* 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



signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] Client 4.1.1.0 for Windows

[Mihai Moldovan]

* On 11/27/2017 12:45 PM, Mario Brese wrote:
> is there a time intended to provide the new Client version for Windows?

Sadly, not yet. I can't provide an ETA.

The Windows maintainer has identified problems when connecting via Kerberos
credentials with this new version and intends to fix this issue before making a
proper release.



Mihai



signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] install x2gobroker

[Mihai Moldovan]

* On 11/17/2017 10:34 AM, Mike Gabriel wrote:
> An update version of python(2,3)-wsgilog is available via Debian unstable.
> 
> I am currently negotiating with Mihai, who will add that package  
> version to our x2go-extras repo area.

For Debian Wheezy, Jessie and Stretch, I have uploaded rebuilt python-wsgilog
and python3-wsgilog packages in the extras component.

Users will need to replace "heuler" in your .lists file with "extras heuler" to
get it. Dependency resolution should work fine after that.


For Ubuntu, I took a shortcut and updated our current package override directly,
so no additional codename is required to get the backported package.


No work has yet been done for RPM-based distributions. I guess I'll have to do
that as well at some point.



Mihai



signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] can't connect to session

[Mihai Moldovan]

* On 11/19/2017 11:21 AM, Andrew Munn wrote:
> Yes deleting /tmp/.x2go-$USER did fix it.  It happens rarely.  I'm not 
> sure how long the session runs before this occurs. A fix for this issue 
> would be great.  Thanks for the suggestion!

Uh, no, my suggestion was *not* to delete this data, it was to make sure that
*nothing* deletes this data in the first place.

Congrats, in the best case x2gocleansessions killed the session after the
metadata vanished, in the worst case you have a stale x2goagent/nxagent process
still running...



Mihai



signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] can't connect to session

[Mihai Moldovan]

* On 11/18/2017 09:32 AM, Andrew Munn wrote:
> Sometimes x2go works fine.  Other times I can't get the session back and 
> logs look like this.  server version 4.0.1.20.  Same results occur when 
> connecting from my Windows or Linux client.

Might that be the same problem as described by the other user - i.e., something
deleting files in /tmp/, which stores the session data?

Does that problem only happen after the session has been created for a while?



Mihai




signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] Hanging Session

[Mihai Moldovan]

* On 11/17/2017 09:27 AM, Markus Kuderer wrote:
> Taking a look on the open files (lsof) shows that the session log file 
> in /tmp has been deleted meanwhile:
> /tmp/.x2go-lmegast5/C-lmegast5-50-1507636342_stDGNOME_dp32/session.log 
> (deleted)
> (background: "old" files in /tmp are deleted automatically after 3 weeks 
> of beeing not used/touched)
> 
> I assume thats the reason why I cannot connect to the session again.
> 
> Do you have an idea how I might make the session working again or 
> overcome the problem in general?
> (I sometimes have simulations running for a longer time and the 
> result/evaluation will be done and shown within this session)

Please disable this automatic /tmp cleanup to avoid having such problems in the
future. Or make it smarter - e.g., by only deleting old files that are bigger
than say 5 MB.

There is no trivial way to connect back to the session with X2Go Client after
the session metadata has been deleted.


One thing you could try is to start a new "identical" session, then take a copy
of this session data, then terminate the session again and put the copy of the
session data in place of the old deleted session data. Doing so, make sure to
replace the differing parts, like DISPLAY number (will likely be 51 instead of
50) and UNIX timestamp, but maybe others as well. This holds for both the
directory name (of course), but also the contents of the files in there. And
it's quite a lot of data to change, for instance you'll also need to fetch the
TCP port to connect to and the authorization cookie.

Luckily, this information should still be available in the database.
x2golistsessions executed as the user in question on the server side should give
you the needed data.


A more manual way, bypassing X2Go session management, would be to connect to the
x2goagent process directly.

ssh -X (or ssh -Y) to the machine, then spawn another shell on that machine,
then execute x2golistsessions.

After you've got the needed information, connect directly via
nxproxy -S nx/nx,cookie=$SESSION_COOKIE,connect=localhost,port=$TCP_PORT:50

On the other terminal issue kill -HUP $AGENT_PID.


$AGENT_PID is the integer in the first column of the output.
$SESSION_COOKIE is the 32 character string in the 7th column.
$TCP_PORT is the integer in the 9th column.


After that, just wait. The proxy should be able to connect.


Note that this is using SSH X11 forwarding, so it will be very slow depending on
both links.



Mihai



signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] Vim

[Mihai Moldovan]

* On 11/17/2017 03:52 AM, Robert Dinse wrote:
>   I have EDITOR set to /bin/ex and VISUAL set to /bin/vi but apparently
> that is not sufficient in Centos6.

No, because, like I said, both CentOS 6's and 7's sudo packages hard-depend upon
vim-minimal currently.



Mihai



signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] Vim

[Mihai Moldovan]

* On 11/17/2017 03:24 AM, Jason Heeris wrote:
> If it's anything like Debian, sudo might depend on an editor (*any* editor) so
> that sudoedit works, and vim is just the first one in a dependency OR 
> condition.
> Do you have another console editor installed (like Pico, Micro, Emacs)?

Yes, in theory. Though see my previous mail.


They currently hard-depend upon vim-minimal.


Maybe Debian and derivatives solved this in a better way through their
alternatives subsystem.



Mihai



signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] Vim

[Mihai Moldovan]

* On 11/17/2017 03:17 AM, Robert Dinse wrote:
>   Should be but centos6 is an ancient kludge.  I really should move this
> stuff to a modern ubuntu installation.

I've just looked it up. sudo on CentOS 7 depends upon vim-minimal, although a
comment in the ChangeLog mentions "visudo requires vim-minimal or setting EDITOR
to something useful (#68605)"

The bug report referenced is https://bugzilla.redhat.com/show_bug.cgi?id=68605 -
and it looks like this is where vim-minimal was added as a dependency.


So it looks like even CentOS 7 has this bug.

Working around it is difficult, though, since without a proper EDITOR
environment variable set, depending on vim-minimal makes sense to get visudo
working.

The alternative would be defaulting to nano for the EDITOR variable and
depending upon nano, but this will just shift the problem to users who hate 
nano.


Just to be clear - this issue is present on both CentOS 6 and 7... and I figure
Debian (or Ubuntu) don't fare better, but I haven't tested these systems.



Mihai



signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] Vim

[Mihai Moldovan]

* On 11/17/2017 03:13 AM, Robert Dinse wrote:
>   On CentOS6, if I remove vim, it removes x2goserver and 
> x2goserver-xsession.  If I re-install these, it install vim-minimal.
> 
>   Yum tells me it requires sudo and vim-minimal.

That makes sense. x2goserver does indeed depend upon sudo, but certainly not on
vim itself.

sudo depending on vim sounds like a bug in EPEL 6/CentOS 6 instead. It should be
editor-agnostic.



Mihai




signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] x2go-Server needs 5 minutes to respond

[Mihai Moldovan]

[Resent with correct header, because I messed up myself this time.]

On 11/14/2017 09:35 AM, K. Reinhold Trier wrote:
> thank you, it helped.

Please remember to also include the mailing list when replying.

Okay, good. Watch the DISPLAY number (the first number after the user name in a
session ID.)

If it keeps raising during normal use to unnaturally large numbers, post another
reply please, since that would mean that session cleanup isn't working 
correctly.

More context: x2goagent DISPLAY numbers start at 50 and should naturally
increase with each new started session. When terminating a session, its DISPLAY
number is free'd and should be reclaimed by the next started session.

Hence, seeing a DISPLAY number of more than 100 for a new session while there
are, say, 20 sessions running would suggest that something's wrong.



Mihai






signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] x2go-Server needs 5 minutes to respond

[Mihai Moldovan]

On 11/13/2017 06:50 PM, K. Reinhold Trier wrote:
> last Thursday after an automatic update of the x2go-server our clients didn't
> receive any more answer from the server.

Yes, X2Go Server 4.0.1.21 was buggy when used with FQDN host names.

> This morning, after an other automatic update of
> the x2go-software, I noticed that clients could connect again

4.0.1.22 fixed this issue.


> - but after an
> unacceptable delay of about 5 minutes. Here our data:
> We are on Ubuntu 16.04.3 LTSUbuntu 16.04.3 LTS
> When starting x2goclient on a ubuntu client, after about 5 minutes it shows 
> the
> details:

It looks like it's taking a long time to find an available DISPLAY number. Given
that you're at 389 already, that's cause for concern.

I don't think that you have that many sessions running.

x2golistsessions_root (executed as root) only lists a few, if any, right?


It looks like we have a problem in the sense that if a session fails to start up
correctly, it's not evicted from the sessions database. It won't show up in
x2golistsessions(_root) either, which makes this even more opaue to users.

You probably started a lot of failed sessions in the past few days (well, you or
your users), which accumulated in the database and were never cleaned up.


To remedy this, please terminate all sessions.

Afterwards, as root, execute x2godbadmin --createdb.

That will re-initialize the database and get rid of stale failed sessions.

Startup should be faster afterwards.


If it's still not, something else that isn't easily visible is wrong.



Mihai



signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] Odp: opensuse client - reverse tunnel problem

[Mihai Moldovan]

On 10/17/2017 08:13 AM, Sebastian Turzański wrote:
> Hi
> I still experience this problem 
> Can anybody take a look at the debug output (pastebin link below)
> I suspect this can have something to do with x2goclient not generating the 
> content of ~./.x2go/etc
> the directory itself is not created either.
> 
> https://pastebin.com/uRzQnKcc
> 
> Dnia Sobota, 22 Października 2016 20:54 Sebastian Turzański  
> napisał(a) 
>> Is anybody able to use x2go client with reverse tunel (folder sharing and/or 
>> client side printing) om Opensuse 
>>
>> I get the same server with reverse ssh tunnel working perfectly well when 
>> connected from ubuntu
>> and failing if used from Opensuse Leap 42.1 nor Tumbleweed

I guess you're using an old version of X2Go Client that expected a system ssh
daemon to be running.

Upgrading should help.



Mihai




signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

[X2Go-User] Upcoming Package Repository Downtime

[Mihai Moldovan]

Hi


I will be releasing new stable versions of nx-libs and x2goserver soon.

Due to some file moves between packages, these releases must happen in lock-step
(or more specifically the binary packages built from these releases be available
at the same time).

In order to not potentially break user systems, I will disable access to the
package repositories on the UTC days of
  - Wed November 8, 2017
  - Fri November 10, 2017 (rain date)
for an unspecified amount of time.


If you experience problems accessing the package repositories on these days,
rest assured that this behavior is intentional. The repositories will be
available once new binary packages for these new releases are available.


A more fine-grained notice will be posted on the Wiki main page and removed
again once the situation is cleared.



Mihai



signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

[X2Go-User] Upcoming Deprecation of (Almost) EOL Distributions

[Mihai Moldovan]

Hi

In order to lower resource stress when building packages, I plan to deprecate
support for distributions that have (almost) reached End Of Life on December
31th 2017.


This includes the following distro versions:

- Debian:
  o 7.0 "wheezy"
- Fedora
  o 23
  o 24
  o 25
- OpenSuSE
  o 13.1
  o 13.2
  o 42.1

Ubuntu builds are ceased automatically after upstream deprecation.


After deprecation, no new builds will be published and existing builds will be
moved to the archive repositories to discourage users from installing
unmaintained software.



Mihai



signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] newbie question multiple monitors

[Mihai Moldovan]

On 11/01/2017 11:40 AM, Thomas Porschberg wrote:
> $ps -ef | grep x2go
> root 17045 1  0 11:06 ?00:00:00 /usr/bin/perl 
> /usr/sbin/x2gocleansessions
> pberg20099  7153  0 11:11 ?00:00:00 /usr/bin/x2godesktopsharing
> 
> My client is a laptop, also running Ubuntu 16.04.
> 
> When I create a new session I see on my laptop both physical monitors from 
> the server,
> divided vertically and of course blurred.
> 
> This is not usable. Can I somehow the client configure in way that I can 
> switch between the two physical monitors from the server?

If you are connecting to the local X display, this isn't possible currently.

Alternatively, switch the scaling mode via Ctrl-Alt-R. Afterwards, the image
should be non-scaled and navigation possible via Ctrl-Alt-Arrow keys.

I acknowledge that this isn't great, since the huge server-side window is still
being transferred whenever something changes remotely.


A workaround would be to start a separate desktop session with the desired
dimension - although some desktop environments don't support multiple concurrent
sessions for the same user.



Mihai



signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] X2goClient with SSH key

[Mihai Moldovan]

We solved this problem a while ago on IRC.

It boiled down to IPv6 connectivity problems (remote server advertised on 
record, on which the ssh daemon wasn't listening) - it wasn't an authentication
failure in the first place. :)



Mihai



signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] x2goclient MacOS

[Mihai Moldovan]

On 09/24/2017 01:25 AM, Robert Dinse wrote:
>   x2go-client versions 4.1.0.0 and 4.1.1.0 both core dump under MacOS X
> 10.7.5 (Lion).  4.0.0.1 does not but also will not login to a non-root account
> on Ubuntu server.

I have no way of reproducing that. We have deprecated 10.7 support and I don't
have a machine running that OS.

Can you start /path/x2go/x2goclient.app/Contents/MacOS/x2goclient --debug >
~/x2goclient.debug.log 2>&1 in a terminal session and provide the output, 
please?



Mihai



signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] x2go fails with tcsh

[Mihai Moldovan]

On 10/09/2017 12:44 PM, Frank Steiner wrote:
> I was able to solve this. When I looked into the code, I saw that you
> already to use "bash -c '...'" for all commands, so quoting shouldn't be
> an issue.

I really think it can get problematic easily, for instance with nested single
quotes, that require special handling that differs from shell to shell - same
thing for double quotes.

Looks like you weren't hit by that issue, though. :)


> But as the error message for tcsh was about
>   Warning: Protocol mismatch or no X authentication data.
> I started looking at xauth and found an interesting difference between
> bash and tcsh as login shell.
> 
> For bash, these entries are added by x2gostartagent:
> 
> myhost/unix:59  MIT-MAGIC-COOKIE-1  e938deb788659f0bf8c99069d199aff6
> myhost.ifi.lmu.de:59  MIT-MAGIC-COOKIE-1  e938deb788659f0bf8c99069d199aff6
> myhost.ifi.lmu.de:59  MIT-MAGIC-COOKIE-1  e938deb788659f0bf8c99069d199aff6

I knew that we're adding two entries, but it didn't come across that this might
be the issue. Great debugging! Thanks.

What feels odd is that there are three entries, two of which are equal. I'm not
sure where the third one is coming from - in a quick test, I only see two
entries on one of my sessions. Might be related to nxproxy adding another entry
via xauth as well, but it still feels odd.

Especially given that the two xauth calls in x2gostartagent both use
${HOSTNAME}, if ${HOSTNAME} is only "myhost", there should only be entries for
myhost/unix:DISPLAY and myhost:DISPLAY.


> For tcsh, I got those:
> myhost.ifi.lmu.de/unix:58  MIT-MAGIC-COOKIE-1  
> 7212fb8aa466de75ea0224a4d010f5e4
> myhost.ifi.lmu.de:58  MIT-MAGIC-COOKIE-1  7212fb8aa466de75ea0224a4d010f5e4
> myhost.ifi.lmu.de:58  MIT-MAGIC-COOKIE-1  7212fb8aa466de75ea0224a4d010f5e4
> 
> And that's the point! For some reason, x2go needs the cookie for
> display "myhost/unix" at some point and "myhost.ifi.lmu.de/unix"
> doesn't suffice.
> 
> Indeed, when I wrote a little bash script
> 
> #!/bin/bash
> echo $HOSTNAME
> 
> and called it with "ssh myhost bash -c './testscript'", it echoed 
> "myhost" with login shell bash, and "myhost.ifi.lmu.de" with 
> login shell tcsh.

That's very interesting. bash seems to automatically populate HOSTNAME according
to its man page, but the tcsh man page doesn't mention HOSTNAME at all -- only
HOST, which is populated automatically by the gethostname() libc call and (on my
system) returns the short hostname.

I guess HOST and HOSTNAME might be the shell equivalents.


It gets worse, though. I tested this on OS X, which is a BSD-like system. On
this system, tcsh's HOST and bash's HOSTNAME values were the same again, BUT
both included the domain name (and, incidentally, the 'hostname' program's
default behavior is to print the FQDN hostname, which corresponds to the
hostname returned by gethostname().)

This may not sound interesting at first, because OS X is not an X2Go Server
target, but according to the hostname man pages on FreeBSD, this matches this
system's behavior (and it would be nice to eventually support *BSD as well at
some point in time, even though that's not possible currently.)

Luckily, all of them support the -s flag to hostname, so I'll just make use of 
it.


> I'm not yet sure where this difference comes from, if it's deep inside
> bash and tcsh or in some server-wide login scripts from SuSE (it
> was not in the users dotfiles, we even removed them all).

Whatever sets it, it's not tcsh itself. Likely some global startup script. Care
to grep -R HOSTNAME /etc?

The problem at hand really is that something sets and exports HOSTNAME. Since
this variable is then defined in the environment, bash won't touch it. Clearly
x2gostartagent uses bash (even if called from a tcsh shell) - but it inherits
the exported HOSTNAME value and stuff goes boom. In my opinion, that's a bug
that the distro should take care of. IMHO, the global startup scripts can set
HOSTNAME, but shouldn't export this variable to the environment.


> Anwyay, I added "setenv HOSTNAME `uname -n`" to my .cshrc and:
> x2go works :-)

Better use hostname -s.


> To make that work for all our users I added 
>   HOSTNAME=${HOSTNAME%%.*}
> into x2gostartagent which doesn't harm if HOSTNAME is already
> without the domain. So maybe you could add this to the next
> release to help people running into the same issue.

I'll fix up the server script.



Mihai



signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] x2go fails with tcsh

[Mihai Moldovan]

On 10/08/2017 12:31 AM, Frank Steiner wrote:
> I see, but that was the latest version the opensuse build repositories offer.
> I'll try to compile form source.

Typically more recent versions are available from our repository, that is
automatically populated with release and nightly builds - but you shouldn't mix
OBS packages with our repository. More information, as always, on the wiki:
https://wiki.x2go.org/doku.php/wiki:repositories:suse


> Ok, I understand that. Getting quoting right for different shells is more
> than complicated...

Yeah, but I don't even want to get it right. I'd rather spawn bash and let it do
the parsing, since that's providing the behavior we actually expect and use
currently.


> We had similiar problems in configuring a host with a bunch of ssh commands.
> Our solution was to create a bash script with all the neccessary code on 
> the client side on the fly, copy it over to the target host and execute it 
> there. Could that be solution here?

I've been thinking about this, yeah. I'd generally like to avoid writing
temporary files and pushing them to the server for every command that the client
executes, but unless I can come up with a better solution I'll probably have to
go with that. As always, no ETA on that, though. Might take quite some time to
get this done.



Mihai



signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] x2go fails with tcsh

[Mihai Moldovan]

On 10/07/2017 01:07 PM, Frank Steiner wrote:
> we just tried to x2go for the first time (client 4.0.5.2 server 4.0.1
> on SLED 12). It works fine for users with bash as login shell on the
> server side, but fails for those with tcsh.

4.0.5.2 is quite old by now. This said, the change that explicitly calls bash on
session startup came in with 4.0.5.0 (which used "sh" previously) and was
updated to use bash as login shell explicitly was part of 4.0.5.1, so 4.0.5.2
should be able to handle that situation.


> According to 
> http://blog.x2go.org/index.php/2012/07/26/x2go-sessions-startups-for-users-with-non-bash-like-shells-e-g-tcsh-and-alike/
> this should have been fixed a while ago, but it seems to have returned.

The mentioned change is very old and relied on executing "sh". We've seen users
changing this to non-bash compatible shells in the past, so it didn't fix all
issues.


> I couldn't see any difference neither in the server log (debug level)
> nor in the output of "x2goclient --debug". The clients are identical until
> the line 
> 
> x2go-DEBUG-../src/onmainwindow.cpp:6014> Proxy wrote on stderr: "Session: 
> Session started at 'Fri Oct  6 16:43:09 2017'.
> 
> and then the tcsh instance exits with
> Warning: Protocol mismatch or no X authentication data.
> 
> while the bash version continues with 
> x2go-DEBUG-../src/onmainwindow.cpp:6014> Proxy wrote on stderr: "Info: 
> Established X server connection.
> 
> The server logs are identical until the line
> 2017-10-06T16:43:09.173981+02:00 knuth 
> /usr/lib/x2go/x2gocreatesession[21667]: db_createsession called, session ID: 
> fst-76-1507300986_stDmwm_dp24, cookie: 7b94de4d7f6bdbcda01a3dc547c42f66, 
> client: xx:xx:xx:xx, pid: 21620, graphics port: 35760, sound port: 35761, 
> file sharing port: 35762
> 
> and then the tcsh instance  exits with
> 2017-10-06T16:43:15.007175+02:00 knuth sshd[21228]: pam_unix(sshd:session): 
> session closed for user fst
> 2017-10-06T16:43:15.011998+02:00 knuth systemd-logind[9940]: Removed session 
> 59.

Yeah, because nxagent died or wasn't started correctly, so the session 
terminates.


> Is this problem known already? Sth. I could try to solve it? We wouldn't
> like to force all our users to switch away from their tcsh...

No, but I guess I know what the problem is. Quoting in bash and tcsh is
different (esp. nested double quotes, which don't work by default in tcsh but is
a special option), so some (or all) commands might not be getting executed
correctly.

I guess we'll need a more sophisticated approach that executes bash directly
once and then uses a bash instance to parse the command line instead of letting
the user's default shell handle parsing the initial command.

Sorry, I can't offer a workaround. It's just buggy currently.



Mihai



signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] ssh-keygen.exe loads the processor every time the client starts

[Mihai Moldovan]

On 09/28/2017 01:49 PM, Max A. wrote:
> I'm using a x2go server on CentOS 6.9 (the latest version from EPEL, 
> 4.0.1.20), clients use Windows XP/7 and the latest version of X2Go 
> Client (4.1.0.0-2017.03.11). Each time the client connects, 
> ssh-keygen.exe (C:\Program Files\x2goclient\ssh-keygen.exe) starts with 
> the parameters "-t rsa -b 4096 -N" "-C" X2Go Client RSA user key "-f C: 
> /Users/max/.x2go/ssh/gen/key.fl1416 ". On not very powerful computers, 
> this causes a delay of a few seconds with each connection and irritates 
> users. Tell me please, if it is possible to generate this key once and 
> for all?

I understand that this may be inconvenient, but no, there's currently no way to
generate a set of keys that will be re-used.

I explicitly decided against that. For more information and the rationale for
this change, refer to the release announcement:
http://lists.x2go.org/pipermail/x2go-announcements/2017/000302.html



Mihai



signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] changing keyboard settings from a Mac to 4.0.1.20 & MATE fails to login

[Mihai Moldovan]

On 09/08/2017 10:31 PM, Robert Kudyba wrote:
> See attached screen shot and suggested commands to run. This is Fedora 26. Any
> ideas?
> 
> Name : x2goserver
> Version  : 4.0.1.20
> Release  : 2.fc26
> Arch : x86_64
> Size : 309 k
> Source   : x2goserver-4.0.1.20-2.fc26.src.rpm
> Repo : @System
> From repo: @commandline
> Summary  : X2Go Server
> URL  : http://www.x2go.org
> License  : GPLv2+
> 
> 
> xprop -root | grep XKB
> _XKB_RULES_NAMES_BACKUP(STRING) = "xorg", "pc105", "us", "", 
> "grab:break_actions"
> _XKB_RULES_NAMES(STRING) = "xorg", "pc105", "us", "", "grab:break_actions"

This is more or less the intended behavior. You cannot and shouldn't be allowed
to change the xkb settings in the remote session when connected from an OS X
client. The XKB settings here are weird though - while they look better in the
forwarded message.


OS X is very special in this regard and seems to set "fake" values, which are
mapped differently internally (most likely via Quartz integration.)

If you change the keyboard layout in the remote session, you will only get a
very garbled layout - even though the same settings would be working fine from
Linux or Windows clients.


AFAIK the functionality to disallow XKB changes is broken though, so I wonder
why it's working in this instance.


Also, given that the session did start up, what do you mean by "fail to login"?
Getting a screenshot of a working session from a failed login would be rather
difficult...



Mihai



signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] RPMs for OpenSUSE Leap 42.3?

[Mihai Moldovan]

On 08/02/2017 06:04 AM, Bruce Ferrell wrote:
> There don't seem to be any right now and as promised, OBS doesn't work.
Yes, there currently aren't OpenSUSE Leap 42.3 builds.

I've already started working on this, should be done in a couple of days.

What exactly did you mean by "as promised"?



Mihai



signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] release of client version 4.1.0.1

[Mihai Moldovan]

On 08/08/2017 02:44 PM, Martin BALVERS wrote:
> When do you expect to release the windows client version 4.1.0.1 ?
> It fixes a very annoying bug with the PATH variable.
> https://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=1100

I currently don't have a release plan for it.

There are SSH connection problems that I need to fix before I'd even consider 
it.

If needed, we also have nightly builds. Not supported of course.



Mihai



signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] X2Go crash from Mac/MATE to Fedora 25 w NIS user getting x2gostartagent: blocking creation of agent's keyboard file

[Mihai Moldovan]

On 01.03.2017 09:01 AM, Robert Dinse wrote:
>   With Fedora 25 it was working with Mate fine for me until very recently,
> as recently as February 7th.  Then some update broke it.  Because several 
> things were updated simultaneously, x2go, mate, and libc, it is hard to know
> which was the cause but mate-session and many xfce programs all core with
> a segfault in libc.
> 
>   I am now in the process of restoring the machine from a February 7th
> backup and will update things individually to determine which broke.

Please check the other messages to the thread, it looks like a MESA upgrade
provoked these failures.



Mihai




signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
http://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] X2Go crash from Mac/MATE to Fedora 25 w NIS user getting x2gostartagent: blocking creation of agent's keyboard file

[Mihai Moldovan]

On 28.02.2017 11:43 PM, Norman Gaywood wrote:
> This might be the update to Mesa in Fedora
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=1427174
> 
> A lot of programs won't start in my XFCE desktop under x2go. Even 
> xfce4-terminal
> 
> The temporary fix is to downgrade mesa:
> 
> dnf downgrade mesa-libGL --allowerasing

Very useful information, thanks!

I had the user run glxinfo and on Fedora 25, he got the exact same message.

I wasn't able to reproduce it on Debian Jessie. There, glxinfo could query the
GLX version information correctly and also reported working direct rendering via
SGI 1.2/MESA 1.4 Gallium software renderer (or the like, I don't remember the
specifics, but certainly not an error.)

Initially I thought this might be a problem with nx-libs. If it's really a bug
in MESA, that would be good, because is a chance this problem can be fixed by
fixing up MESA itself.



Mihai




signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
http://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] X2Go crash from Mac/MATE to Fedora 25 w NIS user getting x2gostartagent: blocking creation of agent's keyboard file

[Mihai Moldovan]

On 28.02.2017 05:31 PM, Robert Kudyba wrote:
> My colleague is giving up on MATE. And XFCE has been having intermittent 
> issues and here are some errors/logs. Anything stick out?

Difficult to say without knowing what to look for?

I've seen kgpg crashing in that log, but that may or may not be a problem.

The missing Composite and Fixes extensions are normal - you won't get any
compositing effects, but that's okay.

Other than that, there's no major problem recorded in there.


This said, I've had a user on FC25 yesterday on IRC and he has reported problems
with Emacs - which was built with GTK3 support. After he rebuilt it with GTK2,
it started to work.

I also (ab)used him to test MATE and found out that mate-session is crashing
upon start. Any GTK3 application crashes, basically, because of a bug in al
ibrary used by GTK3 (libepoxy), that has been filed in Red Hats bugtracker for
Fedora 24 already and fixed upstream for a while.

The root cause of that is that for some reason the GLX version is not reported
correctly - instead a NULL pointer is thrown out. I don't see this behavior on
Debian Jessie, which hints at a deeper problem with our nx-libs builds on Fedora
25 (and maybe even 24?)

I haven't yet been able to figure out why nxagent isn't doing what it should be
doing, though.



Mihai



signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
http://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] X2Go crash from Mac/MATE to Fedora 25 w NIS user getting x2gostartagent: blocking creation of agent's keyboard file

[Mihai Moldovan]

On 26.02.2017 10:25 AM, Robert Dinse wrote:
>   In my case it is the x2goagent on the server.  I can not find a core
> however.

Do you have the same symptom? Is MATE not starting up at all?
Or is it crashing after the session has been running for some time already?

Normally, core files tend to sit in the user's home dir - but that depends
upon some circumstances (like whether creating core dumps at all is
allowed or not - with different systems utilizing different methods of
getting this to work.)

Fedora and RHEL-based distros use ABRT (Automatic Bug Reporting Tool),
which stashes the core dumps and can easily send them to Red Hat's Bugzilla
instance.

The general place to look at is probably /etc/security/limits.conf for
core dumping permissions and then figure out what ABRT exactly does.

If you want to have ABRT out of the way,
echo "core" > /proc/sys/kernel/core_pattern
will take care of that.



Mihai



signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
http://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] X2Go crash from Mac/MATE to Fedora 25 w NIS user getting x2gostartagent: blocking creation of agent's keyboard file

[Mihai Moldovan]

On 26.02.2017 06:29 AM, Robert Kudyba wrote:
> Well kind of had to build in the XFCE work around mentioned in this bug
> .
> 
> Here's what in the log with XFCE:

The non-working MATE log would be more interesting, given that XFCE actually
works in your setup. :)



Mihai




signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
http://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] X2Go Client: Kex error : no match for method server host key alog: server [ssh-rsa], client [ssh-ed25519]

[Mihai Moldovan]

On 24.02.2017 01:14 AM, jmmec2...@yahoo.com wrote:
> I don't know why Windows 8.1 was suddenly only supporting ssh-ed25519 and
> failing to connect to my Linux Mint session with that "kex error".  What is 
> even
> stranger:  the problem suddenly went away and I could once again use the x2go
> client to connect to that session (the same session that I've had running for
> more than a month - maybe two months by now).  At least for now the "kex 
> error"
> is gone with the X2GO client. 

That's weird... libssh shouldn't behaving differently from one invocation to the
other, really. Did you really change nothing server-side?



Mihai



signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
http://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] X2Go crash from Mac/MATE to Fedora 25 w NIS user getting x2gostartagent: blocking creation of agent's keyboard file

[Mihai Moldovan]

On 17.02.2017 07:41 PM, Robert Kudyba wrote:
> This only seems to be affecting one user. He has a NIS account and has tried 2
> NIS accounts to make sure. He's running a Mac with the latest X2Go (2.7.11)

You probably meant XQuartz here.


> connecting to a Fedora 25 server with NIS, choosing the MATE desktop and audio
> disabled. We made sure to check the security settings as per this older post
> screenshot
> 
>  and
> confirmed the .Xauthority permissions problem
>  does not
> exist. Here are some debug-enabled logs. 

What exactly does crash and when? The client? x2goagent on the server?



Mihai



signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
http://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] X2Go Client: Kex error : no match for method server host key alog: server [ssh-rsa], client [ssh-ed25519]

[Mihai Moldovan]

On 14.02.2017 07:30 PM, jmmec2...@yahoo.com wrote:
> Kex error : no match for method server host key alog: server [ssh-rsa], client
> [ssh-ed25519].

This is odd. Karl's suggestion won't help, as this is not related to kex 
algorithms.

Instead, your server provides an RSA host key, but the client (in this case
libssh for X2Go Client) seems to support ssh-ed25519 only.

Odd, because libssh certainly does support RSA keys. Did you generate the server
host keys yourself? Maybe it's too big?

libssh definitely supports RSA keys and it should report that its list as well.


---

You're not seeing this issue with PyHoca, because PyHoca uses Paramiko, an
implementation of SSH in python. The supported features differ based upon the
implementation, as you can see (libssh vs. Paramiko in this case.)



Mihai




signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
http://lists.x2go.org/listinfo/x2go-user