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/0S+ 0:05 /usr/bin/perl
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
Am 03.04.2014 11:51, schrieb Buddy Butterfly:
Am 03.04.2014 10:13, schrieb Stefan Baur:
ps ax | grep x2gocleansessions | grep perl \
| awk ' { print $1 }' | xargs -n 1 kill
Yep, can confirm. Hangs the whole update process.
Just killed the x2gocleansessions process. Btw.
the awk command
Hi Stefan,
Am Donnerstag, 3. April 2014 schrieb Stefan Baur:
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
I've run into the same problem as Panayotis with x2goserver freezing on
cleaning up stale x2go sessions during the upgrade process.
I can break out from that, but connecting from the Windows x2go client v4.0.1.3
results in a keyboard mapping that's completely hosed: q maps to y, w maps to
t,
On Thu, Apr 3, 2014 at 9:13 AM, Holger Krause
holger.kra...@med.uni-duesseldorf.de wrote:
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
that awk pipeline looks
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
Message: 4
Date: Tue, 01 Apr 2014 16:18:39 +0200
From: GZ Nianguan E.T. opensou...@gznianguan.com
To: x2go-user@lists.berlios.de
Subject: Re: [X2Go-User] X2Go-User Digest, Vol 43, Issue 24
Message-ID: lhehs0$815$1...@ger.gmane.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Hi all,
On Do 03 Apr 2014 12:53:38 CEST, Andreas Yankopolus wrote:
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
Mike,
sorry for the inconvenience.
Workaround: killall x2gocleansessions from another terminal
Solution: Upgrade 4.0.1.14 to 4.0.1.15 (which should be available by now)
A cycle of apt-get update apt-get dist-upgrade -y installed 4.0.1.15
without a hitch.
Logging out of the existing
Am 03.04.2014 15:41, schrieb Stefan Baur:
Am 03.04.2014 11:51, schrieb Buddy Butterfly:
Am 03.04.2014 10:13, schrieb Stefan Baur:
ps ax | grep x2gocleansessions | grep perl \
| awk ' { print $1 }' | xargs -n 1 kill
Yep, can confirm. Hangs the whole update process.
Just killed the
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
Am 04.04.2014 01:07, schrieb Jason Heeris:
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
13 matches
Mail list logo
