x2go-dev

x2go-dev@lists.x2go.org

5403 discussions

Re: [X2Go-Dev] Fedora 32 X2Go 4.1.0.3-6:Could not open default font 'fixed''
by Robert Kudyba 20 Aug '20

20 Aug '20

No luck: ./x2goglx glxinfo|grep -i open OpenGL vendor string: VMware, Inc. OpenGL renderer string: llvmpipe (LLVM 10.0.0, 256 bits) OpenGL version string: 3.0 Mesa 20.1.5 OpenGL shading language version string: 3.30 OpenGL context flags: (none) OpenGL extensions: [rkudyba@storm ~]$ ./x2goglx gazebo AL lib: (WW) alcCloseDevice: Releasing context 0x561a7f165b50 AL lib: (WW) alcSetError: Error generated on device (nil), code 0xa002 FWIW this was an issue with Gazeo 9 and this comment https://bugzilla.redhat.com/show_bug.cgi?id=1816487#c1 says: "A workaround is to override the session with environment variable XDG_SESSION_TYPE XDG_SESSION_TYPE=x11 gazebo" Whilst this comment: https://bugzilla.redhat.com/show_bug.cgi?id=1815270#c3 "It looks like it's an OGRE/Wayland issue. I found a similar error report from rviz here: https://github.com/ros-visualization/rviz/issues/1442 The work-around listed in the bug report works, and gazebo launches properly: QT_QPA_PLATFORM=xcb gazebo One way forward is to force gazebo to use xcb platform. I'll see if there's a way to do that in code so you don't have to use the environment variable." None of those made a difference. Here's some more debug upon starting gazebo with verbose option: [Err] [RenderEngine.cc:743] Unable to create glx visual [Wrn] [RenderEngine.cc:93] Unable to create X window. Rendering will be disabled [Wrn] [RenderEngine.cc:293] Cannot initialize render engine since render path type is NONE. Ignore this warning ifrendering has been turned off on purpose. [Err] [RenderEngine.cc:743] Unable to create glx visual [Wrn] [RenderEngine.cc:93] Unable to create X window. Rendering will be disabled [Wrn] [RenderEngine.cc:293] Cannot initialize render engine since render path type is NONE. Ignore this warning ifrendering has been turned off on purpose. [Wrn] [GuiIface.cc:122] X server does not support XInput 2 [Wrn] [GuiIface.cc:122] QXcbConnection: XCB error: 1 (BadRequest), sequence: 168, resource id: 78, major code: 130 (Unknown), minor code: 47 [Err] [GLWidget.cc:178] GLWidget could not create a scene. This will likely result in a blank screen. [Wrn] [Publisher.cc:142] Queue limit reached for topic /gazebo/default/physics/contacts, deleting message. This warning is printed only once. [Wrn] [Event.cc:61] Warning: Deleting a connection right after creation. Make sure to save the ConnectionPtr from a Connect call AL lib: (WW) alcCloseDevice: Releasing context 0x55b168a79810 AL lib: (WW) alcSetError: Error generated on device (nil), code 0xa002 On Thu, Aug 20, 2020 at 3:11 PM Ulrich Sibiller <uli42(a)gmx.de> wrote: > On Thu, Aug 20, 2020 at 5:21 PM Robert Kudyba <rkudyba(a)fordham.edu> wrote: > > > > Is there another step after running ninja? Still getting this error: > > Yes. After compilation you need to preload the resulting lib: > > The easiest way for that is this: > 1. copy build/src/gallium/targets/libgl-xlib dor some safe place > 2. write a small wrapper called "~/x2goglx" with this content: > #!/bin/sh > LD_LIBRARY_PATH=<your directory>/libgl-xlib:${LD_LIBRARY_PATH} exec "$@" > > (replace <your directory> with the path to where you copied the above > directory to) > > Then > $ chmod u+rx ~/x2goglx > > Then test with (should show OpenGL 1.4) > $ ~/x2goglx glxinfo > > Then run gazebo: > > $ ~/x2goglx gazebo > > > > > > gazebo > > AL lib: (WW) alcCloseDevice: Releasing context 0x55b6657b6d20 > > AL lib: (WW) alcSetError: Error generated on device (nil), code 0xa002 > > segfault at 20 ip 00007fe4d7081cc6 sp 00007fff0d0c1280 error 4 in > libOgreMain.so.1.9.0[7fe4d6e7d000+2f0000] > > Aug 20 11:19:11 storm kernel: Code: 00 5b 5d 41 5c 41 5d 41 5e c3 66 2e > 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 55 48 89 e5 41 56 49 89 fe 41 55 41 54 > 53 48 83 ec 60 <48> 8b 7f 20 64 48 8b 04 25 28 00 00 00 48 89 45 d8 31 c0 > 48 85 ff > > > > On Thu, Aug 20, 2020 at 11:17 AM Robert Kudyba <rkudyba(a)fordham.edu> > wrote: > >> > >> I never would've figured this out without your help! I take it these > warnings are safe to ignore? Also, should I CC the dev list? Or did you > intentionally remove it? > >> > >> WARNING: Library target 'GLESv2' has 'name_prefix' set. Compilers may > not find it from its '-lGLESv2' linker flag in the 'glesv2-uninstalled.pc' > pkg-config file. > >> Message: Configuration summary: > >> > >> prefix: /usr/local > >> libdir: lib64 > >> includedir: include > >> > >> OpenGL: yes (ES1: yes ES2: yes) > >> OSMesa: no > >> > >> GLX: Xlib-based (Gallium) > >> > >> EGL: no > >> GBM: no > >> EGL/Vulkan/VL platforms: x11 > >> > >> Vulkan drivers: no > >> > >> llvm: yes > >> llvm-version: 10.0.0 > >> > >> Gallium drivers: swrast > >> Gallium st: mesa > >> HUD lmsensors: no > >> > >> Shared-glapi: yes > >> > >> Build targets in project: 101 > >> WARNING: Project specifies a minimum meson_version '>= 0.46' but uses > features which were added in newer versions: > >> * 0.51.0: {'dep.get_variable'} > >> * 0.52.0: {'version arg in find_program'} > >> > >> Option buildtype is: release [default: debugoptimized] > >> Found ninja-1.10.0 at /usr/bin/ninja > >> WARNING: custom_target 'glcpp-parse.[ch]' has more than one output! > Using the first one. > >> WARNING: custom_target 'glsl_parser' has more than one output! Using > the first one. > >> WARNING: custom_target 'program_parse_tab.[ch]' has more than one > output! Using the first one. > >> (base) [root@storm build]# ninja > >> [187/945] Compiling C object > src/gallium/drivers/softpipe/libsoftpipe.a.p/sp_quad_blend.c.o > >> ../src/gallium/drivers/softpipe/sp_quad_blend.c: In function > ‘blend_fallback’: > >> ../src/gallium/drivers/softpipe/sp_quad_blend.c:245:46: warning: > ‘res[0][0]’ may be used uninitialized in this function > [-Wmaybe-uninitialized] > >> > >> ../src/gallium/auxiliary/gallivm/lp_bld_nir.h:242:27: warning: ‘result’ > may be used uninitialized in this function [-Wmaybe-uninitialized] > >> 242 | LLVMTypeRef arr_type = LLVMArrayType(LLVMTypeOf(values[0]), > value_count); > >> | > ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > >> ../src/gallium/auxiliary/gallivm/lp_bld_nir.c:168:4: warning: ‘undef’ > may be used uninitialized in this function [-Wmaybe-uninitialized] > >> 168 | assign_ssa(bld_base, ssa->index, ssa->num_components == 1 ? > vals[0] : lp_nir_array_build_gather_values(bld_base->base.gallivm->builder, > vals, ssa->num_components)); > >> | > ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > >> [945/945] Linking target src/gallium/targets/libgl-xlib/libGL.so.1.5.0 > >> > >> > >> On Thu, Aug 20, 2020 at 11:09 AM Ulrich Sibiller <uli42(a)gmx.de> wrote: > >>> > >>> Ahm, according to the meson source the error appears when it cannot > >>> find "meson.build" in the parent directory. I have just downloaded the > >>> mesa source (https://archive.mesa3d.org//mesa-20.1.6.tar.xz) and it > >>> contains the relevant file. > >>> > >>> So in detail you need to: > >>> 1. download the tarball > >>> 2. extract it > >>> 3. cd to the extracted dir: cd mesa-20.1.6 > >>> 4. mkdir build > >>> 5. cd build > >>> 6. meson .... > >>> 7. ninja > >>> ... > >>> > >>> Uli > >>> > >>> On Thu, Aug 20, 2020 at 5:00 PM Ulrich Sibiller <uli42(a)gmx.de> wrote: > >>> > > >>> > On Thu, Aug 20, 2020 at 4:41 PM Robert Kudyba <rkudyba(a)fordham.edu> > wrote: > >>> > > So yes to have to compile, but no to the first question on > uninstalling? > >>> > > >>> > exactly. But if the meson of fedora is incompatible to the mesa > source > >>> > you are out of luck for now. > >>> > > >>> > > Yes I am prompted by Fedora to run this when I ran the meson > command. But I'm still not following. I see here > https://docs.mesa3d.org/gallium/drivers/llvmpipe.html > >>> > > > >>> > > scons: *** No SConstruct file found. > >>> > > File "/usr/lib/python3.8/site-packages/SCons/Script/Main.py", line > 940, in _main > >>> > > > >>> > > Then: > >>> > > Alternatively, you can build it with meson with: > >>> > > mkdir build > >>> > > cd build > >>> > > meson -D glx=gallium-xlib -D gallium-drivers=swrast > >>> > > ninja > >>> > > > >>> > > So is this the meson command that I should replace with: > >>> > > meson -D glx=gallium-xlib -D gallium-drivers=swrast -D > platforms=x11 -D dri3=false -D dri-drivers="" -D vulkan-drivers="" -D > buildtype=release -D optimization=3 > >>> > > >>> > exactly. > >>> > > >>> > > I still get ERROR: Must specify at least one directory name. > >>> > > >>> > All the examples I have seen do NOT require a directory being > >>> > specified so I do not know what's going on here. I also do not have a > >>> > fedora to play with. > >>> > > >>> > Uli >

1 0

Re: [X2Go-Dev] Fedora 32 X2Go 4.1.0.3-6:Could not open default font 'fixed''
by Robert Kudyba 20 Aug '20

20 Aug '20

> > > > > On https://wiki.x2go.org/doku.php/wiki:development:glx-xlib-workaround > there's no Fedora/CentOS/Red Hat options. > > > > When I try this command: > > meson -D glx=gallium-xlib -D gallium-drivers=swrast -D platforms=x11 -D > dri3=false -D dri-drivers="" -D vulkan-drivers="" -D buildtype=release -D > optimization=3 > > > > ERROR: Must specify at least one directory name. > > > > What directory name should be used? > > > > Also a typo here: > > "the instructions below are valid for olter Mesa releases" > > Thx, fixed. In the very same paragraph basic compilation instructions > are linked. Simply replace the meson call mentioned there by the one > from above. > Does that mean I should uninstall the packages installed by Fedora via dnf? Do I really have to compile? Install package 'meson' to provide command 'meson'? [N/y] y * Waiting in queue... * Loading list of packages.... The following packages have to be installed: meson-0.54.0-1.fc32.noarch High productivity build system ninja-build-1.10.0-1.fc32.x86_64 Small build system with a focus on speed Proceed with changes? [N/y] y * Waiting in queue... * Waiting for authentication... * Waiting in queue... * Downloading packages... * Requesting data... * Testing changes... * Installing packages...

2 3

Fedora 32 X2Go 4.1.0.3-6:Could not open default font 'fixed''
by Robert Kudyba 20 Aug '20

20 Aug '20

I've seen the previous discussion about this happening on Gentoo from https://x2go-dev.x2go.narkive.com/eHuOYxSn/bug-884-nxagent-aborts-session-w… could this be similar? rpm -qa |grep x2go x2goagent-4.1.0.3-6.fc32.x86_64 x2goserver-common-4.1.0.3-6.fc32.noarch x2goserver-xsession-4.1.0.3-6.fc32.noarch x2goserver-4.1.0.3-6.fc32.x86_64 Warning: Cannot read keystroke file '/home/myuser/.x2go/config/keystrokes.cfg'. Info: using keystrokes file '/etc/x2go/keystrokes.cfg' Info: ignoring unknown keystroke action 'debug_tree'. Info: ignoring unknown keystroke action 'regions_on_screen'. Info: ignoring unknown keystroke action 'test_input'. Info: ignoring unknown keystroke action 'deactivate_input_devices_grab'. Currently known keystrokes: close_session : Ctrl+Alt+t switch_all_screens : Ctrl+Alt+f minimize : Ctrl+Alt+m resize : Ctrl+Alt+r defer : Ctrl+Alt+e ignore : Ctrl+Alt+BackSpace force_synchronization : Ctrl+Alt+j fullscreen : Ctrl+Shift+Alt+f viewport_move_left : Ctrl+Shift+Alt+Left viewport_move_up : Ctrl+Alt+Up viewport_move_right : Ctrl+Alt+Right viewport_move_down : Ctrl+Alt+Down Error: Aborting session with 'Could not open default font 'fixed''. Aug 19 09:30:04 /usr/bin/x2goruncommand[805082]: ERROR: command failed to execute

3 4

X2Go: The Gathering 2020 AKA V/RUS (2020-09-18 - 2020-09-20) will take place at Stuttgart's hackerspace "shackspace"
by Stefan Baur 18 Aug '20

18 Aug '20

Dear $ALL, As stated in the subject line, X2Go: The Gathering 2020 - AKA V/RUS, the Virtual/Remote User Symposium - will take place at Stuttgart's hackerspace "shackspace", from Friday afternoon, 2020-09-18, to Sunday afternoon/evening, 2020-09-20. X2Go: The Gathering is the annual event where users, admins, and developers (including the i18n volunteers) of X2Go meet face to face, to discuss current X2Go-related issues, fix open bugs, and have a good time getting to know each other. As there is some overlap between X2Go, Arctica, and orca e.V., you can expect to meet members of those groups as well. Due to the Covid-19 pandemic, this year's X2Go: The Gathering will be a hybrid event with minimal on-site participation. We will be live-streaming the event, probably via Jitsi or BigBlueButton, and most likely we will have a YouTube stream going on as well. Links to the streams will be posted on <http://wiki.x2go.org/doku.php/events:x2go-gathering-2020> each day before the stream begins. *ATTENTION!* If you're interested in joining us *physically*, please contact <mailto:X2Go-ML-1@baur-itcs.de> with the text "The Gathering" somewhere in the subject and bug me publicly on the X2Go-Project list if you don't receive a confirmation by e-mail after a day or two. We will not be providing accomodation this year (so if you cannot commute daily, you will have to look for a hotel/hostel room yourself), *but we still need your contact info* if you wish to take part in person, due to current Covid-19 health regulations. Also, you will be required to wear a non-medical everyday mask or comparable mouth and nose cover (of course, better masks like N95/KN95/FFP2/FFP3 are okay as well, as long as they do not have an exhalation valve), both when using public transport (and while waiting at the platforms/stops), as well as inside shackspace (you will likely be allowed to take the mask off while sitting at your desk, but we cannot guarantee that yet). For joining us *virtually*, you can join in any time, even on short notice, no sign-up required (it would still be nice if you'd let us know in advance, so we can make sure we have sufficient server and streaming capacity). We will be updating the Wiki page <http://wiki.x2go.org/doku.php/events:x2go-gathering-2020> as more information becomes available. As this year's event is a hybrid event with minimal on-site participation, there is not really a need for event sponsorships. However, if you're a company that had planned to sponsor the event, we'd appreciate it if you'd redirect the money to some paid work on X2Go instead. A list of companies/individuals available for this can be found here: <https://wiki.x2go.org/doku.php/doc:professional-support> CFD.direct, one of our long-time sponsors (<https://wiki.x2go.org/doku.php/doc:sponsors>), has already done so - and not only that, they have increased their funding from 700 EUR, as originally planned, to 1000 EUR, as you can read here: <https://wiki.x2go.org/doku.php/events:x2go-gathering-2020#sponsoring>. We will be pooling their sponsorship money with another donation by KLO Ingeniería Informática, so we will have 1100 EUR at our disposal. This money will be used to try to tackle the long-standing clipboard issues in the NX-libraries. If you want to add money into that pool, or want to sponsor other X2Go-related work, again, please see the above list of companies/individuals available for such work. Sincerely, Stefan Baur, "X2Go: The Gathering" event organizer -- 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

1 0

Bug#1464: x2goclient 4.1.2.2 version does not work with Pageant SSH authentication agent
by saion.chatterjee＠siemens.com 04 Aug '20

04 Aug '20

Package: x2goclient Version: 4.1.2.2 With the latest x2goclient version available as of today ( x2goclient 4.1.2.2-2020.02.13 ), user faces authentication error while trying to login using Pageant SSH agent. The error message received is: "Access denied for 'publickey'. Authentication that can continue: publickey Access denied for 'none'. Authentication that can continue: publickey" The error does not happen with the previous version of x2goclient. Tried and tested with x2goclient 4.1.2.0 and it works fine. Pageant version used is: Pageant Release 0.73 The client's OS: 64-bit x86 Windows 10 The server's OS: Ubuntu 19.04 best regards, Saion

2 3

Bug#1403: Add packages for openSUSE Leap 15.1
by Tristan Miller 30 Jul '20

30 Jul '20

Package: x2goclient Version: 4.1.2.2 Tags: rpm-packages The repository at <http://packages.x2go.org/> contains packages for openSUSE Leap 15.0, which has end of life on 2019-11-25. Please consider adding packages for the current version of the OS, openSUSE Leap 15.1, which was released on 2019-05-22 and will be supported until 2020-11-22. I've filed this bug against x2goclient but the same request applies to x2goserver and ancillary x2go packages.

1 3

Bug#1358: x2goclient for openSUSE 15.0 is missing
by Tristan Miller 30 Jul '20

30 Jul '20

Package: x2goclient Version: 4.1.2.2 The x2goclient package for openSUSE Leap 15.0 seems to have gone missing from the official repository at <http://packages.x2go.org/opensuse/15.0/main/x86_64/>. It has been gone since at least December 2018.

1 2

Bug#1491: Add packages for openSUSE Leap 15.2
by Tristan Miller 29 Jul '20

29 Jul '20

Package: x2goclient Version: 4.1.2.2 Tags: rpm-packages The repository at <http://packages.x2go.org/opensuse> contains packages for openSUSE Leap 15.1, which has end of life on 2020-11-22. Please consider adding packages for the current version of the OS, openSUSE Leap 15.2, which was released on 2020-07-02 and will be supported until 2021-12-31. I've filed this bug against x2goclient but the same request applies to x2goserver and ancillary x2go packages.

1 0

KDrive does not seem to honor compression settings in X2GoClient?
by Stefan Baur 27 Jul '20

27 Jul '20

Hi List, hi Alex, Same environment as for the ten previous issues/oddities ... This time, I tried out "Connect to Windows Terminal Server". In NX mode, I can set the compression to "nopack", and it does have an effect. But it looks like choosing "nopack" when KDrive is selected has no effect. With "16m-jpeg" in NX mode, but not with "nopack", I am getting nasty JPEG artifacts when moving a window around. In KDrive, these artifacts are always there, no matter what I select. I have attached two screenshots, one with the contrast enhanced so the issue is easier to spot. Is this intentional? If so, "compression" should be greyed out in KDrive mode. But, on the other hand, those artifacts are annoying, so we need to make them go away somehow. Should I file a bug? Kind Regards, Stefan Baur -- 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

2 1

Ten X2Go-KDrive bugs/oddities
by Stefan Baur 27 Jul '20

27 Jul '20

Hi List, hHi Alex, Lately I was able to test a few more things with X2Go-KDrive, and I encountered some bugs/oddities with it. Maybe you could comment below which issues I should file as a bug, and what further info (like, screenshots, package versions, content of certain config files, ...) I should try to gather before filing it, to make debugging/fixing it easier? All tests were performed with an Ubuntu 18.04 LTS Client; and X2GoClient from the stable repository. The host ran on Debian 10.4, and was using the X2Go heuler repository, with the following X2Go-related packages: ii libx2go-log-perl 4.1.0.4-0x2go1.2~git20200228.1815+10.heuler.1 all Perl X2Go::Log package ii libx2go-server-db-perl 4.1.0.4-0x2go1.2~git20200228.1815+10.heuler.1 amd64 Perl X2Go::Server:DB package ii libx2go-server-perl 4.1.0.4-0x2go1.2~git20200228.1815+10.heuler.1 all Perl X2Go::Server package ii x2go-keyring 2019.08.21~git20190824.119+11.heuler.1 all GnuPG keys of all X2Go developers and the X2Go archive ii x2goserver 4.1.0.4-0x2go1.2~git20200228.1815+10.heuler.1 amd64 X2Go server ii x2goserver-common 4.1.0.4-0x2go1.2~git20200228.1815+10.heuler.1 amd64 X2Go Server (common files) ii x2goserver-extensions 4.1.0.4-0x2go1.2~git20200228.1815+10.heuler.1 all X2Go Server (extension support) ii x2goserver-fmbindings 4.1.0.4-0x2go1.2~git20200228.1815+10.heuler.1 all X2Go Server (file manager bindings) ii x2goserver-printing 4.1.0.4-0x2go1.2~git20200228.1815+10.heuler.1 all X2Go server (printing support) ii x2goserver-x2goagent 4.1.0.4-0x2go1.2~git20200228.1815+10.heuler.1 amd64 X2Go Server's X2Go Agent Xserver ii x2goserver-x2gokdrive 4.1.0.4-0x2go1.2~git20200228.1815+10.heuler.1 amd64 X2Go Server's X2Go KDrive Xserver ii x2goserver-xsession 4.1.0.4-0x2go1.2~git20200228.1815+10.heuler.1 all X2Go Server (Xsession runner) ii xserver-x2gokdrive 0.0.0.1-0x2go1~git20200120.183+10.heuler.1 amd64 KDrive graphical server backend for X2Go Server ii libnx-x11-6:amd64 2:3.5.99.22-0~git20190928.3526+10.heuler.1 amd64 nxagent's libNX_X11 client-part library ii nx-x11-common 2:3.5.99.22-0~git20190928.3526+10.heuler.1 all nx-X11 (common files) ii nxagent 2:3.5.99.22-0~git20190928.3526+10.heuler.1 amd64 Nested Xserver (aka NX Agent) supporting the NX compression protocol First issue/oddity: No matter which Desktop Environment is being used on the remote end, the local client window seems to snap to the top left position in an 800x600 resolution (or maybe even smaller, like 640x480), then it resizes to the requested size. This can be seen during resume, where the resume happens on the 800x600 (or whatever) resolution, then the screen is resized, and you see "garbage" on the screen (cloned sections of the client window content), until it redraws the entire screen after resizing it properly. This takes about a second or so. This may also be the reason why in one particular situation (during another test, on a different setup) I saw the KDrive window getting stuck at that small size in the upper left corner - probably the "maximize" command didn't reach the window manager, or there was no window manager present, or something like that. Second issue/oddity: Only roughly every second attempt to resize the client-side KDrive window using the mouse works. The other attempts have it snap back to where it originally was, once you let go of the mouse button. Third issue: At least in most of the desktop environments tested, both keyboard autodetection AND keyboard manual selection fails, so you're stuck with a US keyboard inside the session. The notable exception is GNOME, here, keyboard settings work, even in autodetection mode! Fourth ... well, oddity: In Fullscreen sessions, the top-of-the-screen Config Bar's Minimize Button does not work unless fullscreen mode has been toggled off and on again. Fifth issue: The modes "Published Application" and "XDMCP" are selectable with KDrive, but do not do anything useful; "Single Application" is only useful together with KDrive when the application in question has a fullscreen mode (like "rdesktop -f") Sixth issue: The top-of-the-screen Config Bar has a button "Disconnect". This should be named "Suspend" (or "Disconnect and suspend"), to be more in line with current X2Go terminology, and to make it more clear to the user that this isn't terminating the session, but rather suspending it. Also, Ctrl-Alt-T should suspend the session just like in classic NX mode, but currently does nothing. Seventh issue: LXQt complains on session startup that "global keyboard shortcut Ctrl-Alt-D for Desktop could not be registered" (Popup message) Eight issue: In Fullscreen mode (but not in windowed mode!), when using LXQt, MATE, XFCE or KDE, clicking the "Disconnect" button in the top-of-the-screen Config Bar does suspend the session, but any attempts at reconnecting lead to a client-side abort. The only way to recover is to either start X2GoClient with --no-autoresume, and terminating the session from the session chooser, or to log in via ssh and issue a x2goterminate-session command with the corresponding session ID. Ninth issue: KDE complains on session startup that I should enter Admin credentials for configuring a system update proxy? Tenth issue: GNOME complains on session startup that I should enter Admin credentials to update system repositories. (This popup appears even twice.) Kind Regards, Stefan Baur -- 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

2 1

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

x2go-dev