x2go-dev January 2015

x2go-dev@lists.x2go.org

46 participants
246 discussions

Bug#725: client-side printing terminates X2Go Client (+ running session) in certain cases
by Mike Gabriel 08 Jan '15

08 Jan '15

Package: x2goclient Severity: grave Tag: patch I have just found a patch for X2Go upstream bug #702 [1]: What I do: ========== o I launch an X2Go session with X2Go Client, client-side printing support is enabled o I minimize X2Go Client to the systray icon o I configure X2Go Client to show the print dialog window on incoming print jobs o I print a document inside the X2Go session What happens: ============= The print dialog window appears. I select "Print"... X2Go Client simply exits cleanly immediately when I click the Print button of the print dialog window. The issue occurs in this combination of events: o print dialog appears on incoming print job o it doesn't matter what print action is chosen (pdfview, pdfsave, print, etc.) o X2Go Client's main window is hidden (e.g. via clicking on the tray icon) What should happen: =================== The incoming print job should get shown as PDF or printed (whatever I chose in the print dialog window). The print dialog window should disappear, my remote X2Go session should continue... The issue is related to this: ============================= http://stackoverflow.com/questions/5116459/problem-with-hidden-qmainwindow-… The related upstream patch is this: =================================== http://code.x2go.org/gitweb?p=x2goclient.git;a=commitdiff;h=3008b2a I am still waiting for feedback from another upstream dev, once it is there, I will fix the issue in the x2goclient src:package in Debian unstable and hopefully testing (jessie). Mike [1] http://bugs.x2go.org/702 -- 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…

2 2

Bug#727: ss in not in path
by Orion Poplawski 08 Jan '15

08 Jan '15

Package: x2goserver Version: 4.1.0.18 x2golistdesktops uses "ss" to list sockets. However, on Fedora this is in /usr/sbin and not in most user's paths (and certainly not in the default path provided via ssh) so it doesn't work. -- Orion Poplawski Technical Manager 303-415-9701 x222 NWRA, Boulder/CoRA Office FAX: 303-415-9702 3380 Mitchell Lane orion(a)nwra.com Boulder, CO 80301 http://www.nwra.com

1 0

Bug#708: x2gosqlitewrapper.pl reports "unable to open database" on session-resume, while the database is there.
by Zuck, Daniel 08 Jan '15

08 Jan '15

Package: x2goserver Version: 4.0.1.15 Hello The environment ist: x2goagent: 3.5.0.27 x2goserver: 4.0.1.15 x2goserver-compat: 4.0.1.15 x2goserver-extensions: 4.0.1.15 x2goserver-fmbindings: 4.0.1.15 x2goserver-printing: 4.0.1.15 x2goserver-pyhoca: 4.0.1.15 x2goserver-xsession: 4.0.1.15 running on SLES11SP3. We have several servers running X2go, where at two systems a session resume raises an error since the same day: DBD::SQLite::st execute failed: unable to open database file at /usr/lib/x2go/x2gosqlitewrapper.pl line 320. syslog: invalid level/facility: error at /usr/lib/x2go/x2gosqlitewrapper.pl line 323 The message is shown by the X2Go-Client on a reconnect, right before the "session-status-info-window" becomes visible. Now at the GUI "Suspend Session" (in German: Anhalten) is selected, after this a reconnect to the session to resume. On clicking "Suspend Session", the error message is shown again. Then the session is selected and "klicked", which results in a "normal" resume of the session, and the remote GUI becomes visible. The Syslog however has entries which read like the session is suspended/resumed correctly without any issues: Dec 19 10:15:35 mxxxxxxxxx02 /usr/bin/x2gosuspend-session: session with ID XYZAB-76-1417681012_stDGNOME_dp32 has been suspended successfully Dec 19 10:16:30 mxxxxxxxxx02 /usr/bin/x2gosuspend-session: session with ID XYZAB-76-1417681012_stDGNOME_dp32 has been suspended successfully Dec 19 10:16:39 mxxxxxxxxx02 /usr/bin/x2goresume-session: client 10.43.142.67 has successfully resumed session with ID XYZAB-76-1417681012_stDGNOME_dp32 Dec 19 10:16:49 mxxxxxxxxx02 /usr/bin/x2gosetkeyboard: Setting X keyboard according to /home/XYZAB/.x2go/C-XYZAB-76-1417681012_stDGNOME_dp32/keyboard Investigating further: When calling "x2golistsessions_root", the script lists a number of states, including the error-message above. So it appears to me, there is a consistency issue with the SQLite-DB. I strongly assume, it can be worked-around by recreating the DB, but I would like to sort out the reason, why it came to this status. My questions: Is this issue known? - I did not find anything like this at the bugtracker. What information is needed for further investigations? - The system is still in this state, so we can pull further infos. Regards Daniel Zuck SIX DGI-OIE Hardturmstrasse 201 Postfach 8021 Zürich T +41 58 399 23 56 http://www.six-group.com mailto:Daniel.Zuck@six-group.com The content of this e-mail is intended only for the confidential use of the person addressed. If you are not the intended recipient, please notify the sender and delete this email immediately. Thank you.

3 2

Bug#708: x2gosqlitewrapper.pl reports "unable to open database" on session-resume, while the database is there.
by Stefan Baur 08 Jan '15

08 Jan '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Daniel, a little less than a month ago, you reported this bug. I was wondering if we can close it or if you need further assistance? Should you require further assistance, please note that it's kind of hard to debug the issue without having access to the database in question, though. Kind Regards, Stefan PS: It would be really cool if you could describe how you're using X2Go in your company. We'd love to put a write-up of it on our "success stories" page on the wiki, and of course we'll provide a backlink to your company if you so desire. (See http://wiki.x2go.org/doku.php/doc:deployment-stories:start for some examples.) - -- BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) iQEcBAEBAgAGBQJUrrO0AAoJEG7d9BjNvlEZoRAH/3Xvqv+a3Uxu+7ef8Ymw3YtE dFKiTWRIOOEtj6M8Ubk6SZ5an5H4POlkzJ4N0LtqF0Z+qu3hy44Zu/j3oACJY5nH yu/jcQFJ79guWjMoJcBr9ykkhBJ0HVT+mPRGWuy4kFCsKB6xELO3/pZFcyJXQVzM ZjUgf6hEX9Nou4ubkXXTrwDF/zEpkn86dWCtAJsAKWzyGqX6GWcNtbiNM05ImhXn oK1IcKtO+EE334qh2E5df400wUVPFwPUFMVrFoRIWd+dqcTbXUe8nrJfLhaOJ5kf QDXNgqp1VXamZ9gS9HF5pVm2pO5Wlk6JEWAwVt7hb0NleSKaY99ZfdUlhOj0XOI= =ig6y -----END PGP SIGNATURE-----

2 2

Bug#720: Unrecognized arguments when using --broker-krblogin
by Matthew Richardson 08 Jan '15

08 Jan '15

Package: x2goclient Version: 4.0.2.1 (Qt - 4.8.6) I am running x2goclient using the following cmd-line options: x2goclient --debug --broker-krblogin --broker-url=ssh://broker.example.com:22/usr/bin/x2gobroker This returns a suitable session from the broker, but then fails to connect, giving an error about invalid arguments: x2go-DEBUG-../onmainwindow.cpp:2199> Reading 1 session from config file. x2go-DEBUG-../onmainwindow.cpp:2803> Starting session via smartcard, ssh-agent or kerberos token. x2go-DEBUG-../httpbrokerclient.cpp:282> called selectUserSessions x2go-DEBUG-../httpbrokerclient.cpp:467> "usage: x2gobroker.orig [-h] [-M BROKER_MODE] [-C CONFIG_FILE] [-d] [-i] [-b BIND_ADDRESS] [-D] [-P PIDFILE] [-L LOGDIR] [--task BROKER_TASK] [--user USER_NAME] [--auth-cookie AUTH_ID] [--profile-id PROFILE_ID] [--backend BROKER_BACKEND] x2gobroker.orig: error: unrecognized arguments: echo X2GODATAEND:4fc77554-09cf-446a-bd44-1c2abaf8238d " If I run the client without the '--broker-krblogin' option, and authenticate to the broker using password or ssh key, this error never appears and the connection to the server (from the downloaded session) succeeds. I tried replacing the x2gobroker with a wrapper that calls it via strace, and I see the following in the strace output: execve("/usr/bin/x2gobroker.orig", ["/usr/bin/x2gobroker.orig", "--user", "mrichar1", "--authid", "f4d2e31c-8438-4cd3-8248-4b35f86e07ff", "--task", "selectsession", "--sid", "pool-icewm;", "echo", "X2GODATAEND:9c607aa1-a3c3-4c29-a7dc-36847ec8ceb0"], [/* 24 vars */]) I notice that the semi-colon separating the sid value and the subsequent command appears inside the sid value quotes, which seems wrong - indeed running this as a test gives: x2gobroker --debug --sid "test;" true x2gobroker.orig: error: unrecognized arguments: true Can this quoting be sorted out to allow the use of the --broker-krblogin option? Thanks, Matthew -- The University of Edinburgh is a charitable body, registered in Scotland, with registration number SC005336.

3 3

Processed: your mail
by owner＠bugs.x2go.org 08 Jan '15

08 Jan '15

Processing commands for control(a)bugs.x2go.org: > close 541 Bug #541 [x2goclient] Patch to close Bug #525 has undesirable side effects Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 541: http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=541 X2Go Bug Tracking System Contact owner(a)bugs.x2go.org with problems

1 0

Bug#719: Clone screens for touch-enabled devices
by Stefan Baur 08 Jan '15

08 Jan '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 package: x2gothinclient version: 1.1.0.2 priority: wishlist Control: tag -1 patch Hi, when using a touch-enabled device (like a tablet computer) as a thinclient, the cursor isn't properly aligned when you try to run a second display (non-touch-enabled) alongside with it. What happens is that both displays get attached to form one large virtual screen, however, your touch-enabled surface obviously still only covers the primary display. The X server doesn't understand this, and tries to map your movements on the primary display to the entire virtual screen surface, so the further to the side and to the bottom you get, the more off your mouse pointer will be from the actual position where you touch your primary display. PRI SEC VIRT +-----+ +-----+ +----------+ |X | | | |O | | | | | | | | | | | | | | | | | | | +-----+ +-----+ +----------+ +-----+ +-----+ +----------+ | | | | | | | | | | | | | \ | | / | | O | | | | | | | +-----+ +-----+ +----------+ \ = where you touch / = where X draws the cursor in reality X = overlapping \ and / O = where X believes the cursor is, on the virtual screen There's no sensible way to use a touch-enabled device with a second screen and no additional, external pointing device, so I've added this patch/workaround that switches to clone mode instead. Of course, if you give up on using the touchscreen and plug in a USB mouse or other external pointing device, you could use two screens. This patch doesn't cover that situation. Maybe someone else has an idea on what a sensible solution could look like that covers this as well? Like, scan for USB HID pointing devices ("find /dev/input -name "mouse*" | wc -l") and, if present in addition to a touchscreen, don't clone, but do side-by-side s if no touch device was detected at all? Tht might have some additional caveats, though, like the detection mis-firing if the touch component of a tablet device "cloaks" as mouse or offers some sort of mouse emulation support. Also, in that case, it would probably be smart to disable the touch interface completely so as to not confuse users why their touches don't align with the cursor. Does anybody know of a generic way to do this? Again, input/suggestions welcome. - -Stefan - -- BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) iQEcBAEBAgAGBQJUq+xgAAoJEG7d9BjNvlEZrjkIAKDP60/c6aMxGsYiA3uZZ0Iw q2W6g3rsjE5t3r1wLjhCgq6VzH9hOvThT2g+ox6upAXoAtj3c9ePhIViboVmX5dH 8RBPucV14gjP7rXxeMlmQgBKo/y5wvtABxcDHO1jlzQoTL752bfANae7zzTrDQJS vdF+fIScHg/W2Ft/KkyYjlOqawCJ9euZOzvOMUmTLFkSrIu6CKAtVF3YZOptnN25 +VcCoiltYUxmGzhYNmGMa9g+zMCZcaPSKloE/pK4YaxQjbCV5NJKuiiILC/E24qa R3dssyt5m33muyQi+E8Ygger2faTe9efUrsDGMHnacCs94wqySUtTebQQzT12KE= =hoaC -----END PGP SIGNATURE-----

3 7

Bug#719: X2Go issue (in src:x2gothinclient) has been marked as pending for release
by Mike Gabriel 08 Jan '15

08 Jan '15

tag #719 pending fixed #719 1.5.0.0 thanks Hello, X2Go issue #719 (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=373c11f The issue will most likely be fixed in src:x2gothinclient (1.5.0.0). light+love X2Go Git Admin (on behalf of the sender of this mail) --- commit 373c11fc7ea4550996f94ee3a69db8ac8a451c1c Author: Mike Gabriel <mike.gabriel(a)das-netzwerkteam.de> Date: Thu Jan 8 16:23:38 2015 +0100 TCE in displaymanager mode: Don't align multiple heads next to one another if a (Wacom) touchscreen is deteced in the list of heads. (Fixes: #719). diff --git a/debian/changelog b/debian/changelog index baf2ce8..0ecfe84 100644 --- a/debian/changelog +++ b/debian/changelog @@ -63,6 +63,9 @@ x2gothinclient (1.5.0.0-0x2go1) UNRELEASED; urgency=low - For X2Go TCE in display manager mode, set login backgrounds of all screens (if more than one is used) to a blue'ish background color. (Fixes: #718). + - TCE in displaymanager mode: Don't align multiple heads next to + one another if a (Wacom) touchscreen is deteced in the list of heads. + (Fixes: #719). * debian/control: + Rename bin:package: x2gothinclient -> x2gothinclient-daemon. + Make sure x2gothinclient-minidesktop pulls in X11 and X2Go Client.

2 1

Processed: your mail
by owner＠bugs.x2go.org 08 Jan '15

08 Jan '15

Processing commands for control(a)bugs.x2go.org: > priority 701 wishlist Bug #701 [x2goclient] We need to talk about, and document, which options are overridable in which way Severity set to 'wishlist' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 701: http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=701 X2Go Bug Tracking System Contact owner(a)bugs.x2go.org with problems

1 0

Processed: your mail
by owner＠bugs.x2go.org 08 Jan '15

08 Jan '15

Processing commands for control(a)bugs.x2go.org: > close 724 Bug #724 [x2goserver-xsession] Scanning does not work over romote-desktop session with sane Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 724: http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=724 X2Go Bug Tracking System Contact owner(a)bugs.x2go.org with problems

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 January 2015