<div dir="ltr"><div>Hi Markus,<br></div><div><br></div><div>check your env vars, specifically XDG_SESSION_TYPE will tell you wayland or x11 ..... as for versions dpkg -l | grep wayland might get you there.</div><div><br></div><div>x2go doesn't work with wayland at all unless that has changed recently, so the server end always needs to be x11. Remembering wayland is a moving target. Largely though it depends on how you've configured your target session. If you are running kdrive that is its own manager seperate to both wayland and x11.<br></div><div><br></div><div>On a wayland client machine, the client runs in the x11 compatibility layer (xwayland) you can list xwayland based windows with xlsclients -l</div><div><br></div><div>arch doco has some good general info on wayland <a href="https://wiki.archlinux.org/title/wayland">https://wiki.archlinux.org/title/wayland</a></div><div><br></div><div>sai<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, 5 Jun 2024 at 12:10, Sagittarius-A Black Hole <<a href="mailto:nigratruo@gmail.com">nigratruo@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi all,<br>
<br>
using QT_QPA_PLATFORM=xcb does fix the issue for me, I can log in and<br>
use X2goclient.<br>
<br>
This is from a Debian Stable (Bookworm) laptop running Plasma (KDE) to<br>
a server running the very same software. How can I find the version of<br>
the components being used?<br>
At this point, I'm not even sure anymore if I'm still using some X11<br>
components or just wayland. I know there is a compatibility layer too,<br>
which makes it more confusing.<br>
I would assume that X2go (based on certain X11 libs (NX / Nomachine)<br>
does not even work without that compatibility layer or am I mistaken<br>
about that?<br>
<br>
Thank you for the workaround, it makes my life a lot easier, as I<br>
depend on X2go for daily terminal server use.<br>
<br>
Thanks,<br>
<br>
Markus<br>
<br>
<br>
On Wed, 22 May 2024 at 15:31, sairuk <<a href="mailto:sairuk@gmail.com" target="_blank">sairuk@gmail.com</a>> wrote:<br>
><br>
> on a wayland based client machine QT_QPA_PLATFORM=xcb does permit the client to run somewhat, however when I was testing this some time ago two problems resulted in an unusable experience<br>
> - client window resizing eventually stopped worked i.e dragging, fullscreen etc<br>
> - keyboard input was lost in the client window<br>
><br>
> arguably these may have the same root cause, my testing was only out of curiosity so it wasn't exhaustive. I eventually reverted to X11 for this and other performance reasons generally<br>
><br>
> Closing the client whilst running on wayland and restarting the client worked for a time then the same problems would occur.<br>
><br>
> Client machine was KDE, I am not sure what their wayland implementation was at the time.I have not motivation to move to wayland as x2go is my primary interface locally.<br>
><br>
> sai<br>
><br>
><br>
> On Wed, 22 May 2024 at 20:15, Ulrich Sibiller <<a href="mailto:ulrich.sibiller@gmail.com" target="_blank">ulrich.sibiller@gmail.com</a>> wrote:<br>
>><br>
>> Hm,<br>
>><br>
>> is this bug about the x2goclient or is about NX or even kdrive? A lot<br>
>> of guessing here....<br>
>><br>
>> On Stackoverflow<br>
>> (<a href="https://stackoverflow.com/questions/21488072/what-is-the-use-of-various-qt-platform-plugins" rel="noreferrer" target="_blank">https://stackoverflow.com/questions/21488072/what-is-the-use-of-various-qt-platform-plugins</a>)<br>
>> I find this regarding QT_QPA_PLATFORM:<br>
>><br>
>> xcb - Runs on an X11 server and is integrated into the X11 windowing<br>
>> environment. Generally it won't behave correctly without a window<br>
>> manager running as well. Can be made to work on Windows, given a<br>
>> Windows implementation of xlib, if you want to, say, serve<br>
>> applications from a Windows server to X11 thin terminals (typically<br>
>> Unix boxes).<br>
>><br>
>> So if the user has Wayland this is the wrong setting for the client<br>
>> side, at least for the x2go client qt code. Depending on XWayland<br>
>> seems wrong to me here.<br>
>><br>
>> Clients inside the nx session are talking to the remote X server and<br>
>> would require Xwayland. So I _think_ the only component that should<br>
>> run with XWayland is the nxproxy. Setting the var you mentioned will<br>
>> have the side effect of nxproxy finding the XWayland X-server that was<br>
>> started for x2goclient. So a quick test would be to replace nxproxy by<br>
>> a wrapper script that runs nxproxy with XWayland. I have no experience<br>
>> in this wayland stuff, so I may be totally wrong. Until now I was<br>
>> under the impression that XWayland is starts automatically if a client<br>
>> tries to open a Display.<br>
>><br>
>> Uli<br>
>><br>
>><br>
>> On Wed, May 22, 2024 at 8:15 AM Mike Gabriel<br>
>> <<a href="mailto:mike.gabriel@das-netzwerkteam.de" target="_blank">mike.gabriel@das-netzwerkteam.de</a>> wrote:<br>
>> ><br>
>> > HI<br>
>> ><br>
>> > On Mo 20 Mai 2024 21:34:47 CEST, Ulrich Sibiller wrote:<br>
>> ><br>
>> > >> Hi,<br>
>> > >><br>
>> > >> I can't troubleshoot this issue. I have removed X2goclient from the<br>
>> > >> Debian Stable (Bookworm) install, including all config, but when<br>
>> > >> installing it fresh, it still does crash with a Segsev, is this bug<br>
>> > >> known? I can't use X2go anymore on Linux, it just fails, without a way<br>
>> > >> to find out what breaks. This issue has blocked me for many months<br>
>> > >> now, it works on Windows, but most of my machines are running Linux.<br>
>> > >><br>
>> > >> Anybody have an idea what I can try next?<br>
>> > >><br>
>> > >> Thanks,<br>
>> > >><br>
>> > >> Markus<br>
>> ><br>
>> > > Hello,<br>
>> > ><br>
>> > > your bug report is a bit "unspecific". What desktop environment / window<br>
>> > > manager are you using? What kind of session? Where are you connecting to?<br>
>> > > How is your session configured? Have you tried pyhoca-cli and / or<br>
>> > > pyhoca-gui?<br>
>> > ><br>
>> > > Uli<br>
>> > ><br>
>> > > On Mon, May 20, 2024 at 3:54 AM Sagittarius-A Black Hole <<br>
>> > > <a href="mailto:nigratruo@gmail.com" target="_blank">nigratruo@gmail.com</a>> wrote:<br>
>> > ><br>
>> ><br>
>> > Maybe it is about this issue?<br>
>> > <a href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042816" rel="noreferrer" target="_blank">https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042816</a><br>
>> ><br>
>> > What is the best approach to address this. As X2Go Client interacts<br>
>> > with the remote X session, it surely would make sense to launch the<br>
>> > complete X2Go Client process via QT_QPA_PLATFORM=xcb and require<br>
>> > XWayland to run. Is that a viable approach? Where should we enforce<br>
>> > that (that being the switched from Wayland display to X11 display)?<br>
>> ><br>
>> > Mike<br>
>> > --<br>
>> ><br>
>> > DAS-NETZWERKTEAM<br>
>> > c\o Technik- und Ökologiezentrum Eckernförde<br>
>> > Mike Gabriel, Marienthaler Str. 17, 24340 Eckernförde<br>
>> > mobile: +49 (1520) 1976 148<br>
>> > landline: +49 (4351) 850 8940<br>
>> ><br>
>> > GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31<br>
>> > mail: <a href="mailto:mike.gabriel@das-netzwerkteam.de" target="_blank">mike.gabriel@das-netzwerkteam.de</a>, <a href="http://das-netzwerkteam.de" rel="noreferrer" target="_blank">http://das-netzwerkteam.de</a><br>
>> ><br>
>> _______________________________________________<br>
>> x2go-user mailing list<br>
>> <a href="mailto:x2go-user@lists.x2go.org" target="_blank">x2go-user@lists.x2go.org</a><br>
>> <a href="https://lists.x2go.org/listinfo/x2go-user" rel="noreferrer" target="_blank">https://lists.x2go.org/listinfo/x2go-user</a><br>
<br>
<br>
<br>
--<br>
Por sperto kaj lerno ne sufiĉas eterno.<br>
</blockquote></div>