x2go-user April 2023

x2go-user@lists.x2go.org

7 participants
10 discussions

Many segfault across multiple desktops via X2go server on EL9 systems
by Tom Crane 02 May '23

02 May '23

I originally submitted a detailed bug report at the Mate Desktop issues Github page here https://github.com/mate-desktop/mate-desktop/issues/553. I subsequently discovered that other desktops are similarly affected. All of them experienced segfaults or kernel traps in parts of their components, particularly in the Marco window manager that Mate uses. I have also tried Gnome, Kde, xfce, Cinnamon & Icewm desktops, again on a Centos Stream 9 system. Similar results were found on an Alma 9 system so I do not believe the problem is specific to the 'upstream' / lesser-tested nature of CS9. Apart from Icewm which remained usable even with the segfaults, the other desktops (particularly Mate which we use a lot for remote working) are rendered unusable by this problem. None of our Centos 7 systems have this problem. I am running out of ideas to diagnose/fix this problem. Any thoughts? Thanks Tom Crane X2go etc. packages version details (as installed from Epel 9 repository), nxagent-3.5.99.26-6.el9.x86_64 nx-libs-3.5.99.26-6.el9.x86_64 x2goagent-4.1.0.3-17.el9.x86_64 x2goserver-4.1.0.3-17.el9.x86_64 x2goserver-common-4.1.0.3-17.el9.noarch x2goserver-xsession-4.1.0.3-17.el9.noarch

3 4

Font display issues with Motif and X2go
by Michael Eager 30 Apr '23

30 Apr '23

I have a GUI which gives different output when run under X2go and ssh -X or vnc. In the attached image, the left window is running under X2go. The text overflows the buttons, text at ends of lines are truncated, and some text overlays adjacent text. The right window is running remotely using "ssh -X". When I connect to the remote system using tigervnc, the GUI displays correctly. This looks like a problem with X2Go's X rendering. Is there anything I can do to fix this? -- Michael Eager

1 0

How to make the picture smoother
by wc yeah 17 Apr '23

17 Apr '23

hi all， I'm using x2goclient v.4.1.2.2 for windows, connecting to CentOS 7.9 x2goserver 4.1.0.3. When I open the CAD software on the remote desktop and drag my model, the picture is not smooth, and the image display is very jumpy. The client parameters I use are Connection speed: ADSL Compression Method: 256-jpeg Image quality: 0 display width: 2560 height: 1449 DPI: 80 I tried adjusting these parameters and found that there is not much improvement, but if I shrink the remote desktop window, it will become very smooth. Is there any method or parameter setting to make the picture smooth? Hope someone can help me. Thanks. --Yeahwc

2 3

Re: [X2Go-User] Resume/restoration of windows to linux workspaces
by webman＠manfbraun.de 15 Apr '23

15 Apr '23

Hello! I just played around with the xdotool and came to the idea, to run it in a mate-terminal for the same published application, which I am usually using. Astounding result. >xdotool getactivewindow windowsize Your windowmanager claims not to support _NET_ACTIVE_WINDOW, so the attempt to query the active window aborted. xdotool get_desktop Your windowmanager claims not to support _NET_CURRENT_DESKTOP, so the query for the current desktop was aborted. xdotool getactivewindow get_desktop_for_window Your windowmanager claims not to support _NET_ACTIVE_WINDOW, so the attempt to query the active window aborted. xdo_get_active_window reported an error >From what I understand (?!) from your explantion, this must be an answer from the virtualized window-manger which runs in the usersession on the server?? This happens for my main-setup (client/server) as long as a new container, I've setup for testing). In opposite to the x2go session, trying the same (against the same host, using the same user and the same client machine, which behaves equal to my main setup): ssh -X tu1@deskeval mate-terminal tu1@deskeval:~$ xdotool get_desktop 56 It shows my current workspace-number. I just setup an lxc-container with debian/bullseye and in opposite to my usual use of XFCE4, I installed mate. It gave the same result like the mate-terminal from the xfce4-session (both were published applications). If I logon to the desktop, it works as expected! Suspending/resuming sessions give the same result between the mate- and the xfce4-desktop: Windows from other workspaces do not appear (but firefox knows them and its taskmanager can bring them up - the appear on the originally used workspace). May be, this is just another hint. Regards, Manfred ----- Original Message ----- From: Ulrich Sibiller [mailto:uli42@gmx.de] To: <webman(a)manfbraun.de> Cc: x2go-user(a)lists.x2go.org Sent: Mon, 20 Mar 2023 00:27:51 +0100 Subject: Re: [X2Go-User] Resume/restoration of windows to linux workspaces Well, thinking about this... Typically a window manager will store the workspace to use in the _NET_WM_DESKTOP property of a window. You can check that with xprop | grep _NET_WM_DESKTOP (selected the window you are interested in with the mouse). Alternatively you can run xprop -id <windowid> | grep _NET_WM_DESKTOP. Whenever a published application opens a window it will open this window on the x2goagent/nxagent on the server AND open a clone window on you local X server. Internally the agent has a mapping between the window ids of each window pair. On suspend the windows on the local X server are closed, the ones on the agent stay. On resume/reconnect the agent winn again open (new!) clone windows on the local X server and update their window ids in its list. When the local window manager sets the _NET_WM_DESKTOP property the agent will register this and _should_ update the _NET_WM_DESKTOP property on the agent side window, too. If a client changes a window property the agent will forward this change to the twin window on the local X server EXCEPT for properties starting with for WM_, _NET_ and for the _KDE_NET_WM_SYSTEM_TRAY_WINDOW_FOR property. So if firefox is trying to handle these properties itself this might explain why the workspace is not honored (just speculating, have not tested further). But I am wondering: If, e.g., a window was placed on, say, workspace 4 and then suspended and the resume happens on a setup that only has one or two workspaces what would happen? Also there might be further problems arising from restored windows having an other window id than previously. If the window manager chooses to store some workspace information depending on the window id (I don't know if any WM is doing this) this will not work with the restored windows. I am also wondering if setting the desired workspace by the client (in this case the agent is a client to the local X server) is honored by the WM at all. So can you please to some tests with the xprop command described above (run it from a local terminal, NOT from a published application) and check the properties of those windows before and after the reconnect? Does the _NET_WM_DESKTOP property get lost? Please also post the output of xprop -root | grep -e ^_NET -e ^WM - this will show the window manager related configuration. Uli On Sun, Mar 19, 2023 at 11:02 PM <webman(a)manfbraun.de> wrote: > > Hello Uli! > > Thanks for your reply. > > Published applications are not necessarily one-window, strictly > spoken, a terminal with two tabs has (at least) two windows. As > long as they are inside the terminals main-window, everything works > (sad to say: most of the time). > If there are two separate windows, which are in the current > workspace, this works too. > Below of that, it gets complicated. > If two windows are in separate workspaces, it works sometimes. > I am not sure, why at all - from your guess. > If you have two terms at WS1 and WS3 and you resume on WS5, > NO window appear at all, though the processes are running > well on the server side! > For firefox, this is more different. > From several windows, which were originally located in different > workspaces, only one window will be restored, this of the current > workspace. If all were located in the same workspace, they are > restored to the current workspace, if you are in that workspace, > which was current at 'suspend' time - otherwise: NO window > appear at all! > But for the first case, it gets interesting. > Go to 'more tools/taskmanager' (of the fox!), you'll see all > windows as processes. Double-clicking on of them brings it > back to the workspace were it was originally located! > Works for all of them. > Back to the first cases above. > If a session is restored by the x2go-client (I do not know > about this, due to lack of documentation), it knows all > windows and restores them - so ether the session on the server > or the client must give the window-manager advice. > I am starting my caja browsers at logon this way and they will > be even tagged to be visible on all workspaces. > So suspending a session must save the workspace accordingly. > I asked me, on which side, the workspace will be read at all, > server oder client? Just to be sure to have the same number > of WSs, I made them equal (for the testuser), but this does > not change anything (may be, a restart is necessary?). > > From toolchains perspective, X(&co.) were never made for > suspending window sessions (at least, so far I know) and > the window manager is only a filter for the workspace numbers. > What remains is, that only x2go can handle this at all. > > This was - a little - exploration, which shed me light on > the sessions, which do not work after return from hibernate > my box in the morning. > > Regards, > Manfred > > > ----- Original Message ----- > From: Ulrich Sibiller [mailto:uli42@gmx.de] > To: <webman(a)manfbraun.de> > Cc: x2go-user(a)lists.x2go.org > Sent: Fri, 17 Mar 2023 08:29:50 +0100 > Subject: Re: [X2Go-User] Resume/restoration of windows to linux workspaces > > Hello Manfred, > > in published applications mode the local window manager should be responsible for arranging the application windows. The application itself does not know about the workspaces at all. So probably the window manager does not recognize the restored windows as previously known windows. I have no idea at the moment how to even check if this theory applies here. You could try to run another desktop environment locally and check if the behaviour changes. > > Uli > > <webman(a)manfbraun.de> schrieb am Fr., 17. März 2023, 03:19: >> >> Hello! >> >> I am using published applications to run firefox. >> I am on debian bullseye (client and server). >> There is a big behavioral difference from using fox between >> this and using fox local in regard of crash and restore. >> If the fox restores a crashed window set locally, all windows >> appear on the workspace, they were originally running on. >> Not so with x2go - they all appear in the workspace, were >> the restauration starts. >> I usually have >50 windows and this is a big pain. >> Is this the normal behavior? >> If not, where to look for the problem? >> Note, this does not depend on a users profile. >> I created an additional user on the server and it behaves the same. >> >> Thanks, >> Manfred >> >> _______________________________________________ >> x2go-user mailing list >> x2go-user(a)lists.x2go.org >> https://lists.x2go.org/listinfo/x2go-user

1 0

Re: [X2Go-User] Performance problems with x2go - hickups, pause, probably memory-leak
by webman＠manfbraun.de 15 Apr '23

15 Apr '23

Hello! Addendum. I'll add obervations, which may be related. 1) Firefox stucks - no data comes in, network 0b/s. 2) Viewing video, video stucks shortly after start. If this just happens, just change the current workspace on the client side (where the windows are) and switch back immidiately: Problem "solved" in the same moment. The one window has its data, the other play the video. Looks like, it has something to do with window manager or something, which is not knowing, where the rigth window is? (I am using published applications most of the time). Update. Due to updates, I had to shutdown all and restart. This make verything shine golden and remind me, that immidiately after starting the x2go client (and server!), perf is really well (I described my hw/sw already). Its usually over time, that perf degrades that much. Over time is someting really over days, because I usually do no shutdowns, but hibernate my workstation. What I saw before the restart, was additionally a laggy scrolling behavior in Firefox and it reminds me, that I saw this bevore - looks probably related to the memory leak of the x2goagent. After the restart, scrolling works fine. Related. I have two lxc-containers running on my gateway, one for dns, one for a squid proxy. Both works well, but sometimes, perf is in question. I usually run a terminal to the gateway host and monitor this containers using lxc-top. The related thing is: relative high cpu (20%) and growing mem-use, the reason, they must finally rebooted each two weeks. Now, I've disabled x2goserver in both containers and I am running the third day now: 0%(!!) cpu, NO memory leak. They all run debian buster (fully upgraded) on kernel 5.10, x2goserver 4.1.0.3-4. May be this helps. So the memory-leak seems to be obvious. In the current, new cycle for my main-use, mem climbed already up from 0.6% to 5.0%. Regards, Manfred ----- Original Message ----- From: webman(a)manfbraun.de [mailto:webman@manfbraun.de] To: <x2go-user(a)lists.x2go.org> Sent: Tue, 11 Apr 2023 02:27:46 +0200 Subject: [X2Go-User] Performance problems with x2go - hickups, pause, probably memory-leak Hello! I probably detected strong problems with x2go, not very easy to explain. I am running a debian bullseye desktop, on it a kvm guest with debian bullseye, both have kernel6. The kvm guest x2goserver: 4.1.0.3-5, the host (my workstation) x2goclient: 4.1.2.2-2. Usually everything updated. The problem is the performance of firefox, but not generally. It stucks sometimes, up to several minutes and is completely unresponsive, especially(!), if it comes to youtube videos, but most time, it is not video. Astoundigly, in the many cases, it recovers. I am run dstat permanently (in the guest) and usually see a memory bottleneck (mem < 1 GB), not too strong and additionally high cpu usage, load: 6/4/4, but not too long. Often, this box crashes, if mem goes below 500 MB. Known, with firefox. For unknown reasons, this situation is not stabil (I am using up to 500 Tabs), one will never know, when this may happen and pre-actively saveing the session and continue with, say, 50 Tab, doesnt change the problem! The VM got 8 cores(!) on a AMD EPYC-Rome Processor with max 3.4 Ghz and 24 GB(!) mem, it got two network interfaces, one, to communicate with my host over a local bridge (10-36 Gb/s!), this is the "x2go-channel" and a lan-IF (1 Gb/s, hardware-passthrough) to the gateway (has 500 Mb/s) and nothing overloaded ever. Additionally some diskwrite, but with 600MB/s (in the VM!) this should not indicate a bottleneck. But since days, while another hickup, I saw, that the fox needs about only 20% cpu, BUT 'x2goagent' neds 100% !! It looks like the hickup appears exactly at those times. I setup a little processmonitor for the x2goagent and this seems to show a memory leak. I append this at the end. I installed 'glances' and that show me the x2goclient as the second mem consumer, growing. What language is the x2goagent written? Looks like a failing heap-management, garbage collection, which needs a lot of cpu? Some notes would be really welcome! Thanks, Manfred --- x2go-"monitor" ----------------------------------- (to keep this short, it has been cutted in the middle) $ while true; do ts="$(isodate -dt)"; xp="$(ps --no-headers -o user,pid,rss,%mem,comm -p 9430)"; echo "${ts} ${xp}"; sleep 3600; done 2023-04-05--22-21-29 ncu1 9430 1479916 6.0 x2goagent 2023-04-05--23-21-30 ncu1 9430 1491476 6.0 x2goagent 2023-04-06--00-21-30 ncu1 9430 1507612 6.1 x2goagent 2023-04-06--01-21-30 ncu1 9430 1514504 6.1 x2goagent 2023-04-06--02-21-30 ncu1 9430 1545784 6.2 x2goagent 2023-04-06--03-21-30 ncu1 9430 1560096 6.3 x2goagent 2023-04-06--04-21-30 ncu1 9430 1664844 6.7 x2goagent 2023-04-06--05-21-30 ncu1 9430 1684888 6.8 x2goagent 2023-04-06--14-06-28 ncu1 9430 1684888 6.8 x2goagent ....... 2023-04-10--16-06-31 ncu1 9430 2263236 9.1 x2goagent 2023-04-10--17-06-31 ncu1 9430 2274848 9.2 x2goagent 2023-04-10--18-06-31 ncu1 9430 2305704 9.3 x2goagent 2023-04-10--19-06-31 ncu1 9430 2352964 9.5 x2goagent 2023-04-10--20-06-32 ncu1 9430 2352964 9.5 x2goagent 2023-04-10--21-06-32 ncu1 9430 2406988 9.7 x2goagent 2023-04-10--22-06-32 ncu1 9430 2446112 9.9 x2goagent ======================================================

1 0

Performance problems with x2go - hickups, pause, probably memory-leak
by webman＠manfbraun.de 11 Apr '23

11 Apr '23

Hello! I probably detected strong problems with x2go, not very easy to explain. I am running a debian bullseye desktop, on it a kvm guest with debian bullseye, both have kernel6. The kvm guest x2goserver: 4.1.0.3-5, the host (my workstation) x2goclient: 4.1.2.2-2. Usually everything updated. The problem is the performance of firefox, but not generally. It stucks sometimes, up to several minutes and is completely unresponsive, especially(!), if it comes to youtube videos, but most time, it is not video. Astoundigly, in the many cases, it recovers. I am run dstat permanently (in the guest) and usually see a memory bottleneck (mem < 1 GB), not too strong and additionally high cpu usage, load: 6/4/4, but not too long. Often, this box crashes, if mem goes below 500 MB. Known, with firefox. For unknown reasons, this situation is not stabil (I am using up to 500 Tabs), one will never know, when this may happen and pre-actively saveing the session and continue with, say, 50 Tab, doesnt change the problem! The VM got 8 cores(!) on a AMD EPYC-Rome Processor with max 3.4 Ghz and 24 GB(!) mem, it got two network interfaces, one, to communicate with my host over a local bridge (10-36 Gb/s!), this is the "x2go-channel" and a lan-IF (1 Gb/s, hardware-passthrough) to the gateway (has 500 Mb/s) and nothing overloaded ever. Additionally some diskwrite, but with 600MB/s (in the VM!) this should not indicate a bottleneck. But since days, while another hickup, I saw, that the fox needs about only 20% cpu, BUT 'x2goagent' neds 100% !! It looks like the hickup appears exactly at those times. I setup a little processmonitor for the x2goagent and this seems to show a memory leak. I append this at the end. I installed 'glances' and that show me the x2goclient as the second mem consumer, growing. What language is the x2goagent written? Looks like a failing heap-management, garbage collection, which needs a lot of cpu? Some notes would be really welcome! Thanks, Manfred --- x2go-"monitor" ----------------------------------- (to keep this short, it has been cutted in the middle) $ while true; do ts="$(isodate -dt)"; xp="$(ps --no-headers -o user,pid,rss,%mem,comm -p 9430)"; echo "${ts} ${xp}"; sleep 3600; done 2023-04-05--22-21-29 ncu1 9430 1479916 6.0 x2goagent 2023-04-05--23-21-30 ncu1 9430 1491476 6.0 x2goagent 2023-04-06--00-21-30 ncu1 9430 1507612 6.1 x2goagent 2023-04-06--01-21-30 ncu1 9430 1514504 6.1 x2goagent 2023-04-06--02-21-30 ncu1 9430 1545784 6.2 x2goagent 2023-04-06--03-21-30 ncu1 9430 1560096 6.3 x2goagent 2023-04-06--04-21-30 ncu1 9430 1664844 6.7 x2goagent 2023-04-06--05-21-30 ncu1 9430 1684888 6.8 x2goagent 2023-04-06--14-06-28 ncu1 9430 1684888 6.8 x2goagent ....... 2023-04-10--16-06-31 ncu1 9430 2263236 9.1 x2goagent 2023-04-10--17-06-31 ncu1 9430 2274848 9.2 x2goagent 2023-04-10--18-06-31 ncu1 9430 2305704 9.3 x2goagent 2023-04-10--19-06-31 ncu1 9430 2352964 9.5 x2goagent 2023-04-10--20-06-32 ncu1 9430 2352964 9.5 x2goagent 2023-04-10--21-06-32 ncu1 9430 2406988 9.7 x2goagent 2023-04-10--22-06-32 ncu1 9430 2446112 9.9 x2goagent ======================================================

1 0

Re: [X2Go-User] Resume/restoration of windows to linux workspaces
by webman＠manfbraun.de 10 Apr '23

10 Apr '23

Hello, and thanks for your help. First, to mention about about firefox: If one runs firefox on the local machine, restauration after crash are always correct! I understand your explanation about the workspace number. At time of my question, the number of workspaces between user local and on the server were really different. But this should not matter, because - more "accidentally" - my test happened on the first eight workspaces (at that time, the server have luckily had 8 for this user). I made the test you mentioned and the _NET_WM_DESKTOP is always present (before suspend and after restore), BUT windows, which were located in different workspaces even do NOT appear - I checked all workspaces (because I use a lot of them, I have "tools" for this). To the checks. I save all window properties for my attempts and a grep over them shows: test3-win1-ws-6-x-post.txt:_NET_WM_DESKTOP(CARDINAL) = 6 test1-win2-ws-7-post.txt:_NET_WM_DESKTOP(CARDINAL) = 7 test1-win1-ws-6-7-post.txt:_NET_WM_DESKTOP(CARDINAL) = 6 test2-win1-ws-7-post.txt:_NET_WM_DESKTOP(CARDINAL) = 7 test1-win2-ws-7-org.txt:_NET_WM_DESKTOP(CARDINAL) = 7 test2-win2-ws-7-post.txt:_NET_WM_DESKTOP(CARDINAL) = 7 (The 'test1-win1-ws-6-7-post' has had a window on workspace 7 too, which does not appear at resume time). The last test generates a lot of output, I put it at the end. I survive a little with scripts, which saves all window titles (which are not necessarily unique) and I can restore partially the firefox windows. But gave up - would probably need the main-window id for the tabs .... But at login, I start eight caja windows this way. Please, no notes about my workspaces, I am trying something new and have a total of 60(!!). Organized into 15 interest zones with 4 prioritry rows - will see, if this make sense (most of the time, many are empty and will be named later). The problem with the firefox windows was the massivst problem, due to the huge amout of windows to re-arrange, but behind it, is the probably bigger problem: After shutdown or hibernate,most(!) of my remote sessions do NOT appear at all! Firefox, compared, runs in a KVM guest an my host and hibernate freeze everything - this survives! Regards, Manfred ----- xprop -root | grep -e ^_NET -e ^WM -------- (Could send this as attachment, if wished) $ xprop -root | grep -e ^_NET -e ^WM _NET_DESKTOP_LAYOUT(CARDINAL) = 0, 0, 4, 0 _NET_CLIENT_LIST_STACKING(WINDOW): window id # 0x1600028, 0x7e003e5, 0x7e00623, 0x7e00872, 0x820000c, 0x8200bf2, 0x8201937, 0x82025ef, 0x82034d1, 0x8204255, 0x6606e43, 0x840002c, 0x9803f41, 0xa20040d, 0xa200437, 0xa200461, 0xa20048b, 0xa2004a7, 0xa2004d1, 0xa2004fb, 0xa200525, 0xa200541, 0xa20056b, 0xa200595, 0xa2005bf, 0xa2005e9, 0xa200613, 0xa20063d, 0xa200667, 0xa200691, 0xa2006ad, 0xa2006d7, 0xa200701, 0xa20072b, 0xa200755, 0xa200771, 0xa20078d, 0xa2007b7, 0xa2007e1, 0xa20080b, 0xa200835, 0xa200851, 0xa20087b, 0xa2008a5, 0xa2008cf, 0xa2008eb, 0xa200915, 0xa200931, 0xa20095b, 0xa200985, 0x66081ac, 0x9200007, 0x9a00003, 0xa600007, 0x7600256, 0x7600268, 0x7600271, 0x7600283, 0x760027a, 0x760029e, 0x76002a7, 0x76002b0, 0x76002c2, 0x76002b9, 0x76002dd, 0x76002cb, 0x76002ef, 0x7600301, 0x760030a, 0x76002f8, 0x760031c, 0x7600340, 0x7600349, 0x7600352, 0x760044a, 0x7600468, 0x7600471, 0x7600634, 0x9c00003, 0x7600746, 0x666fa22, 0x667013f, 0x66708b8, 0x7605ccd, 0x760ae3a, 0x7610447, 0xb800007, 0x761df90, 0xba00006, 0x7628f61, 0x765381e, 0x6693712, 0x766809f, 0x76681b7, 0x7668218, 0xc800008, 0x7674e37, 0x768aba2, 0x76a6a45, 0x76b5aeb, 0x76bda67, 0x76c76a4, 0x76c76d2, 0x76f7665, 0xa400008, 0x772ec73, 0x830a51c, 0x66c40d1, 0x66d836f, 0xca0000c, 0x7780a47, 0x7780ae9, 0x778a22c, 0x668655a, 0x6600003, 0x660015a, 0x6600105, 0x660005e, 0x6800030, 0xb600003, 0x6601471, 0x6601654, 0x660270f, 0x66025dc, 0xa800003, 0xb201219, 0xb200205, 0x666f154, 0x666cc1a, 0x66710db, 0xae00011, 0x66f10d5, 0x774e3fb, 0x774602c, 0x775b01b, 0x7746082, 0x668071a, 0x66bdafc, 0x66e6679, 0x66c5ab2, 0xcc00003, 0x76002d4, 0x76002e6, 0x6601fb4, 0x6601ff8, 0x66e283d, 0x66c8c74, 0x6800011, 0xc200e9f, 0x66c5329, 0x66e8c6a, 0x66d65ae, 0x66e4cc3, 0x66e8d17, 0x66d72ec, 0x775b116, 0x66f2fd0, 0x771543d, 0x7715389, 0x76ff2b2, 0x77265ff, 0x76c91ef, 0x771545f, 0x76eba78, 0x76d1ece, 0x76f1cf3, 0x76f77ed, 0x76cc87d, 0x76ce82f, 0x802933c, 0x8204dd3, 0x76d1df2, 0x779c3a4, 0x680003c, 0x6800048, 0x779c3c9, 0x779eeb7, 0x829b5c5, 0x8297927, 0x824aeac, 0x6a85792, 0xbe0cd50, 0xa634a91, 0x77a1f24, 0x6a00007, 0x77b9496, 0x77c4aba, 0x77c768c, 0x77a1f48, 0xa634b91, 0x7e0006f, 0x66ffbd3, 0x77e6a13, 0x6603a9f, 0x77e6a61, 0x77de574, 0x6700733, 0x77f2c39, 0x900021c, 0x6a00e44, 0x7800061, 0x7e00246, 0x77c76be, 0xa63b44a, 0x980436c, 0x67007d2, 0x1800012, 0x180001a, 0x180001e, 0x1800016, 0x1800023, 0x1800003, 0x804fe20 _NET_CLIENT_LIST(WINDOW): window id # 0x1800003, 0x1800012, 0x1800016, 0x180001a, 0x180001e, 0x1800023, 0x1600028, 0x6600003, 0x660005e, 0x6600105, 0x660015a, 0x6800011, 0x6800030, 0x680003c, 0x6800048, 0x6601471, 0x6a00e44, 0x6601654, 0x6601fb4, 0x6601ff8, 0x66025dc, 0x660270f, 0x6603a9f, 0x7e0006f, 0x7e00246, 0x7e003e5, 0x7e00623, 0x7e00872, 0x820000c, 0x8200bf2, 0x8201937, 0x82025ef, 0x82034d1, 0x8204255, 0x8204dd3, 0x6606e43, 0x840002c, 0x9803f41, 0xa20040d, 0xa200437, 0xa200461, 0xa20048b, 0xa2004a7, 0xa2004d1, 0xa2004fb, 0xa200525, 0xa200541, 0xa20056b, 0xa200595, 0xa2005bf, 0xa2005e9, 0xa200613, 0xa20063d, 0xa200667, 0xa200691, 0xa2006ad, 0xa2006d7, 0xa200701, 0xa20072b, 0xa200755, 0xa200771, 0xa20078d, 0xa2007b7, 0xa2007e1, 0xa20080b, 0xa200835, 0xa200851, 0xa20087b, 0xa2008a5, 0xa2008cf, 0xa2008eb, 0xa200915, 0xa200931, 0xa20095b, 0xa200985, 0x66081ac, 0x802933c, 0x9200007, 0x9a00003, 0x804fe20, 0xa600007, 0x7600256, 0x7600268, 0x7600271, 0x7600283, 0x760027a, 0x760029e, 0x76002a7, 0x76002b0, 0x76002c2, 0x76002b9, 0x76002d4, 0x76002dd, 0x76002cb, 0x76002e6, 0x76002ef, 0x7600301, 0x760030a, 0x76002f8, 0x760031c, 0x7600340, 0x7600349, 0x7600352, 0x760044a, 0x7600468, 0x7600471, 0x7600634, 0x9c00003, 0x7600746, 0x666cc1a, 0x666f154, 0x666fa22, 0x667013f, 0x66708b8, 0xae00011, 0x66710db, 0xb200205, 0xb201219, 0x7605ccd, 0xa800003, 0x760ae3a, 0x7610447, 0xb600003, 0xb800007, 0x761df90, 0x668071a, 0xba00006, 0x7628f61, 0x668655a, 0x765381e, 0x6693712, 0x766809f, 0x76681b7, 0x7668218, 0xc800008, 0x7674e37, 0x768aba2, 0x76a6a45, 0x76b5aeb, 0x824aeac, 0x76bda67, 0x76c76a4, 0x76c76d2, 0x76c91ef, 0x76cc87d, 0x76ce82f, 0x76d1df2, 0x76d1ece, 0x76eba78, 0x76f1cf3, 0x76f7665, 0x900021c, 0x76f77ed, 0xa400008, 0x76ff2b2, 0xbe0cd50, 0x8297927, 0x7715389, 0x771543d, 0x771545f, 0x77265ff, 0x772ec73, 0x829b5c5, 0x830a51c, 0x66bdafc, 0x66c40d1, 0x66c5329, 0x66c5ab2, 0x66c8c74, 0x66d65ae, 0x7800061, 0x66d72ec, 0x66d836f, 0x980436c, 0xc200e9f, 0x66e283d, 0x774602c, 0x7746082, 0x66e4cc3, 0x66e6679, 0x66e8c6a, 0x66e8d17, 0x774e3fb, 0x775b01b, 0x66f10d5, 0x6a85792, 0x66f2fd0, 0x775b116, 0x6a00007, 0xcc00003, 0xca0000c, 0x7780a47, 0x7780ae9, 0x778a22c, 0x779c3a4, 0x779c3c9, 0x779eeb7, 0x77a1f24, 0x77a1f48, 0xa634a91, 0x77b9496, 0x77c4aba, 0x77c768c, 0x77c76be, 0x77de574, 0xa634b91, 0x77e6a13, 0x66ffbd3, 0x77e6a61, 0x77f2c39, 0x6700733, 0xa63b44a, 0x67007d2 _NET_DESKTOP_NAMES(UTF8_STRING) = "mail 1", "pol-info 2", "pol-extra 3", "pol-more 4", "pol-todo 5", "POL-SoZMed/Main 6", "adm-boxes 7", "adm-search 8", "adm-misc 9", "VMs 10", "Wokspace 11", "admin-base 12", "ws 13", "work-boxes 14", "Workspace 15", "fbox/fun/music 16", "devil 17", "Restore-SIMS 18", "Infra-Extras 19", "infra-edit 20", "infra-misc 21", "infra-anal 22", "admin-logs 23", "admin-gui 24", "Workspace 25", "Workspace 26", "Workspace 27", "Workspace 28", "Workspace 29", "Workspace 30", "User-Org 31", "Workspace 32", "Workspace 33", "Workspace 34", "Workspace 35", "Workspace 36", "Workspace 37", "Workspace 38", "Workspace 39", "Workspace 40", "Workspace 41", "Workspace 42", "Workspace 43", "Workspace 44", "Workspace 45", "Workspace 46", "Workspace 47", "Workspace 48", "Workspace 49", "Workspace 50", "Workspace 51", "Workspace 52", "Workspace 53", "Workspace 54", "InfraDocs 55", "Workspace 56", "Workspace 57", "Workspace 58", "Workspace 59", "Workspace 60", "" _NET_ACTIVE_WINDOW(WINDOW): window id # 0x67007d2, 0x0 _NET_CURRENT_DESKTOP(CARDINAL) = 0 _NET_DESKTOP_VIEWPORT(CARDINAL) = 0, 0 _NET_DESKTOP_GEOMETRY(CARDINAL) = 2560, 1600 _NET_SUPPORTING_WM_CHECK(WINDOW): window id # 0x1000122 _NET_SUPPORTED(ATOM) = _NET_ACTIVE_WINDOW, _NET_CLIENT_LIST, _NET_CLIENT_LIST_STACKING, _NET_CLOSE_WINDOW, _NET_CURRENT_DESKTOP, _NET_DESKTOP_GEOMETRY, _NET_DESKTOP_LAYOUT, _NET_DESKTOP_NAMES, _NET_DESKTOP_VIEWPORT, _NET_FRAME_EXTENTS, _NET_MOVERESIZE_WINDOW, _NET_NUMBER_OF_DESKTOPS, _NET_REQUEST_FRAME_EXTENTS, _NET_SHOWING_DESKTOP, _NET_SUPPORTED, _NET_SUPPORTING_WM_CHECK, _NET_SYSTEM_TRAY_OPCODE, _NET_WM_ACTION_ABOVE, _NET_WM_ACTION_BELOW, _NET_WM_ACTION_CHANGE_DESKTOP, _NET_WM_ACTION_CLOSE, _NET_WM_ACTION_FULLSCREEN, _NET_WM_ACTION_MAXIMIZE_HORZ, _NET_WM_ACTION_MAXIMIZE_VERT, _NET_WM_ACTION_MINIMIZE, _NET_WM_ACTION_MOVE, _NET_WM_ACTION_RESIZE, _NET_WM_ACTION_SHADE, _NET_WM_ACTION_STICK, _NET_WM_ALLOWED_ACTIONS, _NET_WM_BYPASS_COMPOSITOR, _NET_WM_CONTEXT_HELP, _NET_WM_DESKTOP, _NET_WM_FULLSCREEN_MONITORS, _NET_WM_ICON, _NET_WM_ICON_GEOMETRY, _NET_WM_ICON_NAME, _NET_WM_MOVERESIZE, _NET_WM_NAME, _NET_WM_OPAQUE_REGION, _NET_WM_PID, _NET_WM_PING, _NET_WM_STATE, _NET_WM_STATE_ABOVE, _NET_WM_STATE_BELOW, _NET_WM_STATE_DEMANDS_ATTENTION, _NET_WM_STATE_FOCUSED, _NET_WM_STATE_FULLSCREEN, _NET_WM_STATE_HIDDEN, _NET_WM_STATE_MAXIMIZED_HORZ, _NET_WM_STATE_MAXIMIZED_VERT, _NET_WM_STATE_MODAL, _NET_WM_STATE_SHADED, _NET_WM_STATE_SKIP_PAGER, _NET_WM_STATE_SKIP_TASKBAR, _NET_WM_STATE_STICKY, _NET_WM_STRUT, _NET_WM_STRUT_PARTIAL, _NET_WM_SYNC_REQUEST, _NET_WM_SYNC_REQUEST_COUNTER, _NET_WM_USER_TIME, _NET_WM_USER_TIME_WINDOW, _NET_WM_WINDOW_OPACITY, _NET_WM_WINDOW_OPACITY_LOCKED, _NET_WM_WINDOW_TYPE, _NET_WM_WINDOW_TYPE_DESKTOP, _NET_WM_WINDOW_TYPE_DIALOG, _NET_WM_WINDOW_TYPE_DOCK, _NET_WM_WINDOW_TYPE_MENU, _NET_WM_WINDOW_TYPE_NORMAL, _NET_WM_WINDOW_TYPE_SPLASH, _NET_WM_WINDOW_TYPE_TOOLBAR, _NET_WM_WINDOW_TYPE_UTILITY, _NET_WORKAREA, _GTK_FRAME_EXTENTS, _GTK_HIDE_TITLEBAR_WHEN_MAXIMIZED, _GTK_SHOW_WINDOW_MENU, _NET_STARTUP_ID _NET_WORKAREA(CARDINAL) = 0, 83, 2560, 1517, 0, 83, 2560, 1517, 0, 83, 2560, 1517, 0, 83, 2560, 1517, 0, 83, 2560, 1517, 0, 83, 2560, 1517, 0, 83, 2560, 1517, 0, 83, 2560, 1517, 0, 83, 2560, 1517, 0, 83, 2560, 1517, 0, 83, 2560, 1517, 0, 83, 2560, 1517, 0, 83, 2560, 1517, 0, 83, 2560, 1517, 0, 83, 2560, 1517, 0, 83, 2560, 1517, 0, 83, 2560, 1517, 0, 83, 2560, 1517, 0, 83, 2560, 1517, 0, 83, 2560, 1517, 0, 83, 2560, 1517, 0, 83, 2560, 1517, 0, 83, 2560, 1517, 0, 83, 2560, 1517, 0, 83, 2560, 1517, 0, 83, 2560, 1517, 0, 83, 2560, 1517, 0, 83, 2560, 1517, 0, 83, 2560, 1517, 0, 83, 2560, 1517, 0, 83, 2560, 1517, 0, 83, 2560, 1517, 0, 83, 2560, 1517, 0, 83, 2560, 1517, 0, 83, 2560, 1517, 0, 83, 2560, 1517, 0, 83, 2560, 1517, 0, 83, 2560, 1517, 0, 83, 2560, 1517, 0, 83, 2560, 1517, 0, 83, 2560, 1517, 0, 83, 2560, 1517, 0, 83, 2560, 1517, 0, 83, 2560, 1517, 0, 83, 2560, 1517, 0, 83, 2560, 1517, 0, 83, 2560, 1517, 0, 83, 2560, 1517, 0, 83, 2560, 1517, 0, 83, 2560, 1517, 0, 83, 2560, 1517, 0, 83, 2560, 1517, 0, 83, 2560, 1517, 0, 83, 2560, 1517, 0, 83, 2560, 1517, 0, 83, 2560, 1517, 0, 83, 2560, 1517, 0, 83, 2560, 1517, 0, 83, 2560, 1517, 0, 83, 2560, 1517 _NET_NUMBER_OF_DESKTOPS(CARDINAL) = 60 ================================================= ----- Original Message ----- From: Ulrich Sibiller [mailto:uli42@gmx.de] To: <webman(a)manfbraun.de> Cc: x2go-user(a)lists.x2go.org Sent: Mon, 20 Mar 2023 00:27:51 +0100 Subject: Re: [X2Go-User] Resume/restoration of windows to linux workspaces Well, thinking about this... Typically a window manager will store the workspace to use in the _NET_WM_DESKTOP property of a window. You can check that with xprop | grep _NET_WM_DESKTOP (selected the window you are interested in with the mouse). Alternatively you can run xprop -id <windowid> | grep _NET_WM_DESKTOP. Whenever a published application opens a window it will open this window on the x2goagent/nxagent on the server AND open a clone window on you local X server. Internally the agent has a mapping between the window ids of each window pair. On suspend the windows on the local X server are closed, the ones on the agent stay. On resume/reconnect the agent winn again open (new!) clone windows on the local X server and update their window ids in its list. When the local window manager sets the _NET_WM_DESKTOP property the agent will register this and _should_ update the _NET_WM_DESKTOP property on the agent side window, too. If a client changes a window property the agent will forward this change to the twin window on the local X server EXCEPT for properties starting with for WM_, _NET_ and for the _KDE_NET_WM_SYSTEM_TRAY_WINDOW_FOR property. So if firefox is trying to handle these properties itself this might explain why the workspace is not honored (just speculating, have not tested further). But I am wondering: If, e.g., a window was placed on, say, workspace 4 and then suspended and the resume happens on a setup that only has one or two workspaces what would happen? Also there might be further problems arising from restored windows having an other window id than previously. If the window manager chooses to store some workspace information depending on the window id (I don't know if any WM is doing this) this will not work with the restored windows. I am also wondering if setting the desired workspace by the client (in this case the agent is a client to the local X server) is honored by the WM at all. So can you please to some tests with the xprop command described above (run it from a local terminal, NOT from a published application) and check the properties of those windows before and after the reconnect? Does the _NET_WM_DESKTOP property get lost? Please also post the output of xprop -root | grep -e ^_NET -e ^WM - this will show the window manager related configuration. Uli On Sun, Mar 19, 2023 at 11:02 PM <webman(a)manfbraun.de> wrote: > > Hello Uli! > > Thanks for your reply. > > Published applications are not necessarily one-window, strictly > spoken, a terminal with two tabs has (at least) two windows. As > long as they are inside the terminals main-window, everything works > (sad to say: most of the time). > If there are two separate windows, which are in the current > workspace, this works too. > Below of that, it gets complicated. > If two windows are in separate workspaces, it works sometimes. > I am not sure, why at all - from your guess. > If you have two terms at WS1 and WS3 and you resume on WS5, > NO window appear at all, though the processes are running > well on the server side! > For firefox, this is more different. > From several windows, which were originally located in different > workspaces, only one window will be restored, this of the current > workspace. If all were located in the same workspace, they are > restored to the current workspace, if you are in that workspace, > which was current at 'suspend' time - otherwise: NO window > appear at all! > But for the first case, it gets interesting. > Go to 'more tools/taskmanager' (of the fox!), you'll see all > windows as processes. Double-clicking on of them brings it > back to the workspace were it was originally located! > Works for all of them. > Back to the first cases above. > If a session is restored by the x2go-client (I do not know > about this, due to lack of documentation), it knows all > windows and restores them - so ether the session on the server > or the client must give the window-manager advice. > I am starting my caja browsers at logon this way and they will > be even tagged to be visible on all workspaces. > So suspending a session must save the workspace accordingly. > I asked me, on which side, the workspace will be read at all, > server oder client? Just to be sure to have the same number > of WSs, I made them equal (for the testuser), but this does > not change anything (may be, a restart is necessary?). > > From toolchains perspective, X(&co.) were never made for > suspending window sessions (at least, so far I know) and > the window manager is only a filter for the workspace numbers. > What remains is, that only x2go can handle this at all. > > This was - a little - exploration, which shed me light on > the sessions, which do not work after return from hibernate > my box in the morning. > > Regards, > Manfred > > > ----- Original Message ----- > From: Ulrich Sibiller [mailto:uli42@gmx.de] > To: <webman(a)manfbraun.de> > Cc: x2go-user(a)lists.x2go.org > Sent: Fri, 17 Mar 2023 08:29:50 +0100 > Subject: Re: [X2Go-User] Resume/restoration of windows to linux workspaces > > Hello Manfred, > > in published applications mode the local window manager should be responsible for arranging the application windows. The application itself does not know about the workspaces at all. So probably the window manager does not recognize the restored windows as previously known windows. I have no idea at the moment how to even check if this theory applies here. You could try to run another desktop environment locally and check if the behaviour changes. > > Uli > > <webman(a)manfbraun.de> schrieb am Fr., 17. März 2023, 03:19: >> >> Hello! >> >> I am using published applications to run firefox. >> I am on debian bullseye (client and server). >> There is a big behavioral difference from using fox between >> this and using fox local in regard of crash and restore. >> If the fox restores a crashed window set locally, all windows >> appear on the workspace, they were originally running on. >> Not so with x2go - they all appear in the workspace, were >> the restauration starts. >> I usually have >50 windows and this is a big pain. >> Is this the normal behavior? >> If not, where to look for the problem? >> Note, this does not depend on a users profile. >> I created an additional user on the server and it behaves the same. >> >> Thanks, >> Manfred >> >> _______________________________________________ >> x2go-user mailing list >> x2go-user(a)lists.x2go.org >> https://lists.x2go.org/listinfo/x2go-user

1 0

Segfault in nxagent while connecting
by Michael Eager 08 Apr '23

08 Apr '23

I'm running x2goclient-4.1.2.2 on a Fedora 37 system, connecting to a Fedora 33 system running x2goserver-4.1.0.3 and nxagent-3.5.99.26. The x2goagent segfaults: x2goagent[164463]: segfault at 48 ip 000055a0be4ce7ff sp 00007ffc443b5090 error 4 in nxagent[55a0be3c5000+311000] There appears to be a similar bug on RedHat: https://bugzilla.redhat.com/show_bug.cgi?id=2028716 What can I do to make this work? -- Michael Eager

1 0

Enhance Documentation for pageant etc
by James Bowery 04 Apr '23

04 Apr '23

The "getting started" section: doc:usage:x2goclient [X2Go - everywhere@home] <https://wiki.x2go.org/doku.php/doc:usage:x2goclient#getting_started_my_firs…> says: You could also just use an SSH agent if you've got that available. On > Linux, the standard ssh-agent, or any agent that is compatible with it, is > used. On Windows, Pageant, or any agent that is compatible with it (like > KeeAgent) is used. Please enhance that to say something like: > You could also just use an SSH agent if you've got that available. On > Linux, the standard ssh-agent, or any agent that is compatible with it, is > used. On Windows, Pageant, or any agent that is compatible with it (like > KeeAgent) is used. WARNING: The agent doesn't work if you specify a file > in the "Use RSA/DSA ..." field.

1 0

Upcoming X2Go and orca e.V. sponsorship drive - starting tomorrow, 2023-04-04
by Stefan Baur 03 Apr '23

03 Apr '23

Dear $ALL, As you might know, a few years ago, at "X2Go: The Gathering 2017", several key members of X2Go as well as members from other Remote Desktop-/Remote Application projects joined together to form the Open Remote Computing Association - orca e.V. - a registered association under Germanys Civil Code and also registered as a charitable organization, similar to a 501(c)(3) organization in the US. In June 2022, we joined betterplace.org for easier handling of donations. They offer PayPal, SEPA Direct Debit, Credit Card, giropay/paydirekt and Wire transfer. And they also handle issuing donation receipts for us. (Note that while donations towards orca/X2Go are tax-deductible for German tax subjects, this may vary in other jurisdictions.) This is to let you know that the next sponsorship drive starts Tuesday, 2023-04-04, 09:00 CEST (that's tomorrow!) and ends Thursday, 2023-04-06, 23:59 CEST. It is sponsored by the Commercial and Savings Bank Ulm, where orca's bank account resides, and they are going to distribute 10 000 EUR among all charitable organizations registered with them via betterplace.org that receive donations in the timeframe above. So it's not a 1:1 matching of each donation, but the org with the biggest amount of donations gets the biggest piece of the cake, so to speak. If you can, please visit the donation sites below on one or more of the dates mentioned and send a few €€€ our way. (But don't feel bad if you can't. Times are rough. We get that.) We'd prefer if you use the German-language donation forms because with these, we know for sure that the donation counts towards the bank's pledge. However, if you're afraid of hitting the wrong button in a German-language form, feel free to use the link that points to the English version. To donate towards X2Go: German: <https://www.wirwunder.de/projects/111056?wirwunder=235> English: <https://www.betterplace.org/en/projects/111056?wirwunder=235> Note that X2Go currently has a specific need (with a second one probably popping up soon). To donate specifically towards that need, please see the links below: English-language donation form for travel/lodging/supplies costs @ LinuxDays Chemnitz 2023: <https://www.betterplace.org/en/donate/platform/projects/111056?need_id=4715…> German-language donation form for travel/lodging/supplies costs @ LinuxDays Chemnitz 2023: <https://www.betterplace.org/de/donate/platform/projects/111056?need_id=4715…> To donate towards orca e.V., our umbrella org: German: <https://www.wirwunder.de/projects/111057?wirwunder=235> English: <https://www.betterplace.org/en/projects/111057?wirwunder=235> Kind Regards, and Thanks in Advance, Stefan Baur X2Go's Community Manager -- 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

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

x2go-user April 2023