Re: [X2Go-Dev] repository: broken dependencies since today

[Mihai Moldovan]

* On 03/02/2018 05:48 PM, ITM Administrators wrote:
> since this is a packaging bug and not a bug in the code, I wasn't sure if a 
> bug
> report should be filled. Instead, I use this mailing list.
> 
> We are using
> 
> deb http://packages.x2go.org/debian stretch main
> 
> as source to get updates for x2go under Debian 9.0 "Stretch". Since today, the
> dependencies are not correct in this repository:
> 
> The package nxagent was updated today to version
> 2:3.5.99.14-0+git20180302.2954+9.main.1 but this is incompatible with the
> package x2goagent (as of version 2:3.5.0.33-0x2go1+git20180204.776+9.main.1):
> 
> The following packages have unmet dependencies:
>  x2goagent : Depends: nxagent (< 2:3.5.0.33-0x2go1+git20180204.776+9.main.1.1)
> E: Broken packages
> 
> In order to rule out a temporary dependency issue during upload of new 
> packages,
> we waited for 6 hours. The problem still persists.

You should have likely waited a bit longer.

If I remember correctly the new X2Go Server packages hit the repository a few
hours later.


You cannot reproduce that now, is that correct?



Mihai




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

[X2Go-Dev] Processed: Re: Can't connect after jessie update

[X2Go Bug Tracking System]

Processing control commands:

> reassign -1 packages.x2go.org
Bug #1267 [x2goserver] Can't connect after jessie update
Bug reassigned from package 'x2goserver' to 'packages.x2go.org'.
No longer marked as found in versions 4.0.1.22-0x2go1+git20180204.1197+8.main.1.
Ignoring request to alter fixed versions of bug #1267 to the same values 
previously set
> close -1
Bug #1267 [packages.x2go.org] Can't connect after jessie update
Marked Bug as done

-- 
1267: http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=1267
X2Go Bug Tracking System
Contact ow...@bugs.x2go.org with problems
___
x2go-dev mailing list
x2go-dev@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-dev

[X2Go-Dev] Bug#1267: Can't connect after jessie update

[Mihai Moldovan]

Control: reassign -1 packages.x2go.org
Control: close -1

* On 03/02/2018 10:13 PM, Christophe Massez wrote:
> Package: x2goserver
> Version: 4.0.1.22-0x2go1+git20180204.1197+8.main.1
> 
> Hi all,
> 
> After upgrade of debian jessie, I can't connect with x2go.

You have been trying to upgrade at a time when new X2Go Server packages were not
available yet or otherwise upgraded only partly.

Please run apt-get update; apt-get dist-upgrade.

Does the problem persist?


Closing, since this should not be an issue any longer. If it is, we can re-open
the report.



Mihau



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

[X2Go-Dev] repository: broken dependencies since today

[ITM Administrators]

Hello all,

since this is a packaging bug and not a bug in the code, I wasn't sure
if a bug report should be filled. Instead, I use this mailing list.

We are using

deb http://packages.x2go.org/debian stretch main

as source to get updates for x2go under Debian 9.0 "Stretch". Since
today, the dependencies are not correct in this repository:

The package nxagent was updated today to version
2:3.5.99.14-0+git20180302.2954+9.main.1 but this is incompatible with
the package x2goagent (as of version
2:3.5.0.33-0x2go1+git20180204.776+9.main.1):

The following packages have unmet dependencies:
 x2goagent : Depends: nxagent (<
2:3.5.0.33-0x2go1+git20180204.776+9.main.1.1)
E: Broken packages

In order to rule out a temporary dependency issue during upload of new
packages, we waited for 6 hours. The problem still persists.

Kind regards

Dennis Grunert

-- 
Dipl.-Math. Dennis Grunert (system administrator)
Institute of Engineering and Computational Mechanics
(name in German: Institut für Technische und Numerische Mechanik)
University of Stuttgart, Pfaffenwaldring 9, 70569 Stuttgart, Germany
itm...@itm.uni-stuttgart.de, tel +49 711-685-66581, fax -66400
http://www.itm.uni-stuttgart.de/staff/Grunert/
PGP: 0x38CD2BE8 / 6CBC C4EA 9674 266C E396  4C5E 3B4A FC58 38CD 2BE8

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

[X2Go-Dev] Bug#1269: X2go server crashes on Ubuntu 16.04

[Maciej Puzio]

Philip, thanks a lot for the links to the Arctica bugs. 
While my symptoms are somewhat different (the crash occurs "automatically", 
just after the login, no window movement is necessary), 
the underlying cause is probably the same. As the Arctica report suggests, the 
problem is in fact dependent on the dual-screen 
configuration on the client side, and is solved by the fixed packages in the 
nightly build.
___
x2go-dev mailing list
x2go-dev@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-dev

[X2Go-Dev] Bug#1272: nxagent crashes on Ubuntu 16.04, making x2go server unusable

[Maciej Puzio]

Good news! We have an upstream bug:
https://github.com/ArcticaProject/nx-libs/issues/677

It appears that Arctica issue is exactly what I have been experiencing.

I use KDE on two screens with different resolutions (1920x1200 and 1600x1200). 
X2goclient session uses only one of these displays, but the mere presence of 
two monitors on the client causes nxagent to crash on the server. I tested 
another client machine with one screen, and everything worked fine (i.e. I was 
able to open the session, and nxagent did not segfault). It does not matter 
whether I move the x2go session window, maximize it, and so on. All that 
matters is number of displays on the client and their relative size. (I did not 
test with two screens of equal size.)

As the upstream bug suggested, I installed the x2go nightly packages, as 
explained here:
https://wiki.x2go.org/doku.php/wiki:development:nightly-builds
After that, the problem went away and dual-screen setup worked fine. So I guess 
the bug is fixed in nightly builds.

As a side note, the number of bugs that show up in various Linux packages when 
using dual monitors has recently been so astounding that I am ready to give up 
and replace my setup with a larger single screen. Still, I can't force all my 
users to do so.
___
x2go-dev mailing list
x2go-dev@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-dev

[X2Go-Dev] Bug#1269: X2goserver crashes on Ubuntu 16.04

[Philip Kollmannsberger]

This bug might be related to these issues on the Arctica nx-libs repo on
github:

https://github.com/ArcticaProject/nx-libs/issues/679
https://github.com/ArcticaProject/nx-libs/issues/677

With the most recent nightly build, moving and rezising between displays
in windowed mode works fine again.
___
x2go-dev mailing list
x2go-dev@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-dev

[X2Go-Dev] Bug#1269: X2go server crashes on Ubuntu 16.04

[Maciej Puzio]

Seeing that my issue is indeed different from both other submitters, I decided 
to go ahead and post a separate report (bug 1272).
https://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=1272
The underlying cause may be turn out to be the same, so my new bug report may 
end up being a duplicate, or maybe not; difficult to say at this point.
Please everyone who suffers from a segfaulty nxagent after a recent update to 
post to one of these bug reports. We need to attract developers' attention.
___
x2go-dev mailing list
x2go-dev@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-dev

[X2Go-Dev] Bug#1272: nxagent crashes on Ubuntu 16.04, making x2go server unusable

[Maciej Puzio]

Package: nxagent
Version: 3.5.99.15-0~201803072246~ubuntu16.04.1
Severity: grave

I originally submitted this post for bug 1269, but as this is a somewhat 
different issue of greater severity, I am creating a separate bug.
Reason for grave severity: bug makes the package in question unusable, as it 
does the whole x2go server.

Short description:
Attempt of starting an x2go session causes the session window to briefly appear 
and then disappear. Server syslog shows a segfault:
kernel: [ 3899.187248] nxagent[7306]: segfault at 0 ip 558c9d0045fb sp 
7ffdad91c1f0 error 4 in nxagent[558c9cf39000+432000]

In my case, a routine system update (apt-get update && apt-get dist-upgrade) 
rendered a production server unusable, with no easy way to rollback the botched 
x2go update.
The issue did not appear before the update. I recreated the issue on clean 
install of a vanilla Ubuntu 16.04 server running in a VM. I use this install as 
a basis for the description below.

Versions - server:
x2goserver: 4.1.0.0-0~1517~ubuntu16.04.1 (this is the newest server from x2go 
stable PPA for Ubuntu 16.04)
nxagent:3.5.99.15-0~201803072246~ubuntu16.04.1
uname -r:   4.4.0-116-generic
lsb_release -d: Ubuntu 16.04.4 LTS

Versions - client:
x2goclient: 4.0.5.1-1 (this is the newest client from Ubuntu 16.04 repo)
uname -r:   4.13.0-32-generic
lsb_release -d: Ubuntu 16.04.3 LTS


Steps to reproduce:

1. Install Ubuntu 16.04 server in a VM (from ubuntu-16.04.3-server-amd64.iso 
downloaded from ubuntu.com).

2. Update the system (apt-get update && apt-get dist-upgrade) and reboot.

3. Install x2go as described on 
https://wiki.x2go.org/doku.php/wiki:repositories:ubuntu
   All commands run as root (sudo su -)
   apt-add-repository ppa:x2go/stable
   apt-get update
   apt-get install x2goserver x2goserver-xsession --no-install-recommends

4. Install minimal XFCE desktop:
   apt-get install xfwm4 xfce4-panel xfce4-settings xfce4-session 
xfce4-terminal xfdesktop4 xfce4-taskmanager xfce4-appfinder xfce4-artwork 
--no-install-recommends

5. Attempt to connect with a x2go client from another machine:
   My x2goclient version: 4.0.5.1-1

Results:

Messages on client side


NXPROXY - Version 3.5.0

Copyright (C) 2001, 2011 NoMachine.
See http://www.nomachine.com/ for more information.

Info: Proxy running in client mode with pid '16432'.
Session: Starting session at 'Tue Mar 13 16:10:36 2018'.
Info: Connecting to remote host 'localhost:37853'.
Info: Connection to remote proxy 'localhost:37853' established.
Info: Connection with remote proxy completed.
Warning: Unrecognized session type 'unix-kde-depth_24'. Assuming agent session.
Info: Using LAN link parameters 1536/24/1/0.
Info: Using pack method '16m-jpeg-9' with session 'unix-kde-depth_24'.
Info: Not using NX delta compression.
Info: Not using ZLIB data compression.
Info: Not using ZLIB stream compression.
Info: Not using a persistent cache.
Info: Forwarding X11 connections to display ':0'.
Session: Session started at 'Tue Mar 13 16:10:36 2018'.
Info: Established X server connection.
Info: Using shared memory parameters 0/0K.
Error: Failure reading from the peer proxy.
Error: Connection with remote peer broken.
Error: Please check the state of your network and retry.
Session: Terminating session at 'Tue Mar 13 16:10:37 2018'.
Session: Session terminated at 'Tue Mar 13 16:10:37 2018'.
Info: Established X server connection.
Info: Using shared memory parameters 0/0K.


Server syslog messages (with log level: debug)


Mar 13 16:03:59 nano systemd[1]: Started Session 5 of user testuser.
Mar 13 16:03:59 nano x2golistsessions: executing external command ,,x2gopath'' 
with args: libexec
Mar 13 16:03:59 nano x2golistsessions: executing external command ,,x2gopath'' 
with args: libexec
Mar 13 16:03:59 nano x2golistsessions: x2golistsessions has been called with no 
option
Mar 13 16:03:59 nano x2golistsessions: executing external command 
,,/usr/lib/x2go/libx2go-server-db-sqlite3-wrapper'' with args: listsessions,nano
Mar 13 16:03:59 nano /usr/bin/x2gostartagent: x2gostartagent called with 
options: 1920x1150 lan 16m-jpeg-9 unix-kde-depth_24 us auto 1 D XFCE both
Mar 13 16:03:59 nano /usr/lib/x2go/x2gogetrandomport: x2gogetrandomport called 
with options:
Mar 13 16:03:59 nano /usr/lib/x2go/x2gogetrandomport: Full SSH port 
randomization requested.
Mar 13 16:03:59 nano /usr/bin/x2gostartagent: client announced itself as 
"192.168.1.100"
Mar 13 16:03:59 nano /usr/bin/x2gosessionlimit[7186]: x2gosessionlimit has been 
called
Mar 13 16:03:59 nano /usr/bin/x2gosessionlimit[7186]: executing external 
command ,,x2golistsessions'' with args: --all-servers
Mar 13 16:03:59 nano x2golistsessions: executing external command ,,x2gopath'' 
with args: libexec
Mar 13 16:03:59 nano x2golistsessions: executing external command ,,x2gopath'' 
with args: libexec
Mar 13 16:03:59 nano x2golistsessions: x2golistsessions has been 

[X2Go-Dev] Bug#1269: X2go server crashes on Ubuntu 16.04

[Maciej Puzio]

Philip, thank you for your report, but I think you are experiencing a different 
issue, though perhaps related.
In my case, every attempt to open an x2go session fails (and I have Xinerama 
disabled).
I have reverted to the state before the update (with x2goserver 
4.0.1.22-0~1197~ubuntu16.04.1 and nxagent 3.5.0.33-0~710~ubuntu16.04.1), which 
works fine.

May I again ask the admin of x2go bug database to change the severity of this 
bug to grave, or I will file a duplicate bug report. Thank you very much.
___
x2go-dev mailing list
x2go-dev@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-dev

[X2Go-Dev] Bug#1269: X2go server crashes on Ubuntu 16.04

[Maciej Puzio]

Package: nxagent
Version: 3.5.99.15-0~201803072246~ubuntu16.04.1
Severity: grave

I can confirm this bug and would like to ask that its severity is changed to 
GRAVE, as it makes x2go server unusable.

In a nutshell: attempt of starting a session on a client causes a window to 
briefly appear and then disappear. Server syslog shows a segfault:
kernel: [ 3899.187248] nxagent[7306]: segfault at 0 ip 558c9d0045fb sp 
7ffdad91c1f0 error 4 in nxagent[558c9cf39000+432000]

In my case, a routine system update (apt-get update && apt-get dist-upgrade) 
rendered a production server unusable, with no way to rollback the botched x2go 
update.
The issue did not appear before the update. I also recreated the issue on a 
vanilla Ubuntu 16.04 server running in a VM. I use this install as a basis for 
the description below.

Versions - server:
x2goserver: 4.1.0.0-0~1517~ubuntu16.04.1
nxagent:3.5.99.15-0~201803072246~ubuntu16.04.1
uname -a:   4.4.0-116-generic
lsb_release -d: Ubuntu 16.04.4 LTS

Versions - client:
x2goclient: 4.0.5.1-1
uname -a:   4.13.0-32-generic
lsb_release -d: Ubuntu 16.04.3 LTS


Steps to reproduce:

1. Install Ubuntu 16.04 server in a VM (from ubuntu-16.04.3-server-amd64.iso 
downloaded from ubuntu.com).

2. Update the system (apt-get update && apt-get dist-upgrade) and reboot.

3. Install x2go as described on 
https://wiki.x2go.org/doku.php/wiki:repositories:ubuntu
   All commands run as root (sudo su -)
   apt-add-repository ppa:x2go/stable
   apt-get update
   apt-get install x2goserver x2goserver-xsession --no-install-recommends

4. Install minimal XFCE desktop:
   apt-get install xfwm4 xfce4-panel xfce4-settings xfce4-session 
xfce4-terminal xfdesktop4 xfce4-taskmanager xfce4-appfinder xfce4-artwork 
--no-install-recommends

5. Attempt to connect with a x2go client from another machine:
   x2goclient version: 4.0.5.1-1



Messages on client side

NXPROXY - Version 3.5.0

Copyright (C) 2001, 2011 NoMachine.
See http://www.nomachine.com/ for more information.

Info: Proxy running in client mode with pid '16432'.
Session: Starting session at 'Tue Mar 13 16:10:36 2018'.
Info: Connecting to remote host 'localhost:37853'.
Info: Connection to remote proxy 'localhost:37853' established.
Info: Connection with remote proxy completed.
Warning: Unrecognized session type 'unix-kde-depth_24'. Assuming agent session.
Info: Using LAN link parameters 1536/24/1/0.
Info: Using pack method '16m-jpeg-9' with session 'unix-kde-depth_24'.
Info: Not using NX delta compression.
Info: Not using ZLIB data compression.
Info: Not using ZLIB stream compression.
Info: Not using a persistent caError: Failure reading from the peer proxy.
Error: Connection with remote peer broken.
Error: Please check the state of your network and retry.
Session: Terminating session at 'Tue Mar 13 16:10:37 2018'.
Session: Session terminated at 'Tue Mar 13 16:10:37 2018'.
che.
Info: Forwarding X11 connections to display ':0'.
Session: Session started at 'Tue Mar 13 16:10:36 2018'.
Info: Established X server connection.
Info: Using shared memory parameters 0/0K.



Server syslog messages (with log level: debug)

Mar 13 16:03:59 nano systemd[1]: Started Session 5 of user testuser.
Mar 13 16:03:59 nano x2golistsessions: executing external command ,,x2gopath'' 
with args: libexec
Mar 13 16:03:59 nano x2golistsessions: executing external command ,,x2gopath'' 
with args: libexec
Mar 13 16:03:59 nano x2golistsessions: x2golistsessions has been called with no 
option
Mar 13 16:03:59 nano x2golistsessions: executing external command 
,,/usr/lib/x2go/libx2go-server-db-sqlite3-wrapper'' with args: listsessions,nano
Mar 13 16:03:59 nano /usr/bin/x2gostartagent: x2gostartagent called with 
options: 1920x1150 lan 16m-jpeg-9 unix-kde-depth_24 us auto 1 D XFCE both
Mar 13 16:03:59 nano /usr/lib/x2go/x2gogetrandomport: x2gogetrandomport called 
with options:
Mar 13 16:03:59 nano /usr/lib/x2go/x2gogetrandomport: Full SSH port 
randomization requested.
Mar 13 16:03:59 nano /usr/bin/x2gostartagent: client announced itself as 
"129.112.10.165"
Mar 13 16:03:59 nano /usr/bin/x2gosessionlimit[7186]: x2gosessionlimit has been 
called
Mar 13 16:03:59 nano /usr/bin/x2gosessionlimit[7186]: executing external 
command ,,x2golistsessions'' with args: --all-servers
Mar 13 16:03:59 nano x2golistsessions: executing external command ,,x2gopath'' 
with args: libexec
Mar 13 16:03:59 nano x2golistsessions: executing external command ,,x2gopath'' 
with args: libexec
Mar 13 16:03:59 nano x2golistsessions: x2golistsessions has been called with 
options: --all-servers
Mar 13 16:03:59 nano x2golistsessions: executing external command 
,,/usr/lib/x2go/libx2go-server-db-sqlite3-wrapper'' with args: listsessions_all
Mar 13 16:03:59 nano x2gogetdisplays: executing external command ,,x2gopath'' 
with args: libexec
Mar 13 16:03:59 nano x2gogetdisplays: executing external command 

[X2Go-Dev] Bug#1271: Composite XServer extension support

[Ildar Mulyukov]

Package: x2goserver
Version: 4.0.1.20

the Composite XServer extension is currently unsupported. Please fix.
> Some info here: 
> https://wiki.x2go.org/doku.php/wiki:development:roadmap?s[]=composite#first_attempt_at_documenting_missing_nx-libs_features_for_certain_applications_and_desktop_environments

P.S. Might be good to make a metabug for all unsupported XServer extensions
___
x2go-dev mailing list
x2go-dev@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-dev

[X2Go-Dev] Bug#1267: X2go Bug - solved

[Thomas Deuter]

On ubuntu 16.04 this helped:

sudo apt install --reinstall nxagent
___
x2go-dev mailing list
x2go-dev@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-dev

[X2Go-Dev] Bug#1269: X2go server crashes on Ubuntu 16.04 starting at 2018-03-08

[krehberg]

Package: nxagent
Version: 3.5.99.15 (From the Official Ubuntu PPA)

Hello,

X2go server crashes on Ubuntu 16.04 starting at 2018-03-08.  I am using Windows 
10 as the client.  It happens most often when moving the window from one 
display screen to a second one.  It also happens after a short time online, 
usually fewer than 5 minutes.  Perhaps a recent Windows 10 update may have 
caused this since that's the only thing I have changed on these systems.  I am 
also mounting my Windows 10 drive through the X2go client.  Sound is disabled.

I'm pretty sure nxagent was updated on March 8 to this version:
NXAGENT - Version 3.5.99.15

Here is what I see in the kernel log (dmesg):

[  194.802419] nxagent[3035]: segfault at 0 ip 559edeb9c5fb sp 
7ffcbebf71c0 error 4 in nxagent[559edead1000+432000]
[ 9277.059883] nxagent[23367]: segfault at 0 ip 562497ecb5fb sp 
7ffcd24230b0 error 4 in nxagent[562497e0+432000]
[ 9319.625785] nxagent[24275]: segfault at 0 ip 557f7e17f5fb sp 
7ffd7cbda740 error 4 in nxagent[557f7e0b4000+432000]
[ 9696.220810] nxagent[25857]: segfault at 0 ip 5607d52375fb sp 
7ffc87afbb40 error 4 in nxagent[5607d516c000+432000]
[ 9750.298187] nxagent[26894]: segfault at 0 ip 55c8f5dbd5fb sp 
7ffef53ee0e0 error 4 in nxagent[55c8f5cf2000+432000]

I don't see anything remarkable on the Windows 10 side.

Thank you for your efforts.

Kris Rehberg

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

[X2Go-Dev] Bug#1272: Triggered by client window maximisation

[Carsten Lechte]

This perfectly describes the problem I had with the ppa:x2go/stable version, 
both client and server on ubuntu 1604.


The crash of nxagent seems to be triggered by maximisation of the client 
window, e.g. when it is configured to use a whole display. If a static window 
size is configured, the crash happens when I move the client window. Maybe the 
unity window manager is sending some windowing events?


My workaround was to install from the ppa:x2go/saimaa repository.
___
x2go-dev mailing list
x2go-dev@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-dev

[X2Go-Dev] Bug#1269: X2go server crashes on Ubuntu 16.04

[Philip Kollmannsberger]

package: nxagent
Version: 3.5.99.15-0~201803072246~ubuntu16.04.1
Severity: grave

We have the same problem here after upgrading x2go from 4.0.1.22 to 4.1.0.0.

It is independent of client version and OS (both Linux and Windows), and
seems to be related to Xinerama:

- when enabling Xinerama support in the client, x2go works in
fullscreen, but leads to a crash in windowed mode as soon as the window
is resized or moved to a different display.

- when disabling Xinerama support, everything seems ok

The log shows a segfault of nxagent, exactly as described above.
___
x2go-dev mailing list
x2go-dev@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-dev

[X2Go-Dev] Bug#1268: enhancement: add terminate/suspend diaolog when closing session window

[David Clay]

Package: x2g0client
Version: 4.1.1

This was a feature of NX that I liked.  You would not have to bring of the
x20client wimdow to suspend/terminate session.

This could be controlled by an option so existing users could get the
current behavior.
___
x2go-dev mailing list
x2go-dev@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-dev

[X2Go-Dev] Processed: Re: high CPU usage with Fedora 27 and users that disconnect, Caja and Mate crash/coredump

[X2Go Bug Tracking System]

Processing control commands:

> forwarded -1 https://github.com/ArcticaProject/nx-libs/issues/671
Bug #1260 [x2goserver-4.1.0.1-0.0x2go1.0.git20180218.1532.heuler.fc27.x86_64] 
high CPU usage with Fedora 27 and users that disconnect, Caja and Mate 
crash/coredump
Warning: Unknown package 
'x2goserver-4.1.0.1-0.0x2go1.0.git20180218.1532.heuler.fc27.x86_64'
Set Bug forwarded-to-address to 
'https://github.com/ArcticaProject/nx-libs/issues/671'.
Warning: Unknown package 
'x2goserver-4.1.0.1-0.0x2go1.0.git20180218.1532.heuler.fc27.x86_64'
> severity -1 grave
Bug #1260 [x2goserver-4.1.0.1-0.0x2go1.0.git20180218.1532.heuler.fc27.x86_64] 
high CPU usage with Fedora 27 and users that disconnect, Caja and Mate 
crash/coredump
Warning: Unknown package 
'x2goserver-4.1.0.1-0.0x2go1.0.git20180218.1532.heuler.fc27.x86_64'
Severity set to 'grave' from 'normal'
Warning: Unknown package 
'x2goserver-4.1.0.1-0.0x2go1.0.git20180218.1532.heuler.fc27.x86_64'

-- 
1260: http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=1260
X2Go Bug Tracking System
Contact ow...@bugs.x2go.org with problems
___
x2go-dev mailing list
x2go-dev@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-dev

[X2Go-Dev] Bug#1267: Same situation at my system

[M. Tschierschke]

Using Ubuntu 17.10 64 bit.
___
x2go-dev mailing list
x2go-dev@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-dev

[X2Go-Dev] Bug#1267: Can't connect after jessie update

[Christophe Massez]

Package: x2goserver
Version: 4.0.1.22-0x2go1+git20180204.1197+8.main.1

Hi all,

After upgrade of debian jessie, I can't connect with x2go.

On client side, error in log is :
*Error: failure of negotiating the session in stage '7'*
*Loop: PANIC! Wrong version or invalid session authentication cookie*

Error messagebox say :
*The remote proxy closed the connection while negociating the session. This
may be due to the wrong authentication credential passed to the server.*

On server side, in ~/.x2go :
*/usr/lib/nx/../x2go/bin/x2goagent: symbol lookup error:
/usr/lib/x86_64-linux-gnu/libXcomp.so.3: undefined symbol:
pthread_key_create*


I suspect a package problem, so I install a *fresh* jessie, then following
this installation procedure :
https://wiki.x2go.org/doku.php/wiki:repositories:debian
-> replacing (or not) stretch by jessie, when I install x2goserver :

root@x2go:~# apt-get install x2goserver
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances
Lecture des informations d'état... Fait
Certains paquets ne peuvent être installés. Ceci peut signifier
que vous avez demandé l'impossible, ou bien, si vous utilisez
la distribution unstable, que certains paquets n'ont pas encore
été créés ou ne sont pas sortis d'Incoming.
L'information suivante devrait vous aider à résoudre la situation :

Les paquets suivants contiennent des dépendances non satisfaites :
 x2goserver : Dépend: x2goagent (>= 2:3.5.0.33-0~) mais ne sera pas installé
E: Impossible de corriger les problèmes, des paquets défectueux sont en
mode « garder en l'état ».

With x2goagent :

root@x2go:~# apt-get install x2goagent
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances
Lecture des informations d'état... Fait
Certains paquets ne peuvent être installés. Ceci peut signifier
que vous avez demandé l'impossible, ou bien, si vous utilisez
la distribution unstable, que certains paquets n'ont pas encore
été créés ou ne sont pas sortis d'Incoming.
L'information suivante devrait vous aider à résoudre la situation :

Les paquets suivants contiennent des dépendances non satisfaites :
 x2goagent : Dépend: nxagent (<
2:3.5.0.33-0x2go1+git20180204.776+8.main.1.1) mais
2:3.5.99.14-0+git20180302.2954+8.main.1 devra être installé
E: Impossible de corriger les problèmes, des paquets défectueux sont en
mode « garder en l'état ».

-> I can't install x2go server in jessie anymore, I can't upgrade jessie
without compromise x2go access.  Hope I'm not the only one to expect this
issue... I Stay available to do more tests, any help will be welcome.
Christophe
___
x2go-dev mailing list
x2go-dev@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-dev

[X2Go-Dev] Processed: your mail

[X2Go Bug Tracking System]

Processing commands for cont...@bugs.x2go.org:

> severity 1269 grave
Bug #1269 [nxagent] X2go server crashes on Ubuntu 16.04 starting at 2018-03-08
Severity set to 'grave' from 'normal'
> merge 1272 1269
Bug #1272 [nxagent] nxagent crashes on Ubuntu 16.04, making x2go server unusable
Bug #1269 [nxagent] X2go server crashes on Ubuntu 16.04 starting at 2018-03-08
Merged 1269 1272
> forwarded 1272 https://github.com/ArcticaProject/nx-libs/issues/677
Bug #1272 [nxagent] nxagent crashes on Ubuntu 16.04, making x2go server unusable
Bug #1269 [nxagent] X2go server crashes on Ubuntu 16.04 starting at 2018-03-08
Set Bug forwarded-to-address to 
'https://github.com/ArcticaProject/nx-libs/issues/677'.
Set Bug forwarded-to-address to 
'https://github.com/ArcticaProject/nx-libs/issues/677'.
> fixed 1272 3.5.99.16
Bug #1272 [nxagent] nxagent crashes on Ubuntu 16.04, making x2go server unusable
Bug #1269 [nxagent] X2go server crashes on Ubuntu 16.04 starting at 2018-03-08
There is no source info for the package 'nxagent' at version '3.5.99.16' with 
architecture ''
Unable to make a source version for version '3.5.99.16'
Marked as fixed in versions 3.5.99.16.
Marked as fixed in versions 3.5.99.16.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1269: http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=1269
1272: http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=1272
X2Go Bug Tracking System
Contact ow...@bugs.x2go.org with problems
___
x2go-dev mailing list
x2go-dev@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-dev

[X2Go-Dev] Processed (with 3 errors): your mail

[X2Go Bug Tracking System]

Processing commands for cont...@bugs.x2go.org:

> reassign 1272 nxagent 3.5.99.15
Bug #1272 [nxagent] nxagent crashes on Ubuntu 16.04, making x2go server unusable
Ignoring request to reassign bug #1272 to the same package
Bug #1272 [nxagent] nxagent crashes on Ubuntu 16.04, making x2go server unusable
There is no source info for the package 'nxagent' at version '3.5.99.15' with 
architecture ''
Unable to make a source version for version '3.5.99.15'
Marked as found in versions 3.5.99.15; no longer marked as found in versions 
3.5.99.15-0~201803072246~ubuntu16.04.1.
> reassign 1269 nxagent 3.5.99.15
Bug #1269 [nxagent] X2go server crashes on Ubuntu 16.04 starting at 2018-03-08
Ignoring request to reassign bug #1269 to the same package
Bug #1269 [nxagent] X2go server crashes on Ubuntu 16.04 starting at 2018-03-08
There is no source info for the package 'nxagent' at version '3.5.99.15' with 
architecture ''
Unable to make a source version for version '3.5.99.15'
Marked as found in versions 3.5.99.15; no longer marked as found in versions 
3.5.99.15-0~201803072246~ubuntu16.04.1.
> merge 1272 1269
Bug #1272 [nxagent] nxagent crashes on Ubuntu 16.04, making x2go server unusable
Unable to merge bugs because:
severity of #1269 is 'normal' not 'grave'
Failed to merge 1272: Did not alter merged bugs.
Debbugs::Control::set_merged("transcript", GLOB(0x26029c0), 
"requester", "Mihai Moldovan ", "request_addr", 
"control\@bugs.x2go.org", "request_msgid", 
"<9c1f7dc8-920e-5793-f225-1de5a05462a4\@ionic.de>", "request_subject", ...) 
called at /usr/share/perl5/Debbugs/Control/Service.pm line 538
eval {...} called at /usr/share/perl5/Debbugs/Control/Service.pm line 
537
Debbugs::Control::Service::control_line("line", "merge 1272 1269", 
"clonebugs", HASH(0x2566f70), "limit", HASH(0x2555a10), 
"common_control_options", ARRAY(0x25559b0), "errors", ...) called at 
/usr/lib/debbugs/service line 470

> forwarded 1272 https://github.com/ArcticaProject/nx-libs/issues/677
Failed to set the forwarded-to-address of 1272: failed to get lock on 
/var/lib/debbugs/spool/lock/1272 -- Unable to lock 
/var/lib/debbugs/spool/lock/1272 Resource temporarily unavailable.
Unable to lock /var/lib/debbugs/spool/lock/1272 Resource temporarily 
unavailable at /usr/share/perl5/Debbugs/Common.pm line 582.
Unable to lock /var/lib/debbugs/spool/lock/1272 Resource temporarily 
unavailable at /usr/share/perl5/Debbugs/Common.pm line 582.
Unable to lock /var/lib/debbugs/spool/lock/1272 Resource temporarily 
unavailable at /usr/share/perl5/Debbugs/Common.pm line 582.
Unable to lock /var/lib/debbugs/spool/lock/1272 Resource temporarily 
unavailable at /usr/share/perl5/Debbugs/Common.pm line 582.
Unable to lock /var/lib/debbugs/spool/lock/1272 Resource temporarily 
unavailable at /usr/share/perl5/Debbugs/Common.pm line 582.
Unable to lock /var/lib/debbugs/spool/lock/1272 Resource temporarily 
unavailable at /usr/share/perl5/Debbugs/Common.pm line 582.
Unable to lock /var/lib/debbugs/spool/lock/1272 Resource temporarily 
unavailable at /usr/share/perl5/Debbugs/Common.pm line 582.
Unable to lock /var/lib/debbugs/spool/lock/1272 Resource temporarily 
unavailable at /usr/share/perl5/Debbugs/Common.pm line 582.
Unable to lock /var/lib/debbugs/spool/lock/1272 Resource temporarily 
unavailable at /usr/share/perl5/Debbugs/Common.pm line 582. at 
/usr/share/perl5/Debbugs/Common.pm line 600.
Debbugs::Common::filelock("/var/lib/debbugs/spool/lock/1272") called at 
/usr/share/perl5/Debbugs/Status.pm line 213
Debbugs::Status::read_bug("bug", 1272, "lock", 1) called at 
/usr/share/perl5/Debbugs/Status.pm line 468
Debbugs::Status::lock_read_all_merged_bugs("bug", 1272) called at 
/usr/share/perl5/Debbugs/Control.pm line 3674
Debbugs::Control::__begin_control("transcript", GLOB(0x26029c0), 
"request_subject", "", "bug", 1272, "affected_bugs", HASH(0x2456d78), 
"requester", ...) called at /usr/share/perl5/Debbugs/Control.pm line 1211
Debbugs::Control::set_forwarded("transcript", GLOB(0x26029c0), 
"requester", "Mihai Moldovan ", "request_addr", 
"control\@bugs.x2go.org", "request_msgid", 
"<9c1f7dc8-920e-5793-f225-1de5a05462a4\@ionic.de>", "request_subject", ...) 
called at /usr/share/perl5/Debbugs/Control/Service.pm line 389
eval {...} called at /usr/share/perl5/Debbugs/Control/Service.pm line 
388
Debbugs::Control::Service::control_line("line", "forwarded 1272 
https://github.com/ArcticaProject/nx-libs/issu;..., "clonebugs", 
HASH(0x2566f70), "limit", HASH(0x2555a10), "common_control_options", 
ARRAY(0x25559b0), "errors", ...) called at /usr/lib/debbugs/service line 470

> fixed 1272 3.5.99.16
Failed to add fixed on 1272: failed to get lock on 
/var/lib/debbugs/spool/lock/1272 -- Unable to lock 
/var/lib/debbugs/spool/lock/1272 Resource temporarily unavailable.
Unable to lock /var/lib/debbugs/spool/lock/1272 Resource temporarily 
unavailable at 

Re: [X2Go-Dev] x2go wiki : self-debugging instructions ? -> SOLVED

[Manfred Amoureux]

So I first tried reinstalling x2goclient and it did not work, even
with an *apt-get
purge* , deleting the *session* file in ~/.x2goclient/ and rebooting the
server.

Then I finally noticed something :

   - the connection did not work from my Laptop (which is of course, the
   one from which I need it to work) : Linux Mint 18 with x2go client 4.0.5
   - the connection worked from an old Windows 7 with x2go client 4.1.1
   - it also worked from a Debian 9 with x2go client 4.1.1

The version of x2go installed on the server is 4.1.0.

So it made sense to try installing the latest stable x2go client version.
After checking, I ahd indeed not added the ppa to the software sources and
was using the version from the Linux Mint repositories.

So I did that and now it works.

Shall I ask something to the wiki ?

Manfred A.


2018-03-15 15:54 GMT+01:00 Manfred Amoureux :

> Ok.
>
> Now that you have attracted my attention this git request ( *nxagent
> crashes when moving the session window into another screen* ), it
> actually looked more like a client-side issue,
> so I tested again from another computer (with Windows 7 and a single
> screen) and while at the first attempt the connection failed with a message
> that let me think it was because there was an open connection on the server
> with this user, after a reboot from the server machine, the connection now
> works from this computer.
>
> So I guess it really is a client problem now.
> I am first going to to try uninstalling and reinstalling x2go client from
> my computer.
>
>
> Manfred Amoureux
> Tel: (+33)6.800.343.16
>
> 2018-03-15 15:16 GMT+01:00 Mihai Moldovan :
>
>> * On 03/15/2018 03:07 PM, Manfred Amoureux wrote:
>> > I recorded a screen capture while trying to start a connection from
>> another
>> > computer. See the link below.
>> > As you can see, it seems the connection gets opened but the window
>> crashes
>> > immediately. I have tried from several computers (including one with
>> Windows) so
>> > I don't think it's a problem on the client side.
>>
>> Classic pattern of https://github.com/ArcticaProject/nx-libs/issues/677
>>
>> Will be fixed with the next nx-libs release, but I cannot tell when that
>> will
>> be. Ideally I'd like to see more xinerama changes/fixes to make it
>> worthwhile.
>>
>>
>> > I have attached an extract of the /var/log/syslog file these last
>> minutes. I see
>> > nothing that looks like an error to me. Obviously, you should be able to
>> > interpret it better than me.
>> > I have also restarted x2go (/sudo systemctl stop x2goserver.service/
>> and then
>> > /sudo systemctl start x2goserver.service/ ) after changing the
>> > /etc/x2go/x2goserver.conf file with logging to /debug/. That is the
>> second text
>> > file attached.
>> >
>> > In it, I can see :
>> > Mar 15 14:51:15 ServeurITeN /usr/bin/x2gostartagent: successfully
>> started X2Go
>> > Agent session with ID manfred-50-1521121872_stDXFCE_dp24
>> > Which means, I guess, the session was properly started.
>>
>> Well, that message is an euphemism. We launched the binary, but
>> everything that
>> happens after that is unknown since we immediately put the process into
>> background. But yeah, having it spawned nxagent is good.
>>
>>
>> > However, further on, I can also see :
>> > Mar 15 14:51:22 ServeurITeN x2gogetstatus: db_getstatus called, session
>> ID:
>> > manfred-50-1521121872_stDXFCE_dp24, return value:
>> > Mar 15 14:51:22 ServeurITeN x2gocleansessions:
>> > manfred-50-1521121872_stDXFCE_dp24: removed from database, not
>> updating status.
>> > Mar 15 14:51:22 ServeurITeN x2gocleansessions:
>> > manfred-50-1521121872_stDXFCE_dp24: in failed state, but agent is
>> gone, forgetting.
>> > Is that some kind of failure ?
>>
>> That indicates that x2goagent/nxagent died after starting up.
>>
>>
>> > It is also interesting to see that when I issue a /who/ command with
>> the Linux
>> > Terminal , there is one extra session under my login.
>>
>> Yup, X2Go uses SSH connections for everything.
>>
>>
>> > So I tried opening a x2go session with another login, which also failed
>> but with
>> > a different error message : "/Failed to start X2Go Agent session with ID
>> > formation-50-1521122343_stDXFCE_dp24. X2Go Agent terminated
>> unexpectedly.
>> > Aborting session startup./" I then restarted the x2goserver.service
>> again and
>> > tried again with the other user account and got the same error as for
>> the first
>> > user ("The connection with the remote server was shut down. Please
>> check the
>> > state of your network connection.").
>>
>> The first error message is weird, but explainable by the fact that the
>> proxy was
>> not quick enough to connect in the first place (or something like this).
>>
>> Right now, you have two options: wait for a new nx-libs release (as said,
>> unspecified time) or switch to the nightly/heuler repository that
>> contains a fix
>> for this issue... and switch back to the stable version once the 

Re: [X2Go-Dev] x2go wiki : self-debugging instructions ?

[Ulrich Sibiller]

You can  find the nxagent log in ~/.x2go/C-.../session.log. maybe that
contains some hints.

Uli

Mihai Moldovan  schrieb am Do., 15. März 2018, 15:18:

> * On 03/15/2018 03:07 PM, Manfred Amoureux wrote:
> > I recorded a screen capture while trying to start a connection from
> another
> > computer. See the link below.
> > As you can see, it seems the connection gets opened but the window
> crashes
> > immediately. I have tried from several computers (including one with
> Windows) so
> > I don't think it's a problem on the client side.
>
> Classic pattern of https://github.com/ArcticaProject/nx-libs/issues/677
>
> Will be fixed with the next nx-libs release, but I cannot tell when that
> will
> be. Ideally I'd like to see more xinerama changes/fixes to make it
> worthwhile.
>
>
> > I have attached an extract of the /var/log/syslog file these last
> minutes. I see
> > nothing that looks like an error to me. Obviously, you should be able to
> > interpret it better than me.
> > I have also restarted x2go (/sudo systemctl stop x2goserver.service/ and
> then
> > /sudo systemctl start x2goserver.service/ ) after changing the
> > /etc/x2go/x2goserver.conf file with logging to /debug/. That is the
> second text
> > file attached.
> >
> > In it, I can see :
> > Mar 15 14:51:15 ServeurITeN /usr/bin/x2gostartagent: successfully
> started X2Go
> > Agent session with ID manfred-50-1521121872_stDXFCE_dp24
> > Which means, I guess, the session was properly started.
>
> Well, that message is an euphemism. We launched the binary, but everything
> that
> happens after that is unknown since we immediately put the process into
> background. But yeah, having it spawned nxagent is good.
>
>
> > However, further on, I can also see :
> > Mar 15 14:51:22 ServeurITeN x2gogetstatus: db_getstatus called, session
> ID:
> > manfred-50-1521121872_stDXFCE_dp24, return value:
> > Mar 15 14:51:22 ServeurITeN x2gocleansessions:
> > manfred-50-1521121872_stDXFCE_dp24: removed from database, not updating
> status.
> > Mar 15 14:51:22 ServeurITeN x2gocleansessions:
> > manfred-50-1521121872_stDXFCE_dp24: in failed state, but agent is gone,
> forgetting.
> > Is that some kind of failure ?
>
> That indicates that x2goagent/nxagent died after starting up.
>
>
> > It is also interesting to see that when I issue a /who/ command with the
> Linux
> > Terminal , there is one extra session under my login.
>
> Yup, X2Go uses SSH connections for everything.
>
>
> > So I tried opening a x2go session with another login, which also failed
> but with
> > a different error message : "/Failed to start X2Go Agent session with ID
> > formation-50-1521122343_stDXFCE_dp24. X2Go Agent terminated unexpectedly.
> > Aborting session startup./" I then restarted the x2goserver.service
> again and
> > tried again with the other user account and got the same error as for
> the first
> > user ("The connection with the remote server was shut down. Please check
> the
> > state of your network connection.").
>
> The first error message is weird, but explainable by the fact that the
> proxy was
> not quick enough to connect in the first place (or something like this).
>
> Right now, you have two options: wait for a new nx-libs release (as said,
> unspecified time) or switch to the nightly/heuler repository that contains
> a fix
> for this issue... and switch back to the stable version once the new
> version has
> been properly released.
>
>
>
> Mihai
>
> ___
> x2go-dev mailing list
> x2go-dev@lists.x2go.org
> https://lists.x2go.org/listinfo/x2go-dev
___
x2go-dev mailing list
x2go-dev@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-dev

Re: [X2Go-Dev] x2go wiki : self-debugging instructions ?

[Manfred Amoureux]

Ok.

Now that you have attracted my attention this git request ( *nxagent
crashes when moving the session window into another screen* ), it actually
looked more like a client-side issue,
so I tested again from another computer (with Windows 7 and a single
screen) and while at the first attempt the connection failed with a message
that let me think it was because there was an open connection on the server
with this user, after a reboot from the server machine, the connection now
works from this computer.

So I guess it really is a client problem now.
I am first going to to try uninstalling and reinstalling x2go client from
my computer.


Manfred Amoureux
Tel: (+33)6.800.343.16

2018-03-15 15:16 GMT+01:00 Mihai Moldovan :

> * On 03/15/2018 03:07 PM, Manfred Amoureux wrote:
> > I recorded a screen capture while trying to start a connection from
> another
> > computer. See the link below.
> > As you can see, it seems the connection gets opened but the window
> crashes
> > immediately. I have tried from several computers (including one with
> Windows) so
> > I don't think it's a problem on the client side.
>
> Classic pattern of https://github.com/ArcticaProject/nx-libs/issues/677
>
> Will be fixed with the next nx-libs release, but I cannot tell when that
> will
> be. Ideally I'd like to see more xinerama changes/fixes to make it
> worthwhile.
>
>
> > I have attached an extract of the /var/log/syslog file these last
> minutes. I see
> > nothing that looks like an error to me. Obviously, you should be able to
> > interpret it better than me.
> > I have also restarted x2go (/sudo systemctl stop x2goserver.service/ and
> then
> > /sudo systemctl start x2goserver.service/ ) after changing the
> > /etc/x2go/x2goserver.conf file with logging to /debug/. That is the
> second text
> > file attached.
> >
> > In it, I can see :
> > Mar 15 14:51:15 ServeurITeN /usr/bin/x2gostartagent: successfully
> started X2Go
> > Agent session with ID manfred-50-1521121872_stDXFCE_dp24
> > Which means, I guess, the session was properly started.
>
> Well, that message is an euphemism. We launched the binary, but everything
> that
> happens after that is unknown since we immediately put the process into
> background. But yeah, having it spawned nxagent is good.
>
>
> > However, further on, I can also see :
> > Mar 15 14:51:22 ServeurITeN x2gogetstatus: db_getstatus called, session
> ID:
> > manfred-50-1521121872_stDXFCE_dp24, return value:
> > Mar 15 14:51:22 ServeurITeN x2gocleansessions:
> > manfred-50-1521121872_stDXFCE_dp24: removed from database, not updating
> status.
> > Mar 15 14:51:22 ServeurITeN x2gocleansessions:
> > manfred-50-1521121872_stDXFCE_dp24: in failed state, but agent is gone,
> forgetting.
> > Is that some kind of failure ?
>
> That indicates that x2goagent/nxagent died after starting up.
>
>
> > It is also interesting to see that when I issue a /who/ command with the
> Linux
> > Terminal , there is one extra session under my login.
>
> Yup, X2Go uses SSH connections for everything.
>
>
> > So I tried opening a x2go session with another login, which also failed
> but with
> > a different error message : "/Failed to start X2Go Agent session with ID
> > formation-50-1521122343_stDXFCE_dp24. X2Go Agent terminated
> unexpectedly.
> > Aborting session startup./" I then restarted the x2goserver.service
> again and
> > tried again with the other user account and got the same error as for
> the first
> > user ("The connection with the remote server was shut down. Please check
> the
> > state of your network connection.").
>
> The first error message is weird, but explainable by the fact that the
> proxy was
> not quick enough to connect in the first place (or something like this).
>
> Right now, you have two options: wait for a new nx-libs release (as said,
> unspecified time) or switch to the nightly/heuler repository that contains
> a fix
> for this issue... and switch back to the stable version once the new
> version has
> been properly released.
>
>
>
> Mihai
>
>
___
x2go-dev mailing list
x2go-dev@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-dev

Re: [X2Go-Dev] x2go wiki : self-debugging instructions ?

[Mihai Moldovan]

* On 03/15/2018 03:07 PM, Manfred Amoureux wrote:
> I recorded a screen capture while trying to start a connection from another
> computer. See the link below.
> As you can see, it seems the connection gets opened but the window crashes
> immediately. I have tried from several computers (including one with Windows) 
> so
> I don't think it's a problem on the client side.

Classic pattern of https://github.com/ArcticaProject/nx-libs/issues/677

Will be fixed with the next nx-libs release, but I cannot tell when that will
be. Ideally I'd like to see more xinerama changes/fixes to make it worthwhile.


> I have attached an extract of the /var/log/syslog file these last minutes. I 
> see
> nothing that looks like an error to me. Obviously, you should be able to
> interpret it better than me.
> I have also restarted x2go (/sudo systemctl stop x2goserver.service/ and then
> /sudo systemctl start x2goserver.service/ ) after changing the
> /etc/x2go/x2goserver.conf file with logging to /debug/. That is the second 
> text
> file attached.
> 
> In it, I can see :
> Mar 15 14:51:15 ServeurITeN /usr/bin/x2gostartagent: successfully started X2Go
> Agent session with ID manfred-50-1521121872_stDXFCE_dp24
> Which means, I guess, the session was properly started.

Well, that message is an euphemism. We launched the binary, but everything that
happens after that is unknown since we immediately put the process into
background. But yeah, having it spawned nxagent is good.


> However, further on, I can also see :
> Mar 15 14:51:22 ServeurITeN x2gogetstatus: db_getstatus called, session ID:
> manfred-50-1521121872_stDXFCE_dp24, return value:
> Mar 15 14:51:22 ServeurITeN x2gocleansessions:
> manfred-50-1521121872_stDXFCE_dp24: removed from database, not updating 
> status.
> Mar 15 14:51:22 ServeurITeN x2gocleansessions:
> manfred-50-1521121872_stDXFCE_dp24: in failed state, but agent is gone, 
> forgetting.
> Is that some kind of failure ?

That indicates that x2goagent/nxagent died after starting up.


> It is also interesting to see that when I issue a /who/ command with the Linux
> Terminal , there is one extra session under my login.

Yup, X2Go uses SSH connections for everything.


> So I tried opening a x2go session with another login, which also failed but 
> with
> a different error message : "/Failed to start X2Go Agent session with ID
> formation-50-1521122343_stDXFCE_dp24. X2Go Agent terminated unexpectedly.
> Aborting session startup./" I then restarted the x2goserver.service again and
> tried again with the other user account and got the same error as for the 
> first
> user ("The connection with the remote server was shut down. Please check the
> state of your network connection.").

The first error message is weird, but explainable by the fact that the proxy was
not quick enough to connect in the first place (or something like this).

Right now, you have two options: wait for a new nx-libs release (as said,
unspecified time) or switch to the nightly/heuler repository that contains a fix
for this issue... and switch back to the stable version once the new version has
been properly released.



Mihai



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

Re: [X2Go-Dev] x2go wiki : self-debugging instructions ?

[Mihai Moldovan]

* On 03/15/2018 12:59 PM, Manfred Amoureux wrote:
> $ dpkg -l | grep -Ei '(x2go|nx)'
> 
> [...]

Okay, up to date and no partially installed packages or version mismatched for
that matter.

That still leaves the "crash on connect" bug if the window was started a window
different from the first one in a multi-head setup.


> Now, when I have a look at /var/log/syslog, I see this :
> Mar 15 12:55:02 ServeurITeN x2golistsessions_sql: executing external command
> ,,x2gopath'' with args: libexec
> [...]
> 
> /ServeurITeN/ is the name of the machine. I have not been trying to connect 
> with
> x2go to this machine since the last reboot. Does it look like it's trying to
> execute something that fails constantly ?

Nope, it's just the cleanup process that loops through all session data and
syncs up or terminates stale session as necessary.

It's spammy (hence why I said "a lot of data"), but perfectly normal.

You'll have to make an actual connection attempt to see more interesting stuff.



Mihai



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

Re: [X2Go-Dev] x2go wiki : self-debugging instructions ?

[Manfred Amoureux]

Hello. Thanks for helping.

First the result of the command :

$ dpkg -l | grep -Ei '(x2go|nx)'

ii  inxi
2.2.35-0ubuntu1all  full featured
system information script
ii  libnx-x11-6:amd64
2:3.5.99.15-0~201803072246~ubuntu16.04.1
amd64nxagent's libNX_X11 client-part library
ii  libx2go-log-perl
4.1.0.0-0~1517~ubuntu16.04.1   all  Perl X2Go::Log
package
ii  libx2go-server-db-perl
4.1.0.0-0~1517~ubuntu16.04.1   amd64Perl
X2Go::Server:DB package
ii  libx2go-server-perl
4.1.0.0-0~1517~ubuntu16.04.1   all  Perl X2Go::Server
package
ii  libxcomp3:amd64
2:3.5.99.15-0~201803072246~ubuntu16.04.1
amd64NX compression library
ii  libxcompshad3:amd64
2:3.5.99.15-0~201803072246~ubuntu16.04.1
amd64NX shadowing library
ii  nx-x11-common
2:3.5.99.15-0~201803072246~ubuntu16.04.1
all  nx-X11 (common files)
ii  nxagent
2:3.5.99.15-0~201803072246~ubuntu16.04.1
amd64Nested Xserver (aka NX Agent) supporting the NX compression
protocol
ii  nxproxy
2:3.5.99.15-0~201803072246~ubuntu16.04.1
amd64NX proxy
rc  x2goagent
2:3.5.0.33-0~710~ubuntu16.04.1 all  X2Go agent
ii  x2goserver
4.1.0.0-0~1517~ubuntu16.04.1   amd64X2Go server daemon
scripts
ii  x2goserver-common
4.1.0.0-0~1517~ubuntu16.04.1   amd64X2Go Server (common
files)
ii  x2goserver-extensions
4.1.0.0-0~1517~ubuntu16.04.1   all  X2Go Server
(extension support)
ii  x2goserver-fmbindings
4.1.0.0-0~1517~ubuntu16.04.1   all  X2Go Server (file
manager bindings)
ii  x2goserver-printing
4.1.0.0-0~1517~ubuntu16.04.1   all  X2Go server
(printing support)
ii  x2goserver-x2goagent
4.1.0.0-0~1517~ubuntu16.04.1   all  X2Go Server's X2Go
Agent
ii  x2goserver-xsession
4.1.0.0-0~1517~ubuntu16.04.1   all  X2Go Server
(Xsession runner)



Now, when I have a look at /var/log/syslog, I see this :
Mar 15 12:55:02 ServeurITeN x2golistsessions_sql: executing external
command ,,x2gopath'' with args: libexec
Mar 15 12:55:02 ServeurITeN x2golistsessions_sql: executing external
command ,,/usr/lib/x2go/libx2go-server-db-sqlite3-wrapper'' with args:
listsessionsroot,ServeurITeN
Mar 15 12:55:04 ServeurITeN x2golistsessions_sql: executing external
command ,,x2gopath'' with args: libexec
Mar 15 12:55:04 ServeurITeN x2golistsessions_sql: executing external
command ,,/usr/lib/x2go/libx2go-server-db-sqlite3-wrapper'' with args:
listsessionsroot,ServeurITeN
Mar 15 12:55:06 ServeurITeN x2golistsessions_sql: executing external
command ,,x2gopath'' with args: libexec
Mar 15 12:55:06 ServeurITeN x2golistsessions_sql: executing external
command ,,/usr/lib/x2go/libx2go-server-db-sqlite3-wrapper'' with args:
listsessionsroot,ServeurITeN
Mar 15 12:55:08 ServeurITeN x2golistsessions_sql: executing external
command ,,x2gopath'' with args: libexec
Mar 15 12:55:08 ServeurITeN x2golistsessions_sql: executing external
command ,,/usr/lib/x2go/libx2go-server-db-sqlite3-wrapper'' with args:
listsessionsroot,ServeurITeN
Mar 15 12:55:11 ServeurITeN x2golistsessions_sql: executing external
command ,,x2gopath'' with args: libexec
Mar 15 12:55:11 ServeurITeN x2golistsessions_sql: executing external
command ,,/usr/lib/x2go/libx2go-server-db-sqlite3-wrapper'' with args:
listsessionsroot,ServeurITeN
Mar 15 12:55:13 ServeurITeN x2golistsessions_sql: executing external
command ,,x2gopath'' with args: libexec
Mar 15 12:55:13 ServeurITeN x2golistsessions_sql: executing external
command ,,/usr/lib/x2go/libx2go-server-db-sqlite3-wrapper'' with args:
listsessionsroot,ServeurITeN
Mar 15 12:55:15 ServeurITeN x2golistsessions_sql: executing external
command ,,x2gopath'' with args: libexec
Mar 15 12:55:15 ServeurITeN x2golistsessions_sql: executing external
command ,,/usr/lib/x2go/libx2go-server-db-sqlite3-wrapper'' with args:
listsessionsroot,ServeurITeN
Mar 15 12:55:17 ServeurITeN x2golistsessions_sql: executing external
command ,,x2gopath'' with args: libexec
Mar 15 12:55:17 ServeurITeN x2golistsessions_sql: executing external
command ,,/usr/lib/x2go/libx2go-server-db-sqlite3-wrapper'' with args:
listsessionsroot,ServeurITeN
Mar 15 12:55:20 ServeurITeN x2golistsessions_sql: executing external
command ,,x2gopath'' with args: libexec
Mar 15 12:55:20 ServeurITeN x2golistsessions_sql: executing external
command ,,/usr/lib/x2go/libx2go-server-db-sqlite3-wrapper'' with args:
listsessionsroot,ServeurITeN
Mar 15 12:55:22 ServeurITeN x2golistsessions_sql: executing external
command ,,x2gopath'' with args: libexec
Mar 15 12:55:22 ServeurITeN x2golistsessions_sql: executing external
command ,,/usr/lib/x2go/libx2go-server-db-sqlite3-wrapper'' with args:
listsessionsroot,ServeurITeN
Mar 15 12:55:24 ServeurITeN x2golistsessions_sql: executing external
command ,,x2gopath'' with args: libexec
Mar 15 12:55:24 ServeurITeN x2golistsessions_sql: executing external

Re: [X2Go-Dev] x2go wiki : self-debugging instructions ?

[Mihai Moldovan]

* On 03/15/2018 12:36 PM, Mihai Moldovan wrote:
> The general syslog, after enabling server debug output, and client debug 
> output
> (x2goclient --debug) is more important, but this issue looks a lot like
> https://github.com/ArcticaProject/nx-libs/issues/679
> 
> I've only fixed the screen positioning issue today - nightly builds should
> already have that fix.
> 
> A workaround is to start x2goclient on your first (normally also primary)
> display. Are you starting it on a secondary (non-first) display? If yes, then
> it's likely that this is causing the trouble.

After skimming your original post again, I also wonder if you have partly
upgraded packages on that machine.

dpkg -l | grep -Ei '(x2go|nx)'



Mihai



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

Re: [X2Go-Dev] x2go wiki : self-debugging instructions ?

[Mihai Moldovan]

* On 03/13/2018 09:13 PM, Manfred Amoureux wrote:
> Now the purpose of this email:
> After tinkering around my x2go server install, it seems I have broken it
> . I am not here to ask for
> help me fixing it (although, I wouldn't mind) but I have been looking for
> instructions in the x2go wiki
>  about where to look for 
> the
> origin of errors (logs, etc ...) and I have not found such page.

Debugging is complicated. We do have a page at
https://wiki.x2go.org/doku.php/wiki:development:debugging

But most of the time there are special circumstances that lead to failure, which
cannot easily be ticked off using a checklist.

Even when it would be, the output is huge and usually needs proper
interpretation. Difficult to do so without knowing or at least looking at the 
code.


> Indeed, I already searched the /var/log/auth.log , but haven't found a clue of
> what's wrong.
> So, I thought there must be some basic steps that one may undertake looking 
> for
> what's wrong (logs to search, command lines to execute and check the result 
> ...)
> but I cannot figure out which ones.

The general syslog, after enabling server debug output, and client debug output
(x2goclient --debug) is more important, but this issue looks a lot like
https://github.com/ArcticaProject/nx-libs/issues/679

I've only fixed the screen positioning issue today - nightly builds should
already have that fix.

A workaround is to start x2goclient on your first (normally also primary)
display. Are you starting it on a secondary (non-first) display? If yes, then
it's likely that this is causing the trouble.


> I am willing to help the community by filling some pages in the wiki (so 
> nobody
> will have to bother the mailing list again asking what I am currently asking) 
> -
> I just need to find out how one create an account for the wiki.

You can't. User registration has been disabled due to spam bots creating
accounts and vandalizing pages. Wiki administrators (Heinz, me) can create new
accounts for users.

I typically need an email address (mandatory), a nickname (optional but
preferred, otherwise I'll guess it) and a real name (optional) for registration
and I will create an account accordingly.



Mihai



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