Is something wrong with the x2goserver-4.0.1.18-1.el7.x86_64 package in EPEL. The CentOS7 hosts that worked with the previous version (w/MATE desktop) now just open a black window on the client that closes almost instantly. On one system I upgraded only the x2goserver package to make sure it wasn't some other update causing the problem.
-- Les Mikesell lesmikesell@gmail.com
Nope, it's not a problem with X2Go per se', it's a problem with Gnome-3 and any other compositing desktop being incompatible with X2Go (and freeNX). Install mate on Centos7, then specify "mate-session" as the command or choose Mate from the drop-down in X2Go and it will work fine.
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting. Knowledgeable human assistance, not telephone trees or script readers. See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.
On Fri, 31 Oct 2014, Les Mikesell wrote:
Date: Fri, 31 Oct 2014 17:31:20 -0500 From: Les Mikesell <lesmikesell@gmail.com> To: x2go-user <x2go-user@lists.x2go.org> Subject: [X2Go-User] CentOS7/EPEL package?
Is something wrong with the x2goserver-4.0.1.18-1.el7.x86_64 package in EPEL. The CentOS7 hosts that worked with the previous version (w/MATE desktop) now just open a black window on the client that closes almost instantly. On one system I upgraded only the x2goserver package to make sure it wasn't some other update causing the problem.
-- Les Mikesell lesmikesell@gmail.com
x2go-user mailing list x2go-user@lists.x2go.org http://lists.x2go.org/listinfo/x2go-user
On Fri, Oct 31, 2014 at 5:33 PM, Robert Dinse <nanook@eskimo.com> wrote:
Nope, it's not a problem with X2Go per se', it's a problem with Gnome-3and any other compositing desktop being incompatible with X2Go (and freeNX). Install mate on Centos7, then specify "mate-session" as the command or choose Mate from the drop-down in X2Go and it will work fine.
In case I wasn't clear: a system that _was_ working with x2go/MATE before the x2goserver-4.0.1.18-1.el7.x86_64 update now fails with no other change. As do the other systems where I've done a 'yum update' that brought in this change along with others including some MATE component updates.
-- Les Mikesell lesmikesell@gmail.com
Ok, let me verify which version I have on my system.-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting. Knowledgeable human assistance, not telephone trees or script readers. See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.
On Fri, 31 Oct 2014, Les Mikesell wrote:
Date: Fri, 31 Oct 2014 17:46:34 -0500 From: Les Mikesell <lesmikesell@gmail.com> To: Robert Dinse <nanook@eskimo.com> Cc: x2go-user <x2go-user@lists.x2go.org> Subject: Re: [X2Go-User] CentOS7/EPEL package?
On Fri, Oct 31, 2014 at 5:33 PM, Robert Dinse <nanook@eskimo.com> wrote:
Nope, it's not a problem with X2Go per se', it's a problem with Gnome-3and any other compositing desktop being incompatible with X2Go (and freeNX). Install mate on Centos7, then specify "mate-session" as the command or choose Mate from the drop-down in X2Go and it will work fine.
In case I wasn't clear: a system that _was_ working with x2go/MATE before the x2goserver-4.0.1.18-1.el7.x86_64 update now fails with no other change. As do the other systems where I've done a 'yum update' that brought in this change along with others including some MATE component updates.
-- Les Mikesell lesmikesell@gmail.com
Les
I had problems with the build of the package x2goserver-4.0.1.18-1 for Fedora 20 under KDE - the session would fail to start.
Orion has built a new package 4.0.1.18-3 which fixes that problem. It hasn't made it through the update channels yet, but I fished it out of koji and tested it.
It may be that your mate issue is fixed as well in the equivalent build for el7. You can get the package from: http://koji.fedoraproject.org/koji/packageinfo?packageID=16717
Roderick Johnstone
On 31/10/2014 22:31, Les Mikesell wrote:
Is something wrong with the x2goserver-4.0.1.18-1.el7.x86_64 package in EPEL. The CentOS7 hosts that worked with the previous version (w/MATE desktop) now just open a black window on the client that closes almost instantly. On one system I upgraded only the x2goserver package to make sure it wasn't some other update causing the problem.
Ok, I checked, the version I have is:x2goserver.x86_64 4.0.1.18-3.el7 @epel-testing
It is working.-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting. Knowledgeable human assistance, not telephone trees or script readers. See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.
On Fri, 31 Oct 2014, Roderick Johnstone wrote:
Date: Fri, 31 Oct 2014 23:03:55 +0000 From: Roderick Johnstone <rmj@ast.cam.ac.uk> To: x2go-user@lists.x2go.org Subject: Re: [X2Go-User] CentOS7/EPEL package?
Les
I had problems with the build of the package x2goserver-4.0.1.18-1 for Fedora 20 under KDE - the session would fail to start.
Orion has built a new package 4.0.1.18-3 which fixes that problem. It hasn't made it through the update channels yet, but I fished it out of koji and tested it.
It may be that your mate issue is fixed as well in the equivalent build for el7. You can get the package from: http://koji.fedoraproject.org/koji/packageinfo?packageID=16717
Roderick Johnstone
On 31/10/2014 22:31, Les Mikesell wrote:
Is something wrong with the x2goserver-4.0.1.18-1.el7.x86_64 package in EPEL. The CentOS7 hosts that worked with the previous version (w/MATE desktop) now just open a black window on the client that closes almost instantly. On one system I upgraded only the x2goserver package to make sure it wasn't some other update causing the problem.
x2go-user mailing list x2go-user@lists.x2go.org http://lists.x2go.org/listinfo/x2go-user
Hi all,
On Sa 01 Nov 2014 00:03:55 CET, Roderick Johnstone wrote:
Les
I had problems with the build of the package x2goserver-4.0.1.18-1
for Fedora 20 under KDE - the session would fail to start.Orion has built a new package 4.0.1.18-3 which fixes that problem.
It hasn't made it through the update channels yet, but I fished it
out of koji and tested it.It may be that your mate issue is fixed as well in the equivalent
build for el7. You can get the package from:
http://koji.fedoraproject.org/koji/packageinfo?packageID=16717Roderick Johnstone
Make sure you have x2goserver-xsession installed as well. I guess the
new x2goserver package version (haven't looked at the package, but
discussed the issue with Orion, the EPEL maintainer recently) pulls in
x2goserver-xsession as a dependency.
Mike
--
DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976 148
GnuPG Key ID 0x25771B31 mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...
On 03/11/14 09:34, Mike Gabriel wrote:
Hi all,
On Sa 01 Nov 2014 00:03:55 CET, Roderick Johnstone wrote:
Les
I had problems with the build of the package x2goserver-4.0.1.18-1 for Fedora 20 under KDE - the session would fail to start.
Orion has built a new package 4.0.1.18-3 which fixes that problem. It hasn't made it through the update channels yet, but I fished it out of koji and tested it.
It may be that your mate issue is fixed as well in the equivalent build for el7. You can get the package from: http://koji.fedoraproject.org/koji/packageinfo?packageID=16717
Roderick Johnstone
Make sure you have x2goserver-xsession installed as well. I guess the new x2goserver package version (haven't looked at the package, but discussed the issue with Orion, the EPEL maintainer recently) pulls in x2goserver-xsession as a dependency.
Mike
Mike
Curiously, for me, with Orion's 4.0.1.18-3 packages on Fedora 20 a KDE session fails to start if I have x2goserver-xsession installed, but works fine if x2goserver-xsession is not installed.
Roderick
On 11/03/2014 04:12 AM, Roderick Johnstone wrote:
Mike
Curiously, for me, with Orion's 4.0.1.18-3 packages on Fedora 20 a KDE session fails to start if I have x2goserver-xsession installed, but works fine if x2goserver-xsession is not installed.
Roderick
Details? grep x2go /var/log/messages, session log?
-- Orion Poplawski Technical Manager 303-415-9701 x222 NWRA, Boulder/CoRA Office FAX: 303-415-9702 3380 Mitchell Lane orion@nwra.com Boulder, CO 80301 http://www.nwra.com
On 03/11/14 17:51, Orion Poplawski wrote:
On 11/03/2014 04:12 AM, Roderick Johnstone wrote:
Mike
Curiously, for me, with Orion's 4.0.1.18-3 packages on Fedora 20 a KDE session fails to start if I have x2goserver-xsession installed, but works fine if x2goserver-xsession is not installed.
Roderick
Details? grep x2go /var/log/messages, session log?
Orion
Here they are.
Roderick
# cat session.log
running as X2Go Agent
NXAGENT - Version 3.5.0
Copyright (C) 2001, 2011 NoMachine. See http://www.nomachine.com/ for more information.
Info: Agent running with pid '14938'. Session: Starting session at 'Mon Nov 3 17:56:47 2014'. Info: Proxy running in server mode with pid '14938'. Info: Waiting for connection from 'localhost' on port '30355'. Info: Accepted connection from '127.0.0.1'. Info: Connection with remote proxy completed. Info: Using ADSL link parameters 512/24/1/0. Info: Using agent parameters 5000/10/50/0/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: Listening to X11 connections on display ':167'. Info: Established X client connection. Info: Using shared memory parameters 1/1/0/0K. Info: Using alpha channel in render extension. Info: Not using local device configuration changes. keyboard file created Session: Session started at 'Mon Nov 3 17:56:53 2014'. Session: Terminating session at 'Mon Nov 3 17:56:53 2014'. Info: Waiting the cleanup timeout to complete. Session: Session terminated at 'Mon Nov 3 17:56:54 2014'.
# grep x2go /var/log/messages Nov 3 17:56:45 xxx /usr/bin/x2gostartagent: x2gostartagent called with options: 800x600 adsl 16m-jpeg-9 unix-kde-depth_32 us query 0 D KDE Nov 3 17:56:45 xxx /usr/bin/x2gosessionlimit[14729]: x2gosessionlimit has been called Nov 3 17:56:45 xxx /usr/bin/x2golistsessions[14732]: x2golistsessions has been called with options: --all-servers Nov 3 17:56:47 xxx /usr/bin/x2gofeature: x2gofeature called with options: X2GO_RUN_EXTENSIONS Nov 3 17:56:47 xxx /usr/share/x2go/x2gofeature.d/x2goserver-extensions.features: x2goserver-extensions.features called with options: X2GO_RUN_EXTENSIONS Nov 3 17:56:47 xxx /usr/bin/x2goserver-run-extensions: x2goserver-run-extensions called with options: rmj-167-1415037405_stDKDE_dp32 pre-start Nov 3 17:56:47 xxx /usr/bin/x2gostartagent: successfully started X2Go agent session with ID rmj-167-1415037405_stDKDE_dp32 Nov 3 17:56:47 xxx /usr/bin/x2gofeature: x2gofeature called with options: X2GO_RUN_EXTENSIONS Nov 3 17:56:47 xxx /usr/share/x2go/x2gofeature.d/x2goserver-extensions.features: x2goserver-extensions.features called with options: X2GO_RUN_EXTENSIONS Nov 3 17:56:47 xxx /usr/bin/x2goserver-run-extensions: x2goserver-run-extensions called with options: rmj-167-1415037405_stDKDE_dp32 post-start Nov 3 17:56:47 xxx /usr/bin/x2gostartagent: blocking creation of agent's keyboard file /tmp/.x2go-rmj/C-rmj-167-1415037405_stDKDE_dp32/keyboard as requested by session startup command Nov 3 17:56:48 xxx /usr/bin/x2goruncommand: x2goruncommand called with options: 167 14938 rmj-167-1415037405_stDKDE_dp32 30356 startkde nosnd D Nov 3 17:56:48 xxx /usr/bin/x2gofeature: x2gofeature called with options: X2GO_RUN_EXTENSIONS Nov 3 17:56:48 xxx /usr/share/x2go/x2gofeature.d/x2goserver-extensions.features: x2goserver-extensions.features called with options: X2GO_RUN_EXTENSIONS Nov 3 17:56:48 xxx /usr/bin/x2goserver-run-extensions: x2goserver-run-extensions called with options: rmj-167-1415037405_stDKDE_dp32 pre-runcommand Nov 3 17:56:48 xxx /usr/bin/x2gosetkeyboard: x2gosetkeyboard called with options: Nov 3 17:56:48 xxx /usr/bin/x2gofeature: x2gofeature called with options: X2GO_XSESSION Nov 3 17:56:48 xxx /usr/bin/x2gosetkeyboard: /home/rmj/.x2go/C-rmj-167-1415037405_stDKDE_dp32/keyboard is blocked, not setting keyboard parameters from client-side settings Nov 3 17:56:48 xxx /usr/share/x2go/x2gofeature.d/x2goserver-extensions.features: x2goserver-extensions.features called with options: X2GO_XSESSION Nov 3 17:56:48 xxx /usr/share/x2go/x2gofeature.d/x2goserver-printing.features: x2goserver-printing.features called with options: X2GO_XSESSION Nov 3 17:56:48 xxx /usr/share/x2go/x2gofeature.d/x2goserver-xsession.features: x2goserver-xsession.features called with options: X2GO_XSESSION Nov 3 17:56:48 xxx /usr/bin/x2goruncommand: launching session with Xsession-x2go mechanism, using STARTUP="startkde" Nov 3 17:56:53 xxx /usr/bin/x2gofeature: x2gofeature called with options: X2GO_RUN_EXTENSIONS Nov 3 17:56:53 xxx /usr/share/x2go/x2gofeature.d/x2goserver-extensions.features: x2goserver-extensions.features called with options: X2GO_RUN_EXTENSIONS Nov 3 17:56:53 xxx /usr/bin/x2goserver-run-extensions: x2goserver-run-extensions called with options: rmj-167-1415037405_stDKDE_dp32 post-runcommand Nov 3 17:56:53 xxx /usr/bin/x2gofeature: x2gofeature called with options: X2GO_DESKTOPSHARING Nov 3 17:56:53 xxx /usr/share/x2go/x2gofeature.d/x2goserver-extensions.features: x2goserver-extensions.features called with options: X2GO_DESKTOPSHARING Nov 3 17:56:53 xxx /usr/share/x2go/x2gofeature.d/x2goserver-printing.features: x2goserver-printing.features called with options: X2GO_DESKTOPSHARING Nov 3 17:56:53 xxx /usr/share/x2go/x2gofeature.d/x2goserver-xsession.features: x2goserver-xsession.features called with options: X2GO_DESKTOPSHARING Nov 3 17:56:53 xxx /usr/share/x2go/x2gofeature.d/x2goserver.features: x2goserver.features called with options: X2GO_DESKTOPSHARING Nov 3 17:56:53 xxx /usr/bin/x2goumount-session[15322]: x2goumount-session has been called with options: rmj-167-1415037405_stDKDE_dp32 Nov 3 17:56:54 xxx /usr/bin/x2gocmdexitmessage: x2gocmdexitmessage called with options: rmj-167-1415037405_stDKDE_dp32
On 11/03/2014 11:08 AM, Roderick Johnstone wrote:
On 03/11/14 17:51, Orion Poplawski wrote:
On 11/03/2014 04:12 AM, Roderick Johnstone wrote:
Mike
Curiously, for me, with Orion's 4.0.1.18-3 packages on Fedora 20 a KDE session fails to start if I have x2goserver-xsession installed, but works fine if x2goserver-xsession is not installed.
Roderick
Details? grep x2go /var/log/messages, session log?
Orion
Here they are.
Roderick
Hmm, I'm not seeing anything there. How about in ~/.xsession-x2go-errors?
-- Orion Poplawski Technical Manager 303-415-9701 x222 NWRA, Boulder/CoRA Office FAX: 303-415-9702 3380 Mitchell Lane orion@nwra.com Boulder, CO 80301 http://www.nwra.com
On 03/11/2014 20:50, Orion Poplawski wrote:
On 11/03/2014 11:08 AM, Roderick Johnstone wrote:
On 03/11/14 17:51, Orion Poplawski wrote:
On 11/03/2014 04:12 AM, Roderick Johnstone wrote:
Mike
Curiously, for me, with Orion's 4.0.1.18-3 packages on Fedora 20 a KDE session fails to start if I have x2goserver-xsession installed, but works fine if x2goserver-xsession is not installed.
Roderick
So I tested it with a Terminal session. That works fine. I tested the KDE session as root. That fails.
What happens is that, very briefly, the remote screen pops up. Its black with the x2go logo and disappears in a fraction of a second.
By the way, I was able to reconnect to an already running session that had been created without the x2goserver-xsession package installed when the x2goserver-xsession packages was installed.
Let me know if I can run any more tests that might be helpful for debugging.
Roderick
Hi Roderick,
On Di 04 Nov 2014 09:25:59 CET, Roderick Johnstone wrote:
On 03/11/2014 20:50, Orion Poplawski wrote:
On 11/03/2014 11:08 AM, Roderick Johnstone wrote:
On 03/11/14 17:51, Orion Poplawski wrote:
On 11/03/2014 04:12 AM, Roderick Johnstone wrote:
Mike
Curiously, for me, with Orion's 4.0.1.18-3 packages on Fedora 20
a KDE session fails to start if I have x2goserver-xsession installed, but works fine if x2goserver-xsession is not installed.Roderick
So I tested it with a Terminal session. That works fine. I tested
the KDE session as root. That fails.What happens is that, very briefly, the remote screen pops up. Its
black with the x2go logo and disappears in a fraction of a second.By the way, I was able to reconnect to an already running session
that had been created without the x2goserver-xsession package
installed when the x2goserver-xsession packages was installed.Let me know if I can run any more tests that might be helpful for debugging.
Roderick
Please edit /usr/bin/x2goruncommand and add extra debug messages.
Place them everywhere, so to say and look which of the messages appear
in the messages log file and which don't. You need to track down the
code path that is gone while running x2goruncommand.
Thanks+greets, mike
--
DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976 148
GnuPG Key ID 0x25771B31 mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...
On 04/11/14 09:45, Mike Gabriel wrote:
Hi Roderick,
On Di 04 Nov 2014 09:25:59 CET, Roderick Johnstone wrote:
On 03/11/2014 20:50, Orion Poplawski wrote:
On 11/03/2014 11:08 AM, Roderick Johnstone wrote:
On 03/11/14 17:51, Orion Poplawski wrote:
On 11/03/2014 04:12 AM, Roderick Johnstone wrote:
Mike
Curiously, for me, with Orion's 4.0.1.18-3 packages on Fedora 20 a KDE session fails to start if I have x2goserver-xsession installed, but works fine if x2goserver-xsession is not installed.
Roderick
So I tested it with a Terminal session. That works fine. I tested the KDE session as root. That fails.
What happens is that, very briefly, the remote screen pops up. Its black with the x2go logo and disappears in a fraction of a second.
By the way, I was able to reconnect to an already running session that had been created without the x2goserver-xsession package installed when the x2goserver-xsession packages was installed.
Let me know if I can run any more tests that might be helpful for debugging.
Roderick
Please edit /usr/bin/x2goruncommand and add extra debug messages. Place them everywhere, so to say and look which of the messages appear in the messages log file and which don't. You need to track down the code path that is gone while running x2goruncommand.
Thanks+greets, mike
Mike
Thanks for your input.
I've actually started on a different tack in this debugging.
Having identified which files are installed by x2goserver-xsession, I've been systematically renaming these files so that they are not found.
Using this technique I have found that the session works fine when I move /etc/x2go/xinitrc.d/50-input.sh to /etc/x2go/xinitrc.d.off/50-input.sh so I think this file is where the problem lies.
50-input.sh is quite a busy file, so I suppose I'll have to pepper it with echo's to find out at what point the session evaporates.
Where would I expect to find the output from an echo command in that file logged?
Given what I have found so far, do you think there is still merit in putting debugging statements into /usr/bin/x2goruncommand?
Thanks
Roderick
On 10/31/2014 04:31 PM, Les Mikesell wrote:
Is something wrong with the x2goserver-4.0.1.18-1.el7.x86_64 package in EPEL. The CentOS7 hosts that worked with the previous version (w/MATE desktop) now just open a black window on the client that closes almost instantly. On one system I upgraded only the x2goserver package to make sure it wasn't some other update causing the problem.
Yes, there is an issue with if if you don't have x2goserver-xsession installed as well. Please test https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-3596/x2goserver-4.0... from epel-testing and give feedback.
-- Orion Poplawski Technical Manager 303-415-9701 x222 NWRA/CoRA Division FAX: 303-415-9702 3380 Mitchell Lane orion@cora.nwra.com Boulder, CO 80301 http://www.cora.nwra.com
This is what I have installed and it is working well for me.-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting. Knowledgeable human assistance, not telephone trees or script readers. See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.
On Sat, 1 Nov 2014, Orion Poplawski wrote:
Date: Sat, 01 Nov 2014 08:27:10 -0600 From: Orion Poplawski <orion@cora.nwra.com> To: Les Mikesell <lesmikesell@gmail.com>, x2go-user <x2go-user@lists.x2go.org> Subject: Re: [X2Go-User] CentOS7/EPEL package?
On 10/31/2014 04:31 PM, Les Mikesell wrote:
Is something wrong with the x2goserver-4.0.1.18-1.el7.x86_64 package in EPEL. The CentOS7 hosts that worked with the previous version (w/MATE desktop) now just open a black window on the client that closes almost instantly. On one system I upgraded only the x2goserver package to make sure it wasn't some other update causing the problem.
Yes, there is an issue with if if you don't have x2goserver-xsession installed as well. Please test https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-3596/x2goserver-4.0... from epel-testing and give feedback.
-- Orion Poplawski Technical Manager 303-415-9701 x222 NWRA/CoRA Division FAX: 303-415-9702 3380 Mitchell Lane orion@cora.nwra.com Boulder, CO 80301 http://www.cora.nwra.com
x2go-user mailing list x2go-user@lists.x2go.org http://lists.x2go.org/listinfo/x2go-user
On Sat, Nov 1, 2014 at 9:27 AM, Orion Poplawski <orion@cora.nwra.com> wrote:
On 10/31/2014 04:31 PM, Les Mikesell wrote:
Is something wrong with the x2goserver-4.0.1.18-1.el7.x86_64 package in EPEL. The CentOS7 hosts that worked with the previous version (w/MATE desktop) now just open a black window on the client that closes almost instantly. On one system I upgraded only the x2goserver package to make sure it wasn't some other update causing the problem.
Yes, there is an issue with if if you don't have x2goserver-xsession installed as well. Please test https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-3596/x2goserver-4.0... from epel-testing and give feedback.
That fixes the problem - but what is the story with x2go-server-xsession? Should that be installed too?
-- Les Mikesell lesmikesell@gmail.com
On 11/01/2014 12:59 PM, Les Mikesell wrote:
On Sat, Nov 1, 2014 at 9:27 AM, Orion Poplawski <orion@cora.nwra.com> wrote:
On 10/31/2014 04:31 PM, Les Mikesell wrote:
Is something wrong with the x2goserver-4.0.1.18-1.el7.x86_64 package in EPEL. The CentOS7 hosts that worked with the previous version (w/MATE desktop) now just open a black window on the client that closes almost instantly. On one system I upgraded only the x2goserver package to make sure it wasn't some other update causing the problem.
Yes, there is an issue with if if you don't have x2goserver-xsession installed as well. Please test https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-3596/x2goserver-4.0... from epel-testing and give feedback.
That fixes the problem - but what is the story with x2go-server-xsession? Should that be installed too?
It's recommended for setting up full desktop environments, and probably should be installed.
-- Orion Poplawski Technical Manager 303-415-9701 x222 NWRA/CoRA Division FAX: 303-415-9702 3380 Mitchell Lane orion@cora.nwra.com Boulder, CO 80301 http://www.cora.nwra.com
On Sat, Nov 1, 2014 at 3:31 PM, Orion Poplawski <orion@cora.nwra.com> wrote:
That fixes the problem - but what is the story with x2go-server-xsession? Should that be installed too?
It's recommended for setting up full desktop environments, and probably should be installed.
Unless there is some downside, why not make it a dependency for x2go-server?
-- Les Mikesell lesmikesell@gmail.com
On Sat, Nov 1, 2014 at 1:59 PM, Les Mikesell <lesmikesell@gmail.com> wrote:
On Sat, Nov 1, 2014 at 9:27 AM, Orion Poplawski <orion@cora.nwra.com> wrote:
On 10/31/2014 04:31 PM, Les Mikesell wrote:
Is something wrong with the x2goserver-4.0.1.18-1.el7.x86_64 package in EPEL. The CentOS7 hosts that worked with the previous version (w/MATE desktop) now just open a black window on the client that closes almost instantly. On one system I upgraded only the x2goserver package to make sure it wasn't some other update causing the problem.
Yes, there is an issue with if if you don't have x2goserver-xsession installed as well. Please test https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-3596/x2goserver-4.0... from epel-testing and give feedback.
That fixes the problem - but what is the story with x2go-server-xsession? Should that be installed too?
And now I'm back to not working again... I updated the windows client (although since the latest download always has the same name it's not obvious if it changed) and have done yum updates on the Centos 7 side. How are you supposed to debug the scenario where you connect, the new window flashes open momentarily, then closes and the other window just says 'session terminated' - and even that part goes away too quickly to see any details.
-- Les Mikesell lesmikesell@gmail.com
Look in /var/log/syslog /var/log/messages /var/log/secure, etc on yourserver. Problem I had was related to hosts.allow, had to have localhost there for ssh.
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting. Knowledgeable human assistance, not telephone trees or script readers. See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.
On Thu, 20 Nov 2014, Les Mikesell wrote:
Date: Thu, 20 Nov 2014 12:50:20 -0600 From: Les Mikesell <lesmikesell@gmail.com> To: Orion Poplawski <orion@cora.nwra.com> Cc: x2go-user <x2go-user@lists.x2go.org> Subject: Re: [X2Go-User] CentOS7/EPEL package?
On Sat, Nov 1, 2014 at 1:59 PM, Les Mikesell <lesmikesell@gmail.com> wrote:
On Sat, Nov 1, 2014 at 9:27 AM, Orion Poplawski <orion@cora.nwra.com> wrote:
On 10/31/2014 04:31 PM, Les Mikesell wrote:
Is something wrong with the x2goserver-4.0.1.18-1.el7.x86_64 package in EPEL. The CentOS7 hosts that worked with the previous version (w/MATE desktop) now just open a black window on the client that closes almost instantly. On one system I upgraded only the x2goserver package to make sure it wasn't some other update causing the problem.
Yes, there is an issue with if if you don't have x2goserver-xsession installed as well. Please test https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-3596/x2goserver-4.0... from epel-testing and give feedback.
That fixes the problem - but what is the story with x2go-server-xsession? Should that be installed too?
And now I'm back to not working again... I updated the windows client (although since the latest download always has the same name it's not obvious if it changed) and have done yum updates on the Centos 7 side. How are you supposed to debug the scenario where you connect, the new window flashes open momentarily, then closes and the other window just says 'session terminated' - and even that part goes away too quickly to see any details.
-- Les Mikesell lesmikesell@gmail.com
x2go-user mailing list x2go-user@lists.x2go.org http://lists.x2go.org/listinfo/x2go-user
On Thu, Nov 20, 2014 at 12:59 PM, Robert Dinse <nanook@eskimo.com> wrote:
Look in /var/log/syslog /var/log/messages /var/log/secure, etc on yourserver. Problem I had was related to hosts.allow, had to have localhost there for ssh.
ssh works fine on its own, the session looks like it starts, but I can't see a reason that it terminates immediately:
Nov 20 12:47:17 c7 /usr/bin/x2gostartagent: successfully started X2Go agent session with ID les-78-1416509234_stDMATE_dp32 Nov 20 12:47:19 c7 /usr/bin/x2gosetkeyboard: Setting X keyboard according to /home/les/.x2go/C-les-78-1416509234_stDMATE_dp32/keyboard Nov 20 12:47:19 c7 /usr/bin/x2goruncommand: launching session with Xsession-x2go mechanism, using STARTUP="mate-session" Nov 20 12:47:31 c7 systemd-logind: Removed session 11642.
Hmmm..., doing 'yum remove x2goserver-xsession' seems to have fixed it. I had added that package due to the recommendation earlier in this thread.
-- Les Mikesell lesmikesell@gmail.com
The thing is, unless I'm confusing with freenx, which is possible, sshis invoked twice, once from the remote host and then again through the localhost loopback. So ssh to the host initially can succeed, if allowed from the remote IP, then fail, if disallowed from localhost. But I may be confusing with freenx, I've got both on all my servers.
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting. Knowledgeable human assistance, not telephone trees or script readers. See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.
On Thu, 20 Nov 2014, Les Mikesell wrote:
Date: Thu, 20 Nov 2014 13:17:34 -0600 From: Les Mikesell <lesmikesell@gmail.com> To: Robert Dinse <nanook@eskimo.com> Cc: Orion Poplawski <orion@cora.nwra.com>, x2go-user <x2go-user@lists.x2go.org> Subject: Re: [X2Go-User] CentOS7/EPEL package?
On Thu, Nov 20, 2014 at 12:59 PM, Robert Dinse <nanook@eskimo.com> wrote:
Look in /var/log/syslog /var/log/messages /var/log/secure, etc on yourserver. Problem I had was related to hosts.allow, had to have localhost there for ssh.
ssh works fine on its own, the session looks like it starts, but I can't see a reason that it terminates immediately:
Nov 20 12:47:17 c7 /usr/bin/x2gostartagent: successfully started X2Go agent session with ID les-78-1416509234_stDMATE_dp32 Nov 20 12:47:19 c7 /usr/bin/x2gosetkeyboard: Setting X keyboard according to /home/les/.x2go/C-les-78-1416509234_stDMATE_dp32/keyboard Nov 20 12:47:19 c7 /usr/bin/x2goruncommand: launching session with Xsession-x2go mechanism, using STARTUP="mate-session" Nov 20 12:47:31 c7 systemd-logind: Removed session 11642.
Hmmm..., doing 'yum remove x2goserver-xsession' seems to have fixed it. I had added that package due to the recommendation earlier in this thread.
-- Les Mikesell lesmikesell@gmail.com
-
Les Mikesell -
Mike Gabriel -
Orion Poplawski -
Robert Dinse -
Roderick Johnstone