x2go-dev August 2015

x2go-dev@lists.x2go.org

25 participants
137 discussions

Bug#917: Printer command with spaces does not work
by Mikhail Gonchar 07 Aug '15

07 Aug '15

Package: x2goclient Version: 4.0.5.0 A custom printer command in x2goclient does not work when it contains spaces. I reproduced this on Debian "jessie" and Windows XP: 1) Open x2goclient settings and set printer command to value with spaces. I set it to "/home/reji/evince and spaces" on Debian (this is a simlink to /usr/bin/evince). 2) Print something in remote session to virtual X2Go printer. As result error message pop ups on the client: "Failed to execute command: /home/reji/evince and spaces /home/reji/.x2go/S-redge-52-1438889300_stDLXDE_dp32/spool/redge-52-1438889300_stDLXDE_dp32_33-redge-cupsjob7726ykoKRCRrXh30G41C.pdf" Printing works if I set a command to "/usr/bin/evince" or "evince".

1 0

Bug#916: sshd not start on Windows XP
by Mikhail Gonchar 07 Aug '15

07 Aug '15

Package: x2goclient Version: 4.0.5.0 sshd not start on Windows XP because of an error in its config file (sshd_config): StrictModes no UsePrivilegeSeparation no PidFile C:/Documents and Settings/redge/.x2go/var/sshd.pid Subsystem shell C:/PROGRA~1/X2GOCL~1/sh Subsystem sftp C:/PROGRA~1/X2GOCL~1/sftp-server AuthorizedKeysFile "/cygdrive/C/Documents and Settings/%u/.x2go/.ssh/authorized_keys" The third line (PidFile ...) contains unquoted path with spaces. As workaround one can add quotes and change config file permissions (so it won't be rewritten by x2goclient). But this can be easily fixed in src/onmainwindow.cpp on the line 9997: out<<"StrictModes no\n"<< "UsePrivilegeSeparation no\n"<< "PidFile " + varDir + "/sshd.pid\n" <<

1 0

Bug#914: X2Go Logout Issue with Mate on Centos7
by Paul Raines 06 Aug '15

06 Aug '15

Just adding that doing Ctrl-Alt-T to terminate when at the hung background screen on MATE logout does not clean up the session. However clicking the Terminate button on the X2Go client login dialog in the master window does work. So for some reason Ctrl-Alt-T is not doing the same thing as that Terminate button.

2 1

Bug#914: X2Go Logout Issue with Mate on Centos7
by Robert Dinse 06 Aug '15

06 Aug '15

Package: <x2goserver> Version: <4.0.1.19-3.el7> X2Goserver installed on a CentOS7 system with Mate desktop. When I logout, the top and bottom bars disappear but the background image remains and in this state it hangs indefinitely. If I then use alt-control-M to minimize the screen, click on the little white seal and when the initial screen comes up, terminate the session, it terminates. This behavior did not exist when I first installed Mate and X2Go server on this machine, something has changed recently. Also perhaps relevant, I have exactly the same version of x2go server and Mate installed on a Scientific Linux 7 machine and it terminates the session properly when I logout so this behavior appears to be specific to Centos 7. This is the x2goserver.conf, it is identical on both the Centos7 machine that doesn't logout properly and the scientific7 machine which does, I have not altered it from the defaults: --------------------------------------------------------------------------- [limit users] #user-foo=1 [limit groups] #bar-group=1 [security] # SSHFS umask for client-side folder sharing. Leave uncommented to keep the server's default umask #umask="0117" [log] # possible levels are: emerg, alert, crit, err, warning, notice, info, debug loglevel=notice -------------------------------------------------------------------------- I thought maybe the contents of x2go_logout.d which is a single script called 010_userscripts.sh containing: -------------------------------------------------------------------------- # call $HOME/.x2go_logout script... test -r $HOME/.x2go_logout && . $HOME/.x2go_logout -------------------------------------------------------------------------- ... might be relevant but that to is identical on both machines as are $HOME/.x2go_logout which actually is non-existent on both machines (actually home directory is identical as it is NFS mounted on both machines from a common server). The one thing that is different is the version of mate-desktop, on the broken box it's version 1.8.2-2.el7 and on the working system 1.10.1-2.el7. I upgraded the broken box to Mate 1.10.1-2.e17, the same as the working machine but logout still hangs. -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- 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.

2 1

Bug#914: Fwd: Re: [X2Go-User] x2go on RHEL7/CentOS7
by Stefan Baur 05 Aug '15

05 Aug '15

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(a)nmr.mgh.harvard.edu> An: Robert Dinse <nanook(a)eskimo.com> Kopie (CC): x2go-user(a)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 >> >> 1) 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 >> >> 2) 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. >> >> 3) 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.

1 0

Processed: your mail
by owner＠bugs.x2go.org 05 Aug '15

05 Aug '15

Processing commands for control(a)bugs.x2go.org: > reassign 914 x2goserver 4.0.1.19-3.el7 Bug #914 [<x2goserver>] X2Go Logout Issue with Mate on Centos7 Warning: Unknown package '<x2goserver>' Bug reassigned from package '<x2goserver>' to 'x2goserver'. Ignoring request to alter found versions of bug #914 to the same values previously set Ignoring request to alter fixed versions of bug #914 to the same values previously set Bug #914 [x2goserver] X2Go Logout Issue with Mate on Centos7 There is no source info for the package 'x2goserver' at version '4.0.1.19-3.el7' with architecture '' Unable to make a source version for version '4.0.1.19-3.el7' Marked as found in versions 4.0.1.19-3.el7. > End of message, stopping processing here. Please contact me if you need assistance. -- 914: http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=914 X2Go Bug Tracking System Contact owner(a)bugs.x2go.org with problems

1 0

Mac keyboard fixes
by Steve Gaarder 04 Aug '15

04 Aug '15

I installed the x2go client on a Mac, connecting to a Linux machine running x2goserver 4.0.1.19. The keyboard is totally garbled. I researched the situation. This was in the bug database as bug 112, and to fix it, these lines were added to /usr/bin/x2gostartagent in 4.0.1.8: # Mac OS keyboard issue workaround: for old/broken clients that used to call type=query and usekbd=0... if [ "$X2GO_KBD_TYPE" = "query" ]; then X2GO_SET_KBD=1 fi These lines were then removed in the fix for bug #348, with the log message: - Revert keyboard workaround for Mac OS X, as it causes other issues. In my case, if those lines are there it works, and if they aren't it doesn't. Now I expect that someday one of my users will hit #348, so I want to help fix this one properly. Can anyone provide some background info to help me get started? thanks, Steve Gaarder System Administrator, Dept of Mathematics Cornell University, Ithaca, NY, USA gaarder(a)math.cornell.edu

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

x2go-dev August 2015