Looks like my ssh is hurt:
[256092.528160] SshMasterConnec[4630]: segfault at dd ip 00007fc61a459eec sp
00007fc5ee2b8928 error 4 in libssh.so.4.4.2[7fc61a433000+6d000]
[256163.639990] SshMasterConnec[5083]: segfault at dd ip 00007fa0a3453eec sp
00007fa0772ee928 error 4 in libssh.so.4.4.2[7fa0a342d000+6d000]
This might be my issue rather than x2go, but it never happens when I do
a straight ssh session.
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting.
Knowledgeable human assistance, not telephone trees or script readers.
See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.
I updated a Ubuntu system with nightly builds and now it is doing the
same as Mint but only if I login as root. If I login with a normal UID it
does not.
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting.
Knowledgeable human assistance, not telephone trees or script readers.
See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.
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.
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting.
Knowledgeable human assistance, not telephone trees or script readers.
See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.
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.
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting.
Knowledgeable human assistance, not telephone trees or script readers.
See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.
After todays Fedora updates, the Nightly Builds of x2goserver no longer
works. It starts up and then immediately exits, the mate-session crashes.
Yet Mate does not crash under the stable build but also does not set the screen
size properly owing to the xrandr version issue.
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting.
Knowledgeable human assistance, not telephone trees or script readers.
See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.
Updates broke on every Ubuntu server I have x2go nightly builds installed
upon. It ends with:
dpkg: error processing package x2goserver-fmbindings (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
x2goserver
x2goserver-extensions
x2goserver-printing
x2goserver-xsession
x2goserver-fmbindings
And a non-functional server though many more errors leading up to that.
If you need the full dialogue let me know.
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting.
Knowledgeable human assistance, not telephone trees or script readers.
See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.
It seems that 'loginctl linger' does not work anymore as an ordinary user
on Fedora 27. This worked on Fedora 26.
From: https://bugzilla.redhat.com/show_bug.cgi?id=1478974#c15
On Fedora 27 it seems that enable-linger does not work as an ordinary user
which is required for x2goserver keep sessions alive.
Inside an x2go session:
$ loginctl enable-linger
Failed to look up user 62: No such process
and (as root) "loginctl show-user ngaywood" shows:
Linger=no
As root I can:
loginctl enable-linger ngaywood
and Linger will be set.
This used to work in Fedora 26
x2goserver-4.0.1.22-0.0x2go1.1.git20180204.1197.main.fc27.x86_64
--
Norman Gaywood, Computer Systems Officer
School of Science and Technology
University of New England
Armidale NSW 2351, Australia
ngaywood(a)une.edu.au http://turing.une.edu.au/~ngaywood
Phone: +61 (0)2 6773 2412 Mobile: +61 (0)4 7862 0062
Please avoid sending me Word or Power Point attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html
I know this is a hazard of using nightly builds but the stable does not
have the right version of xrandr. Is there anything I can do to fix or do I
just need to wait for another push?
dpkg --configure x2goserver
Setting up x2goserver (4.1.0.1-0x2go1~git20180301.1604+9.heuler.1) ...
Job for x2goserver.service failed because the control process exited with error
code.
See "systemctl status x2goserver.service" and "journalctl -xe" for details.
invoke-rc.d: initscript x2goserver, action "start" failed.
â x2goserver.service - X2Go Server Daemon
Loaded: loaded (/lib/systemd/system/x2goserver.service; enabled; vendor
preset: enabled)
Active: failed (Result: exit-code) since Wed 2018-02-28 18:16:37 PST; 3ms
ago
Process: 16339 ExecStart=/usr/sbin/x2gocleansessions (code=exited, status=2)
Main PID: 906 (code=exited, status=0/SUCCESS)
Feb 28 18:16:37 debian systemd[1]: Starting X2Go Server Daemon...
Feb 28 18:16:37 debian x2gocleansessions[16339]: Can't locate
X2Go/Server/DB/MySQL.pm in @INC (you may need to install the
X2Go::Server::DB::MySQL moduleâ¦2.
Feb 28 18:16:37 debian x2gocleansessions[16339]: BEGIN failed--compilation
aborted at /usr/share/perl5/X2Go/Server/DB.pm line 42.
Feb 28 18:16:37 debian x2gocleansessions[16339]: Compilation failed in require
at /usr/sbin/x2gocleansessions line 34.
Feb 28 18:16:37 debian x2gocleansessions[16339]: BEGIN failed--compilation
aborted at /usr/sbin/x2gocleansessions line 34.
Feb 28 18:16:37 debian systemd[1]: x2goserver.service: Control process exited,
code=exited status=2
Feb 28 18:16:37 debian systemd[1]: Failed to start X2Go Server Daemon.
Feb 28 18:16:37 debian systemd[1]: x2goserver.service: Unit entered failed
state.
Feb 28 18:16:37 debian systemd[1]: x2goserver.service: Failed with result
'exit-code'.
Hint: Some lines were ellipsized, use -l to show in full.
dpkg: error processing package x2goserver (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
x2goserver
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting.
Knowledgeable human assistance, not telephone trees or script readers.
See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.
The daily build formerly was working on Zorin, save for the xrandr issue.
Now it is failing with:
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 'Mon Feb 26 23:28:49 2018'.
Session: Session terminated at 'Mon Feb 26 23:28:49 2018'.
Connection timeout, abortingConnection timeout,
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting.
Knowledgeable human assistance, not telephone trees or script readers.
See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.
The stable build of x2go presently works on Zorin except xrandr version
issues but the Nightly Builds does not. Nightly builds nxagent core dumps
when the session tries to start. Got to go now but will provide more details,
try to get a backtrace if I can, later when I get back.
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting.
Knowledgeable human assistance, not telephone trees or script readers.
See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.