x2go-dev June 2020

x2go-dev@lists.x2go.org

13 participants
93 discussions

Bug#1297: do not look for keys when one is supplied already
by nounce＠posteo.net 08 Jan '24

08 Jan '24

Package: python-x2go Version: 0.5.99.0 Tag: patch When a server and no profile is selected and a ssh-key is provided python-x2go will ignore the provided ssh key and ask for a password instead. $ mkdir ~/.x2go $ docker run -it -d -p 2222:22 --name=x2go quay.io/tatsuya6502/x2go:latest $ docker logs x2go | tail -n +2 > ~/.x2go/x2go-key $ pyhoca-cli --server localhost --ssh-key ~/.x2go/x2go-key -p 2222 -N -c xclock --user docker

3 2

Bug#1298: KeyError: '6ab639d6-5521-11e8-a326-54ee759b5b41' in registry.py
by Mike Gabriel 08 Jan '24

08 Jan '24

Package: src:python-x2go Version: 0.6~git I recently saw a crash in PyHoca-CLI: Traceback (most recent call last): File "/home/mike/MyDocuments/4projects/x2go-upstream/pyhoca-cli/x2go/registry.py", line 122, in __call__ return self.registry[session_uuid] KeyError: '6ab639d6-5521-11e8-a326-54ee759b5b41' It came when I issued a "reboot" from within the X2Go session on the remote host. More a reminder to myself to try/except around it. Mike -- DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby mobile: +49 (1520) 1976 148 landline: +49 (4354) 8390 139 GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31 mail: mike.gabriel(a)das-netzwerkteam.de, http://das-netzwerkteam.de

1 1

Bug#1184: crucial packages missing in opensuse repo
by Alberto Bursi 08 Jan '24

08 Jan '24

Package: python-x2go x2goclient Version: not-relevant The x2go repo of opensuse leap (version 42.1 and 42.2) lacks very important packages like python-x2go (pyhoca GUI/CLI can't work without) or x2goclient So it's basically impossible to install a client application without using OBS (Opensuse's third party repo). See here: http://packages.x2go.org/opensuse/42.2/main/x86_64/ It seems in your repo for opensuse 13.2 these packages exist. http://packages.x2go.org/opensuse/13.2/main/x86_64/

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

loginctl 'enable-linger' causes systemd --user to respawn on boot
by Montjoy, Robert (montjoy) 28 Sep '23

28 Sep '23

Hi. At one time "loginctl enable-linger" was added to the x2gostartagent to make sure the systemd did not kill the x2go process on disconnect. This has had the probably undesired affect of having systemd --user username being executed on boot for every x2go user. At the last boot about 70 processes (one for systemd and one for pam) were spawned. This is probably not what we want. Is there a better way to handle the systemd termination issue? Should something like systemd-run --scope --user x2goagent ..... be used instead? Or can x2go cleanup this entry on termination? Maybe have x2gocleansessions do it? Note: I will probably cleanup /var/lib/systemd/linger on boot by executing rm -f /var/lib/systemd/linger/* but that it is more of a "hammer" approach than anything else. Thanks in advance. Rob

3 2

← Newer
1
2
3
4
5
6
7
8
9
10
Older →

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

x2go-dev June 2020