Do you mean that I should configure my x2go client to launch "vglrun -c proxy xterm -ls" instead of just "xterm" as the "Single Application"? If so, that doesn't work; the x2go session connects but then terminates immediately. Yes, this is what I did, but I didn't have the problem of the x2go session terminating.
-----Original Message----- From: x2go-user-bounces@lists.x2go.org [mailto:x2go-user-bounces@lists.x2go.org] On Behalf Of Tristan Miller Sent: Thursday, November 10, 2016 9:51 AM To: x2go-user@lists.x2go.org Subject: Re: [X2Go-User] Emacs crashes on start
Greetings.
On Thu, 10 Nov 2016 15:26:15 +0000, "Thackeray, Neil L" <neilt@illinois.edu> wrote:
Does this happen with other Gtk apps?
I can't speak for Robert's problem, which seems to be unrelated. In my case, Emacs is the only program that crashes, though other GTK+ programs have problems displaying the pull-down menus. See the "GTK+ pull-down menus not displayed" thread in this list.
Are you running with an Nvidia card?
The client has an Nvidia card, yes. The remote server doesn't.
I had to install VirtualGL and run some application through a proxy to get them to work.
vglrun -c proxy xterm -ls
It's not clear to me how or where you're suggesting I use VirtualGL. Do you mean that I should configure my x2go client to launch "vglrun -c proxy xterm -ls" instead of just "xterm" as the "Single Application"? If so, that doesn't work; the x2go session connects but then terminates immediately.
If I use x2go to launch a remote xterm as usual, and then type your vglrun command in that xterm, then it returns with the error "Invalid MIT-MAGIC-COOKIE-1 key[VGL] ERROR: Could not open display :0.".
Regards, Tristan
--
Tristan Miller