x2go-user April 2014

x2go-user@lists.x2go.org

19 participants
23 discussions

Start a nNew thread

X2Go isn't working over ssh with my keyfile
by Daniela Meyer 13 Apr '14

13 Apr '14

3 2

Re: [X2Go-User] [X2Go-Announcement] X2Go Client (4.0.2.0) released
by Nigra Truo 11 Apr '14

11 Apr '14

Thanks Mike for all the hard work on the new release! It is appreciated! Markus On Thu, Apr 10, 2014 at 5:08 AM, Mike Gabriel < mike.gabriel(a)das-netzwerkteam.de> wrote: > Dear all, > > the X2Go project is proud to announce a new release of the X2Go > component ,,x2goclient''. > > New gains of this version of ,,x2goclient'' are: > > o Fully support building againt libssh 0.6.x. > o Provide solution for Google Authenticator support. > o Provide a better help window. > o Show changelog and git-log on the terminal > (new options: --changelog, --git-info). > o More improvement for the Mac OS X keyboard. > o Fix of multimonitor support on Linux. > o Use QNetworkAccessManager class for the > communicatio with a broker http(s) server. > o Allow OTP authentications against http(s) brokers > o Fix pulseaudio integration on Windows (Big thanks > to Mike#2 for the debugging effort and the communication > to pulseaudio upstream!!!) > > Above all, Mike#2 (Michael DePaulo) has been very busy on testing > and improving the MS Windows builds of X2Go Client. Thanks a lot for > this!!! You have become a highly valuable member of the X2Go developers > team. Good to have you on board!!! > > > X2Go Component: x2goclient > Version: 4.0.2.0 > Status: RELEASE > Date: Thu, 10 Apr 2014 13:47:56 +0200 > Fixes these bug report(s): 138 349 422 440 446 448 453 > Changes: > x2goclient (4.0.2.0) RELEASED; urgency=low > . > [ Oleksandr Shneyder ] > * New upstream version (4.0.2.0): > - Revrite SSH Classes to support libssh fix. > - Add Class HelpDialog to show options in scroll area. > - Fix authentication on SSH Broker with key + passphrase. > - Set modmap timer timeout to 10 sec on Mac. > - Fix running xmodmap if X2Go Client not started from terminal. > - Setting keyboard modifiers with xmodmap. > - Fix multimonitor support on Linux. > - Display more version info. Parameters --version, --git, --changelog. > - Don't show GUI dialog for --version, --help, etc, if started > from terminal on linux and mac. > - If no user in session config, display system username in pass form. > - Check if txt/changelog and txt/git exist on config phase. > Rename option "--git" to "--git-info". > - Change x2goclient.nsi for nightly builds. > . > [ Josh Lukens ] > * New upstream version (4.0.2.0): > - Switch to QNetworkAccessManager. Appropriately set content type > header to "application/x-www-form-urlencoded" for HTTP post > requests. (Fixes: #440, #138). > - Fix copy+paste errors in QNetworkAccessManager code. > - Provide support for dynamic authentication IDs. This is > a requirement for using the broker client against brokers > that use some sort of OTP authentication mechanism. > (Fixes: #446). > . > [ Mike Gabriel ] > * New upstream version (4.0.2.0): > - Drop create_text.sh again, implement changelog copying > in distro build files. Implement Git history creation for > nightly builds in build scripts. > - Rename txt/git to txt/git-info (make it compliant with cmdline > options). > - Allow starting shadow sessions from the command line with > option --hidden being enabled. (Fixes: #349). > * debian/control: > + Build-depend on libssh-dev (>= 0.5.4-2). > + Bump Standards: to 3.9.5. No changes needed. > * debian/rules: > + Copy debian/changelog into txt/ subfolder during dh_auto_configure. > + Create txt/git-info files for ChangeLog.git if it exists. > * x2goclient.spec: > + Copy ChangeLog (or debian/changelog) into txt/ subfolder during > %setup. > + Copy ChangeLog.gitlog (if present) into txt/ subfolder during > %setup. > + B-R (epel-7): man2html-core (same as for Fedora builds). > . > [ Mike DePaulo ] > * New upstream version (4.0.2.0): > - Decrease HelpDialog's tab width from 320 to 30 > (the width of 10 spaces.) (Fixes: #453) > - Windows: Fix compatibility with PulseAudio 3.0 & later through > new cookie handling. (Fixes: #422) > - Windows: Upgrade included PulseAudio from 1.1 to 5.0. > The 5.0 build is patched for X2Go bug #363. and available here: > https://build.opensuse.org/project/show/home:mikedep333: > branches:home:\ > mkbosmans:mingw32:pulseaudio > - Windows: Reapply KDE on Windows's patch for Pageant support to > libssh 0.5.5. (Fixes: #448) > > > Regards, > Mike Gabriel > > -- > > DAS-NETZWERKTEAM > mike gabriel, herweg 7, 24357 fleckeby > fon: +49 (1520) 1976 148 > > GnuPG Key ID 0x25771B31 > mail: mike.gabriel(a)das-netzwerkteam.de, http://das-netzwerkteam.de > > freeBusy: > https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das- > netzwerkteam.de.xfb > > _______________________________________________ > X2Go-Announcement mailing list > X2Go-Announcement(a)lists.berlios.de > https://lists.berlios.de/mailman/listinfo/x2go-announcement >

4 4

Re: [X2Go-User] Problem resuming the session
by Borys Saulyak 09 Apr '14

09 Apr '14

X2goserver 4.0.1.13 X2goclient 4.0.1.3 Server is running on sles11sp2 Client is on opensuse 12.2 On 9 Apr 2014 03:21, "GZ Nianguan E.T.opensource(a)gznianguan.com" <opensource(a)gznianguan.com> wrote: Hi, What client and server OS, and what is the exact version number of your client and server side packages? On 04/01/2014 05:17 PM, Borys Saulyak wrote: > Hi guys, > > > I have quite often a problem to resume a session that was suspended after unexpected disconnect of the client. > In most of the cases it does not work. > > On the client side I get this: > Loop: WARNING! Unrecognized session type 'unix-kde-depth_24'. Assuming agent session. > Loop: WARNING! Unrecognized session type 'unix-kde-depth_24'. Assuming agent session. > Loop: PANIC! The remote NX proxy closed the connection. > Loop: PANIC! Failure negotiating the session in stage '7'. > Loop: PANIC! Wrong version or invalid session authentication cookie. > Loop: PANIC! The remote NX proxy closed the connection. > Loop: PANIC! Failure negotiating the session in stage '7'. > Loop: PANIC! Wrong version or invalid session authentication cookie. > Loop: WARNING! Unrecognized session type 'unix-kde-depth_24'. Assuming agent session. > Loop: WARNING! Unrecognized session type 'unix-kde-depth_24'. Assuming agent session. > Loop: PANIC! The remote NX proxy closed the connection. > > > On the server side I see this: > Apr 1 07:09:00 xxx /usr/local/bin/x2gosetkeyboard: Setting X keyboard according to /home/dadfmg/.x2go/C-dadfmg-77-1396335925_stDKDE_dp24/keyboard > Apr 1 07:11:32 xxx sshd[9739]: Accepted keyboard-interactive/pam for dadfmg from 10.10.1.13 port 59401 ssh2 > Apr 1 07:11:34 xxx /usr/local/bin/x2gosuspend-session: session with ID dadfmg-77-1396335925_stDKDE_dp24 has been suspended successfully > Apr 1 07:11:36 xxx /usr/local/bin/x2goresume-session: client 10.10.1.13 has successfully resumed session with ID dadfmg-77-1396335925_stDKDE_dp24 > Apr 1 07:11:36 xxx sshd[9742]: error: connect_to localhost port 30081: failed. > Apr 1 07:11:36 xxx sshd[9742]: channel_by_id: 0: bad id: channel free > Apr 1 07:11:36 xxx sshd[9742]: Disconnecting: Received ieof for nonexistent channel 0. > > I am on the latest version of client/server. > > I also noticed that I can achieve the same result if I suspend the session and then try to resume it by login in to the server via ssh and executing x2goresume-session <sessionid> > In this case even healthy and cleanly suspended session get screwed. > So far I was not able to figure out how can I get the session back. It just does not work. I found a workaround for the time being which is to connect via local desktop (desktop sharing). This works even if session is screwed, but this is not what I want. I would like to get my session resumed correctly no matter what happened. Is this a known bug? Or is it only happening to me? I would really appreciate any help! X2GO is a great project and it has a great potential! > > Thanks in advance for any help! > _______________________________________________ X2Go-User mailing list X2Go-User(a)lists.berlios.de https://lists.berlios.de/mailman/listinfo/x2go-user

1 0

Problem resuming the session
by Borys Saulyak 09 Apr '14

09 Apr '14

Hi guys, I have quite often a problem to resume a session that was suspended after unexpected disconnect of the client. In most of the cases it does not work. On the client side I get this: Loop: WARNING! Unrecognized session type 'unix-kde-depth_24'. Assuming agent session. Loop: WARNING! Unrecognized session type 'unix-kde-depth_24'. Assuming agent session. Loop: PANIC! The remote NX proxy closed the connection. Loop: PANIC! Failure negotiating the session in stage '7'. Loop: PANIC! Wrong version or invalid session authentication cookie. Loop: PANIC! The remote NX proxy closed the connection. Loop: PANIC! Failure negotiating the session in stage '7'. Loop: PANIC! Wrong version or invalid session authentication cookie. Loop: WARNING! Unrecognized session type 'unix-kde-depth_24'. Assuming agent session. Loop: WARNING! Unrecognized session type 'unix-kde-depth_24'. Assuming agent session. Loop: PANIC! The remote NX proxy closed the connection. On the server side I see this: Apr 1 07:09:00 xxx /usr/local/bin/x2gosetkeyboard: Setting X keyboard according to /home/dadfmg/.x2go/C-dadfmg-77-1396335925_stDKDE_dp24/keyboard Apr 1 07:11:32 xxx sshd[9739]: Accepted keyboard-interactive/pam for dadfmg from 10.10.1.13 port 59401 ssh2 Apr 1 07:11:34 xxx /usr/local/bin/x2gosuspend-session: session with ID dadfmg-77-1396335925_stDKDE_dp24 has been suspended successfully Apr 1 07:11:36 xxx /usr/local/bin/x2goresume-session: client 10.10.1.13 has successfully resumed session with ID dadfmg-77-1396335925_stDKDE_dp24 Apr 1 07:11:36 xxx sshd[9742]: error: connect_to localhost port 30081: failed. Apr 1 07:11:36 xxx sshd[9742]: channel_by_id: 0: bad id: channel free Apr 1 07:11:36 xxx sshd[9742]: Disconnecting: Received ieof for nonexistent channel 0. I am on the latest version of client/server. I also noticed that I can achieve the same result if I suspend the session and then try to resume it by login in to the server via ssh and executing x2goresume-session <sessionid> In this case even healthy and cleanly suspended session get screwed. So far I was not able to figure out how can I get the session back. It just does not work. I found a workaround for the time being which is to connect via local desktop (desktop sharing). This works even if session is screwed, but this is not what I want. I would like to get my session resumed correctly no matter what happened. Is this a known bug? Or is it only happening to me? I would really appreciate any help! X2GO is a great project and it has a great potential! Thanks in advance for any help!

3 3

Re: [X2Go-User] Problem resuming the session
by Borys Saulyak 08 Apr '14

08 Apr '14

Thanks Mike. On 8 Apr 2014 22:04, Mike Gabriel <mike.gabriel(a)das-netzwerkteam.de> wrote: Hi Borys, On Di 08 Apr 2014 13:55:10 CEST, Borys Saulyak wrote: > Is there any chance that somebody will have a look at this problem? > I cannot resume the sessions in 50% of the times. It is almost > unusable. I added the info how to reproduce to the #302. I'll see what I can do during the next two weeks. Stay tuned... Mike -- DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976 148 GnuPG Key ID 0x25771B31 mail: mike.gabriel(a)das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.x…

1 0

X2Go Ubuntu upgrade stuck at "Cleaning up stale X2Go sessions"
by Jason Heeris 03 Apr '14

03 Apr '14

Hi, I'm using X2Go (4.0.1.14-0~842~ubuntu13.10.1) on Ubuntu 13.10. I let Ubuntu's update manager upgrade the package yesterday, and it got stuck at: * Cleaning up stale X2Go sessions. I killed the upgrade process, rebooted and ran "sudo dpkg --configure -a", and once again, it's stuck at the same point. Is there anything I can do manually to let the update proceed past this point? — Jason Heeris

2 1

Re: [X2Go-User] [X2Go-Dev] Bug#471: Bug#471: ATTENTION @Mike#1 - serious bug in x2goserver upgrade script (debian wheezy+squeeze)
by Stefan Baur 03 Apr '14

03 Apr '14

Further Info: 1) I'm guessing it's a race condition, with two instances of x2gocleansessions running simpultaneously and locking each other up: e.g. sample output: ps ax|grep clean 1995 ? S 0:36 /usr/bin/perl /usr/sbin/x2gocleansessions 16142 pts/0 S+ 0:05 /usr/bin/perl /usr/sbin/x2gocleansessions 2) The kill command given below in my previous e-mail doesn't work. What worked was this: ps ax | grep x2gocleansessions | grep perl \ | awk ' { print $1 }' | xargs -n 1 kill (the backslash is so it can be broken up in two lines) You have to run this in a second terminal session (as root) while the apt-get upgrade process is stuck in the first. It will then continue without reporting an error. -Stefan Am 03.04.2014 09:52, schrieb Stefan Baur: > Gah. E_NOTENOUGHCAFFEINE. This was supposed to go to the list and > bugtracker as well. > > > -------- Original-Nachricht -------- > Betreff: Re: [X2Go-Dev] Bug#471: ATTENTION @Mike#1 - serious bug in > x2goserver upgrade script (debian wheezy+squeeze) > Datum: Thu, 03 Apr 2014 09:50:09 +0200 > Von: Stefan Baur <newsgroups.mail2(a)stefanbaur.de> > Antwort an: Stefan Baur <newsgroups.mail2(a)stefanbaur.de>, > 471(a)bugs.x2go.org, x2go-dev(a)lists.berlios.de > An: Mike Gabriel <mike.gabriel(a)das-netzwerkteam.de> > > Addendum: > > This is part of the "ps ax" output on one of the affected machines: > > 2563 pts/2 S+ 0:00 apt-get upgrade -y > 4958 pts/1 S+ 0:00 /usr/bin/perl -w /usr/share/debconf/frontend > /var/lib/dpkg/info/x2goserver.postinst configure 4.0.1.13-0x2go1+ > 4962 pts/1 Z+ 0:00 [x2goserver.post] <defunct> > 5004 pts/1 S+ 0:00 /usr/bin/perl /usr/sbin/x2gocleansessions > > manually killing x2gocleansessions (" kill $(pidof x2gocleansessions)") > seems to be a workaround, but still, we need a real fix in the form of > an updated package. > > -Stefan > > Am 03.04.2014 08:47, schrieb Stefan Baur: >> Package: x2goserver >> Severity: grave >> Version: 4.0.1.14 >> >> Hi Mike, >> >> this is happening on >> >> x2goserver (4.0.1.14-0x2go1+git20140402.842+squeeze.main.1) >> >> as well. >> >> Please help! All my machines are stuck in the upgrade process! This is >> not good! >> >> -Stefan >> >> >> -------- Original-Nachricht -------- >> Betreff: [X2Go-User] Unable to upgrade >> Datum: Wed, 2 Apr 2014 19:14:53 +0300 >> Von: Panayotis Katsaloulis <panayotis(a)panayotis.com> >> An: x2go-user(a)lists.berlios.de >> >> Hello all! >> >> I have installed x2go, I can connect - everything is fine. >> In the past I think there was a problem when I tried to launch a client >> (as xterm session), and which I was unable to properly close, so I >> forced close it. >> >> The problem is that I am unable to upgrade through apt-get upgrade though. >> >> Now when I try to upgrade I get this message: >> >> Processing triggers for menu (2.1.46) ... >> Setting up x2goserver (4.0.1.14-0x2go1+git20140402.842+wheezy.main.1) ... >> Group x2gouser already exists. >> User x2gouser already exists. >> [info] Cleaning up stale X2Go sessions.. >> >> … and the screen remains like this forever. >> >> The uname -a command produces the following result: >> >> Linux danube 3.13-1-amd64 #1 SMP Debian 3.13.7-1 (2014-03-25) x86_64 >> GNU/Linux >> >> Any help? >> >> -- >> Panayotis >> >> >> _______________________________________________ >> X2Go-User mailing list >> X2Go-User(a)lists.berlios.de >> https://lists.berlios.de/mailman/listinfo/x2go-user >> _______________________________________________ >> X2Go-Dev mailing list >> X2Go-Dev(a)lists.berlios.de >> https://lists.berlios.de/mailman/listinfo/x2go-dev >> > _______________________________________________ > X2Go-Dev mailing list > X2Go-Dev(a)lists.berlios.de > https://lists.berlios.de/mailman/listinfo/x2go-dev >

4 5

Re: [X2Go-User] X2Go-User Digest, Vol 44, Issue 2
by Nigra Truo 03 Apr '14

03 Apr '14

> > Message: 4 > Date: Tue, 01 Apr 2014 16:18:39 +0200 > From: "GZ Nianguan E.T." <opensource(a)gznianguan.com> > To: x2go-user(a)lists.berlios.de > Subject: Re: [X2Go-User] X2Go-User Digest, Vol 43, Issue 24 > Message-ID: <lhehs0$815$1(a)ger.gmane.org> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > Hi, > > I cant remember ever having to start something on the local display... > Just make sure you log in with the same user on X2Go and you are logged > in with on the local display.... > > In the X2Go connection settings, under "Session Type" select "Connect > to local desktop" then when you log in you should see a list of local > displays you can connect to... at least you should see one (:0) if > there is a local X running.. Oh, thanks! I did not even see that setting and it does work, I just tried it. But it is always read only in my case, I cannot click on anything or move windows, even if I set full access. Markus

2 1

Re: [X2Go-User] Unable to upgrade
by Andreas Yankopolus 03 Apr '14

03 Apr '14

I'm having the same problem on my Ubuntu 13.10 system. $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 13.10 Release: 13.10 Codename: saucy $ uname -a Linux phobos 3.11.0-19-generic #33-Ubuntu SMP Tue Mar 11 18:48:34 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

2 2

Printing on RHEL 6.5 Server
by Eric Work 03 Apr '14

03 Apr '14

I'm trying to print from a RHEL 6.5 server running both x2goserver and cups to a Fedora 20 client. Both are running x2go 4.0.1.3. I have installed the x2goserver-printing and cups-x2go packages for RHEL. I have added the virtual printer to the cups server. On the client I have setup printing to show the dialog and start evince to view the PDF. When I attempt to print something, select the virtual printer, then click print, nothing happens. I see a pdf file in the cups spool directory but nothing in the client spool directory. When I attempt to manually copy the pdf file to this directory nothing happens. Maybe this is expected. I see from strace that x2goclient is reading the contents of the client spool directory and the number of files changes but it doesn't do anything. Is there something related to fuse and sshfs that prevents the cups/x2goserver processes from copying over the generated PDF? Is copying the file to the client spool directory not enough? Is there some other sort of signal passed from the server to the client to initiate printing? Below are the log messages I get when I try to print, which doesn't seem to have any clear error messages. Apr 2 22:33:31 XXX /usr/lib/cups/backend/cups-x2go[6070]: Print job received from cups -> 5 YYY Google 1 Resolution=300dpi number-up=1 PageSize=Letter job-uuid=urn:uuid:c5c9e233-bfff-31c5-69e9-9ebed5ec4207 job-originating-host-name=localhost Apr 2 22:33:31 XXX /usr/lib/cups/backend/cups-x2go[6070]: Print job comes from STDIN, writing incoming job to temp file /tmp/5-YYY-cupsjob6070 Apr 2 22:33:31 XXX /usr/lib/cups/backend/cups-x2go[6070]: Converting printjob with command: /usr/bin/gs -q -dCompatibilityLevel=1.4 -dNOPAUSE -dBATCH -dSAFER -sDEVICE=pdfwrite -sOutputFile="/tmp/5-YYY-cupsjob6070.pdf" -dAutoRotatePages=/PageByPage -dAutoFilterColorImages=false -dColorImageFilter=/FlateEncode -dPDFSETTINGS=/prepress -dDoNumCopies -c .setpdfwrite -f "/tmp/5-YYY-cupsjob6070" Apr 2 22:33:32 XXX /usr/bin/x2golistsessions[6073]: x2golistsessions has been called with options: --all-servers Apr 2 22:33:32 XXX /usr/bin/x2goprint[6081]: x2goprint has been called with options: YYY YYY-50-1396503119_stDGNOME_dp24 YYY-50-1396503119_stDGNOME_dp24_5-YYY-cupsjob6070.pdf YYY-50-1396503119_stDGNOME_dp24_5-YYY-cupsjob6070.pdf.title Apr 2 22:33:32 XXX /usr/bin/x2goprint[6081]: x2goprint is processing /var/spool/x2goprint/YYY-50-1396503119_stDGNOME_dp24_5-YYY-cupsjob6070.pdf with print job title ,,Google'' Any help would be appreciated. -Eric

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

x2go-user April 2014