tag #251 pending
fixed #251 1.0.99.1
thanks
Hello,
X2Go issue #251 (src:x2gothinclient) 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=x2gothinclient.git;a=commitdiff;h=7ee07a9
The issue will most likely be fixed in src:x2gothinclient (1.0.99.1).
light+love
X2Go Git Admin (on behalf of the sender of this mail)
---
commit 7ee07a96063a3266bd79ce109924a88c8eaa4ab5
Author: Mike Gabriel <mike.gabriel(a)das-netzwerkteam.de>
Date: Thu Jun 27 21:38:30 2013 +0200
TCE creation: install the TCE from the nightly builds while this project is not yet released. (Fixes: #251).
diff --git a/debian/changelog b/debian/changelog
index 2494e04..6cc8c51 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -68,6 +68,8 @@ x2gothinclient (1.0.99.1-0~x2go1) UNRELEASED; urgency=low
- Fix shutdown button failures.
- TCE management: Do an apt-get clean after TCE creation/upgrade.
- TCE creation: fix installation path of FreeRDP's known_hosts file.
+ - TCE creation: install the TCE from the nightly builds while this
+ project is not yet released. (Fixes: #251).
* /debian/control:
+ Maintainer change in package: X2Go Developers <x2go-dev(a)lists.berlios.de>.
+ Priority: optional.
Package: x2gothinclient
Version: 1.0.1.8-0
A user "x2gothinclient" is established in the TCE- environment, but
/usr/sbin/x2gothinclientd expects the user "x2goclient", with its home
directory at /home/x2goclient. Therefore /usr/bin/x2goclient will not start,
leaving the user in front of a black screen.
Intruducing the user 'x2goclient' solved the problem.
Stephan
--
__________________________________________________
Dr. Stephan Wagner
ITos GmbH
Bitzi-Bendel 2555
9642 Ebnat-Kappel
Tel: +41 (0)71 990 05 94
mailto:swagner@itos-gmbh.com
http://www.itos-gmbh.com
--------------------------------------------------
Package: x2gothinclient
Severity: wishlist
On Mi 26 Jun 2013 18:02:20 CEST Stephan Wagner wrote:
> We use the 'hostname' to distinguish the xorg.conf's for different thin
> clients. The attached init-script 'x2gohostname' replaces the default
> 'hostname' with the ethernet address of the network device eth0. Colons are
> replaced by dashes. Xorg will search the xorg.conf.<hostname> file in the
> directory /usr/etc/X11/, which correspond to
> /opt/x2gothinclient/chroot/usr/etc/X11/ in the PXE-boot environment.
>
> The init-script goes to /opt/x2gothinclient/chroot/etc/init.d/. Enter the
> chroot-environment executing 'x2gothinclient_shell'. 'update-rc.d
> x2gohostname
> defaults' will generate the symlinks for the different run-levels.
>
> Hope this helps someone, Stephan
Can you please re-send this mail to submit(a)bugs.x2go.org and put the
below lines as first lines of the mail body:?:
"""
Package: x2gothinclient
Severity: wishlist
"""
My suggestion would be to improve this script a little further. From
Debian Edu I know that it is rather easy to retrieve the hostname from
DNS.
Like this: MAC -> DHCP -> retrieve IP -> DNS -> set FQDN (revDNS) as hostname
If this fails, MAC as hostname is a fallback that is good enough.
Thanks+Greets,
Mike
--
__________________________________________________
Dr. Stephan Wagner
ITos GmbH
Bitzi-Bendel 2555
9642 Ebnat-Kappel
Tel: +41 (0)71 990 05 94
mailto:swagner@itos-gmbh.com
http://www.itos-gmbh.com
--------------------------------------------------
Processing commands for control(a)bugs.x2go.org:
> tag #241 patch
Bug #241 [x2goclient] Changed host key cannot be updated
Added tag(s) patch.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
241: http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=241
X2Go Bug Tracking System
Contact owner(a)bugs.x2go.org with problems
tag #166 pending
fixed #166 0.4.0.3
thanks
Hello,
X2Go issue #166 (src:pyhoca-gui) 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=pyhoca-gui.git;a=commitdiff;h=e089adc
The issue will most likely be fixed in src:pyhoca-gui (0.4.0.3).
light+love
X2Go Git Admin (on behalf of the sender of this mail)
---
commit e089adced12ab9596a8c0b6f58ed8ce6f2bd2d3a
Author: Mike Gabriel <mike.gabriel(a)das-netzwerkteam.de>
Date: Tue Jun 25 22:49:47 2013 +0200
Catch SSH Exception for mismatching host keys and make it translatable. (Fixes: #166).
diff --git a/debian/changelog b/debian/changelog
index 50ca626..4f1b0b1 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -4,6 +4,8 @@ pyhoca-gui (0.4.0.3-0~x2go1) UNRELEASED; urgency=low
- On selecting »Unshare All Local Folders« purge all shares from the
»export« session profile parameter if »restoreexports« is set to true
in the session profile.
+ - Catch SSH Exception for mismatching host keys and make it translatable.
+ (Fixes: #166).
-- Mike Gabriel <mike.gabriel(a)das-netzwerkteam.de> Sun, 21 Apr 2013 23:09:12 +0200
tag #195 moreinfo
found #195 4.0.0.3
thanks
Hi Matthias,
On Mo 29 Apr 2013 14:52:01 CEST Matthias Kauer wrote:
> Package: X2Go Client
> Version: 4.0.0.3 (Qt - 4.8.1)
>
> I want to use x2go over port 17022. For testing I therefore set
> Virtualbox to forward 17022 -> 22 and entered 17022 as ssh port in
> the x2goclient's config. After a while, a connection timeout window
> appears detailing that 127.0.0.2:22 could not be reached. Having
> VBox forward 22 -> 22 and entering 22 in x2goclient resolved this.
>
> Best,
> Matthias
>
> I am using Win7 64bit Host, Vbox 4.2.12, Xubuntu 12.10 guest
> matthias@matthias-VirtualBox:~$ uname -a
> Linux matthias-VirtualBox 3.5.0-27-generic #46-Ubuntu SMP Mon Mar 25
> 19:58:17 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
thanks for your bug report.
Please give us some feedback on the questions below:
o do you manipulate the SSH port in the global X2Go Client configuration
(Windows Registry folder ,,settings'')?
o or do you manipulate the SSH port in the session profile?
o (I presume a yes for first of the two questions above)
Neither am I getting clean the setup you have.
o is the VBox VM your X2Go Server?
o or your X2Go Client?
I hope to get your problem fixed with the next X2Go Client release, so
a quick response is appreciated.
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: x2goclient
Version: 4.0.1.0
Severity: severe
When trying to connect to a x2go server I experience a first failure
when the session should be established and a segmentation error ending
x2goclient when closing the session window:
== Packages installed ==
.../libxcomp3_2%3a3.5.0.20-0+wheezy~main~405~build1_amd64.deb) ...
.../nxproxy_2%3a3.5.0.20-0+wheezy~main~405~build1_amd64.deb) ...
.../x2goclient_4.0.1.0-0~x2go1+wheezy~main~380~build1_amd64.deb) ...
== Output in x2goclient ==
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 '9249'.
Session: Starting session at 'Sun Jun 23 22:35:13 2013'.
Info: Connecting to remote host 'localhost:31001'.
Info: Connection to remote proxy 'localhost:31001' established.
ZeitüberschreitungInfo: Aborting the procedure due to signal '15'.
Session: Session terminated at 'Sun Jun 23 22:35:43 2013'.
== Output in console ==
ONMainWindow constructor
ONMainWindows constructor finished, home Directory is: "/home/user"
read 1 sessions from config file
start new ssh connection to server: "10.0.0.5" : "22" krb: false
ssh connection ok
continue normal x2go session
"x2gostartagent 1280x1024 lan 16m-jpeg-9 unix-kde-depth_24 de pc105/de 1
D KDE"
Agent output: "50
cf4921e4ba383a630708d7a92be69259
14724
user-50-1372019694_stDKDE_dp24
30001
30002
30003
"
starting nxproxy with: "nxproxy -S
nx/nx,options=/home/user/.x2go/S-user-50-1372019694_stDKDE_dp24/options:50"
"
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 '9249'.
Session: Starting session at 'Sun Jun 23 22:35:13 2013'.
Info: Connecting to remote host 'localhost:31001'.
Info: Connection to remote proxy 'localhost:31001' established.
"
"channel_forward_listen schlug fehl" - ""
deleting proxy
nxproxy not running
proxy deleted
checking exit status
check command message
Speicherzugriffsfehler (segmentation fault)
== Valgrind Output ==
==9291== Process terminating with default action of signal 11 (SIGSEGV)
==9291== Access not within mapped region at address 0x5C
==9291== at 0x49C128: ??? (in /usr/bin/x2goclient)
==9291== by 0x446ABF: ??? (in /usr/bin/x2goclient)
==9291== by 0x446D05: ??? (in /usr/bin/x2goclient)
==9291== by 0x4CAD69: ??? (in /usr/bin/x2goclient)
==9291== by 0x6E5854E: QMetaObject::activate(QObject*, QMetaObject
const*, int, void**) (in /usr/lib/x86_64-linux-gnu/libQtCore.so.4.8.2)
==9291== by 0x6511F31: QAbstractButton::clicked(bool) (in
/usr/lib/x86_64-linux-gnu/libQtGui.so.4.8.2)
==9291== by 0x626606D: ??? (in
/usr/lib/x86_64-linux-gnu/libQtGui.so.4.8.2)
==9291== by 0x626689F: ??? (in
/usr/lib/x86_64-linux-gnu/libQtGui.so.4.8.2)
==9291== by 0x6266B0B:
QAbstractButton::mouseReleaseEvent(QMouseEvent*) (in
/usr/lib/x86_64-linux-gnu/libQtGui.so.4.8.2)
==9291== by 0x6320A89: QToolButton::mouseReleaseEvent(QMouseEvent*)
(in /usr/lib/x86_64-linux-gnu/libQtGui.so.4.8.2)
==9291== by 0x5EFBE0F: QWidget::event(QEvent*) (in
/usr/lib/x86_64-linux-gnu/libQtGui.so.4.8.2)
==9291== by 0x5EAC70B: QApplicationPrivate::notify_helper(QObject*,
QEvent*) (in /usr/lib/x86_64-linux-gnu/libQtGui.so.4.8.2)
==9291== If you believe this happened as a result of a stack
==9291== overflow in your program's main thread (unlikely but
==9291== possible), you can try to increase the size of the
==9291== main thread stack using the --main-stacksize= flag.
==9291== The main thread stack size used in this run was 8388608.
Package: x2goclient
Version: 4.0.1.0
Severity: normal
If I run x2goclient with valgrind I get a lot of output like
==7278== Conditional jump or move depends on uninitialised value(s)
==7278== at 0x46745B: ??? (in /usr/bin/x2goclient)
==7278== by 0x4CB487: ??? (in /usr/bin/x2goclient)
==7278== by 0x6E5854E: QMetaObject::activate(QObject*, QMetaObject
const*, int, void**) (in /usr/lib/x86_64-linux-gnu/libQtCore.so.4.8.2)
==7278== by 0x6DDA27E: QProcess::finished(int, QProcess::ExitStatus)
(in /usr/lib/x86_64-linux-gnu/libQtCore.so.4.8.2)
==7278== by 0x6DDE386: ??? (in
/usr/lib/x86_64-linux-gnu/libQtCore.so.4.8.2)
==7278== by 0x6DDE40D: ??? (in
/usr/lib/x86_64-linux-gnu/libQtCore.so.4.8.2)
==7278== by 0x6E5854E: QMetaObject::activate(QObject*, QMetaObject
const*, int, void**) (in /usr/lib/x86_64-linux-gnu/libQtCore.so.4.8.2)
==7278== by 0x6EA2D5D: QSocketNotifier::activated(int) (in
/usr/lib/x86_64-linux-gnu/libQtCore.so.4.8.2)
==7278== by 0x6E5FE7A: QSocketNotifier::event(QEvent*) (in
/usr/lib/x86_64-linux-gnu/libQtCore.so.4.8.2)
==7278== by 0x5EAC70B: QApplicationPrivate::notify_helper(QObject*,
QEvent*) (in /usr/lib/x86_64-linux-gnu/libQtGui.so.4.8.2)
==7278== by 0x5EB0B89: QApplication::notify(QObject*, QEvent*) (in
/usr/lib/x86_64-linux-gnu/libQtGui.so.4.8.2)
==7278== by 0x6E42B5D: QCoreApplication::notifyInternal(QObject*,
QEvent*) (in /usr/lib/x86_64-linux-gnu/libQtCore.so.4.8.2)
I would suggest to build debug packages
libqtgui4-dbg and x2goclient-dbg as described on
http://wiki.debian.org/DebugPackage
tag #202 pending
fixed #202 4.0.0.5
thanks
Hello,
X2Go issue #202 (src:x2goserver) 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=x2goserver.git;a=commitdiff;h=1c1bc4d
The issue will most likely be fixed in src:x2goserver (4.0.0.5).
light+love
X2Go Git Admin (on behalf of the sender of this mail)
---
commit 1c1bc4d2fb367f6de135d37f1040f11c66ccf5d3
Author: Mike Gabriel <mike.gabriel(a)das-netzwerkteam.de>
Date: Sat Jun 22 14:57:06 2013 +0200
Make x2goumount-session tolerant towards usernames that contain spaces (Fixes: #202).
Conflicts (resolved by Mike Gabriel):
debian/changelog
diff --git a/debian/changelog b/debian/changelog
index b2655c9..cd382e6 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+x2goserver (4.0.0.5-0~x2go1) UNRELEASED; urgency=low
+
+ * New upstream version (4.0.0.5):
+ - Make x2goumount-session tolerant towards usernames that contain spaces
+ (Fixes: #202).
+
+ -- Mike Gabriel <mike.gabriel(a)das-netzwerkteam.de> Thu, 13 Jun 2013 14:56:28 +0200
+
x2goserver (4.0.0.4-0~x2go1) unstable; urgency=low
[ Jan Engelhardt ]
Processing commands for control(a)bugs.x2go.org:
> retitle #202 Possibly breakage in x2goumount-session for usernames that contain spaces
Bug #202 [x2goserver] Possibly breakage in x2goumount-sessio for usernames that contain spaces
Changed Bug title to 'Possibly breakage in x2goumount-session for usernames that contain spaces' from 'Possibly breakage in x2goumount-sessio for usernames that contain spaces'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
202: http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=202
X2Go Bug Tracking System
Contact owner(a)bugs.x2go.org with problems