My friend and I are still affected by this bug on his system:
Debian GNU/Linux 7.5 (wheezy) 64-bit
nxagent 3.5.0.24-0x2go1+git20140508.472+wheezy.main.1
x2goserver 4.0.1.15-0x2go1+git20140403.847+wheezy.main.1
x2goserver-xsession 4.0.1.15-0x2go1+git20140403.847+wheezy.main.1
gnome-session-fallback 3.4.2.1-4
gnome-control-center 3.4.3.1-2
Hi all,
the RSS/news feed sync to GMANE for the x2go-announcements list has
been fixed yesterday. Syncs for all other mailing lists have been in
place already earlier, but the x2go-announcements ML seemed to be a
little stubborn (and required a re-subscribe from the GMANE admin side).
Greets,
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…
Package: x2gognomebindings
Severity: important
Version: 2.0.1.6
When a GNOME3 desktop is opened via X2Go in non-fullscreen mode the
GNOME3 xrandr / monitor settings code does some awful resizing of the
desktop session window.
Reproduce (GNOME3, also an issue with Unity):
o you need a client-side display greater than 1024x768
o set desktop size to 1024x768 in x2goclient session profile settings
o set desktop session to GNOME on a Debian wheezy server
o launch session
Compare to KDE4:
o you need a client-side display greater than 1024x768
o set desktop size to 1024x768 in x2goclient session profile settings
o set desktop session to KDE on a Debian wheezy server
o launch session
What you see:
o with KDE4 the desktop session window will have the expected size
o with GNOME3 the window appears in the expected size and then gets resized
from inside the starting up GNOME3 session
o in my case: GNOME3 tries to resize to 1920x1200 pixel. The windows gets
adapted to the greatest size possible on my client display (i.e. the
window maximizes)
o However, the desktop shell inside the window does not adapt to the window
size
o I can manually resize the window afterwards via the client-side window
manager (play with your mouse on the window borders...)
o Still, the desktop shell inside does not adapt its size
This might well be a GNOME3 bug (detection of X server resize events),
but it normally won't cause problems on physical hardware. So, the
X2Go team may have to discover a GNOME3 patch for this problem.
Greets,
Mike
--
DAS-NETZWERKTEAM
mike gabriel, rothenstein 5, 24214 neudorf-bornstein
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…
Control: close -1
Hi Paul,
On Fr 16 Mai 2014 14:09:47 CEST, Paul van der Vlis wrote:
> Hello,
>
> It looks-like that bug 42 has been fixed, and that Gnome3 works fine now
> ;-) Great!
>
> I am using Debian Wheezy as client and as server.
Yeah, let's close that one.
Thanks for feedback.
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…
Package: python-x2go
Version: 0.4.0.9
Seems like a couple issues:
- pyhoca-gui shouldn't emit a traceback
- How to handle multiple session profiles with the same name?
- Is x2goclient allowing that to happen?
-------- Original Message --------
Subject: [Bug 1098201] New: [abrt] pyhoca-gui:
_file.py:330:to_profile_id:X2GoProfileException: The sessions config file
contains multiple session profiles with name: nbecker7
Date: Thu, 15 May 2014 13:16:18 +0000
From: bugzilla(a)redhat.com
To: orion(a)cora.nwra.com
https://bugzilla.redhat.com/show_bug.cgi?id=1098201
Bug ID: 1098201
Summary: [abrt] pyhoca-gui:
_file.py:330:to_profile_id:X2GoProfileException: The
sessions config file contains multiple session
profiles with name: nbecker7
Product: Fedora
Version: 20
Component: pyhoca-gui
Assignee: orion(a)cora.nwra.com
Reporter: ndbecker2(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: orion(a)cora.nwra.com
Description of problem:
1st time trying pyhoca-gui (have used x2goclient before)
On icon in tray, left click, then try to connect to existing session
Version-Release number of selected component:
pyhoca-gui-0.4.0.9-1.fc20
Additional info:
reporter: libreport-2.2.2
cmdline: pyhoca-gui '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' ''
dso_list: python-x2go-0.4.0.9-1.fc20.noarch
executable: /usr/bin/pyhoca-gui
kernel: 3.14.3-200.fc20.x86_64
runlevel: N 5
type: Python
uid: 1000
Truncated backtrace:
_file.py:330:to_profile_id:X2GoProfileException: The sessions config file
contains multiple session profiles with name: nbecker7
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/pyhoca/wxgui/frontend.py", line 784,
in OnSessionAuthenticate
if self.session_profiles.get_profile_config(profile_name)['directrdp']:
File "/usr/lib/python2.7/site-packages/x2go/backends/profiles/_file.py", line
213, in get_profile_config
_profile_id = profile_id or
self.check_profile_id_or_name(profile_id_or_name)
File "/usr/lib/python2.7/site-packages/x2go/backends/profiles/_file.py", line
456, in check_profile_id_or_name
_profile_id = self.to_profile_id(profile_id_or_name)
File "/usr/lib/python2.7/site-packages/x2go/backends/profiles/_file.py", line
330, in to_profile_id
raise X2GoProfileException('The sessions config file contains multiple
session profiles with name: %s' % profile_name)
X2GoProfileException: The sessions config file contains multiple session
profiles with name: nbecker7
Local variables in innermost frame:
_profile_ids: ['20131224085249847', '20140403135324010']
self: X2GoIniFile(_cached_profile_ids=['20131224085249847',
'20140403135324010', '20140416095719622'],_cached_profile_names=[u'New
session', u'nbecker7', u'nbecker7'],_profile_metatypes={'20140416095719622':
u'KDE Desktop', '20131224085249847': u'KDE Desktop', '20140403135324010': u'KDE
Desktop'},_profiles_need_profile_id_renewal=[],config_files=['/home/nbecker/.x2goclient/sessions'],defaultValues={},iniConfig=<ConfigParser.SafeConfigParser
instance at 0x239ccf8>,logger=<x2go.log.X2GoLogger object at
0x239e5d0>,session_profiles=['20131224085249847', '20140403135324010',
'20140416095719622'],user_config_file=/home/nbecker/.x2goclient/sessions)
profile_name: u'nbecker7'
p: '20140416095719622'
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
Package: x2goserver
Version: 4.0.15-0~847
(x2goserver: 4.0.15-0~847~~ubuntu12.04.1 on Ubuntu Linux 12.04.4 LTS kernel 3.8.0-39-generic,
x2goclient: 4.0.15-0~847~ubuntu14.04.1 on Ubuntu Linux 14.04 LTS kernel 3.14.3-031403-generic)
Please note: I have labelled package x2goserver, but the bug is displayed on x2goclient even though I *think* the bug is in the server somewhere (see below).
Sometimes after an abrupt (e.g. CTRL-C, probably also network
failure or laptop sleep/wake cycle) termination of x2goclient, I
cannot reconnect to the server. I get errors such as the dreaded
"Failure negotiating the session in stage '7'." and "Error: Wrong
version or invalid session authentication cookie." instead.
I am connecting through a proxy using ssh key-based
authentication (using "Try auto-login" with "ssh-agent or default
ssh key" on the proxy, although switching to password made no
difference). I can connect with ssh through the proxy with no
problem. I can *start* an x2go session with no problem. I can
restart a session with no problem *provided I cleanly exit
x2goclient* (e.g. by clicking on the close button on the window).
If I exit x2goclient with a CTRL-C in the terminal, I cannot
connect again. Note that I can connect to an NX session through
the proxy without any problem and this does not have the same
problem when CTRL-C.
Steps to repeat:
1) On the client, open a new desktop on the server using
x2goclient. (I am running KDE but I doubt it matters).
2) On the client, press CTRL-C to stop x2goclient.
3) On the client, try to reconnect -- it fails with errors (which
are very hard to copy-paste as they go so fast, this is a bug in
the GUI):
------------------------
NXPROXY - Version 3.5.0
Copyright (C) 2001, 2010 NoMachine.
See http://www.nomachine.com/ for more information.
Info: Proxy running in client mode with pid '7219'.
Session: Starting session at 'Thu May 8 17:33:51 2014'.
Info: Connecting to remote host 'localhost:31007'.
Info: Connection to remote proxy 'localhost:31007' established.
Error: The remote NX proxy closed the connection.
Error: Failure negotiating the session in stage '7'.
Error: Wrong version or invalid session authentication cookie.
Session: Terminating session at 'Thu May 8 17:33:51 2014'.
Session: Session terminated at 'Thu May 8 17:33:51 2014'.
------------------------
At this point the CPU usage of x2goclient jumps to 100% and I
have to kill it (although the GUI continues to respond). This is
just a minor annoyance at the moment.
And in .x2go/SESSION_ID/sessions on the client, similar warnings:
------------------------
Loop: PANIC! No shutdown of proxy link performed by remote proxy.
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.
------------------------
The server clearly detects the disconnect in its session.log,
followed by “Display failure detected” errors on attempted
reconnect:
-----------------------
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 '17414'.
Session: Starting session at 'Fri May 9 14:44:26 2014'.
Info: Proxy running in server mode with pid '17414'.
Info: Waiting for connection from 'localhost' on port '30004'.
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-png-9' with session
'unix-kde-depth_24'.
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 ':51'.
Info: Established X client connection.
Info: Using shared memory parameters 1/1/1/2048K.
Info: Using alpha channel in render extension.
Info: Not using local device configuration changes.
keyboard file created
SessionPath not defined
Session: Session started at 'Fri May 9 14:44:27 2014'.
Error: Failure reading from the peer proxy.
Error: Connection with remote peer broken.
Error: Please check the state of your network and retry.
Session: Display failure detected at 'Fri May 9 14:44:44 2014'.
Session: Suspending session at 'Fri May 9 14:44:44 2014'.
Session: Session suspended at 'Fri May 9 14:44:44 2014'.
Session: Resuming session at 'Fri May 9 14:45:11 2014'.
Info: Proxy running in server mode with pid '17414'.
Info: Waiting for connection from 'localhost' on port '30004'.
Info: Aborting the procedure due to signal '1'.
Session: Display failure detected at 'Fri May 9 14:45:27 2014'.
Session: Suspending session at 'Fri May 9 14:45:27 2014'.
Session: Session suspended at 'Fri May 9 14:45:27 2014'.
--------------
In .x2go/C-SESSION_ID/session.log on the server, I now have the
following text repeated over and over:
Session: Suspending session at 'Fri May 9 15:08:49 2014'.
[then hundreds or thousands of times, with later timestamps]
The problem appears to be with the file
/var/lib/x2go/x2go_sessions on the server. If I back this up
*before* hitting CTRL-C on the client, then do the CTRL-C, then
reinstate the backup, I can restart the session with no problems.
Clearly this is beyond the ability of a normal user (without root
on the server) and is not really a fix, even if it does work.
It seems that there is a problem with the x2go_sessions file on
the server being corrupted in some way when the remote session is
abruptly disconnected. This is a failure bad enough for me to
stop using x2go and go back to NX.
* Backing up this file all the time is not an option.
* Deleting this file and continuing, as suggested at
http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=323, is not an
option.
* Note that unlink suggested in
http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=323, there is no
*server* crash.
* I have tried the other options at
http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=323, none apply
here (e.g. permissions are fine).
* The action that precipitates the problem is on the *client*
side.
* Note also that the network itself is not at fault: I can
connect from a laptop in the same office (but on a different
subnet) as the server, or from home to the proxy server direct.
Same problem.
* This seems similar to
http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=101 but the fixes
are more than a year ago and presumably (?) are in the latest
x2goclient already.
* No amount of calls to x2gosuspend-session or x2goresume-session
on the appropriate session makes any difference.
* If I suspend the session with x2gosuspend-session, attempting
to connect *does* set the session into the “Running” state (just
as x2goresume-session). The error seems to occur after this.
Thanks for all your help x2go team, I hope we can fix this
because I'd like to recommend x2go for my colleagues.
Rob
tag #498 pending
fixed #498 4.0.2.1
thanks
Hello,
X2Go issue #498 (src:x2goclient) reported by you has been
fixed in X2Go Git. You can see the changelog below, and you can
check the diff of the fix at:
http://code.x2go.org/gitweb?p=x2goclient.git;a=commitdiff;h=ea9fd44
The issue will most likely be fixed in src:x2goclient (4.0.2.1).
light+love
X2Go Git Admin (on behalf of the sender of this mail)
---
commit ea9fd44a57f24f87dd7d44cdf314d9be72e48289
Author: Mike Gabriel <mike.gabriel(a)das-netzwerkteam.de>
Date: Wed May 14 11:42:50 2014 +0200
Fix FTBFS on arm64 (and others) architecture. (Fixes: #498).
diff --git a/debian/changelog b/debian/changelog
index bc6e4ad..f135146 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,5 +1,7 @@
x2goclient (4.0.2.1-0x2go1) UNRELEASED; urgency=low
+ * New upstream release (4.0.2.1):
+ - Fix FTBFS on arm64 (and others) architecture. (Fixes: #498).
* debian/control:
+ Add dbg:package x2goplugin-dbg.