We have been using x2go fairly successful on CentOS6 machines now for a while. We are investigating upgrading to CentOS7 and I am now looking at the x2go situation
We get our x2go RPMS from EPEL
x2goagent-3.5.0.31-1.el7.x86_64 x2goclient-4.0.3.1-1.el7.x86_64 x2goserver-4.0.1.19-3.el7.x86_64 x2godesktopsharing-3.1.1.1-1.el7.x86_64
So far we have not discovered
doesn't work at all with GNOME desktop giving the "Oops" screen. Web search seems to imply this is a known issue with GNOME3 with no real solution though I am suprised this is not mentioned in the X2Go wiki FAQ. I hate GNOME3 anyway so can live without it for X2Go
works partially with the KDE desktop. There is the kscreen issue that is mentioned in the FAQ. Really unusable unless one does disable kscreen. Need to investigate further what consequences that has on normal logins.
installed MATE from EPEL. On first login it looks and works great but when you "Logout ..." to terminate the session it just hangs on a blank background. If you "suspend" the session via force closing the window and then try to reconnect it fails or just takes you right back to the blank background. One can force terminate the session with x2goterminate-session to clear it out and then get a clean login again, but I don't really want my users having to go though this.
So my question is really about the MATE issue which I would prefer to use. Anyone have any clues as to what might be going on or a fix?
Paul Raines http://help.nmr.mgh.harvard.edu MGH/MIT/HMS Athinoula A. Martinos Center for Biomedical Imaging 149 (2301) 13th Street Charlestown, MA 02129 USA
The information in this e-mail is intended only for the person to whom it is addressed. If you believe this e-mail was sent to you in error and the e-mail contains patient information, please contact the Partners Compliance HelpLine at http://www.partners.org/complianceline . If the e-mail was sent to you in error but does not contain patient information, please contact the sender and properly dispose of the e-mail.
Am 05.08.2015 um 19:54 schrieb Paul Raines:
So far we have not discovered
- doesn't work at all with GNOME desktop giving the "Oops" screen. Web search seems to imply this is a known issue with GNOME3 with no real solution though I am suprised this is not mentioned in the X2Go wiki FAQ.
Um? First hit when you type "Gnome" in the wiki's search bar is
http://wiki.x2go.org/doku.php/doc:de-compat?s[]=gnome
And subsection http://wiki.x2go.org/doku.php/doc:de-compat?s[]=gnome#compatibility_and_workarounds_depend_on_what_version explains which versions of Gnome X2Go is compatible with.
Where were you looking for the information?
Kind Regards, Stefan
-- BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243
Thanks
I was looking at
http://wiki.x2go.org/doku.php/doc:faq:start
-- Paul Raines (http://help.nmr.mgh.harvard.edu)
On Wed, 5 Aug 2015 2:31pm, Stefan Baur wrote:
Am 05.08.2015 um 19:54 schrieb Paul Raines:
So far we have not discovered
- doesn't work at all with GNOME desktop giving the "Oops" screen. Web search seems to imply this is a known issue with GNOME3 with no real solution though I am suprised this is not mentioned in the X2Go wiki FAQ.
Um? First hit when you type "Gnome" in the wiki's search bar is
http://wiki.x2go.org/doku.php/doc:de-compat?s[]=gnome
And subsection http://wiki.x2go.org/doku.php/doc:de-compat?s[]=gnome#compatibility_and_workarounds_depend_on_what_version explains which versions of Gnome X2Go is compatible with.
Where were you looking for the information?
Kind Regards, Stefan
-- BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243
The information in this e-mail is intended only for the person to whom it is addressed. If you believe this e-mail was sent to you in error and the e-mail contains patient information, please contact the Partners Compliance HelpLine at http://www.partners.org/complianceline . If the e-mail was sent to you in error but does not contain patient information, please contact the sender and properly dispose of the e-mail.
On Wed, 5 Aug 2015, Paul Raines wrote:
We have been using x2go fairly successful on CentOS6 machines now for a while. We are investigating upgrading to CentOS7 and I am now looking at the x2go situation
We get our x2go RPMS from EPEL
x2goagent-3.5.0.31-1.el7.x86_64 x2goclient-4.0.3.1-1.el7.x86_64 x2goserver-4.0.1.19-3.el7.x86_64 x2godesktopsharing-3.1.1.1-1.el7.x86_64
So far we have not discovered
doesn't work at all with GNOME desktop giving the "Oops" screen. Web search seems to imply this is a known issue with GNOME3 with no real solution though I am suprised this is not mentioned in the X2Go wiki FAQ. I hate GNOME3 anyway so can live without it for X2Go
works partially with the KDE desktop. There is the kscreen issue that is mentioned in the FAQ. Really unusable unless one does disable kscreen. Need to investigate further what consequences that has on normal logins.
installed MATE from EPEL. On first login it looks and works great but when you "Logout ..." to terminate the session it just hangs on a blank background. If you "suspend" the session via force closing the window and then try to reconnect it fails or just takes you right back to the blank background. One can force terminate the session with x2goterminate-session to clear it out and then get a clean login again, but I don't really want my users having to go though this.
So my question is really about the MATE issue which I would prefer to use. Anyone have any clues as to what might be going on or a fix?
I'm not sure if it's Mate or X2Go but when I first installed both X2Go and
Mate on CentOS7 and tested, all was good.
Now it's broken for me also but somewhat differently. When I logout it
just hangs with the background image that I used on my desktop. So I use control-alt-M to and then click on the white seal or whatever that animal is, and then when I get the start-up screen back, I select terminate to terminate the session.
Now I tried the same thing on Scientific Linux 7, which like Centos7 is
derived from Enterprise Linux 7, and it still works correctly, so whatever is broken isn't X2Go or Mate, but rather something specific to CentOS 7.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
Am 05.08.2015 um 20:35 schrieb Robert Dinse:
I'm not sure if it's Mate or X2Go but when I first installed both X2Go and Mate on CentOS7 and tested, all was good.
Now it's broken for me also but somewhat differently. When I logout it just hangs with the background image that I used on my desktop. So I use control-alt-M to and then click on the white seal or whatever that animal is, and then when I get the start-up screen back, I select terminate to terminate the session.
Now I tried the same thing on Scientific Linux 7, which like Centos7 is derived from Enterprise Linux 7, and it still works correctly, so whatever is broken isn't X2Go or Mate, but rather something specific to CentOS 7.
Robert, I think this is an issue that you should raise over on X2Go-Dev, or file a bug for it. Even if CentOS is at fault, it's more likely to catch the attention of the developers "over there", and reporting it as a bug makes sure it doesn't get lost as time goes on.
BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2
iQEcBAEBCAAGBQJVwlqCAAoJEG7d9BjNvlEZTvUH/1hT914BEV7IHSiqcDXyAMZ1 oD2RzXzjF567bdXWTxki6pTuHH8JCuJyMbE1UvjvCCO5gXvtVi/lfk/c5FAO5LVV BzJirsnKkp7MV5tEbfbNdSH860XdtHIynvDFwMNHgmLJGTstLA8rrcqQosgPA9dy 6hLLY/RRGz2DDgYBzdo1tF/OoJxw8E/YL6StM6LyUBqkIXvWk2jijN8b7shX9WOY c3fq4QxrgJ84Qcv+7hX80DSb0YrT8SILZwxaDSNNTzCKk1bR8j4N/Qob5Rd/l/R+ 2shgn55p8XXjfUHE4SaQpv7yQbj2LIH1zkWR2+gRZFhNLGwkPtpTgaQDiZbtB2k= =XMkf -----END PGP SIGNATURE-----
Doing Ctrl-Alt-T to terminate in the windows client will make the windows close but doesn't clean up the session on the server. Reconnecting still just connects you to a empty background screen.
Doing a logout on the MATE desktop locally works just fine.
I am testing on pretty freshly installed and updated server and on a new user where I first wiped out all settings by removing all dot files/directories
This is what is still running on the server as the user after trying to logout over X2Go
applet.py───{applet.py}
at-spi-bus-laun─┬─dbus-daemon └─3*[{at-spi-bus-laun}]
at-spi2-registr───{at-spi2-registr}
dbus-daemon
dbus-launch
dconf-service───2*[{dconf-service}]
goa-daemon───3*[{goa-daemon}]
goa-identity-se───2*[{goa-identity-se}]
gvfs-afc-volume───2*[{gvfs-afc-volume}]
gvfs-goa-volume───{gvfs-goa-volume}
gvfs-gphoto2-vo───{gvfs-gphoto2-vo}
gvfs-mtp-volume───{gvfs-mtp-volume}
gvfs-udisks2-vo───2*[{gvfs-udisks2-vo}]
gvfsd───{gvfsd}
gvfsd-fuse───4*[{gvfsd-fuse}]
gvfsd-metadata───{gvfsd-metadata}
gvfsd-trash───3*[{gvfsd-trash}]
mate-screensave───3*[{mate-screensave}]
mate-volume-con───{mate-volume-con}
nm-applet───2*[{nm-applet}]
polkit-mate-aut───{polkit-mate-aut}
pulseaudio───{pulseaudio}
x2goagent
x2goruncommand
-- Paul Raines (http://help.nmr.mgh.harvard.edu)
On Wed, 5 Aug 2015 2:35pm, Robert Dinse wrote:
On Wed, 5 Aug 2015, Paul Raines wrote:
We have been using x2go fairly successful on CentOS6 machines now for a while. We are investigating upgrading to CentOS7 and I am now looking at the x2go situation
We get our x2go RPMS from EPEL
x2goagent-3.5.0.31-1.el7.x86_64 x2goclient-4.0.3.1-1.el7.x86_64 x2goserver-4.0.1.19-3.el7.x86_64 x2godesktopsharing-3.1.1.1-1.el7.x86_64
So far we have not discovered
doesn't work at all with GNOME desktop giving the "Oops" screen. Web search seems to imply this is a known issue with GNOME3 with no real solution though I am suprised this is not mentioned in the X2Go wiki FAQ. I hate GNOME3 anyway so can live without it for X2Go
works partially with the KDE desktop. There is the kscreen issue that is mentioned in the FAQ. Really unusable unless one does disable kscreen. Need to investigate further what consequences that has on normal logins.
installed MATE from EPEL. On first login it looks and works great but when you "Logout ..." to terminate the session it just hangs on a blank background. If you "suspend" the session via force closing the window and then try to reconnect it fails or just takes you right back to the blank background. One can force terminate the session with x2goterminate-session to clear it out and then get a clean login again, but I don't really want my users having to go though this.
So my question is really about the MATE issue which I would prefer to use. Anyone have any clues as to what might be going on or a fix?
I'm not sure if it's Mate or X2Go but when I first installed both X2Go
and Mate on CentOS7 and tested, all was good.
Now it's broken for me also but somewhat differently. When I logout it
just hangs with the background image that I used on my desktop. So I use control-alt-M to and then click on the white seal or whatever that animal is, and then when I get the start-up screen back, I select terminate to terminate the session.
Now I tried the same thing on Scientific Linux 7, which like Centos7 is
derived from Enterprise Linux 7, and it still works correctly, so whatever is broken isn't X2Go or Mate, but rather something specific to CentOS 7.
The information in this e-mail is intended only for the person to whom it is addressed. If you believe this e-mail was sent to you in error and the e-mail contains patient information, please contact the Partners Compliance HelpLine at http://www.partners.org/complianceline . If the e-mail was sent to you in error but does not contain patient information, please contact the sender and properly dispose of the e-mail.
On Wed, 5 Aug 2015, Paul Raines wrote:
Doing Ctrl-Alt-T to terminate in the windows client will make the windows close but doesn't clean up the session on the server. Reconnecting still just connects you to a empty background screen.
Instead of reconnecting, select the session and Terminate it, then
select a new session.
That is the work-around that works for me. I've filed a bug report on
this so hopefully it will be resolved. I have verified that exactly the same version of x2go and exactly the same version of Mate exists on both my SL7 and Centos7 servers and that conf files are the same, yet it works on SL7 but not Centos7, even though both are derived from EL7.
Oddly Remmina with the NX plugin works properly with Centos7 even though
X2Go does not.
I am never given the list of sessions to have the option to terminate it before reconnecting. Only running x2goterminate-session as root seems to be able to clear it. Or a reboot.
-- Paul Raines (http://help.nmr.mgh.harvard.edu)
On Wed, 5 Aug 2015 4:32pm, Robert Dinse wrote:
On Wed, 5 Aug 2015, Paul Raines wrote:
Doing Ctrl-Alt-T to terminate in the windows client will make the windows close but doesn't clean up the session on the server. Reconnecting still just connects you to a empty background screen.
Instead of reconnecting, select the session and Terminate it, then
select a new session.
That is the work-around that works for me. I've filed a bug report on
this so hopefully it will be resolved. I have verified that exactly the same version of x2go and exactly the same version of Mate exists on both my SL7 and Centos7 servers and that conf files are the same, yet it works on SL7 but not Centos7, even though both are derived from EL7.
Oddly Remmina with the NX plugin works properly with Centos7 even though
X2Go does not.
The information in this e-mail is intended only for the person to whom it is addressed. If you believe this e-mail was sent to you in error and the e-mail contains patient information, please contact the Partners Compliance HelpLine at http://www.partners.org/complianceline . If the e-mail was sent to you in error but does not contain patient information, please contact the sender and properly dispose of the e-mail.
Odd, if I bring up the original login screen it shows the 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.
On Wed, 5 Aug 2015, Paul Raines wrote:
Date: Wed, 5 Aug 2015 16:49:19 -0400 (EDT) From: Paul Raines <raines@nmr.mgh.harvard.edu> To: Robert Dinse <nanook@eskimo.com> Cc: "x2go-user@lists.x2go.org" <x2go-user@lists.x2go.org> Subject: Re: [X2Go-User] x2go on RHEL7/CentOS7
I am never given the list of sessions to have the option to terminate it before reconnecting. Only running x2goterminate-session as root seems to be able to clear it. Or a reboot.
-- Paul Raines (http://help.nmr.mgh.harvard.edu)
On Wed, 5 Aug 2015 4:32pm, Robert Dinse wrote:
On Wed, 5 Aug 2015, Paul Raines wrote:
Doing Ctrl-Alt-T to terminate in the windows client will make the windows close but doesn't clean up the session on the server. Reconnecting still just connects you to a empty background screen.
Instead of reconnecting, select the session and Terminate it, then
select a new session.
That is the work-around that works for me. I've filed a bug report on
this so hopefully it will be resolved. I have verified that exactly the same version of x2go and exactly the same version of Mate exists on both my SL7 and Centos7 servers and that conf files are the same, yet it works on SL7 but not Centos7, even though both are derived from EL7.
Oddly Remmina with the NX plugin works properly with Centos7 even
though X2Go does not.
The information in this e-mail is intended only for the person to whom it is addressed. If you believe this e-mail was sent to you in error and the e-mail contains patient information, please contact the Partners Compliance HelpLine at http://www.partners.org/complianceline . If the e-mail was sent to you in error but does not contain patient information, please contact the sender and properly dispose of the e-mail.
Oh, you mean instead of doing Ctrl-Alt-T I should go to the main X2Go client window and click the Terminate button in the bottom right of the dialog in the left hand pane. Yes, that does seem to clean it up correctly.
I don't understand why there is a difference between doing that and doing Ctrl-Alt-T
-- Paul Raines (http://help.nmr.mgh.harvard.edu)
On Wed, 5 Aug 2015 4:51pm, Robert Dinse wrote:
Odd, if I bring up the original login screen it shows the 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.
On Wed, 5 Aug 2015, Paul Raines wrote:
Date: Wed, 5 Aug 2015 16:49:19 -0400 (EDT) From: Paul Raines <raines@nmr.mgh.harvard.edu> To: Robert Dinse <nanook@eskimo.com> Cc: "x2go-user@lists.x2go.org" <x2go-user@lists.x2go.org> Subject: Re: [X2Go-User] x2go on RHEL7/CentOS7
I am never given the list of sessions to have the option to terminate it before reconnecting. Only running x2goterminate-session as root seems to be able to clear it. Or a reboot.
-- Paul Raines (http://help.nmr.mgh.harvard.edu)
On Wed, 5 Aug 2015 4:32pm, Robert Dinse wrote:
On Wed, 5 Aug 2015, Paul Raines wrote:
Doing Ctrl-Alt-T to terminate in the windows client will make the windows close but doesn't clean up the session on the server. Reconnecting still just connects you to a empty background screen.
Instead of reconnecting, select the session and Terminate it, then
select a new session.
That is the work-around that works for me. I've filed a bug report
on this so hopefully it will be resolved. I have verified that exactly the same version of x2go and exactly the same version of Mate exists on both my SL7 and Centos7 servers and that conf files are the same, yet it works on SL7 but not Centos7, even though both are derived from EL7.
Oddly Remmina with the NX plugin works properly with Centos7 even
though X2Go does not.
The information in this e-mail is intended only for the person to whom it is addressed. If you believe this e-mail was sent to you in error and the e-mail contains patient information, please contact the Partners Compliance HelpLine at http: //www.partners.org/complianceline . If the e-mail was sent to you in error but does not contain patient information, please contact the sender and properly dispose of the e-mail.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
Am 05.08.2015 um 22:58 schrieb Paul Raines:
I don't understand why there is a difference between doing that and doing Ctrl-Alt-T
IIRC, there's something broken with that, but I don't remember the details. Might be related to Bug 510. http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=510
BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2
iQEcBAEBCAAGBQJVwnmyAAoJEG7d9BjNvlEZn1wH/2rOOkgddOpJ3Oq59/Jyb9KU bWgh9tKbsdj39S/UPKGcp7RqDKq3WwXsRsnlKVHrhkk1sSlwgucfFDglEv1tAj19 xanTmgFWgnLcGziEere0BW8BC8FbxJZJj42a+e3waPn23r/2GeZljQ1CeqoeqaMp bRyU4FNt7o/P5xsAuVQlCDiARskdzV4w4SkJWUvGAxMVi9n/5mTEllIZuagzFVo3 CibYnAMpseuy5WtKOcv5wy9jj2Rfg7hxWDzZkxazMeDoSHlChy1Mw4sWP5F8TjvE O3lS705sviNnyYPGtNPHOP6qAMlETLxtsgrVYzqJnyPOyRwF3wx4wEDp4H9gEuA= =hwwC -----END PGP SIGNATURE-----
Yes, neither do I just know that experimentally I found that works.
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- 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 Wed, 5 Aug 2015, Paul Raines wrote:
Date: Wed, 5 Aug 2015 16:58:41 -0400 (EDT) From: Paul Raines <raines@nmr.mgh.harvard.edu> To: Robert Dinse <nanook@eskimo.com> Cc: "x2go-user@lists.x2go.org" <x2go-user@lists.x2go.org> Subject: Re: [X2Go-User] x2go on RHEL7/CentOS7
Oh, you mean instead of doing Ctrl-Alt-T I should go to the main X2Go client window and click the Terminate button in the bottom right of the dialog in the left hand pane. Yes, that does seem to clean it up correctly.
I don't understand why there is a difference between doing that and doing Ctrl-Alt-T
-- Paul Raines (http://help.nmr.mgh.harvard.edu)
On Wed, 5 Aug 2015 4:51pm, Robert Dinse wrote:
Odd, if I bring up the original login screen it shows the 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.
On Wed, 5 Aug 2015, Paul Raines wrote:
Date: Wed, 5 Aug 2015 16:49:19 -0400 (EDT) From: Paul Raines <raines@nmr.mgh.harvard.edu> To: Robert Dinse <nanook@eskimo.com> Cc: "x2go-user@lists.x2go.org" <x2go-user@lists.x2go.org> Subject: Re: [X2Go-User] x2go on RHEL7/CentOS7
I am never given the list of sessions to have the option to terminate it before reconnecting. Only running x2goterminate-session as root seems to be able to clear it. Or a reboot.
-- Paul Raines (http://help.nmr.mgh.harvard.edu)
On Wed, 5 Aug 2015 4:32pm, Robert Dinse wrote:
> Doing Ctrl-Alt-T to terminate in the windows client will make
On Wed, 5 Aug 2015, Paul Raines wrote: the > > windows close but doesn't clean up the session on the server. Reconnecting still just connects you to a empty background screen. Instead of reconnecting, select the session and Terminate it, then select a new session. That is the work-around that works for me. I've filed a bug report > on this so hopefully it will be resolved. I have verified that exactly the > same version of x2go and exactly the same version of Mate exists on both my SL7 and Centos7 servers and that conf files are the same, yet it works on SL7 but not Centos7, even though both are derived from EL7. Oddly Remmina with the NX plugin works properly with Centos7 even though X2Go does not.
>
The information in this e-mail is intended only for the person to whom it is addressed. If you believe this e-mail was sent to you in error and the e-mail contains patient information, please contact the Partners Compliance HelpLine at http: //www.partners.org/complianceline . If the e-mail was sent to you in error but does not contain patient information, please contact the sender and properly dispose of the e-mail.
Forwarding this to the bug reported by Robert Dinse, in case it is of help there.
-------- Weitergeleitete Nachricht -------- Betreff: Re: [X2Go-User] x2go on RHEL7/CentOS7 Datum: Wed, 5 Aug 2015 15:54:30 -0400 (EDT) Von: Paul Raines <raines@nmr.mgh.harvard.edu> An: Robert Dinse <nanook@eskimo.com> Kopie (CC): x2go-user@lists.x2go.org
Doing Ctrl-Alt-T to terminate in the windows client will make the windows close but doesn't clean up the session on the server. Reconnecting still just connects you to a empty background screen.
Doing a logout on the MATE desktop locally works just fine.
I am testing on pretty freshly installed and updated server and on a new user where I first wiped out all settings by removing all dot files/directories
This is what is still running on the server as the user after trying to logout over X2Go
applet.py{applet.py}
at-spi-bus-laundbus-daemon 3*[{at-spi-bus-laun}]
at-spi2-registr{at-spi2-registr}
dbus-daemon
dbus-launch
dconf-service2*[{dconf-service}]
goa-daemon3*[{goa-daemon}]
goa-identity-se2*[{goa-identity-se}]
gvfs-afc-volume2*[{gvfs-afc-volume}]
gvfs-goa-volume{gvfs-goa-volume}
gvfs-gphoto2-vo{gvfs-gphoto2-vo}
gvfs-mtp-volume{gvfs-mtp-volume}
gvfs-udisks2-vo2*[{gvfs-udisks2-vo}]
gvfsd{gvfsd}
gvfsd-fuse4*[{gvfsd-fuse}]
gvfsd-metadata{gvfsd-metadata}
gvfsd-trash3*[{gvfsd-trash}]
mate-screensave3*[{mate-screensave}]
mate-volume-con{mate-volume-con}
nm-applet2*[{nm-applet}]
polkit-mate-aut{polkit-mate-aut}
pulseaudio{pulseaudio}
x2goagent
x2goruncommand
-- Paul Raines (http://help.nmr.mgh.harvard.edu)
On Wed, 5 Aug 2015 2:35pm, Robert Dinse wrote:
On Wed, 5 Aug 2015, Paul Raines wrote:
We have been using x2go fairly successful on CentOS6 machines now for a while. We are investigating upgrading to CentOS7 and I am now looking at the x2go situation
We get our x2go RPMS from EPEL
x2goagent-3.5.0.31-1.el7.x86_64 x2goclient-4.0.3.1-1.el7.x86_64 x2goserver-4.0.1.19-3.el7.x86_64 x2godesktopsharing-3.1.1.1-1.el7.x86_64
So far we have not discovered
doesn't work at all with GNOME desktop giving the "Oops" screen. Web search seems to imply this is a known issue with GNOME3 with no real solution though I am suprised this is not mentioned in the X2Go wiki FAQ. I hate GNOME3 anyway so can live without it for X2Go
works partially with the KDE desktop. There is the kscreen issue that is mentioned in the FAQ. Really unusable unless one does disable kscreen. Need to investigate further what consequences that has on normal logins.
installed MATE from EPEL. On first login it looks and works great but when you "Logout ..." to terminate the session it just hangs on a blank background. If you "suspend" the session via force closing the window and then try to reconnect it fails or just takes you right back to the blank background. One can force terminate the session with x2goterminate-session to clear it out and then get a clean login again, but I don't really want my users having to go though this.
So my question is really about the MATE issue which I would prefer to use. Anyone have any clues as to what might be going on or a fix?
I'm not sure if it's Mate or X2Go but when I first installed both X2Go
and Mate on CentOS7 and tested, all was good.
Now it's broken for me also but somewhat differently. When I logout it
just hangs with the background image that I used on my desktop. So I use control-alt-M to and then click on the white seal or whatever that animal is, and then when I get the start-up screen back, I select terminate to terminate the session.
Now I tried the same thing on Scientific Linux 7, which like Centos7 is
derived from Enterprise Linux 7, and it still works correctly, so whatever is broken isn't X2Go or Mate, but rather something specific to CentOS 7.
The information in this e-mail is intended only for the person to whom it is addressed. If you believe this e-mail was sent to you in error and the e-mail contains patient information, please contact the Partners Compliance HelpLine at http://www.partners.org/complianceline . If the e-mail was sent to you in error but does not contain patient information, please contact the sender and properly dispose of the e-mail.