x2go-dev July 2023

x2go-dev@lists.x2go.org

3 participants
66 discussions

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

x2goagent Segmentation fault
by Petit Eric 16 Oct '23

16 Oct '23

Hi, I use x2goclient Mageia8 x86_64 and x2go server + desktopsharing on Raspeberry PI 400 Debian ARM64. x2goclient --version x2go-INFO-1> "Starting X2Go Client 4.1.2.2.. sudo apt list x2go* |grep installé x2godesktopsharing/oldstable,now 3.2.0.0-2+b1 arm64 [installé,] x2goserver-common/oldstable,oldstable,now 4.1.0.3-5 all [installé, ] x2goserver-desktopsharing/oldstable,oldstable,now 4.1.0.3-5 all [installé] x2goserver-extensions/oldstable,oldstable,now 4.1.0.3-5 all [installé] x2goserver-fmbindings/oldstable,oldstable,now 4.1.0.3-5 all [installé, ] x2goserver-printing/oldstable,oldstable,now 4.1.0.3-5 all [installé, ] x2goserver-x2goagent/oldstable,now 4.1.0.3-5 arm64 [installé, ] x2goserver-xsession/oldstable,oldstable,now 4.1.0.3-5 all [installé, ] x2goserver/oldstable,now 4.1.0.3-5 arm64 [installé] gdb x2goagent ./core Core was generated by `x2goagent -nolisten tcp -nolisten tcp -S -auth /home/pi/.Xauthority -shadow :0'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x0000007fbbb2a4e8 in Poller::updateDamagedAreas() () from /lib/aarch64-linux-gnu/libXcompshad.so.3 (gdb) bt #0 0x0000007fbbb2a4e8 in Poller::updateDamagedAreas() () from /lib/aarch64-linux-gnu/libXcompshad.so.3 #1 0x0000007fbbb2a7cc in Poller::getEvents() () from /lib/aarch64-linux-gnu/libXcompshad.so.3 #2 0x0000007fbbb28130 in NXShadowHasChanged () from /lib/aarch64-linux-gnu/libXcompshad.so.3 #3 0x00000055945e09d4 in ?? () #4 0x00000055945d9658 in ?? () #5 0x00000055945a3554 in ?? () #6 0x00000055945af830 in ?? () #7 0x0000005594584ca0 in ?? () #8 0x0000005594567dfc in ?? () #9 0x0000007fbb552e18 in __libc_start_main (main=0x55945679f0, argc=17, argv=0x7ffea69348, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=<optimized out>) at ../csu/libc-start.c:308 #10 0x000000559456810c in ?? () Backtrace stopped: not enough registers or memory available to unwind further

2 1

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

Bug#1445: pyhoca-cli fails to connect to suspended x2go session
by Randy Goldenberg 22 Aug '23

22 Aug '23

Package: pyhoca-cli Version: 0.6.1.2 Tag: patch pyhoca-cli fails to connect to suspended x2g0 sessions. $ pyhoca-cli --server my.x2go.server -t desktop -c openbox-session -g maximize -R NEWEST pyhoca-cli[13131] NOTICE: preparing requested X2Go session pyhoca-cli[13131] (PyHocaCLI) NOTICE: preparing requested X2Go session pyhoca-cli[13131] (x2gosessregistry-pylib) NOTICE: registering X2Go session Pyhoca-Client_Session... pyhoca-cli[13131] (x2goclient-pylib) NOTICE: initializing X2Go session... pyhoca-cli[13131] (x2gocontrolsession-pylib) NOTICE: connecting to [my.x2go.server]:22 /usr/lib/python3/dist-packages/Crypto/Cipher/blockalgo.py:141: FutureWarning: CTR mode needs counter parameter, not IV self._cipher = factory.new(key, *args, **kwargs) pyhoca-cli[13131] (PyHocaCLI) NOTICE: authentication has been successful pyhoca-cli[13131] (PyHocaCLI) NOTICE: give the X2Go session some time to come up... Traceback (most recent call last): File "/usr/bin/pyhoca-cli", line 455, in <module> thisPyHocaCLI.MainLoop() File "/usr/lib/python3/dist-packages/pyhoca/cli/frontend.py", line 702, in MainLoop self.resume_session(self.x2go_session_hash) File "/usr/lib/python3/dist-packages/pyhoca/cli/frontend.py", line 229, in resume_session if available_sessions is None: UnboundLocalError: local variable 'available_sessions' referenced before assignment client OS: Ubuntu 16.04.6 LTS server OS: Ubuntu 16.04.6 LTS server's version of the x2goserver package: x2goserver: 4.1.0.4 x2goserver-common: 4.1.0.4 x2goserver-desktopsharing: 4.1.0.3 x2goserver-extensions: 4.1.0.4 x2goserver-fmbindings: 4.1.0.4 x2goserver-printing: 4.1.0.4 x2goserver-xsession: 4.1.0.4 Patch attached. ----- End forwarded message -----

4 4

x2gokdrive build question
by Orion Poplawski 17 Jul '23

17 Jul '23

I'm working on packaging x2gokdrive for Fedora and I'm seeing the following in the configure log for the xorg x11 server: configure: WARNING: *********************************************** Neither HAL nor udev backend will be enabled. Input device hotplugging will not be available! *********************************************** Is this of any concern for kdrive? I do see that there is an explicit: --disable-config-hal \ --disable-config-udev \ so probably not. But it *seems* like input device hotplugging might be useful just judging by the name. But perhaps not since this is on the server end of things? Orion -- Orion Poplawski he/him/his - surely the least important thing about me IT Systems Manager 720-772-5637 NWRA, Boulder/CoRA Office FAX: 303-415-9702 3380 Mitchell Lane orion(a)nwra.com Boulder, CO 80301 https://www.nwra.com/

5 12

Bug#1610: x2goclient 4.1.2.3 build failure on Fedora rawhide
by Orion Poplawski 14 Jul '23

14 Jul '23

Package: x2goclient Version: 4.1.2.3 Updating the Fedora x2goclient package to 4.1.2.3 I get the following when building on Fedora rawhide: Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.qe1X0s + umask 022 + cd /builddir/build/BUILD + CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer ' + export CFLAGS + CXXFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer ' + export CXXFLAGS + FFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules ' + export FFLAGS + FCFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules ' + export FCFLAGS + VALAFLAGS=-g + export VALAFLAGS + RUSTFLAGS='-Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cforce-frame-pointers=yes -Clink-arg=-Wl,-z,relro -Clink-arg=-Wl,-z,now -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn' + export RUSTFLAGS + LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -Wl,--build-id=sha1 -specs=/usr/lib/rpm/redhat/redhat-package-notes ' + export LDFLAGS + LT_SYS_LIBRARY_PATH=/usr/lib64: + export LT_SYS_LIBRARY_PATH + CC=gcc + export CC + CXX=g++ + export CXX + cd x2goclient-4.1.2.3 + export PATH=/usr/lib64/qt5/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/sbin + PATH=/usr/lib64/qt5/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/sbin + /usr/bin/make -O -j6 V=1 VERBOSE=1 /usr/bin/make -f Makefile.man2html build make[1]: *** No rule to make target 'SHELL'. Stop. This seems to be related to these new items: @@ -52,13 +65,13 @@ # implementation to make implementation. # GNU make way. -MAKEOVERRIDES= +MAKEOVERRIDES = SHELL QT_VERSION INSTALL_DIR INSTALL_FILE INSTALL_SYMLINK INSTALL_PROGRAM RM_FILE RM_DIR DESTDIR PREFIX ETCDIR BINDIR SHAREDIR MANDIR QMAKE_BINARY LRELEASE_BINARY QMAKE_OPTS LDFLAGS LIBS # FreeBSD and NetBSD way. -.MAKEOVERRIDES= +.MAKEOVERRIDES = SHELL QT_VERSION INSTALL_DIR INSTALL_FILE INSTALL_SYMLINK INSTALL_PROGRAM RM_FILE RM_DIR DESTDIR PREFIX ETCDIR BINDIR SHAREDIR MANDIR QMAKE_BINARY LRELEASE_BINARY QMAKE_OPTS LDFLAGS LIBS # OpenBSD way. -.MAKEFLAGS= +.MAKEFLAGS = SHELL QT_VERSION INSTALL_DIR INSTALL_FILE INSTALL_SYMLINK INSTALL_PROGRAM RM_FILE RM_DIR DESTDIR PREFIX ETCDIR BINDIR SHAREDIR MANDIR QMAKE_BINARY LRELEASE_BINARY QMAKE_OPTS LDFLAGS LIBS all: build @@ -89,13 +102,14 @@ rm -fr $(CLIENT_DIR) clean_man: - make -f Makefile.man2html clean + $(MAKE) -f Makefile.man2html clean but I don't really understand why. This is with make 4.4.1. I don't see any problems with make 4.2.1. -- Orion Poplawski IT Systems Manager 720-772-5637 NWRA, Boulder/CoRA Office FAX: 303-415-9702 3380 Mitchell Lane orion(a)nwra.com Boulder, CO 80301 https://www.nwra.com/

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

x2go-dev July 2023