x2go-dev

x2go-dev@lists.x2go.org

1 participants
5399 discussions

Bug#1161: x2goclient fullscreen mode on macOS Sierra having two displays
by Michael Ledin 20 Mar '17

20 Mar '17

Package: x2goclient Version: 4.1.0.0 I'm running x2goclient on Macbook Pro Retina 15 Late 2013 with macOS Sierra installed and external display connected, so I have two displays. I have XQuartz 2.7.11 (xorg-server 1.18.4) installed. My session is set to run in fullscreen mode (also I tried "Use whole display" option set to external monitor). Xinerama extension is disabled. XQuartz fullscreen mode is enabled. When I launch this session it goes in fullscreen mode but its window stretches to summary width of both displays (built-in and external) but visible only on external display, so I do not see part of the window. -- Michael Ledin

2 1

x2goclient ssh agent forwarding
by Michael Ledin 20 Mar '17

20 Mar '17

Hi, x2go developers. I recently started to use x2go as remote control solution and very happy with it. Thanks for your work. But I miss the ssh agent forwarding feature. I searched the web today a lot about this question and found several links to mailing lists: https://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=501 https://www.libssh.org/archive/libssh/2016-11/0000007.html both contain messages from the same person Hadmut Danisch. The last one even contains patches for x2goclient and libssh. What is the status of this feature? Is it not implement or is it me doing something wrong? -- Michael Ledin

3 3

Bug#1160: Actually it's nx-libs
by Michael Ledin 19 Mar '17

19 Mar '17

Actually not x2goserver but nx-libs should have xkbcomp as required dependency https://code.x2go.org/gitweb?p=nx-libs.git&a=search&h=HEAD&st=grep&s=xkbcomp

1 0

Bug#1160: x2goserver.spec does not list xkbcomp as required dependency
by Michael Ledin 17 Mar '17

17 Mar '17

Package: x2goserver Version: 4.0.1.20 I installed x2goserver on Archlinux and everything works perfectly with x2goclient except it does not apply keyboard settings. The reason was that Archlinux x2goserver package does not depend on xorg-setxkbmap though it listed as dependency here (https://code.x2go.org/gitweb?p=x2goserver.git;a=blob;f=x2goserver.spec;h=1d…) and I reported a bug to Archlinux team https://bugs.archlinux.org/task/53345. But also x2go-agent package does not list xkbcomp as dependency. Nor does x2goserver.spec though "hexdump -C /usr/lib/x2go/bin/x2goagent | grep xkbcomp" says the opposite. After I installed xorg-setxkbmap and xorg-xkbcomp packages x2goserver started to apply keyboard settings normally. -- Michael Ledin

1 0

Bug#1158: PyHoca GUI still showing terminated session (error: Semaphore released too many times)
by Michael Ledin 16 Mar '17

16 Mar '17

Package: pyhoca-gui Version: 0.5.0.4 I'm using Archlinux and installed pyhoca-gui from AUR. Before that I used x2goclient and created several profiles there so in pyhoca-gui I continued to use these profiles. I connect to server and then start new desktop environment (XFCE). Then I try to terminate the session. It terminated but PyHoca still shows it in server menu like "Running: ...session name here" but in gray color and session menu is not accessible so I can not terminate it again. Here is the full log for "pyhoca-gui -d": 21:25:37: Warning: Mismatch between the program and library build versions detected. The library used 3.0 (wchar_t,compiler with C++ ABI 1010,wx containers,compatible with 2.8), and wxPython used 3.0 (wchar_t,compiler with C++ ABI 1009,wx containers,compatible with 2.8). pyhoca-gui[11764] (PyHoca-GUI) DEBUG: PyHoca-GUI's user interface language is: en_US. pyhoca-gui[11764] (PyHoca-GUI) INFO: PyHoca GUI is starting up pyhoca-gui[11764] (PyHoca-GUI) INFO: start TaskBarIcon of type: ('__WXGTK__', 'wxGTK', 'unicode', 'gtk2', 'wx-assertions-on', 'SWIG-1.3.29') pyhoca-gui[11764] (PyHoca-GUI) WARN: the current release of PyHoca-GUI does not support client configuration pyhoca-gui[11764] (x2gosessregistry-pylib) NOTICE: registering X2Go session AppHeads WAN... pyhoca-gui[11764] (x2goclient-pylib) NOTICE: initializing X2Go session... pyhoca-gui[11764] (x2gocontrolsession-pylib) NOTICE: connecting to [my.domain.here]:22 pyhoca-gui[11764] (PyHoca-GUI) NOTICE: [AppHeads WAN - connect] SSH key authentication has been successful. pyhoca-gui[11764] (x2gosessregistry-pylib) NOTICE: using already initially-registered yet-unused session fa565712-0a75-11e7-9d4b-58946b494d4c pyhoca-gui[11764] (x2goclient-pylib) NOTICE: initializing X2Go session... pyhoca-gui[11764] (x2gosession-pylib) NOTICE: Using session appheads-50-1489688865_stDXFCE_dp24 as master session for profile AppHeads WAN. pyhoca-gui[11764] (PyHoca-GUI) NOTICE: [AppHeads WAN - start] New X2Go session starting up... appheads-50-1489688865_stDXFCE_dp24 pyhoca-gui[11764] (x2goterminalsession-pylib) NOTICE: x2goumount-session (all mounts) for session appheads-50-1489688865_stDXFCE_dp24 has been successful pyhoca-gui[11764] (x2goterminalsession-pylib) NOTICE: cleaning up session appheads-50-1489688865_stDXFCE_dp24 after termination Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/gevent/greenlet.py", line 536, in run result = self._run(*self.args, **self.kwargs) File "/usr/lib/python2.7/site-packages/x2go/client.py", line 1680, in terminate_session return session.terminate() File "/usr/lib/python2.7/site-packages/x2go/session.py", line 2374, in terminate self._lock.release() File "src/gevent/_semaphore.py", line 266, in gevent._semaphore.BoundedSemaphore.release (src/gevent/gevent._semaphore.c:5353) File "src/gevent/_semaphore.py", line 268, in gevent._semaphore.BoundedSemaphore.release (src/gevent/gevent._semaphore.c:5291) error: Semaphore released too many times Thu Mar 16 21:26:52 2017 <Greenlet at 0x7f340f8a5910: <bound method PyHocaGUI.terminate_session of <pyhoca.wxgui.frontend.PyHocaGUI; proxy of <Swig Object of type 'wxPyApp *' at 0x55e7af0c6320> >>('fa565712-0a75-11e7-9d4b-58946b494d4c', session_name='appheads-50-1489688865_stDXFCE_dp24', match_profile_name=u'AppHeads WAN')> failed with error Exception in thread Thread-1: Traceback (most recent call last): File "/usr/lib/python2.7/threading.py", line 801, in __bootstrap_inner self.run() File "/usr/lib/python2.7/threading.py", line 754, in run self.__target(*self.__args, **self.__kwargs) File "/usr/lib/python2.7/site-packages/x2go/guardian.py", line 116, in guardian update_mounts=self.auto_update_listmounts_cache, File "/usr/lib/python2.7/site-packages/x2go/client.py", line 3148, in update_cache_all_profiles update_mounts=update_mounts, File "/usr/lib/python2.7/site-packages/x2go/client.py", line 3089, in update_cache_by_profile_name self.listsessions_cache.update(profile_name, update_sessions=_update_sessions, update_desktops=_update_desktops, update_mounts=_update_mounts, ) File "/usr/lib/python2.7/site-packages/x2go/cache.py", line 135, in update self._update_sessions(profile_name, control_session) File "/usr/lib/python2.7/site-packages/x2go/cache.py", line 204, in _update_sessions self.x2go_listsessions_cache[profile_name]['sessions'] = control_session.list_sessions() File "/usr/lib/python2.7/site-packages/x2go/backends/control/plain.py", line 1749, in list_sessions self.associated_terminals[_session_name].__del__() File "/usr/lib/python2.7/site-packages/x2go/backends/terminal/plain.py", line 413, in __del__ self._x2go_tidy_up() File "/usr/lib/python2.7/site-packages/x2go/backends/terminal/plain.py", line 424, in _x2go_tidy_up self._share_local_folder_lock.release() File "src/gevent/_semaphore.py", line 266, in gevent._semaphore.BoundedSemaphore.release (src/gevent/gevent._semaphore.c:5353) File "src/gevent/_semaphore.py", line 268, in gevent._semaphore.BoundedSemaphore.release (src/gevent/gevent._semaphore.c:5291) error: Semaphore released too many times If I'll try then to disconnect from server then GUI shows that server is disconnected but I still will get the following log output: pyhoca-gui[11764] (PyHoca-GUI) NOTICE: [AppHeads WAN - disconnect] X2Go Profile is now disconnected. Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/gevent/greenlet.py", line 536, in run result = self._run(*self.args, **self.kwargs) File "/usr/lib/python2.7/site-packages/x2go/client.py", line 3005, in disconnect_profile _retval = s.disconnect() | _retval File "/usr/lib/python2.7/site-packages/x2go/session.py", line 1377, in disconnect self._lock.release() File "src/gevent/_semaphore.py", line 266, in gevent._semaphore.BoundedSemaphore.release (src/gevent/gevent._semaphore.c:5353) File "src/gevent/_semaphore.py", line 268, in gevent._semaphore.BoundedSemaphore.release (src/gevent/gevent._semaphore.c:5291) error: Semaphore released too many times Thu Mar 16 21:28:59 2017 <Greenlet at 0x7f340f8a5370: <bound method PyHocaGUI.disconnect_profile of <pyhoca.wxgui.frontend.PyHocaGUI; proxy of <Swig Object of type 'wxPyApp *' at 0x55e7af0c6320> >>(u'AppHeads WAN')> failed with error Next if I try to connect to server again then GUI looks like I was connected to server, but previously terminated session is showed like running (though pressing "Show session windows" results in nothing) and "An unknown error occured during authentication" message is popped up and the following log is outputed: pyhoca-gui[11764] (x2gosessregistry-pylib) NOTICE: registering X2Go session AppHeads WAN... pyhoca-gui[11764] (x2goclient-pylib) NOTICE: initializing X2Go session... pyhoca-gui[11764] (PyHoca-GUI) NOTICE: [AppHeads WAN - unknown error] An unknown error occurred during authentication! Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/gevent/greenlet.py", line 536, in run result = self._run(*self.args, **self.kwargs) File "/usr/lib/python2.7/site-packages/pyhoca/wxgui/frontend.py", line 636, in _do_authenticate self._X2GoClient__connect_session(session_uuid, add_to_known_hosts=self.add_to_known_hosts) File "/usr/lib/python2.7/site-packages/x2go/client.py", line 1367, in connect_session sshproxy_force_password_auth=sshproxy_force_password_auth, File "/usr/lib/python2.7/site-packages/x2go/session.py", line 1355, in connect self.update_status() File "/usr/lib/python2.7/site-packages/x2go/session.py", line 1603, in update_status session_list = self.control_session.list_sessions() File "/usr/lib/python2.7/site-packages/x2go/backends/control/plain.py", line 1749, in list_sessions self.associated_terminals[_session_name].__del__() File "/usr/lib/python2.7/site-packages/x2go/backends/terminal/plain.py", line 413, in __del__ self._x2go_tidy_up() File "/usr/lib/python2.7/site-packages/x2go/backends/terminal/plain.py", line 424, in _x2go_tidy_up self._share_local_folder_lock.release() File "src/gevent/_semaphore.py", line 266, in gevent._semaphore.BoundedSemaphore.release (src/gevent/gevent._semaphore.c:5353) File "src/gevent/_semaphore.py", line 268, in gevent._semaphore.BoundedSemaphore.release (src/gevent/gevent._semaphore.c:5291) error: Semaphore released too many times Thu Mar 16 21:34:17 2017 <Greenlet at 0x7f340f8a5370: <bound method PyHocaGUI._do_authenticate of <pyhoca.wxgui.frontend.PyHocaGUI; proxy of <Swig Object of type 'wxPyApp *' at 0x55e7af0c6320> >>(<wx._core.CommandEvent; proxy of <Swig Object of t, '299442ea-0a77-11e7-9d4b-58946b494d4c')> failed with error After that if I press "Disconnect from server" nothing happens except showing popup that profile is disconnected though GUI says that there is still active connection and I even can start new desktop session. pyhoca-cli also has that "Semaphore released too many times" error. I will report it as separate bug. -- Michael Ledin

1 0

Bug#1157: Windows client pop-up box too long
by John Cobo 16 Mar '17

16 Mar '17

Package: Windows Client Version: 4.1.0.0 With a Windows 10 tool bar at the bottom of the screen, pop-up boxes from Windows client have the "OK" and "Cancel" buttons hidden below the tool bar. Thanks. [image: Inline images 1]

1 0

Bug#1100: Looking in to how to solve this
by Mike DePaulo 16 Mar '17

16 Mar '17

FYI, I am currently looking into how to solve this. I do not want to simply revert to the old functionality.

1 0

Bug#1152: X2Go issue (in src:x2goclient) has been marked as closed
by Mike DePaulo 11 Mar '17

11 Mar '17

close #1152 thanks Hello, we are very hopeful that X2Go issue #1152 reported by you has been resolved in the new release (4.1.0.0) of the X2Go source project »src:x2goclient«. You can view the complete changelog entry of src:x2goclient (4.1.0.0) below, and you can use the following link to view all the code changes between this and the last release of src:x2goclient. http://code.x2go.org/gitweb?p=x2goclient.git;a=commitdiff;h=45a6a96b2f53a99… If you feel that the issue has not been resolved satisfyingly, feel free to reopen this bug report or submit a follow-up report with further observations described based on the new released version of src:x2goclient. Thanks a lot for contributing to X2Go!!! light+love X2Go Git Admin (on behalf of the sender of this mail) --- X2Go Component: src:x2goclient Version: 4.1.0.0--2017.03.11 Status: RELEASE Date: Sat, 11 Mar 2017 13:24:19 -0500 Fixes: 1152 Changes: x2goclient (4.1.0.0--2017.03.11) RELEASED; urgency=medium . [ Mike DePaulo ] * New upstream version (4.1.0.0-2017.03.11): - Windows: Upgrade PulseAudio from 6.0 to 7.1 Fixes: #1152 Issues with audio when playing HTML5 videos - Windows: Remove uninstaller from start menu. It is still available in "Programs and Features". - Windows: Upgrade Win32 OpenSSL from 1.0.1t to 1.0.2k Fixes numerous CVEs - Windows: Upgrade libssh from 0.7.0 to 0.7.4 (while maintaining Pageant support). The possibly relevant changes are: + CVE-2016-0739 was fixed + improved id_ed25519 support + numerous bug fixes - Windows: Update PuTTY from 0.67 to 0.68 The possibly relevant changes are: + CVE-2016-6167 was fixed (did not affect X2Go Client by default because the installation dir is not writeable by users) + CVE-2017-6542 was fixed

2 1

Bug#1152: X2Go issue (in src:x2goclient) has been marked as pending for release
by Mike DePaulo 11 Mar '17

11 Mar '17

tag #1152 pending fixed #1152 4.1.0.1 thanks Hello, X2Go issue #1152 (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=d5d9856 The issue will most likely be fixed in src:x2goclient (4.1.0.1). light+love X2Go Git Admin (on behalf of the sender of this mail) --- commit d5d985652ef00e3880938316f48cc811051b54f6 Author: Mike DePaulo <mikedep333(a)gmail.com> Date: Sat Mar 11 07:52:53 2017 -0500 Windows: Upgrade PulseAudio from 6.0 to 7.1 Fixes: #1152 diff --git a/debian/changelog b/debian/changelog index e801167..45af200 100644 --- a/debian/changelog +++ b/debian/changelog @@ -160,6 +160,11 @@ x2goclient (4.1.0.1-0x2go1) UNRELEASED; urgency=medium * New upstream version (4.1.0.1): - res/i18n/x2goclient_fi.ts: update Finnish translation file. + [ Mike DePaulo ] + * New upstream version (4.1.0.1): + - Windows: Upgrade PulseAudio from 6.0 to 7.1 + Fixes: #1152 Issues with audio when playing HTML5 videos + -- X2Go Release Manager <git-admin(a)x2go.org> Wed, 22 Feb 2017 07:13:10 +0100 x2goclient (4.1.0.0-0x2go1) unstable; urgency=medium

2 1

Bug#1046: x2go session causes dbus conflicts with logged in desktop on Fedora 24
by Andy Wang 10 Mar '17

10 Mar '17

Package: x2goserver Version: 4.0.1.19-8.fc24 When attempting to login with a client desktop session that uses dbus while logged in as the same user on the console causes an error to appear in a pop up window: Could not acquire name on session bus You can dismiss the error but the desktop never full starts and attempts to logout triggers the logout on the console session. >From the error, I this appears to be resolved by using a custom session script in x2go and making sure to call: unset DBUS_SESSION_BUS_ADDRESS For example: #!/bin/sh unset DBUS_SESSION_BUS_ADDRESS # redirect to /dev/null due to x2go bug 914 /usr/bin/mate-session > /dev/null Doing some digging, it looks like the dbus socket (/usr/lib/systemd/user/dbus.socket) on fedora 24 (dbus-1.11.2-1.fc24.x86_64) does this: ExecStartPost=-/usr/bin/systemctl --user set-environment DBUS_SESSION_BUS_ADDRESS=unix:path=%t/bus And sets the DBUS_SESSION_BUS_ADDRESS for all logins for your user. This same workaround appears to be what tigervnc used as their permanent solution: https://github.com/TigerVNC/tigervnc/commit/c071e493a093d7ee9a568729dd2e151… So I think this is the proper solution. FYI, a bug was filed against Fedora as well: https://bugzilla.redhat.com/show_bug.cgi?id=1350004

3 2

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

x2go-dev