Re: [X2Go-User] freezing after update to fedora 37
Hi Neal, Have you tried disabling or uninstalling the screensaver on the server? On Tue, 29 Nov 2022 at 07:54, Neal Becker wrote: > Been using x2go for many fedora releases. After updating both client and > server to fedora f37, I have a new problem. I've tried multiple desktops, > including xfce and lxde, and have the same symptoms. > After starting a session, it initially works fine. When I come back later > to try to use it, it is frozen. So I have not disconnected from the > session and reconnected. On the client side the screen was locked and then > unlocked when I returned. The client did not suspend - it is running on > A/C power. > > The session is frozen and completely unresponsive to input. > Disconnect/reconnect it's still frozen. Only terminate/new session will > unfreeze it. > > Any suggestions? > > Thanks > Neal > ___ > x2go-user mailing list > x2go-user@lists.x2go.org > https://lists.x2go.org/listinfo/x2go-user > -- Norman Gaywood, Computer Systems Officer School of Science and Technology University of New England Armidale NSW 2351, Australia ngayw...@une.edu.au http://turing.une.edu.au/~ngaywood Phone: +61 (0)2 6773 2412 Mobile: +61 (0)4 7862 0062 Please avoid sending me Word or Power Point attachments. See http://www.gnu.org/philosophy/no-word-attachments.html ___ x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
Re: [X2Go-User] Fedora 36 and glx fails with GLXUnsupportedPrivateRequest
Thanks Sai, Glad someone else is seeing this :-) I've reported a bug in the Fedora bugzilla. Hopefully this gets to the right developers. https://bugzilla.redhat.com/show_bug.cgi?id=2093528 On Sat, 4 Jun 2022 at 14:50, sairuk wrote: > Hi Norman, > > I've run into similar issues after an upgrade to Ubuntu 22.04 on one of my > machines which is now Mesa 22, i've been trying to investigate further this > morning to no avail, thanks for the workaround on Fedora, good to at least > understand a potential cause. > > I setup a separate vm today with a fresh 22.04+x2go and the issue is > repeatable, so I had a test space > > I'll have to look at downgrading, although I don't know offhand how > reasonable that is in debian land, time to go have a play > > (meant to reply to all, sorry for the dupe email Norman) > > sai > > On Sat, Jun 4, 2022 at 2:25 PM Norman Gaywood wrote: > >> OK, further downgrades gets glxinfo to work again. >> >> On my test F36 system I downloaded F35 mesa* and libglvnd* packages and >> did: >> dnf downgrade ./mesa*rpm ./libglv*.rpm >> >> Which resulted in the packages listed below to be downgraded. >> After that, glxinfo and glxgears work again. >> >> So, a bug in mesa 22? >> >> libglvnd-1:1.3.4-2.fc35.i686 >> libglvnd-1:1.3.4-2.fc35.x86_64 >> libglvnd-core-devel-1:1.3.4-2.fc35.x86_64 >> libglvnd-devel-1:1.3.4-2.fc35.x86_64 >> libglvnd-egl-1:1.3.4-2.fc35.x86_64 >> libglvnd-gles-1:1.3.4-2.fc35.x86_64 >> libglvnd-glx-1:1.3.4-2.fc35.i686 >> libglvnd-glx-1:1.3.4-2.fc35.x86_64 >> libglvnd-opengl-1:1.3.4-2.fc35.x86_64 >> mesa-dri-drivers-21.3.8-2.fc35.i686 >> mesa-dri-drivers-21.3.8-2.fc35.x86_64 >> mesa-filesystem-21.3.8-2.fc35.i686 >> mesa-filesystem-21.3.8-2.fc35.x86_64 >> mesa-libEGL-21.3.8-2.fc35.x86_64 >> mesa-libEGL-devel-21.3.8-2.fc35.x86_64 >> mesa-libgbm-21.3.8-2.fc35.i686 >> mesa-libgbm-21.3.8-2.fc35.x86_64 >> mesa-libGL-21.3.8-2.fc35.i686 >> mesa-libGL-21.3.8-2.fc35.x86_64 >> mesa-libglapi-21.3.8-2.fc35.i686 >> mesa-libglapi-21.3.8-2.fc35.x86_64 >> mesa-libGL-devel-21.3.8-2.fc35.x86_64 >> mesa-libGLU-9.0.1-5.fc35.i686 >> mesa-libGLU-9.0.1-5.fc35.x86_64 >> mesa-libOpenCL-21.3.8-2.fc35.i686 >> mesa-libOpenCL-21.3.8-2.fc35.x86_64 >> mesa-libOSMesa-21.3.8-2.fc35.x86_64 >> mesa-libxatracker-21.3.8-2.fc35.x86_64 >> mesa-vulkan-drivers-21.3.8-2.fc35.i686 >> mesa-vulkan-drivers-21.3.8-2.fc35.x86_64 >> >> >> On Sat, 4 Jun 2022 at 11:15, Norman Gaywood wrote: >> >>> >>> On Fedora 36 we have: >>> libglvnd-1.4.0-2.fc36.x86_64 >>> libglvnd-glx-1.4.0-2.fc36.x86_64 >>> >>> On Fedora 35: >>> libglvnd-1.3.4-2.fc35.x86_64 >>> libglvnd-glx-1.3.4-2.fc35.x86_64 >>> >>> I managed to download the libglvnd* packages for F35, and on an F36 >>> system, I downgraded: >>> dnf downgrade ./libglvnd* ./glx-utils* >>> and rebooted. >>> >>> So now on my F36 system I have: >>> libglvnd-1.3.4-2.fc35.x86_64 >>> libglvnd-glx-1.3.4-2.fc35.x86_64 >>> >>> (I've trimmed the package lists in the above, there are more libglvnd* >>> installed/downgraded). >>> >>> And the same behaviour occurs: >>> $ glxinfo >>> name of display: :50.0 >>> X Error of failed request: GLXUnsupportedPrivateRequest >>> Major opcode of failed request: 143 (GLX) >>> Minor opcode of failed request: 17 (X_GLXVendorPrivateWithReply) >>> Serial number of failed request: 27 >>> Current serial number in output stream: 27 >>> >>> So this suggests it's not the upgrade from 1.3 to 1.4 of libglvnd-glx ??? >>> >>> glxinfo is part of the glx-utils package, which I also downgraded. But >>> they have the same version number: >>> glx-utils-8.4.0-12.20210504git0f9e7d9.fc35.x86_64 >>> glx-utils-8.4.0-13.20210504git0f9e7d9.fc36.x86_64 >>> >>> So, I'm not sure what to look at next. >>> >>> >>> On Fri, 3 Jun 2022 at 17:26, Ulrich Sibiller wrote: >>> >>>> The version of x2goserver and x2goclient is irrelevant here. The GLX >>>> code is in nx-libs (nxagent/x2goagent). However, nothing has changed >>>> there in years, so I suggest to downgrade glxinfo and retry. Let me >>>> know the result. >>>> >>>> Uli >>>> >>>> On Fri, Jun 3, 2022 at 1:51 AM Norman Gaywood >>>> wrote: >>>> > >>>> > In Fedora 35 glxinfo (and glxgear
Re: [X2Go-User] Fedora 36 and glx fails with GLXUnsupportedPrivateRequest
OK, further downgrades gets glxinfo to work again. On my test F36 system I downloaded F35 mesa* and libglvnd* packages and did: dnf downgrade ./mesa*rpm ./libglv*.rpm Which resulted in the packages listed below to be downgraded. After that, glxinfo and glxgears work again. So, a bug in mesa 22? libglvnd-1:1.3.4-2.fc35.i686 libglvnd-1:1.3.4-2.fc35.x86_64 libglvnd-core-devel-1:1.3.4-2.fc35.x86_64 libglvnd-devel-1:1.3.4-2.fc35.x86_64 libglvnd-egl-1:1.3.4-2.fc35.x86_64 libglvnd-gles-1:1.3.4-2.fc35.x86_64 libglvnd-glx-1:1.3.4-2.fc35.i686 libglvnd-glx-1:1.3.4-2.fc35.x86_64 libglvnd-opengl-1:1.3.4-2.fc35.x86_64 mesa-dri-drivers-21.3.8-2.fc35.i686 mesa-dri-drivers-21.3.8-2.fc35.x86_64 mesa-filesystem-21.3.8-2.fc35.i686 mesa-filesystem-21.3.8-2.fc35.x86_64 mesa-libEGL-21.3.8-2.fc35.x86_64 mesa-libEGL-devel-21.3.8-2.fc35.x86_64 mesa-libgbm-21.3.8-2.fc35.i686 mesa-libgbm-21.3.8-2.fc35.x86_64 mesa-libGL-21.3.8-2.fc35.i686 mesa-libGL-21.3.8-2.fc35.x86_64 mesa-libglapi-21.3.8-2.fc35.i686 mesa-libglapi-21.3.8-2.fc35.x86_64 mesa-libGL-devel-21.3.8-2.fc35.x86_64 mesa-libGLU-9.0.1-5.fc35.i686 mesa-libGLU-9.0.1-5.fc35.x86_64 mesa-libOpenCL-21.3.8-2.fc35.i686 mesa-libOpenCL-21.3.8-2.fc35.x86_64 mesa-libOSMesa-21.3.8-2.fc35.x86_64 mesa-libxatracker-21.3.8-2.fc35.x86_64 mesa-vulkan-drivers-21.3.8-2.fc35.i686 mesa-vulkan-drivers-21.3.8-2.fc35.x86_64 On Sat, 4 Jun 2022 at 11:15, Norman Gaywood wrote: > > On Fedora 36 we have: > libglvnd-1.4.0-2.fc36.x86_64 > libglvnd-glx-1.4.0-2.fc36.x86_64 > > On Fedora 35: > libglvnd-1.3.4-2.fc35.x86_64 > libglvnd-glx-1.3.4-2.fc35.x86_64 > > I managed to download the libglvnd* packages for F35, and on an F36 > system, I downgraded: > dnf downgrade ./libglvnd* ./glx-utils* > and rebooted. > > So now on my F36 system I have: > libglvnd-1.3.4-2.fc35.x86_64 > libglvnd-glx-1.3.4-2.fc35.x86_64 > > (I've trimmed the package lists in the above, there are more libglvnd* > installed/downgraded). > > And the same behaviour occurs: > $ glxinfo > name of display: :50.0 > X Error of failed request: GLXUnsupportedPrivateRequest > Major opcode of failed request: 143 (GLX) > Minor opcode of failed request: 17 (X_GLXVendorPrivateWithReply) > Serial number of failed request: 27 > Current serial number in output stream: 27 > > So this suggests it's not the upgrade from 1.3 to 1.4 of libglvnd-glx ??? > > glxinfo is part of the glx-utils package, which I also downgraded. But > they have the same version number: > glx-utils-8.4.0-12.20210504git0f9e7d9.fc35.x86_64 > glx-utils-8.4.0-13.20210504git0f9e7d9.fc36.x86_64 > > So, I'm not sure what to look at next. > > > On Fri, 3 Jun 2022 at 17:26, Ulrich Sibiller wrote: > >> The version of x2goserver and x2goclient is irrelevant here. The GLX >> code is in nx-libs (nxagent/x2goagent). However, nothing has changed >> there in years, so I suggest to downgrade glxinfo and retry. Let me >> know the result. >> >> Uli >> >> On Fri, Jun 3, 2022 at 1:51 AM Norman Gaywood >> wrote: >> > >> > In Fedora 35 glxinfo (and glxgears) worked fine with >> x2goserver-4.1.0.3-17.fc35.x86_64 >> > >> > After updating to Fedora 36, x2goserver-4.1.0.3-17.fc36.x86_64, glxinfo >> no longer works. >> > $ glxinfo >> > name of display: :50.0 >> > X Error of failed request: GLXUnsupportedPrivateRequest >> > Major opcode of failed request: 143 (GLX) >> > Minor opcode of failed request: 17 (X_GLXVendorPrivateWithReply) >> > Serial number of failed request: 27 >> > Current serial number in output stream: 27 >> > >> > Linux x2goclient X2Go Client v. 4.1.2.2 (Qt - 5.15.3) >> > >> > Is there any way to make this work? Not sure what programs actually use >> it. >> > Thankfully matlab still seems to work. >> > -- >> > Norman Gaywood, Computer Systems Officer >> > School of Science and Technology >> > University of New England >> > Armidale NSW 2351, Australia >> > >> > ngayw...@une.edu.au http://turing.une.edu.au/~ngaywood >> > Phone: +61 (0)2 6773 2412 Mobile: +61 (0)4 7862 0062 >> > >> > Please avoid sending me Word or Power Point attachments. >> > See http://www.gnu.org/philosophy/no-word-attachments.html >> > ___ >> > x2go-user mailing list >> > x2go-user@lists.x2go.org >> > https://lists.x2go.org/listinfo/x2go-user >> > > > -- > Norman Gaywood, Computer Systems Officer > School of Science and Technology > University of New England > Armidale NSW 2351, Australia > > ngayw...@une.edu.au http://turing.une.edu.au/~ngayw
Re: [X2Go-User] Fedora 36 and glx fails with GLXUnsupportedPrivateRequest
On Fedora 36 we have: libglvnd-1.4.0-2.fc36.x86_64 libglvnd-glx-1.4.0-2.fc36.x86_64 On Fedora 35: libglvnd-1.3.4-2.fc35.x86_64 libglvnd-glx-1.3.4-2.fc35.x86_64 I managed to download the libglvnd* packages for F35, and on an F36 system, I downgraded: dnf downgrade ./libglvnd* ./glx-utils* and rebooted. So now on my F36 system I have: libglvnd-1.3.4-2.fc35.x86_64 libglvnd-glx-1.3.4-2.fc35.x86_64 (I've trimmed the package lists in the above, there are more libglvnd* installed/downgraded). And the same behaviour occurs: $ glxinfo name of display: :50.0 X Error of failed request: GLXUnsupportedPrivateRequest Major opcode of failed request: 143 (GLX) Minor opcode of failed request: 17 (X_GLXVendorPrivateWithReply) Serial number of failed request: 27 Current serial number in output stream: 27 So this suggests it's not the upgrade from 1.3 to 1.4 of libglvnd-glx ??? glxinfo is part of the glx-utils package, which I also downgraded. But they have the same version number: glx-utils-8.4.0-12.20210504git0f9e7d9.fc35.x86_64 glx-utils-8.4.0-13.20210504git0f9e7d9.fc36.x86_64 So, I'm not sure what to look at next. On Fri, 3 Jun 2022 at 17:26, Ulrich Sibiller wrote: > The version of x2goserver and x2goclient is irrelevant here. The GLX > code is in nx-libs (nxagent/x2goagent). However, nothing has changed > there in years, so I suggest to downgrade glxinfo and retry. Let me > know the result. > > Uli > > On Fri, Jun 3, 2022 at 1:51 AM Norman Gaywood wrote: > > > > In Fedora 35 glxinfo (and glxgears) worked fine with > x2goserver-4.1.0.3-17.fc35.x86_64 > > > > After updating to Fedora 36, x2goserver-4.1.0.3-17.fc36.x86_64, glxinfo > no longer works. > > $ glxinfo > > name of display: :50.0 > > X Error of failed request: GLXUnsupportedPrivateRequest > > Major opcode of failed request: 143 (GLX) > > Minor opcode of failed request: 17 (X_GLXVendorPrivateWithReply) > > Serial number of failed request: 27 > > Current serial number in output stream: 27 > > > > Linux x2goclient X2Go Client v. 4.1.2.2 (Qt - 5.15.3) > > > > Is there any way to make this work? Not sure what programs actually use > it. > > Thankfully matlab still seems to work. > > -- > > Norman Gaywood, Computer Systems Officer > > School of Science and Technology > > University of New England > > Armidale NSW 2351, Australia > > > > ngayw...@une.edu.au http://turing.une.edu.au/~ngaywood > > Phone: +61 (0)2 6773 2412 Mobile: +61 (0)4 7862 0062 > > > > Please avoid sending me Word or Power Point attachments. > > See http://www.gnu.org/philosophy/no-word-attachments.html > > ___ > > x2go-user mailing list > > x2go-user@lists.x2go.org > > https://lists.x2go.org/listinfo/x2go-user > -- Norman Gaywood, Computer Systems Officer School of Science and Technology University of New England Armidale NSW 2351, Australia ngayw...@une.edu.au http://turing.une.edu.au/~ngaywood Phone: +61 (0)2 6773 2412 Mobile: +61 (0)4 7862 0062 Please avoid sending me Word or Power Point attachments. See http://www.gnu.org/philosophy/no-word-attachments.html ___ x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
[X2Go-User] Fedora 36 and glx fails with GLXUnsupportedPrivateRequest
In Fedora 35 glxinfo (and glxgears) worked fine with x2goserver-4.1.0.3-17.fc35.x86_64 After updating to Fedora 36, x2goserver-4.1.0.3-17.fc36.x86_64, glxinfo no longer works. $ glxinfo name of display: :50.0 X Error of failed request: GLXUnsupportedPrivateRequest Major opcode of failed request: 143 (GLX) Minor opcode of failed request: 17 (X_GLXVendorPrivateWithReply) Serial number of failed request: 27 Current serial number in output stream: 27 Linux x2goclient X2Go Client v. 4.1.2.2 (Qt - 5.15.3) Is there any way to make this work? Not sure what programs actually use it. Thankfully matlab still seems to work. -- Norman Gaywood, Computer Systems Officer School of Science and Technology University of New England Armidale NSW 2351, Australia ngayw...@une.edu.au http://turing.une.edu.au/~ngaywood Phone: +61 (0)2 6773 2412 Mobile: +61 (0)4 7862 0062 Please avoid sending me Word or Power Point attachments. See http://www.gnu.org/philosophy/no-word-attachments.html ___ x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
Re: [X2Go-User] session freezing
Hi Neal, Perhaps you have both xfce4-screensaver and xscreensaver installed and active? I saw the same problem until I uninstalled xscreensaver. On Wed, 26 Jan 2022 at 23:22, Neal Becker wrote: > Client and server are both Fedora 35. > > xfce session. > > This setup has worked for years. An SSD failed on the server, and after > re-installing F35 on it, now x2go session keeps freezing. Seems to happen > at least when it is left running unattended. The x2go screen is shown, but > unable to get focus into any window, click on any icon. Suspend/unsuspend > does not fix it. Only terminate and restart fixes it. > > Any suggestions? > > Thanks, > Neal > > -- > *Those who don't understand recursion are doomed to repeat it* > ___ > x2go-user mailing list > x2go-user@lists.x2go.org > https://lists.x2go.org/listinfo/x2go-user > -- Norman Gaywood, Computer Systems Officer School of Science and Technology University of New England Armidale NSW 2351, Australia ngayw...@une.edu.au http://turing.une.edu.au/~ngaywood Phone: +61 (0)2 6773 2412 Mobile: +61 (0)4 7862 0062 Please avoid sending me Word or Power Point attachments. See http://www.gnu.org/philosophy/no-word-attachments.html ___ x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
Re: [X2Go-User] x2goagent segfaulting on client connect
I had something similar a few months ago: https://lists.x2go.org/pipermail/x2go-user/2021-July/006579.html Essentially, nvidia taking over libGL. I fixed it with (from the above post): Thanks Ulrich! > Yes indeed the system was using the libGL of nvidia. I did these steps to > recover the system: yum reinstall libglvnd* mesa* That fixes most of the symlinks of libGL in /usr/lib64 to again point to > the system's libGL. Except for this one: > # ll /usr/lib64/libGLX_indirect.so.0 > lrwxrwxrwx. 1 root root 26 Jul 1 16:03 /usr/lib64/libGLX_indirect.so.0 -> > libGLX_nvidia.so.470.42.01 So I did this: > # cd /usr/lib64 > # rm -f libGLX_indirect.so.0 > # ln -s libGLX_mesa.so.0.0.0 libGLX_indirect.so.0 > # ll /usr/lib64/libGLX_indirect.so.0 > lrwxrwxrwx. 1 root root 20 Jul 14 11:43 /usr/lib64/libGLX_indirect.so.0 -> > libGLX_mesa.so.0.0.0 Now glxinfo (and firefox) don't crash nxagent! > Not sure of the full implications of manually modifying that symlink. On Wed, 20 Oct 2021 at 04:36, Eric Shell wrote: > I have a CentOS 7.9 system on which X2Go was previously working perfectly, > but which is now broken. It broke after a typical yum update but I am not > sure what changed to break things and I would like some help debugging and > resolving this issue. I should mention that as part of my troubleshooting I > have begun using NVIDIA kmod drivers from the ELRepo instead of ones > installed from NVIDIA's .run file. > > The behavior I'm seeing in every failed connection produces the following > log entries. The system has both XFCE and MATE installed and both produce > the same output. > > - > > Oct 19 10:21:29 c113256 /usr/bin/x2goruncommand: launching session with > Xsession-x2go mechanism, using STARTUP="mate-session" > Oct 19 10:21:29 c113256 /usr/bin/x2goruncommand: dbus wrapper available as > /usr/bin/dbus-run-session > Oct 19 10:21:30 c113256 kernel: resource sanity check: requesting [mem > 0x000c-0x000f], which spans more than PCI Bus :00 [mem > 0x000c4000-0x000c7fff window] > Oct 19 10:21:30 c113256 kernel: caller > os_map_kernel_space.part.6+0x95/0xc0 [nvidia] mapping multiple BARs > Oct 19 10:21:31 c113256 kernel: x2goagent[58376]: segfault at 48 ip > 555fbee349ab sp 7ffe380702a0 error 4 in nxagent[555fbecd6000+439000] > Oct 19 10:21:31 c113256 abrt-hook-ccpp: Process 58376 (nxagent) of user > 1001 killed by SIGSEGV - dumping core > > - > > Interestingly, x2goagent does not segfault if I have the X2Go client run > /bin/xclock. The window opens without issue. /bin/firefox fails. > /bin/glxgears also fails. Is this related to GL/GLX? How can I obtain more > detailed information? > > Thank you! > > -- > Eric Shell > PBSci Technical Staff > esh...@ucsc.edu > 831 459 4919 > ___ > x2go-user mailing list > x2go-user@lists.x2go.org > https://lists.x2go.org/listinfo/x2go-user > -- Norman Gaywood, Computer Systems Officer School of Science and Technology University of New England Armidale NSW 2351, Australia ngayw...@une.edu.au http://turing.une.edu.au/~ngaywood Phone: +61 (0)2 6773 2412 Mobile: +61 (0)4 7862 0062 Please avoid sending me Word or Power Point attachments. See http://www.gnu.org/philosophy/no-word-attachments.html ___ x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
Re: [X2Go-User] nxagent SIGSEGV when running glxinfo (and firefox) on a host with cuda installed
Thanks Ulrich! Yes indeed the system was using the libGL of nvidia. I did these steps to recover the system: yum reinstall libglvnd* mesa* That fixes most of the symlinks of libGL in /usr/lib64 to again point to the system's libGL. Except for this one: # ll /usr/lib64/libGLX_indirect.so.0 lrwxrwxrwx. 1 root root 26 Jul 1 16:03 /usr/lib64/libGLX_indirect.so.0 -> libGLX_nvidia.so.470.42.01 So I did this: # cd /usr/lib64 # rm -f libGLX_indirect.so.0 # ln -s libGLX_mesa.so.0.0.0 libGLX_indirect.so.0 # ll /usr/lib64/libGLX_indirect.so.0 lrwxrwxrwx. 1 root root 20 Jul 14 11:43 /usr/lib64/libGLX_indirect.so.0 -> libGLX_mesa.so.0.0.0 Now glxinfo (and firefox) don't crash nxagent! Not sure of the full implications of manually modifying that symlink. On Tue, 13 Jul 2021 at 20:07, Ulrich Sibiller wrote: > I think the problem is that the system now uses the libGL of nvidia > instead of the libGL that came with the system. So try to reinstall > the lib. See > https://forums.developer.nvidia.com/t/multiple-glx-client-libraries-in-the-nvidia-linux-driver-installer-package/41308 > for some details regarding the libGL handling in the nvidia driver. > > Hope that helps! > > Uli > > On Tue, Jul 13, 2021 at 9:05 AM Norman Gaywood > wrote: > > > > We have some centos 7 systems with GPUs that users access with x2go to > run their machine learning task. > > > > After an update to cuda on the centos 7 systems, nxagent now segfaults > when I run glxinfo or firefox. > > > > nxagent-3.5.99.26-1.el7.x86_64 > > x2goserver-4.1.0.3-9.el7.x86_64 > > cuda-11.4.0-1.x86_64 > > kmod-nvidia-latest-dkms-470.42.01-1.el7.x86_64 > > > > What's also interesting is that if I x2go into a host that does not have > cuda installed, and then: > >ssh -Y cudahost glxinfo > > then the nxagent on the non-cuda host segfaults. > > > > This happens with glxinfo and when trying to start firefox. > google-chrome works fine. > > > > This was all working fine until I updated cuda and the GPU driver. On > Centos 7.9.2009 > > This happens on a host with a K80 GPU and another host that has a V100 > GPU. > > > > I also have cuda-11.4 on a Fedora 34 host with a V100 GPU. > > If I x2go (or ssh -Y) to the Fedora 34 host, glxinfo (and firefox) run > fine. > > > > nxagent-3.5.99.26-1.fc34.x86_64 > > x2goserver-4.1.0.3-10.fc34.x86_64 > > cuda-11.4.0-1.x86_64 > > kmod-nvidia-latest-dkms-3:465.19.01-1.fc33.x86_64 > > > > Any suggestions on how I might provide some debugging information to the > developers? > > > > > > abrt-cli list --since 1626070479 > > id 35db2c461122be7229abdbe219ddfd92d0613da8 > > reason: nxagent killed by SIGSEGV > > time: Mon 05 Jul 2021 09:37:02 AEST > > cmdline:x2goagent -nolisten tcp -nolisten tcp -dpi 97 -D -auth > /home/ngaywood/.Xauthority -geometry 2560x1440 -name > X2GO-ngaywood-50-1625441817_stDMATE_dp24 :50 > > package:nxagent-3.5.99.26-1.el7 > > uid:5125 (ngaywood) > > count: 21 > > Directory: /var/spool/abrt/ccpp-2021-07-05-09:37:02-2523 > > > > > > > > -- > > Norman Gaywood, Computer Systems Officer > > School of Science and Technology > > University of New England > > Armidale NSW 2351, Australia > > > > ngayw...@une.edu.au http://turing.une.edu.au/~ngaywood > > Phone: +61 (0)2 6773 2412 Mobile: +61 (0)4 7862 0062 > > > > Please avoid sending me Word or Power Point attachments. > > See http://www.gnu.org/philosophy/no-word-attachments.html > > ___ > > x2go-user mailing list > > x2go-user@lists.x2go.org > > https://lists.x2go.org/listinfo/x2go-user > -- Norman Gaywood, Computer Systems Officer School of Science and Technology University of New England Armidale NSW 2351, Australia ngayw...@une.edu.au http://turing.une.edu.au/~ngaywood Phone: +61 (0)2 6773 2412 Mobile: +61 (0)4 7862 0062 Please avoid sending me Word or Power Point attachments. See http://www.gnu.org/philosophy/no-word-attachments.html ___ x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
[X2Go-User] nxagent SIGSEGV when running glxinfo (and firefox) on a host with cuda installed
We have some centos 7 systems with GPUs that users access with x2go to run their machine learning task. After an update to cuda on the centos 7 systems, nxagent now segfaults when I run glxinfo or firefox. nxagent-3.5.99.26-1.el7.x86_64 x2goserver-4.1.0.3-9.el7.x86_64 cuda-11.4.0-1.x86_64 kmod-nvidia-latest-dkms-470.42.01-1.el7.x86_64 What's also interesting is that if I x2go into a host that does not have cuda installed, and then: ssh -Y cudahost glxinfo then the nxagent on the non-cuda host segfaults. This happens with glxinfo and when trying to start firefox. google-chrome works fine. This was all working fine until I updated cuda and the GPU driver. On Centos 7.9.2009 This happens on a host with a K80 GPU and another host that has a V100 GPU. I also have cuda-11.4 on a Fedora 34 host with a V100 GPU. If I x2go (or ssh -Y) to the Fedora 34 host, glxinfo (and firefox) run fine. nxagent-3.5.99.26-1.fc34.x86_64 x2goserver-4.1.0.3-10.fc34.x86_64 cuda-11.4.0-1.x86_64 kmod-nvidia-latest-dkms-3:465.19.01-1.fc33.x86_64 Any suggestions on how I might provide some debugging information to the developers? abrt-cli list --since 1626070479 id 35db2c461122be7229abdbe219ddfd92d0613da8 reason: nxagent killed by SIGSEGV time: Mon 05 Jul 2021 09:37:02 AEST cmdline:x2goagent -nolisten tcp -nolisten tcp -dpi 97 -D -auth /home/ngaywood/.Xauthority -geometry 2560x1440 -name X2GO-ngaywood-50-1625441817_stDMATE_dp24 :50 package:nxagent-3.5.99.26-1.el7 uid:5125 (ngaywood) count: 21 Directory: /var/spool/abrt/ccpp-2021-07-05-09:37:02-2523 -- Norman Gaywood, Computer Systems Officer School of Science and Technology University of New England Armidale NSW 2351, Australia ngayw...@une.edu.au http://turing.une.edu.au/~ngaywood Phone: +61 (0)2 6773 2412 Mobile: +61 (0)4 7862 0062 Please avoid sending me Word or Power Point attachments. See http://www.gnu.org/philosophy/no-word-attachments.html ___ x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
Re: [X2Go-User] Wayland launch scripts being used?
XFCE works with Fedora 34 if you turn off compositing. See: Applications->Settings->Window Manager Tweaks->Compositor To turn off globally (can be overridden by user), I created: /etc/xdg/xfce4/xfconf/xfce-perchannel-xml/xfwm4.xml with this added: On Mon, 3 May 2021 at 01:38, Jeff Sadowski wrote: > So I'm not sure why so many of my desktops in Fedora have stopped working > with x2go but I heavily suspect it is them transitioning all desktops to > wayland. I know gnome still has an option to select xorg from the console > but x2go does not provide any clarification on this kind of selection. > Maybe if I understood how the server side selects the script to run to > start the desktop depending on the selection from the client side I could > help the package maintainers make things easier for x2go users. All I know > for certain is: I was using XFCE desktop in Fedora 33 when I upgraded to > Fedora 34 XFCE became unusable over x2go. I started trying other desktops > and noticed they do not act right. Gnome over x2g on fedora 34 doesn't even > start. KDE seems to have some issues. Mate seems to work. > ___ > x2go-user mailing list > x2go-user@lists.x2go.org > https://lists.x2go.org/listinfo/x2go-user > -- Norman Gaywood, Computer Systems Officer School of Science and Technology University of New England Armidale NSW 2351, Australia ngayw...@une.edu.au http://turing.une.edu.au/~ngaywood Phone: +61 (0)2 6773 2412 Mobile: +61 (0)4 7862 0062 Please avoid sending me Word or Power Point attachments. See http://www.gnu.org/philosophy/no-word-attachments.html ___ x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
Re: [X2Go-User] session.log file fills disk
Hi David, Yes, I see this quite a bit. I have a lot of students using x2goclient. Every now and then someone seems to lose control of their application (I don't know how) and it starts writing to the session log file in a loop. Quite often the log information is something like a program writing a prompt message (Like "Enter a number:") and this gets stuck in a loop. In a terminal, do a tail on the session log file, something like: tail -f .xsession.log and you might see what's writing to the log file. To fix it, you have to kill the program that's doing the logging, terminate the session and then remove the session log. You have to make sure the program doing the logging is gone and not holding the session log open, otherwise the space is not reclaimed. On Wed, 16 Dec 2020 at 06:17, David Schumm wrote: > We are seeing this on multiple machines where the session.log file is > massive. I’ve seen them as large as 82gb. This of course causes the disk > to fill > > When you attempt to open it it says it’s a binary file > > Server is Centos 7 running x2go server 4.1.0.3-9 > > Anyone seen this? > > > > > > -- > > This e-mail may contain SEAKR Engineering (SEAKR) Confidential and > Proprietary Information. If this message is not intended for you, you are > strictly prohibited from using this message, its contents or attachments in > any way. If you have received this message in error, please delete the > message from your mailbox. This e-mail may contain export-controlled > material and should be handled accordingly. > ___ > x2go-user mailing list > x2go-user@lists.x2go.org > https://lists.x2go.org/listinfo/x2go-user > -- Norman Gaywood, Computer Systems Officer School of Science and Technology University of New England Armidale NSW 2351, Australia ngayw...@une.edu.au http://turing.une.edu.au/~ngaywood Phone: +61 (0)2 6773 2412 Mobile: +61 (0)4 7862 0062 Please avoid sending me Word or Power Point attachments. See http://www.gnu.org/philosophy/no-word-attachments.html ___ x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
Re: [X2Go-User] Pulseaudio failed to start x2goclient 4.1.2.0
This is the WIndows (10) client. Connecting to Fedora 29 but the problem occurs before even trying to connect to a remote system. On Fri, 29 Mar 2019 at 12:51, Norman Gaywood wrote: > Hi, > We are looking to update x2goclient in our computer labs from 4.1.0.0 to > 4.1.2.0 > 4.1.0.0 suffers from the flashing screen when maximised problem. > 4.1.2.0 fixes the maximising problem, hover we now get a: > "Pulseaudio failed to start" popup when starting x2goclient. > > I notice a couple of bugs reporting this but can't see how to fix it. > Is there a fix? > > Cheers. > -- > Norman Gaywood, Computer Systems Officer > School of Science and Technology > University of New England > Armidale NSW 2351, Australia > > ngayw...@une.edu.au http://turing.une.edu.au/~ngaywood > Phone: +61 (0)2 6773 2412 Mobile: +61 (0)4 7862 0062 > > Please avoid sending me Word or Power Point attachments. > See http://www.gnu.org/philosophy/no-word-attachments.html > -- Norman Gaywood, Computer Systems Officer School of Science and Technology University of New England Armidale NSW 2351, Australia ngayw...@une.edu.au http://turing.une.edu.au/~ngaywood Phone: +61 (0)2 6773 2412 Mobile: +61 (0)4 7862 0062 Please avoid sending me Word or Power Point attachments. See http://www.gnu.org/philosophy/no-word-attachments.html ___ x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
Re: [X2Go-User] Can we have some old rpms in the x2go.repo?
On Thu, 15 Mar 2018 at 13:45, Mihai Moldovan <io...@ionic.de> wrote: > > > The move across the screen segfault has happened to 3 users (including > me) and > > all have been linux clients (Fedora I think). > > The move across screen segfault seems to go away sometimes for > undermined reasons. > > I personally wasn't able to reproduce that either, but it seems to be > depending > on quite some factors. > If I connect, suspend the session, resume the session. I can then move my session across screens. Worked for me a few times so far. > Can you tell me the display configuration (size and positioning) you are > seeing > this with and what window managers/desktop environments and operating > systems > are used on the client and server side? > Not sure I can in a useful manner, but: I keep changing my connection screen size to many different sizes. I'm not sure how to report my physical workstation screen sizes but: Dell 27" 2560x1440, Dell 29" 2560x1018 The workstation x2goclient is x2goclient-4.1.1.0-1.fc27.x86_64 All desktop environments on the server(s) are XFCE, xfce4-session-4.12.1-12.fc27.x86_64 The server(s) are running: libNX_X11-6-3.5.99.15-0.0build1.1.git20180308.2971.main.fc27.x86_64 libXcompext3-3.5.0.33-0.0x2go1.1.git20180204.776.main.fc27.x86_64 nxagent-3.5.99.15-0.0build1.1.git20180308.2971.main.fc27.x86_64 nx-libs-3.5.99.15-0.0build1.1.git20180308.2971.main.fc27.x86_64 nxproxy-3.5.99.15-0.0build1.1.git20180308.2971.main.fc27.x86_64 perl-X2Go-Log-4.1.0.0-0.0x2go1.1.git20180302.1517.main.fc27.x86_64 perl-X2Go-Server-4.1.0.0-0.0x2go1.1.git20180302.1517.main.fc27.x86_64 perl-X2Go-Server-DB-4.1.0.0-0.0x2go1.1.git20180302.1517.main.fc27.x86_64 x2goserver-4.1.0.0-0.0x2go1.1.git20180302.1517.main.fc27.x86_64 x2goserver-common-4.1.0.0-0.0x2go1.1.git20180302.1517.main.fc27.x86_64 x2goserver-extensions-4.1.0.0-0.0x2go1.1.git20180302.1517.main.fc27.x86_64 x2goserver-x2goagent-4.1.0.0-0.0x2go1.1.git20180302.1517.main.fc27.x86_64 x2goserver-xsession-4.1.0.0-0.0x2go1.1.git20180302.1517.main.fc27.x86_64 The prod server would have mostly Windows x2go clients connecting, but some Mac and some Linux, all different versions. The dev server would only have x2goclient-4.1.1.0-1.fc27.x86_64 connecting. The servers (dev and prod) are Fedora 27 running: libNX_X11-6-3.5.99.15-0.0build1.1.git20180308.2971.main.fc27.x86_64 libXcompext3-3.5.0.33-0.0x2go1.1.git20180204.776.main.fc27.x86_64 nxagent-3.5.99.15-0.0build1.1.git20180308.2971.main.fc27.x86_64 nx-libs-3.5.99.15-0.0build1.1.git20180308.2971.main.fc27.x86_64 nxproxy-3.5.99.15-0.0build1.1.git20180308.2971.main.fc27.x86_64 perl-X2Go-Log-4.1.0.0-0.0x2go1.1.git20180302.1517.main.fc27.x86_64 perl-X2Go-Server-4.1.0.0-0.0x2go1.1.git20180302.1517.main.fc27.x86_64 perl-X2Go-Server-DB-4.1.0.0-0.0x2go1.1.git20180302.1517.main.fc27.x86_64 x2goserver-4.1.0.0-0.0x2go1.1.git20180302.1517.main.fc27.x86_64 x2goserver-common-4.1.0.0-0.0x2go1.1.git20180302.1517.main.fc27.x86_64 x2goserver-extensions-4.1.0.0-0.0x2go1.1.git20180302.1517.main.fc27.x86_64 x2goserver-x2goagent-4.1.0.0-0.0x2go1.1.git20180302.1517.main.fc27.x86_64 x2goserver-xsession-4.1.0.0-0.0x2go1.1.git20180302.1517.main.fc27.x86_64 -- Norman Gaywood, Computer Systems Officer School of Science and Technology University of New England Armidale NSW 2351, Australia ngayw...@une.edu.au http://turing.une.edu.au/~ngaywood Phone: +61 (0)2 6773 2412 Mobile: +61 (0)4 7862 0062 Please avoid sending me Word or Power Point attachments. See http://www.gnu.org/philosophy/no-word-attachments.html ___ x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
Re: [X2Go-User] Can we have some old rpms in the x2go.repo?
So I've updated dev to the latest again 3.5.99.15-0.0build1.1.git20180308.2971.main.fc27 And I seem to get an nxagent segfault every time I move the session window into another screen. Same version in production and it was stable for a few days now. I could move it across screens. I suspended and resumed several times. But, after logging out of production and logging back in again, I'm back to segfaulting when moving across screens. It's a very strange problem :-( Executive summary: The segfault on connect I have not reproduced. But its been reported by several of my users. I have around 50 logged in users at the moment. The login segfault only happens to very few (5/6). Some of them seemed to be working now. The move across the screen segfault has happened to 3 users (including me) and all have been linux clients (Fedora I think). The move across screen segfault seems to go away sometimes for undermined reasons. On Thu, 15 Mar 2018 at 12:36, Norman Gaywood <ngayw...@une.edu.au> wrote: > On Tue, 13 Mar 2018 at 20:29, Mihai Moldovan <io...@ionic.de> wrote: > >> * On 03/13/2018 10:25 AM, Norman Gaywood wrote: >> >> https://snapshots.packages.x2go.org/20180302/fedora/27/main/x86_64/rpms/nx-libs/ >> >> >> > Fixing the bug could take weeks, so it would be good to roll back 1 >> version that >> > seemed to be more stable while we wait. >> >> The other version has a different severe bug, related to Screen Savers >> and DPMS. >> Make sure to disable them, if you really want to downgrade. >> > > Thanks for those snapshot links. I manage to use them an roll back 1 > version on the dev system to avoid: > > https://github.com/ArcticaProject/nx-libs/issues/679 (Coredump when > connecting) > https://github.com/ArcticaProject/nx-libs/issues/677 (nxagent crashes > when moving the session window into another screen) > > I was about to roll back production, but users that were getting seg > faults (on connecting or moving across screens) seemed to start working! > > So I've left production alone for now. > > Of the 5/6 users that hit these problems most of them seem to be > connecting again. > > Seg faults are still occurring in nxagent and some users still have not > connected successfully, but most seem fine and get on after a few retries. > > ??? > > 3.5.99.14-0.0build1.1.git20180302.2954.main.fc27 (dev) > 3.5.99.15-0.0build1.1.git20180308.2971.main.fc27 (prod) > > -- > Norman Gaywood, Computer Systems Officer > School of Science and Technology > University of New England > Armidale NSW 2351, Australia > > ngayw...@une.edu.au http://turing.une.edu.au/~ngaywood > Phone: +61 (0)2 6773 2412 Mobile: +61 (0)4 7862 0062 > > Please avoid sending me Word or Power Point attachments. > See http://www.gnu.org/philosophy/no-word-attachments.html > -- Norman Gaywood, Computer Systems Officer School of Science and Technology University of New England Armidale NSW 2351, Australia ngayw...@une.edu.au http://turing.une.edu.au/~ngaywood Phone: +61 (0)2 6773 2412 Mobile: +61 (0)4 7862 0062 Please avoid sending me Word or Power Point attachments. See http://www.gnu.org/philosophy/no-word-attachments.html ___ x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
Re: [X2Go-User] Can we have some old rpms in the x2go.repo?
On Tue, 13 Mar 2018 at 20:29, Mihai Moldovan <io...@ionic.de> wrote: > * On 03/13/2018 10:25 AM, Norman Gaywood wrote: > > https://snapshots.packages.x2go.org/20180302/fedora/27/main/x86_64/rpms/nx-libs/ > > > > Fixing the bug could take weeks, so it would be good to roll back 1 > version that > > seemed to be more stable while we wait. > > The other version has a different severe bug, related to Screen Savers and > DPMS. > Make sure to disable them, if you really want to downgrade. > Thanks for those snapshot links. I manage to use them an roll back 1 version on the dev system to avoid: https://github.com/ArcticaProject/nx-libs/issues/679 (Coredump when connecting) https://github.com/ArcticaProject/nx-libs/issues/677 (nxagent crashes when moving the session window into another screen) I was about to roll back production, but users that were getting seg faults (on connecting or moving across screens) seemed to start working! So I've left production alone for now. Of the 5/6 users that hit these problems most of them seem to be connecting again. Seg faults are still occurring in nxagent and some users still have not connected successfully, but most seem fine and get on after a few retries. ??? 3.5.99.14-0.0build1.1.git20180302.2954.main.fc27 (dev) 3.5.99.15-0.0build1.1.git20180308.2971.main.fc27 (prod) -- Norman Gaywood, Computer Systems Officer School of Science and Technology University of New England Armidale NSW 2351, Australia ngayw...@une.edu.au http://turing.une.edu.au/~ngaywood Phone: +61 (0)2 6773 2412 Mobile: +61 (0)4 7862 0062 Please avoid sending me Word or Power Point attachments. See http://www.gnu.org/philosophy/no-word-attachments.html ___ x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
Re: [X2Go-User] Can we have some old rpms in the x2go.repo?
Ah yes, thanks. Now to do some more testing :-( On Tue, 13 Mar 2018 at 20:29, Mihai Moldovan <io...@ionic.de> wrote: > * On 03/13/2018 10:25 AM, Norman Gaywood wrote: > > But all those links/folders on http://snapshots.packages.x2go.org/ seem > to be empty. > > > > Or am I missing something? > > Nope, they are not. See for instance > > https://snapshots.packages.x2go.org/20180302/fedora/27/main/x86_64/rpms/nx-libs/ > > It's just the index page that is "blank", just like > https://packages.x2go.org/ is. > > > > Fixing the bug could take weeks, so it would be good to roll back 1 > version that > > seemed to be more stable while we wait. > > The other version has a different severe bug, related to Screen Savers and > DPMS. > Make sure to disable them, if you really want to downgrade. > > > > Mihai > > > -- Norman Gaywood, Computer Systems Officer School of Science and Technology University of New England Armidale NSW 2351, Australia ngayw...@une.edu.au http://turing.une.edu.au/~ngaywood Phone: +61 (0)2 6773 2412 Mobile: +61 (0)4 7862 0062 Please avoid sending me Word or Power Point attachments. See http://www.gnu.org/philosophy/no-word-attachments.html ___ x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
Re: [X2Go-User] X2Go server, nxagent causes segfault
I've got several users reporting seg faults in nxagent Mine occur when moving my x2goclient window from one screen to another. Simple resizing seems OK. Not sure if this is the same for all my users though. Seems to be happening after these updates: nxproxy-3.5.99.15-0.0build1.1.git20180308.2971.main.fc27.x86_64 Mon 12 Mar 2018 09:14:38 AEDT nxagent-3.5.99.15-0.0build1.1.git20180308.2971.main.fc27.x86_64 Mon 12 Mar 2018 09:14:38 AEDT libXcompshad3-3.5.99.15-0.0build1.1.git20180308.2971.main.fc27.x86_64 Mon 12 Mar 2018 09:14:37 AEDT libXcomp3-3.5.99.15-0.0build1.1.git20180308.2971.main.fc27.x86_64 Mon 12 Mar 2018 09:14:36 AEDT libNX_X11-6-3.5.99.15-0.0build1.1.git20180308.2971.main.fc27.x86_64 Mon 12 Mar 2018 09:14:36 AEDT nx-libs-3.5.99.15-0.0build1.1.git20180308.2971.main.fc27.x86_64 Mon 12 Mar 2018 09:14:35 AEDT It does not seem to be possible to roll back. On Tue, 13 Mar 2018 at 15:02, Norman Gaywood <ngayw...@une.edu.au> wrote: > I'm thinking it may be the latest update to libNX_X11 (a few days ago) > > But the x2go repo does not contain old versions, so I can't test the > downgrade. > > Anyone know how to downgrade? > rpm -q libNX_X11-6 > libNX_X11-6-3.5.99.15-0.0build1.1.git20180308.2971.main.fc27.x86_64 > > dnf downgrade libNX_X11-6 > Last metadata expiration check: 0:00:00 ago on Tue 13 Mar 2018 15:01:38 > AEDT. > Package libNX_X11-6 of lowest version already installed, cannot downgrade > it. > Error: No packages marked for downgrade. > > > > > On Tue, 13 Mar 2018 at 14:44, Norman Gaywood <ngayw...@une.edu.au> wrote: > >> I'm getting this on Fedora 27 (XFCE) as well. >> >> x2goserver-4.1.0.0-0.0x2go1.1.git20180302.1517.main.fc27.x86_64 >> >> I notice that if you don't resize or move the x2go client window it stays >> stable (does not segfault). >> >> >> On Mon, 12 Mar 2018 at 22:35, Kalle Tuulos <ka...@tuulos.net> wrote: >> >>> Hello >>> >>> I'm using X2Go server in several computers, all running Ubuntu. Just >>> today, one of my computers (headless Linux box) just froze and I had to >>> give it a power cycle reset. After powering up again, I can't any more >>> connect to X2Go. >>> >>> I'm getting following into /var/log/syslog: >>> ---8<---8<--- >>> Mar 12 13:15:40 kallebuntu systemd[1]: Started Session 10 of user >>> ktuulos. >>> Mar 12 13:15:49 kallebuntu /usr/sbin/x2gocleansessions[1091]: >>> ktuulos-50-1520853345_stDLXDE_dp32: state file for this session does not >>> exist: /tmp/.x2go-ktuulos/C-ktuulos-50-1520853345_stDLXDE_dp32/state (this >>> can be ignored during session startups) >>> Mar 12 13:15:51 kallebuntu /usr/bin/x2gostartagent: successfully started >>> X2Go Agent session with ID ktuulos-50-1520853345_stDLXDE_dp32 >>> Mar 12 13:15:58 kallebuntu kernel: [ 1315.845394] nxagent[9647]: >>> segfault at 8 ip 56286f70db3a sp 7ffea2bd1bc0 error 4 in >>> nxagent[56286f693000+432000] >>> Mar 12 13:16:04 kallebuntu /usr/bin/x2gosetkeyboard: Setting X keyboard >>> according to >>> /home/ktuulos/.x2go/C-ktuulos-50-1520853345_stDLXDE_dp32/keyboard >>> Mar 12 13:16:05 kallebuntu /usr/bin/x2goruncommand: launching session >>> with Xsession-x2go mechanism, using STARTUP="startlxde" >>> Mar 12 13:16:05 kallebuntu /usr/bin/x2goruncommand: dbus wrapper >>> available as /usr/bin/dbus-run-session >>> ---8<---8<--- >>> >>> This computer is running Ubuntu 16.04. X2go server has been installed >>> using the ppa method. >>> ---8<---8<--- >>> ktuulos@kallebuntu:~$ uname -a >>> Linux kallebuntu 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 >>> 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux >>> ktuulos@kallebuntu:~$ dpkg -s x2goserver | grep Version >>> Version: 4.1.0.0-0~1517~ubuntu16.04.1 >>> ktuulos@kallebuntu:~$ cat >>> /etc/apt/sources.list.d/x2go-ubuntu-stable-xenial.list >>> deb http://ppa.launchpad.net/x2go/stable/ubuntu xenial main >>> # deb-src http://ppa.launchpad.net/x2go/stable/ubuntu xenial main >>> ---8<---8<--- >>> >>> There seem to be no hardware problems - I installed mcelog and I'm now >>> monitoring its output. Nothing. >>> >>> Could anyone give some hints? I have spent the last hour googling about >>> "nxagent segfault", but I haven't found anything, which would help. >>> >>> Thanks, >>> Kalle >>> >>> ___ >>> x2go-user mailing list >>> x2go-user@lists.x
Re: [X2Go-User] X2Go server, nxagent causes segfault
I'm thinking it may be the latest update to libNX_X11 (a few days ago) But the x2go repo does not contain old versions, so I can't test the downgrade. Anyone know how to downgrade? rpm -q libNX_X11-6 libNX_X11-6-3.5.99.15-0.0build1.1.git20180308.2971.main.fc27.x86_64 dnf downgrade libNX_X11-6 Last metadata expiration check: 0:00:00 ago on Tue 13 Mar 2018 15:01:38 AEDT. Package libNX_X11-6 of lowest version already installed, cannot downgrade it. Error: No packages marked for downgrade. On Tue, 13 Mar 2018 at 14:44, Norman Gaywood <ngayw...@une.edu.au> wrote: > I'm getting this on Fedora 27 (XFCE) as well. > > x2goserver-4.1.0.0-0.0x2go1.1.git20180302.1517.main.fc27.x86_64 > > I notice that if you don't resize or move the x2go client window it stays > stable (does not segfault). > > > On Mon, 12 Mar 2018 at 22:35, Kalle Tuulos <ka...@tuulos.net> wrote: > >> Hello >> >> I'm using X2Go server in several computers, all running Ubuntu. Just >> today, one of my computers (headless Linux box) just froze and I had to >> give it a power cycle reset. After powering up again, I can't any more >> connect to X2Go. >> >> I'm getting following into /var/log/syslog: >> ---8<---8<--- >> Mar 12 13:15:40 kallebuntu systemd[1]: Started Session 10 of user ktuulos. >> Mar 12 13:15:49 kallebuntu /usr/sbin/x2gocleansessions[1091]: >> ktuulos-50-1520853345_stDLXDE_dp32: state file for this session does not >> exist: /tmp/.x2go-ktuulos/C-ktuulos-50-1520853345_stDLXDE_dp32/state (this >> can be ignored during session startups) >> Mar 12 13:15:51 kallebuntu /usr/bin/x2gostartagent: successfully started >> X2Go Agent session with ID ktuulos-50-1520853345_stDLXDE_dp32 >> Mar 12 13:15:58 kallebuntu kernel: [ 1315.845394] nxagent[9647]: segfault >> at 8 ip 56286f70db3a sp 7ffea2bd1bc0 error 4 in >> nxagent[56286f693000+432000] >> Mar 12 13:16:04 kallebuntu /usr/bin/x2gosetkeyboard: Setting X keyboard >> according to >> /home/ktuulos/.x2go/C-ktuulos-50-1520853345_stDLXDE_dp32/keyboard >> Mar 12 13:16:05 kallebuntu /usr/bin/x2goruncommand: launching session >> with Xsession-x2go mechanism, using STARTUP="startlxde" >> Mar 12 13:16:05 kallebuntu /usr/bin/x2goruncommand: dbus wrapper >> available as /usr/bin/dbus-run-session >> ---8<---8<--- >> >> This computer is running Ubuntu 16.04. X2go server has been installed >> using the ppa method. >> ---8<---8<--- >> ktuulos@kallebuntu:~$ uname -a >> Linux kallebuntu 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 >> 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux >> ktuulos@kallebuntu:~$ dpkg -s x2goserver | grep Version >> Version: 4.1.0.0-0~1517~ubuntu16.04.1 >> ktuulos@kallebuntu:~$ cat >> /etc/apt/sources.list.d/x2go-ubuntu-stable-xenial.list >> deb http://ppa.launchpad.net/x2go/stable/ubuntu xenial main >> # deb-src http://ppa.launchpad.net/x2go/stable/ubuntu xenial main >> ---8<---8<--- >> >> There seem to be no hardware problems - I installed mcelog and I'm now >> monitoring its output. Nothing. >> >> Could anyone give some hints? I have spent the last hour googling about >> "nxagent segfault", but I haven't found anything, which would help. >> >> Thanks, >> Kalle >> >> ___ >> x2go-user mailing list >> x2go-user@lists.x2go.org >> https://lists.x2go.org/listinfo/x2go-user > > > > -- > Norman Gaywood, Computer Systems Officer > School of Science and Technology > University of New England > Armidale NSW 2351, Australia > > ngayw...@une.edu.au http://turing.une.edu.au/~ngaywood > Phone: +61 (0)2 6773 2412 Mobile: +61 (0)4 7862 0062 > > Please avoid sending me Word or Power Point attachments. > See http://www.gnu.org/philosophy/no-word-attachments.html > -- Norman Gaywood, Computer Systems Officer School of Science and Technology University of New England Armidale NSW 2351, Australia ngayw...@une.edu.au http://turing.une.edu.au/~ngaywood Phone: +61 (0)2 6773 2412 Mobile: +61 (0)4 7862 0062 Please avoid sending me Word or Power Point attachments. See http://www.gnu.org/philosophy/no-word-attachments.html ___ x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
Re: [X2Go-User] X2Go server, nxagent causes segfault
I'm getting this on Fedora 27 (XFCE) as well. x2goserver-4.1.0.0-0.0x2go1.1.git20180302.1517.main.fc27.x86_64 I notice that if you don't resize or move the x2go client window it stays stable (does not segfault). On Mon, 12 Mar 2018 at 22:35, Kalle Tuulos <ka...@tuulos.net> wrote: > Hello > > I'm using X2Go server in several computers, all running Ubuntu. Just > today, one of my computers (headless Linux box) just froze and I had to > give it a power cycle reset. After powering up again, I can't any more > connect to X2Go. > > I'm getting following into /var/log/syslog: > ---8<---8<--- > Mar 12 13:15:40 kallebuntu systemd[1]: Started Session 10 of user ktuulos. > Mar 12 13:15:49 kallebuntu /usr/sbin/x2gocleansessions[1091]: > ktuulos-50-1520853345_stDLXDE_dp32: state file for this session does not > exist: /tmp/.x2go-ktuulos/C-ktuulos-50-1520853345_stDLXDE_dp32/state (this > can be ignored during session startups) > Mar 12 13:15:51 kallebuntu /usr/bin/x2gostartagent: successfully started > X2Go Agent session with ID ktuulos-50-1520853345_stDLXDE_dp32 > Mar 12 13:15:58 kallebuntu kernel: [ 1315.845394] nxagent[9647]: segfault > at 8 ip 56286f70db3a sp 7ffea2bd1bc0 error 4 in > nxagent[56286f693000+432000] > Mar 12 13:16:04 kallebuntu /usr/bin/x2gosetkeyboard: Setting X keyboard > according to > /home/ktuulos/.x2go/C-ktuulos-50-1520853345_stDLXDE_dp32/keyboard > Mar 12 13:16:05 kallebuntu /usr/bin/x2goruncommand: launching session with > Xsession-x2go mechanism, using STARTUP="startlxde" > Mar 12 13:16:05 kallebuntu /usr/bin/x2goruncommand: dbus wrapper available > as /usr/bin/dbus-run-session > ---8<---8<--- > > This computer is running Ubuntu 16.04. X2go server has been installed > using the ppa method. > ---8<---8<--- > ktuulos@kallebuntu:~$ uname -a > Linux kallebuntu 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 > 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux > ktuulos@kallebuntu:~$ dpkg -s x2goserver | grep Version > Version: 4.1.0.0-0~1517~ubuntu16.04.1 > ktuulos@kallebuntu:~$ cat > /etc/apt/sources.list.d/x2go-ubuntu-stable-xenial.list > deb http://ppa.launchpad.net/x2go/stable/ubuntu xenial main > # deb-src http://ppa.launchpad.net/x2go/stable/ubuntu xenial main > ---8<---8<--- > > There seem to be no hardware problems - I installed mcelog and I'm now > monitoring its output. Nothing. > > Could anyone give some hints? I have spent the last hour googling about > "nxagent segfault", but I haven't found anything, which would help. > > Thanks, > Kalle > > ___ > x2go-user mailing list > x2go-user@lists.x2go.org > https://lists.x2go.org/listinfo/x2go-user -- Norman Gaywood, Computer Systems Officer School of Science and Technology University of New England Armidale NSW 2351, Australia ngayw...@une.edu.au http://turing.une.edu.au/~ngaywood Phone: +61 (0)2 6773 2412 Mobile: +61 (0)4 7862 0062 Please avoid sending me Word or Power Point attachments. See http://www.gnu.org/philosophy/no-word-attachments.html ___ x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
[X2Go-User] Fedora 27 and loginctl linger
It seems that 'loginctl linger' does not work anymore as an ordinary user on Fedora 27. This worked on Fedora 26. From: https://bugzilla.redhat.com/show_bug.cgi?id=1478974#c15 On Fedora 27 it seems that enable-linger does not work as an ordinary user which is required for x2goserver keep sessions alive. Inside an x2go session: $ loginctl enable-linger Failed to look up user 62: No such process and (as root) "loginctl show-user ngaywood" shows: Linger=no As root I can: loginctl enable-linger ngaywood and Linger will be set. This used to work in Fedora 26 x2goserver-4.0.1.22-0.0x2go1.1.git20180204.1197.main.fc27.x86_64 -- Norman Gaywood, Computer Systems Officer School of Science and Technology University of New England Armidale NSW 2351, Australia ngayw...@une.edu.au http://turing.une.edu.au/~ngaywood Phone: +61 (0)2 6773 2412 Mobile: +61 (0)4 7862 0062 Please avoid sending me Word or Power Point attachments. See http://www.gnu.org/philosophy/no-word-attachments.html ___ x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
Re: [X2Go-User] Segfault with rstudio and x2goclient on Fedora 26
I think I found a fix. From this thread: http://www.bioinformatics.org/pipermail/bio-linux-list/2015-March/000804.html Where it says: > Tim discovered that this was caused by the Qt binaries bundled in the > RStudio .deb. A similar fix might work for you: > >> cd /usr/lib/rstudio/bin >> mkdir notused >> mv -i libQ* notused/ >> mv -i qt.conf notused/ As shown, I moved aside those rstudio Qt libraries on my Fedora 26 and Centos 7.4 x2goservers. Also installed qt5-* on the f26 and centos 7.4 x2goservers After that connecting from my Fedora 25 x2goclient, rstudio did not segfault and seems to work. On 15 November 2017 at 15:17, Norman Gaywood <ngayw...@une.edu.au> wrote: > I have a few installations of rstudio > > https://www.rstudio.com/products/rstudio/download/#download > > running on Fedora 26, Centos 7.4 and Red Hat Enterprise 7.4 x2go server: > > x2goserver-4.0.1.20-2.fc26.x86_64 > x2goserver-4.0.1.20-1.el7.x86_64 > > With the these two x2goclient on Fedora 26: > x2goclient-4.1.0.0-1.fc26.x86_64 > x2goclient-4.1.1.0-1.fc26.x86_64 > > rstudio will segfault on startup. > > Any other x2goclient I've tried, 4.1.0 on Windows and 4.0.5 on Mac, > rstudio works no problem. > Also doing "ssh -Y" to the hosts running x2goserver, rstudio starts with > no problem. > > rstudio has worked in the past (maybe several months ago). Perhaps I was > using Fedora 25 then. So I'm guessing that it's something to do with the > x2goclient on Fedora 26. > > Any ideas? > > On trying to start rstudio inside an x2gosession the segfault looks like: > $ rstudio > QXcbConnection: Failed to get the primary output of the screen > Unsupported screen format: depth: 24, red_mask: ff, blue_mask: ff > QXcbConnection: XCB error: 172 (Unknown), sequence: 161, resource id: 174, > major code: 149 (Unknown), minor code: 20 > QWidget::paintEngine: Should no longer be called > QPainter::begin: Paint device returned engine == 0, type: 1 > QWidget::paintEngine: Should no longer be called > QPainter::begin: Paint device returned engine == 0, type: 1 > QPainter::setRenderHint: Painter must be active to set rendering hints > QPainter::setRenderHint: Painter must be active to set rendering hints > QPainter::setBrush: Painter not active > QPainter::pen: Painter not active > QPainter::setPen: Painter not active > QPainter::save: Painter not active > QPainter::setClipRect: Painter not active > QPainter::translate: Painter not active > QPainter::translate: Painter not active > QPainter::setClipRect: Painter not active > QPainter::setCompositionMode: Painter not active > QPainter::setCompositionMode: Painter not active > QPainter::restore: Unbalanced save/restore > QPainter::save: Painter not active > QPainter::setClipRect: Painter not active > QPainter::restore: Unbalanced save/restore > QWidget::paintEngine: Should no longer be called > QPainter::begin: Paint device returned engine == 0, type: 1 > QPainter::setClipRect: Painter not active > QPainter::save: Painter not active > QPainter::pen: Painter not active > QPainter::setPen: Painter not active > QPainter::setPen: Painter not active > QPainter::setPen: Painter not active > QPainter::restore: Unbalanced save/restore > QPainter::setClipRect: Painter not active > QPainter::save: Painter not active > QPainter::pen: Painter not active > QPainter::setPen: Painter not active > QPainter::setPen: Painter not active > QPainter::setPen: Painter not active > QPainter::restore: Unbalanced save/restore > QPainter::setClipRect: Painter not active > QPainter::save: Painter not active > QPainter::pen: Painter not active > QPainter::setPen: Painter not active > QPainter::setPen: Painter not active > QPainter::setPen: Painter not active > QPainter::restore: Unbalanced save/restore > QPainter::setClipRect: Painter not active > QPainter::save: Painter not active > QPainter::pen: Painter not active > QPainter::setPen: Painter not active > QPainter::setPen: Painter not active > QPainter::setPen: Painter not active > QPainter::restore: Unbalanced save/restore > QPainter::setClipRect: Painter not active > QPainter::save: Painter not active > QPainter::pen: Painter not active > QPainter::setPen: Painter not active > QPainter::setPen: Painter not active > QPainter::setPen: Painter not active > QPainter::restore: Unbalanced save/restore > QPainter::setClipRect: Painter not active > QPainter::save: Painter not active > QPainter::pen: Painter not active > QPainter::setPen: Painter not active > QPainter::setPen: Painter not active > QPainter::setPen: Painter not active > QPainter::restore: Unbalanced save/restore > QPainter::setClipRect: Painter not active > QPainter::save: Painter n
[X2Go-User] Segfault with rstudio and x2goclient on Fedora 26
etClipRect: Painter not active QPainter::worldTransform: Painter not active QPainter::setCompositionMode: Painter not active QPainter::setCompositionMode: Painter not active QPainter::pen: Painter not active QPainter::setPen: Painter not active Segmentation fault (core dumped) -- Norman Gaywood, Computer Systems Officer School of Science and Technology University of New England Armidale NSW 2351, Australia ngayw...@une.edu.au http://turing.une.edu.au/~ngaywood Phone: +61 (0)2 6773 2412 Mobile: +61 (0)4 7862 0062 Please avoid sending me Word or Power Point attachments. See http://www.gnu.org/philosophy/no-word-attachments.html ___ x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
[X2Go-User] Utility for cleaning x2go sessions
I can have 50-60 users logged on via x2go. Sometimes I need to logout many
users. I use the following utility to list and match x2go sessions.
Using the -r switch will run x2goterminate-session against the matched
sessions.
Others may find this useful, so I post my script here.
Running the script without arguments will simply list all x2go sessions.
The -h switch will show usage.
I've attached the file but I suspect that will it be lost in the mailing
list archives.
Since it's short I also cut and paste here:
-- cut --
#!/usr/bin/perl
# List (and terminate) x2go sessions
use strict;
use warnings;
use v5.10;
use Getopt::Std;
my %opts;
getopts('hjqr', \%opts);
my $help = defined $opts{h} ? $opts{h} : 0;
my $printjob = defined $opts{j} ? $opts{j} : 0;
my $quite= defined $opts{q} ? $opts{q} : 0;
my $run = defined $opts{r} ? $opts{r} : 0;
my $x2goterminate= '/usr/bin/x2goterminate-session';
my $x2golistsessions = '/usr/sbin/x2golistsessions_root';
if ($help) {
print STDERR <<EOT;
Usage: $0 [-hjqr] [[pattern] .. pattern]
Runs $x2golistsessions and outputs in a more readable format
Only print x2go sessions that match the pattern[s]
If no pattern is given, lists all x2go sessions
-h This message
-j print job command to terminate matched sessions, not session
information
-q quite, don't print anything
-r Terminate the matched sessions with $x2goterminate
EOT
exit 1;
}
# $x2golistsessions lists sessions like this:
#456|user-122-1460160892_stDXFCE_dp32|122|host.com
|R|2016-04-09T10:14:52|cba4aa51a29c4b7e2d529e6f628245eb|123.456.789.012|30259|30261|2016-04-09T10:14:56|user|1125|30262|
# 0 1 2 345
67 8 9 10
11 12 13
#
# These are the fields that we print (@pretty) and/or we match against
my @pretty = (4,5,7,1);
#
# The sessionID field required for $x2goterminate
my $sessionID = 1;
# Results sorted by time
my $sessionTime = 5;
# Generate the string we print and match against
sub pretty {
my $s = shift;
return "" unless defined $s; # (ref to) array of session fields
return sprintf "%s %s %-16s %s", @{$s}[@pretty];
}
# Get the session list and split the fields in each session
my $sessions = qx( $x2golistsessions );
my @sessions = ();
for my $s (split /\n/, $sessions) {
push @sessions, [ split '\|', $s ];
}
# If no command line patterns, match all sessions
unless (@ARGV) {
@ARGV = ( '.' );
}
# patten match on the session information
my %tokill;# sessions to kill/display
for my $p (@ARGV) {
my @tokill = grep { grep /$p/, pretty($_) } @sessions;
# convert to hash to eliminate duplicates over multiple @ARGV
for my $s (@tokill) {
$tokill{$s->[$sessionID]} = $s;
}
}
# pretty = session information that patterns are matched against
# job= command that would execute to terminate session
for my $s (sort {$a->[$sessionTime] cmp $b->[$sessionTime]} values %tokill)
{
my $pretty = pretty($s);
my $job= sprintf "%s %s", $x2goterminate, $s->[$sessionID];
unless ($quite) {
say $printjob ? $job : $pretty;
}
system $job if $run;
}
--
Norman Gaywood, Computer Systems Officer
School of Science and Technology
University of New England
Armidale NSW 2351, Australia
ngayw...@une.edu.au http://turing.une.edu.au/~ngaywood
Phone: +61 (0)2 6773 2412 Mobile: +61 (0)4 7862 0062
Please avoid sending me Word or Power Point attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html
x2go_clean
Description: Binary data
___
x2go-user mailing list
x2go-user@lists.x2go.org
http://lists.x2go.org/listinfo/x2go-user
Re: [X2Go-User] X2Go crash from Mac/MATE to Fedora 25 w NIS user getting x2gostartagent: blocking creation of agent's keyboard file
This might be the update to Mesa in Fedora https://bugzilla.redhat.com/show_bug.cgi?id=1427174 A lot of programs won't start in my XFCE desktop under x2go. Even xfce4-terminal The temporary fix is to downgrade mesa: dnf downgrade mesa-libGL --allowerasing On 1 March 2017 at 03:51, Mihai Moldovan <io...@ionic.de> wrote: > On 28.02.2017 05:31 PM, Robert Kudyba wrote: > > My colleague is giving up on MATE. And XFCE has been having intermittent > issues and here are some errors/logs. Anything stick out? > > Difficult to say without knowing what to look for? > > I've seen kgpg crashing in that log, but that may or may not be a problem. > > The missing Composite and Fixes extensions are normal - you won't get any > compositing effects, but that's okay. > > Other than that, there's no major problem recorded in there. > > > This said, I've had a user on FC25 yesterday on IRC and he has reported > problems > with Emacs - which was built with GTK3 support. After he rebuilt it with > GTK2, > it started to work. > > I also (ab)used him to test MATE and found out that mate-session is > crashing > upon start. Any GTK3 application crashes, basically, because of a bug in al > ibrary used by GTK3 (libepoxy), that has been filed in Red Hats bugtracker > for > Fedora 24 already and fixed upstream for a while. > > The root cause of that is that for some reason the GLX version is not > reported > correctly - instead a NULL pointer is thrown out. I don't see this > behavior on > Debian Jessie, which hints at a deeper problem with our nx-libs builds on > Fedora > 25 (and maybe even 24?) > > I haven't yet been able to figure out why nxagent isn't doing what it > should be > doing, though. > > > > Mihai > > > _______ > x2go-user mailing list > x2go-user@lists.x2go.org > http://lists.x2go.org/listinfo/x2go-user > -- Norman Gaywood, Computer Systems Officer School of Science and Technology University of New England Armidale NSW 2351, Australia ngayw...@une.edu.au http://turing.une.edu.au/~ngaywood Phone: +61 (0)2 6773 2412 Mobile: +61 (0)4 7862 0062 Please avoid sending me Word or Power Point attachments. See http://www.gnu.org/philosophy/no-word-attachments.html ___ x2go-user mailing list x2go-user@lists.x2go.org http://lists.x2go.org/listinfo/x2go-user
