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

Re: [X2Go-User] nxagent SIGSEGV when running glxinfo (and firefox) on a host with cuda installed

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

[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

Re: [X2Go-User] nxagent

o-user@lists.x2go.org Subject: Re: [X2Go-User] nxagent Am 07.03.2018 um 01:45 schrieb Robert Dinse: What I do: apt purge nx* libnx* *x2go* That does not sound clever. "purge" also removes config files, which may not be what you want, especially if you made custom change

Re: [X2Go-User] nxagent

Am 07.03.2018 um 01:45 schrieb Robert Dinse: > What I do: > > apt purge nx* libnx* *x2go* That does not sound clever. "purge" also removes config files, which may not be what you want, especially if you made custom changes to any of them. A simple "remove" will leave them in place

Re: [X2Go-User] nxagent

+0100 From: Mario Theodoridis <ma...@schmut.com> To: x2go-user@lists.x2go.org Subject: Re: [X2Go-User] nxagent On 06/03/18 14:18, martti pitkanen wrote: Hi, Is there hands-on instructions how to downgrade to Saimaa in Ubuntu (4.13.0-)? X2Go sessions terminate in random way. Yes. This is

Re: [X2Go-User] nxagent

On 06.03.2018 16:26, martti pitkanen wrote: Hi Mario, Thanks for your clear instructions, X2Go seems now to be in stable state. Only the v-e-r-y slow  phase "Status: connecting" has returned, takes 2-3 minutes. I actually followed Roberts advice and went back to x2goserver-4.1. So far it

Re: [X2Go-User] nxagent

On 06/03/18 15:23, Robert Kudyba wrote: Why not just disable DPMS (Display Power Management Signaling) support? https://github.com/ArcticaProject/nx-libs/issues/671#issuecomment-370715419 Cause i hadn't seen the comment that it worked yet. I'll try that now and hopefully can get back to work.

Re: [X2Go-User] nxagent

Why not just disable DPMS (Display Power Management Signaling) support? https://github.com/ArcticaProject/nx-libs/issues/671#issuecomment-370715419 So a command like: /usr/bin/xset -dpms s off s noblank s 0 0 s noexpose -dpms On Tue, Mar 6, 2018 at 9:03 AM, Mario Theodoridis

Re: [X2Go-User] nxagent

On 06/03/18 14:18, martti pitkanen wrote: Hi, Is there hands-on instructions how to downgrade to Saimaa in Ubuntu (4.13.0-)? X2Go sessions terminate in random way. Yes. This is what i just did more or less following Stefans advice. sudo mv x2go-stable-trusty.list

Re: [X2Go-User] nxagent

Am 06.03.2018 um 14:18 schrieb martti pitkanen: > Is there hands-on instructions how to downgrade to Saimaa in Ubuntu > (4.13.0-)? > X2Go sessions terminate in random way. > This is untested, but it should work something like this: - Remove your current X2Go PPA - use

Re: [X2Go-User] nxagent

Hi, Is there hands-on instructions how to downgrade to Saimaa in Ubuntu (4.13.0-)? X2Go sessions terminate in random way. On 03/06/2018 03:03 PM, Stefan Baur wrote: Am 06.03.2018 um 13:54 schrieb Mario Theodoridis: Is there a way to downgrade? Several, actually. You can switch to the

Re: [X2Go-User] nxagent

Am 06.03.2018 um 13:54 schrieb Mario Theodoridis: > Is there a way to downgrade? Several, actually. You can switch to the saimaa repository, or to a timestamped repository with a timestamp before the change. I would suggest saimaa, as it means you will not be cut off from security updates,

Re: [X2Go-User] nxagent

On 05/03/18 16:48, Mario Theodoridis wrote: On 05/03/18 13:41, Mario Theodoridis wrote: On 04/03/18 09:44, Mihai Moldovan wrote: * On 03/04/2018 01:54 AM, Robert Dinse wrote: Yes consuming a large amount of CPU and not doing anything useful, customer is disconnected. Connection is

Re: [X2Go-User] nxagent

On 05/03/18 13:41, Mario Theodoridis wrote: On 04/03/18 09:44, Mihai Moldovan wrote: * On 03/04/2018 01:54 AM, Robert Dinse wrote: Yes consuming a large amount of CPU and not doing anything useful, customer is disconnected. Connection is still possible but doesn't get rid of the stuck

Re: [X2Go-User] nxagent

On 04/03/18 09:44, Mihai Moldovan wrote: * On 03/04/2018 01:54 AM, Robert Dinse wrote: Yes consuming a large amount of CPU and not doing anything useful, customer is disconnected. Connection is still possible but doesn't get rid of the stuck processes, I have to kill -9 to get rid of

Re: [X2Go-User] nxagent

On 04/03/18 09:44, Mihai Moldovan wrote: * On 03/04/2018 01:54 AM, Robert Dinse wrote: Yes consuming a large amount of CPU and not doing anything useful, customer is disconnected. Connection is still possible but doesn't get rid of the stuck processes, I have to kill -9 to get rid of

Re: [X2Go-User] nxagent

* On 03/04/2018 10:51 AM, Robert Dinse wrote: > It hasn't happened to me so I don't know what the people are doing > before > it gets stuck, could be mate, kde, lxde, lfce, openbox, they're all on there. > Next time it happens I'll trace it to see what it is doing. Please follow

Re: [X2Go-User] nxagent

It hasn't happened to me so I don't know what the people are doing before it gets stuck, could be mate, kde, lxde, lfce, openbox, they're all on there. Next time it happens I'll trace it to see what it is doing.

Re: [X2Go-User] nxagent

* On 03/04/2018 01:54 AM, Robert Dinse wrote: > Yes consuming a large amount of CPU and not doing anything useful, > customer is disconnected. Connection is still possible but doesn't get rid > of the stuck processes, I have to kill -9 to get rid of them. Uhm... "stuck" is pretty

Re: [X2Go-User] nxagent

Yes consuming a large amount of CPU and not doing anything useful, customer is disconnected. Connection is still possible but doesn't get rid of the stuck processes, I have to kill -9 to get rid of them. -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-

Re: [X2Go-User] nxagent

* On 03/04/2018 01:35 AM, Robert Dinse wrote: > We are seeing nxagent processes stuck running in a loop when the > customer > is no longer logged in. Stuck in a loop, i.e., using a high amount of CPU resources and not doing anything useful? Is connecting still possible? Does the usage

[X2Go-User] nxagent

We are seeing nxagent processes stuck running in a loop when the customer is no longer logged in. -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting. Knowledgeable human assistance,