x2go-dev September 2016

x2go-dev@lists.x2go.org

26 participants
134 discussions

Bug#190: debug-sftpxfer creates operation not permitted
by Dick Kniep 08 Jan '24

08 Jan '24

Package: pyhoca-gui Severity: normal Version 4.0.3 When the switch debug-sftpxfer is used in pyhoca-gui, sometimes network drives on windows are not accessible and generate the message "operation not permitted"

3 2

Bug#359: Desktop/Startmenu icon for X2Go Admin Center
by Mike Gabriel 08 Jan '24

08 Jan '24

Package: x2goadmincenter Severity: wishlist Version: 0.0.0.1 Hi Heinz, I have been playing with X2Go Admin Center lately and I would really love to see it get more focus (from me, from others). One step towards that would be a nice desktop icon set. For now, we use the X2Go Client icon for X2Go Admin Center [1] and we show the .desktop file in the System menu category. Maybe you can take a look at this some time... (very low prio, this wishlist bug is simply so that we don't forget it). Mike [1] http://code.x2go.org/gitweb?p=x2goadmincenter.git;a=tree;f=x2goadmincenter/… -- 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…

1 1

Bug#709: unity-greter brakes desktop
by Theo Gorm Lindbæk 08 Jan '24

08 Jan '24

Package: unity-greter-x2go Version: 14.04.01-0~24~ubuntu.14.04.1 Install on Ubuntu 14.04.1 64 bit Hello We install unity-greter-x2go from ppa:x2go/ppa after reboot the menu disappear regards Gorm

4 4

Bug#237: No Qt'isms in ~/.x2goclient/sessions
by Mike Gabriel 08 Jan '24

08 Jan '24

Package: x2goclient2 Severity: serious Version: 0.0.0.1 Hi Alex, I have played with x2goclient2 recently and have notices that it adds picture=QByteArray(...) to session profiles that get edited with x2goclient2. Please do not use any Qt'isms on the sessions file as Python X2Go won't be able to handle those. There must be a generic, non-Qt way for storing session PNGs. Thanks+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…

2 2

Bug#626: NX agent dies not reliably remove socket files under /tmp/.X11-unix
by Mike Gabriel 08 Jan '24

08 Jan '24

Package: nxagent Version: 3.5.0.27 Severity: important 17:02 < bigfoot-> hmmm. x2goagent is started with -extension XFIXES -nolisten tcp -nolisten tcp -dpi 96 -D -auth /fs/staff/hsc/.Xauthority -geometry 800x600 -name X2GO-hsc-51-1412262126_stDmyxfce_dp24 :51 17:02 < bigfoot-> :50 is the already running (first) session 17:03 < bigfoot-> and x2goagent dies with https://pbot.rmdir.de/tt64QL-NNXqZomZoahDhJg [...] 17:08 < bigfoot-> woglinde: I had to remove remaining /tmp/.X*-lock and /tmp/.X11-unix/X* that were owned by other users. Works like a charm again now. 17:09 < bigfoot-> iow, a reboot would've helped, too (if it cleans up /tmp, that is). but that's a non-option on this machine. [...] 17:23 <@sunweaver> please report it as a bug!!!! 17:24 < bigfoot-> I'm still investigating; seeing this issue again now. The process is as follows: 17:25 < bigfoot-> - some user logs in, gets :50 17:25 < bigfoot-> - some user logs in, gets :50 17:25 < bigfoot-> - /tmp/.X50-lock and /tmp/.X11-unix/X50 are owned by him now 17:25 < bigfoot-> - user logs out, which doesn't succeed completely (due to some yet unknown reason; he's got a default xfce setup in his home) 17:26 < bigfoot-> - user logs in via ssh and kills all his processes via killall -u username 17:26 < bigfoot-> afterwards, x2go seems to assume :50 is free, but the two aforementioned files still exist 17:26 < bigfoot-> the next user gets assigned :50, but this fails as the user doesn't have the permissions to access these files 17:27 < bigfoot-> So, who (or, which part of x2go) is responsible for removing these files? When does/should this happen? 17:51 < bigfoot-> sunweaver: this change seemingly only changes the output, does this have an effect on the cleanup stuff? 17:51 <@sunweaver> no 17:51 <@sunweaver> the fix is four smoothing out mkigration from 4.0.1.15 to higher... 17:52 <@sunweaver> though there could be unexpected side effects... 17:52 <@sunweaver> there also is a patch in NX I introduced lately... 17:53 < bigfoot-> ok, but how should the new x2golistsessions and x2golistsessions_root affect my issue with cleanup? 17:55 <@sunweaver> http://code.x2go.org/gitweb?p=nx-libs.git;a=blob;f=debian/patches/027_nxcom… -- DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976148 GnuPG Key ID 0x25771B13 mail: mike.gabriel(a)das-netzwerkteam.de, http://das-netzwerkteam.de

3 4

Bug#196: Make tests optional
by Jan Engelhardt 08 Jan '24

08 Jan '24

Package: libpam-x2go Version: 0.0.1.0

3 2

X2goclient fullscreen does not adjust screen resolution after update
by christoffer krakou 08 Jan '24

08 Jan '24

Hello list I have recently upgraded the following packages Upgrade package libnx-x11 2:3.5.0.16-0~278~precise1 to 2:3.5.0.17-0~320~precise1 Upgrade package libxcomp3 2:3.5.0.16-0~278~precise1 to 2:3.5.0.17-0~320~precise1 Upgrade package libxcompext3 2:3.5.0.16-0~278~precise1 to 2:3.5.0.17-0~320~precise1 Upgrade package libxcompshad3 2:3.5.0.16-0~278~precise1 to 2:3.5.0.17-0~320~precise1 Upgrade package nxagent 2:3.5.0.16-0~278~precise1 to 2:3.5.0.17-0~320~precise1 Upgrade package nxproxy 2:3.5.0.16-0~278~precise1 to 2:3.5.0.17-0~320~precise1 Upgrade package x2goagent 2:3.5.0.16-0~278~precise1 to 2:3.5.0.17-0~320~precise1 On my Ubuntu 12.04 server. Now, when i connect using the x2goclient, it works well when i select a resolution and run it in a window, but when i select fullscreen, the resolution is 1920 X 1200, no matter the resolution on the client monitor. This results in the Unity controls being unusable. Before the upgrades, there were no trouble. Is anyone else experiencing the same? -- Venlig Hilsen / Best Regards Christoffer Krakou Fleten.net APS

3 3

Bug#913: Inaccurate scaling of dialog boxes and fonts for large DPI screen in Windows 10
by Alves-Foss, James (jimaf＠uidaho.edu) 02 Aug '21

02 Aug '21

Package: x2goclient for windows Version: 4.0.5.0 Downloaded new version of x2goclient for a new Dell Laptop. Screen resolution 3200x1800. OS Windows 10 (just checked, same problem on similar machine in Windows 8.1) When I open the main program, the fonts and windows do not scale well in the session selection boxes When I create a new session and try to open it, I can not see the list of open sessions to connect to. This appears to be a scaling issue for high DPI systems. I tried Windows 7, Windows 8 compatibility modes. I tries to disable display scaling on high DPI systems (see attached images)

3 2

Bug#581: VirtualBox Clipboard Sharing does not work when accessing the host over X2Go
by Michael DePaulo 18 Jun '21

18 Jun '21

Package: nx-libs Version: 3.5.0.27 Severity: normal If you run a VirtualBox VM with its display running under X2Go, the VM's clipboard sharing fails to work in either direction. You cannot copy and paste text between the VM and an app running under X2Go server, nor can you copy and paste text between the VM and an app running on the X2Go Client system. (I believe VirtualBox VMs use SDL to interact with the X server, which in this case is nxagent. This differs from the VirtualBox GUI, which is written in QT.) Specifically, when the X sesssion starts on the guest, a VirtualBox-provided script for X calls "VBoxClient --clipboard" to start the clipboard service. The service runs as the user logged into the guest. However, this service fails to stay running, and thus the clipboard sharing does not work. If you launch the VirtualBox VM on the local X.org X server, the guest's clipboard service stays running and clipboard sharing works. You can also launch the VM in RDP headless mode from x2go (so the VM does not render its display to any nxagent). In this use case, the clipboard service stays running and clipboard sharing works. The strange part is that the configuration of the host affects the behavior of the guest. It makes sense though because it's a bug in the guest's code to integrate with the host. Also, when you do call "VBoxClient --clipboard", it returns 0. And if you call it after the X11 session has already started, the problem still occurs. In x2goclient, I tried turning on and off the following setting, but it had no effect: Options -> Settings -> X-Server settings -> do not use primary clipboard My theory is that this is a bug in nx-libs, and that the bug is probably related to nx-libs being forked from such an old X.org codebase. It is worth looking into whether other SDL apps have clipboard trouble with X2Go on Ubuntu 14.04. (It's also worth testing an older release of Ubuntu as the host OS, since it would have an older release of SDL.) Host system: OS: Ubuntu 14.04.1 64-bit with latest bugfix & security updates nxagent: 2:3.5.0.27-0~446~ubuntu14.04.1 x2goserver: 4.0.1.15-0~847~ubuntu14.04.1 x2goserver-xsession: 4.0.1.15-0~847~ubuntu14.04.1 VirtualBox 4.3.14 (from download.virtualbox.org) "Shared Clipboard" is set to "Bidirectional" for the VM $ cat /etc/x2go/x2goagent.options | grep -v '^#' | grep -v '^$' X2GO_NXAGENT_DEFAULT_OPTIONS="" X2GO_NXAGENT_DEFAULT_OPTIONS+=" -extension XFIXES" X2GO_NXAGENT_DEFAULT_OPTIONS+=" -nolisten tcp" Guest OS: Ubuntu 12.04.5 64-bit with precise HWE stack, the virtual kernel, and all the latest bugfix & security updates OS-provided XFCE virtualbox-guest-dkms: 4.1.12-dfsg-2ubuntu0.6 virtualbox-guest-utils: 4.1.12-dfsg-2ubuntu0.6 virtualbox-guest-x11: 4.1.12-dfsg-2ubuntu0.6 Configured according to: https://github.com/mikedep333/duckpan-vagrant/tree/duckduckhack-vm The aforementioned script is: /etc/X11/Xsession.d/98vboxadd-xclient (I'm sure a different script would be used for distros like CentOS which lack the /etc/X11/Xsession.d/ folder). Client system: Windows 8.1 64-bit with Update 1 and all the minor/monthly updates available X2GoClient 4.0.2.1+hotfix1+build3

2 1

Bug#1072: X2Go Client: top 24 pixels in fullscreen session do not respond to mouse clicks
by Chris Martin 09 Feb '21

09 Feb '21

Package: x2goclient Version: 4.0.5.1 I am trying to start a full screen X2Go session which 1. takes up the entire display, and 2. responds to my mouse clicks everywhere in the session, but cannot accomplish this with any combination of settings. Client OS: Debian Jessie / 8 / Stable, GNOME 3 desktop environment Client X2Go Client: 4.0.5.1 and 4.0.3.1 Server OS: Xubuntu 16.04 LTS Server x2goserver version: 4.0.1.19 Server x2goserver-xsession version: 4.0.1.19 When I choose "fullscreen", I get different behavior intermittently: 1. The client spawns across the entire screen but the *top panel inside the X2Go session* does not respond to any mouse clicks. I suspect the panel in my GNOME session running the X2Go client (which occupies the same pixels behind the panel inside the X2Go session) is stealing mouse focus. My mouse pointer turns black instead of white when I hover over the top 24 pixels or so, inside the X2Go session. 2. The client spawns what I would call a "maximized window". The top of the screen is still consumed by the title bar of the X2Go window, and the panel of the enclosing GNOME session in which the X2Go client is running. I have observed both cases 1 (most common) and 2 with X2Go Client 4.0.5.1, and only case 1 with X2Go client 4.0.3.1. When I choose "Display 1" in the Input/Output settings, the X2Go session displays only in the upper-left quadrant of my display; the rest of the screen is black. Thank you, Chris Martin

4 5

← Newer
1
2
3
4
5
6
7
8
...
14
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

x2go-dev September 2016