x2go-dev

x2go-dev@lists.x2go.org

1 participants
5399 discussions

Bug#1475: Fwd: Error on iconize
by Max V 11 Sep '20

11 Sep '20

Package: x2goclient Version: 4.0.5.1 Hello, my x2go server run on LXDE server, all ok. My client is Cinnamon, When I start all is ok, when I minimize the window, clicking in the top right, the windows is minimized, but it's dimension become about 2x25 pixels, so even I restore, I can't see anything and I can't maximize it anymore. I made a screenshot, it's that sort of capital I in the center of the screen. My Cinnamon version is 3.4.6 My x2goclient is 4.0.5.1 Best regards Max

3 4

Bug#1493: Fullscreen client gets minimized when switching virtual desktops on Windows 10
by Tyler Anderson 06 Sep '20

06 Sep '20

Package: x2go-client Version: 4.1.2.2 I am using the x2go client in full-screen mode on one of my virtual desktops on windows 10. I can swipe through my virtual desktops with a four-fingered swipe on the trackpad or by pressing Win+ctrl+left/right. When I have the client in fullscreen, if I swipe to a different desktop and then back to the desktop containing the client, it has become minimized. It does not maintain its full-screen mode when switching virtual desktops. The same also occurs if I enter task view with a four-finger swipe up, the window is minimized when I return.

1 0

Windows 7 x2go Client Access Violation Connecting to CentOS 6 server using GNOME - Crashes in Latest Version Only
by OwN-3m-All 03 Sep '20

03 Sep '20

Hi All, I recently upgraded my x2go client from version 4.1.2.0 (Qt - 4.8.6) to 4.1.2.2 (Qt - 4.8.6). When I try to connect to one of my servers running CentOS 6 with the latest updates, my x2go client on Windows 7 x64 SP1 immediately crashes. In fact, the connection never even makes it to the remote server for processing according to the logs on the remote server, as the client forces the connection closed (due to it crashing). I even installed the debug version of the x2go client, and it doesn't output anything of value before it crashes either. Plus, it doesn't appear to log anything to a file either? After installing the old version of x2go in a different directory than the newest version, I am able to connect just fine to the server using the old x2go client version. Something broke from the update. What I can tell you is that I get this error message when debugging the crash through Visual Studio: https://serv1.dragndropz.com/user_images/2020_09_03/2256_oERSXY_2020-09-031… Also, I was able to replicate this issue in a virtualized instance of Windows 7 x64 SP1 via VirtualBox. The CentOS 6 server I'm trying to connect to isn't running anything special. However, it is one of my oldest servers, and as a result, it is the only server that is still running GNOME (usually I use MATE or XFCE). I'm using a non-standard ssh port, a private key that uses a passphrase, and "Session type" is set to GNOME. I've disabled sound support and client side printing support to make sure the crash didn't have anything to do with these features. Any chance someone could look into this further? For now, I will just run both versions of x2go side-by-side. Thanks OwN

1 0

Bug#1476: x2goclient interface code needs refactoring to make it more accessible and make improvements easier to implement and test
by Dave Chamberlin-Kidd 03 Sep '20

03 Sep '20

Package: x2goclient Version: 4.1.2.3 Severity: wishlist Tag: patch There are a number of minor issues, oddities and limitations with the current x2goclient gui which would be good to fix, resolve and improve on. Like all projects however the core team have more important issues to resolve. The code in its current state is difficult to understand and amend and as it has no tests it is risky for developers to make functional changes unless they spend a lot of time getting to know the code and doing extensive manual testing. Attached are 10 small refactorings which start extracting out some of the code into smaller functions. As the code is separated out it becomes easier to understand and change. There are no functional changes in these patches, nor do they attempt or claim to fix any known issues. On their own the benefit of these patches is limited however the hope is that over time I will be able to submit more refactorings as I learn more and then start fixing issues and improving the UI. Extracting out functions is just one of many techniques that can be used to make code cleaner but in my experience it's a good one to start with. It should also be noted that sometimes code is extracted "as is" even when it is clear further refactoring can be done to improve things, this is by design in order to keep risk and size of patches to a minimum. Cheers Dave

2 3

Bug#1492: Package: Multiple monitors / Xinerama crashes
by John Watson 02 Sep '20

02 Sep '20

Package: x2goserver-xsession Version: 4.1.0.3-5 NOTE: this is CentOS8's epel8.playground.noarch package Remove server environment: OS: CentOS 8 - 8.1.1911 (Core) x2goserver-xsession: x2goserver-xsession-4.1.0.3-5.epel8.playground.noarch nx-libs: nx-libs-3.5.99.23-1.epel8.playground.x86_64 Local server environment: OS: MacOS Catalina 10.15.6 x2go: X2Go Client v. 4.1.2.2 (Qt -4.8.7) When I invoke `xterm` or any other X11 app over x2go client on the laptop alone (not connected to any external monitors), everything works without any hiccups. With multiple monitors connected, however, an existing session will only render a blank screen locally, and the mouse pointer will disappear. When *creating* a new session, the remote server process crashes with the following in /var/log/messages (CentOS equivalent of /var/log/syslog) Aug 30 14:08:39 <server host> kernel: [62624.705481] x2goagent[2960736]: segfault at 0 ip 0000000000000000 sp 00007ffd426f92e8 error 14 in nxagent[5655328cb000+437000] This looks strikingly similar to the bug described in https://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=943, but it's now 2020 and I'm on the latest yum repo available to CentOS 8... I've added "+xinerama" to X2GO_NXAGENT_DEFAULT_OPTIONS in /etc/x2go/x2goagent.options and enabled it in the x2go client as well. Should I attempt playing with building nx-libs from source myself and installing?

1 0

x2goclient resumes session with wrong X-Server options
by Maarten Boekhold 02 Sep '20

02 Sep '20

Hi all, (I tried to sent this twice to x2go-user, but after more than 24 hours it still hasn't shown up there) Windows 10, x2goclient 4.1.2.2 When resuming a "paused" x2Go session, x2goclient is using the wrong X-Server settings. I have configured my x2goclient with the following settings for X.Org Server settings: **X.Org Server settings** [X] use custom X-Server Executable: C:/Program Files (x86)/x2goclient/VcXsrv/vcxsrv.exe [ ] start X-Server on X2Go Client start Window mode: -screen 0 %wx%h -notrayicon -clipboard -keyhook \ -nowinkill -nopn -silent-dup-error Fullscreen mode: -fullscreen -notrayicon -clipboard -keyhook \ -nowinkill -nopn -silent-dup-error Single application: -multiwindow -notrayicon -clipboard \ -keyhook -nowinkill -nopn -silent-dup-error Whole display: -nodecoration -notrayicon -clipboard -keyhook \ -nopn -silent-dup-error -screen 0 @ My x2goclient session is configured as: **Session preferences: Input/Output** [ ] Fullscreen [ ] Custom Width (greyed out 3696) Height (greyed out 2160) [X] Use whole display [ ] Maximum available Display: 2 When I start a new x2Go session, it correctly runs the X-Server with the "Whole display" command: "C:\Program Files (x86)\x2goclient\VcXsrv\vcxsrv.exe" \ -nodecoration -notrayicon -clipboard -keyhook -nowinkill \ -nopn -silent-dup-error screen 0 @2 :0 But if I then "pause" this session and reconnect, x2goclient uses the "Window mode" command line options instead: "C:\Program Files (x86)\x2goclient\VcXsrv\vcxsrv.exe" \ -screen 3696x2160 -notrayicon -clipboard -keyhook \ -nowinkill -nopn -silent-dup-error :0 This is really annoying. I suspect this has something to do with the code around line 4442 in onmainwindow.cpp, but I've not been able to figure out the exact details yet. I've tried to debug this by running x2goclient.debug.exe --debug, but there's an issue here. When running the debug version, the "Use whole display" option is not available in the session settings tab: **Session Input/Output with x2goclient.debug.exe --debug** [ ] Fullscreen [ ] Custom Width (greyed out 3696) Height (greyed out 2160) [ ] Maximum available See the "Use whole display" option missing in front of the "Maximum available" radio box. It's almost as if the debug build included in this distribution is of an older x2goclient version (but it shows the correct version number in the About dialog). I hope that based on the provided information a fix can be created for this issue? Regards, Maarten

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

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

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

x2go-dev