Hi
I'm connecting from a Mac (X2Go Client v. 4.0.5.1 (Qt - 4.8.7)) to Fedora 24 with a xfce session using the x2goserver-4.0.1.19-11.fc24.x86_64 packages from the fedora repos.
On starting emacs, I get the error below. This issue seems to have been around for a while in similar forms, but didn't affect me under Fedora 22.
Is anyone in a position to confirm this issue on Fedora 24 and suggest a work around? I tried setting various environment variables suggested on various web pages for similar issues and in the bug report noted in the error message (and checked /etc/PROBLEMS), but nothing was effective.
emacs starts fine in an xfce session at the console.
Thanks
Roderick Johnstone
X protocol error: BadRequest (invalid request code or no such operation) on protocol request 131 When compiled with GTK, Emacs cannot recover from X disconnects. This is a GTK bug: https://bugzilla.gnome.org/show_bug.cgi?id=85715 For details, see etc/PROBLEMS. Fatal error 6: Aborted Backtrace: emacs[0x50ad3c] emacs[0x4f11ec] emacs[0x50ade3] emacs[0x4c0f60] emacs[0x4c58b6] emacs[0x4c593b] /lib64/libX11.so.6(_XError+0x12d)[0x2b5baa0ff57d] /lib64/libX11.so.6(+0x413e7)[0x2b5baa0fc3e7] /lib64/libX11.so.6(+0x414ad)[0x2b5baa0fc4ad] /lib64/libX11.so.6(_XReply+0x238)[0x2b5baa0fd478] /lib64/libX11.so.6(XQueryPointer+0x91)[0x2b5baa0f3351] /lib64/libgdk-3.so.0(+0x4da2a)[0x2b5ba8150a2a] /lib64/libgdk-3.so.0(+0x6a605)[0x2b5ba816d605] /lib64/libgdk-3.so.0(gdk_window_get_device_position_double+0x10b)[0x2b5ba8143d1b] /lib64/libgdk-3.so.0(gdk_window_get_device_position+0x2d)[0x2b5ba8143e1d] /lib64/libgtk-3.so.0(+0x321199)[0x2b5ba7b48199] /lib64/libgtk-3.so.0(+0x3216f4)[0x2b5ba7b486f4] /lib64/libgdk-3.so.0(+0x253d8)[0x2b5ba81283d8] /lib64/libglib-2.0.so.0(+0x4a173)[0x2b5ba97d0173] /lib64/libglib-2.0.so.0(g_main_context_dispatch+0x163)[0x2b5ba97cf703] emacs[0x5e0b78] emacs[0x5a6025] emacs[0x4fc1bc] emacs[0x4fdfdd] emacs[0x4ffc24] emacs[0x564642] emacs[0x4f16b4] emacs[0x5645e3] emacs[0x4f1670] emacs[0x4f5e6b] emacs[0x4f61c8] emacs[0x419b52] /lib64/libc.so.6(__libc_start_main+0xf1)[0x2b5bb17db731] emacs[0x41a639] Aborted (core dumped)
https://bugzilla.redhat.com/show_bug.cgi?id=1349412
Roderick Johnstone wrote:
Hi
I'm connecting from a Mac (X2Go Client v. 4.0.5.1 (Qt - 4.8.7)) to Fedora 24 with a xfce session using the x2goserver-4.0.1.19-11.fc24.x86_64 packages from the fedora repos.
On starting emacs, I get the error below. This issue seems to have been around for a while in similar forms, but didn't affect me under Fedora 22.
Is anyone in a position to confirm this issue on Fedora 24 and suggest a work around? I tried setting various environment variables suggested on various web pages for similar issues and in the bug report noted in the error message (and checked /etc/PROBLEMS), but nothing was effective.
emacs starts fine in an xfce session at the console.
Thanks
Roderick Johnstone
X protocol error: BadRequest (invalid request code or no such operation) on protocol request 131 When compiled with GTK, Emacs cannot recover from X disconnects. This is a GTK bug: https://bugzilla.gnome.org/show_bug.cgi?id=85715 For details, see etc/PROBLEMS. Fatal error 6: Aborted Backtrace: emacs[0x50ad3c] emacs[0x4f11ec] emacs[0x50ade3] emacs[0x4c0f60] emacs[0x4c58b6] emacs[0x4c593b] /lib64/libX11.so.6(_XError+0x12d)[0x2b5baa0ff57d] /lib64/libX11.so.6(+0x413e7)[0x2b5baa0fc3e7] /lib64/libX11.so.6(+0x414ad)[0x2b5baa0fc4ad] /lib64/libX11.so.6(_XReply+0x238)[0x2b5baa0fd478] /lib64/libX11.so.6(XQueryPointer+0x91)[0x2b5baa0f3351] /lib64/libgdk-3.so.0(+0x4da2a)[0x2b5ba8150a2a] /lib64/libgdk-3.so.0(+0x6a605)[0x2b5ba816d605] /lib64/libgdk-3.so.0(gdk_window_get_device_position_double+0x10b) [0x2b5ba8143d1b] /lib64/libgdk-3.so.0(gdk_window_get_device_position+0x2d)[0x2b5ba8143e1d] /lib64/libgtk-3.so.0(+0x321199)[0x2b5ba7b48199] /lib64/libgtk-3.so.0(+0x3216f4)[0x2b5ba7b486f4] /lib64/libgdk-3.so.0(+0x253d8)[0x2b5ba81283d8] /lib64/libglib-2.0.so.0(+0x4a173)[0x2b5ba97d0173] /lib64/libglib-2.0.so.0(g_main_context_dispatch+0x163)[0x2b5ba97cf703] emacs[0x5e0b78] emacs[0x5a6025] emacs[0x4fc1bc] emacs[0x4fdfdd] emacs[0x4ffc24] emacs[0x564642] emacs[0x4f16b4] emacs[0x5645e3] emacs[0x4f1670] emacs[0x4f5e6b] emacs[0x4f61c8] emacs[0x419b52] /lib64/libc.so.6(__libc_start_main+0xf1)[0x2b5bb17db731] emacs[0x41a639] Aborted (core dumped)
Hi Neal
Thanks for the pointer to the work around.
Do we know why this started to happen with F24?
Thanks again.
Roderick
On 06/07/2016 12:03, Neal Becker wrote:
https://bugzilla.redhat.com/show_bug.cgi?id=1349412
Roderick Johnstone wrote:
Hi
I'm connecting from a Mac (X2Go Client v. 4.0.5.1 (Qt - 4.8.7)) to Fedora 24 with a xfce session using the x2goserver-4.0.1.19-11.fc24.x86_64 packages from the fedora repos.
On starting emacs, I get the error below. This issue seems to have been around for a while in similar forms, but didn't affect me under Fedora 22.
Is anyone in a position to confirm this issue on Fedora 24 and suggest a work around? I tried setting various environment variables suggested on various web pages for similar issues and in the bug report noted in the error message (and checked /etc/PROBLEMS), but nothing was effective.
emacs starts fine in an xfce session at the console.
Thanks
Roderick Johnstone
X protocol error: BadRequest (invalid request code or no such operation) on protocol request 131 When compiled with GTK, Emacs cannot recover from X disconnects. This is a GTK bug: https://bugzilla.gnome.org/show_bug.cgi?id=85715 For details, see etc/PROBLEMS. Fatal error 6: Aborted Backtrace: emacs[0x50ad3c] emacs[0x4f11ec] emacs[0x50ade3] emacs[0x4c0f60] emacs[0x4c58b6] emacs[0x4c593b] /lib64/libX11.so.6(_XError+0x12d)[0x2b5baa0ff57d] /lib64/libX11.so.6(+0x413e7)[0x2b5baa0fc3e7] /lib64/libX11.so.6(+0x414ad)[0x2b5baa0fc4ad] /lib64/libX11.so.6(_XReply+0x238)[0x2b5baa0fd478] /lib64/libX11.so.6(XQueryPointer+0x91)[0x2b5baa0f3351] /lib64/libgdk-3.so.0(+0x4da2a)[0x2b5ba8150a2a] /lib64/libgdk-3.so.0(+0x6a605)[0x2b5ba816d605] /lib64/libgdk-3.so.0(gdk_window_get_device_position_double+0x10b) [0x2b5ba8143d1b] /lib64/libgdk-3.so.0(gdk_window_get_device_position+0x2d)[0x2b5ba8143e1d] /lib64/libgtk-3.so.0(+0x321199)[0x2b5ba7b48199] /lib64/libgtk-3.so.0(+0x3216f4)[0x2b5ba7b486f4] /lib64/libgdk-3.so.0(+0x253d8)[0x2b5ba81283d8] /lib64/libglib-2.0.so.0(+0x4a173)[0x2b5ba97d0173] /lib64/libglib-2.0.so.0(g_main_context_dispatch+0x163)[0x2b5ba97cf703] emacs[0x5e0b78] emacs[0x5a6025] emacs[0x4fc1bc] emacs[0x4fdfdd] emacs[0x4ffc24] emacs[0x564642] emacs[0x4f16b4] emacs[0x5645e3] emacs[0x4f1670] emacs[0x4f5e6b] emacs[0x4f61c8] emacs[0x419b52] /lib64/libc.so.6(__libc_start_main+0xf1)[0x2b5bb17db731] emacs[0x41a639] Aborted (core dumped)
x2go-user mailing list x2go-user@lists.x2go.org http://lists.x2go.org/listinfo/x2go-user
Roderick Johnstone wrote:
Hi Neal
Thanks for the pointer to the work around.
Do we know why this started to happen with F24?
Thanks again.
Roderick
On 06/07/2016 12:03, Neal Becker wrote:
https://bugzilla.redhat.com/show_bug.cgi?id=1349412
Roderick Johnstone wrote:
Hi
I'm connecting from a Mac (X2Go Client v. 4.0.5.1 (Qt - 4.8.7)) to Fedora 24 with a xfce session using the x2goserver-4.0.1.19-11.fc24.x86_64 packages from the fedora repos.
On starting emacs, I get the error below. This issue seems to have been around for a while in similar forms, but didn't affect me under Fedora 22.
Is anyone in a position to confirm this issue on Fedora 24 and suggest a work around? I tried setting various environment variables suggested on various web pages for similar issues and in the bug report noted in the error message (and checked /etc/PROBLEMS), but nothing was effective.
emacs starts fine in an xfce session at the console.
Thanks
Roderick Johnstone
X protocol error: BadRequest (invalid request code or no such operation) on protocol request 131 When compiled with GTK, Emacs cannot recover from X disconnects. This is a GTK bug: https://bugzilla.gnome.org/show_bug.cgi?id=85715 For details, see etc/PROBLEMS. Fatal error 6: Aborted Backtrace: emacs[0x50ad3c] emacs[0x4f11ec] emacs[0x50ade3] emacs[0x4c0f60] emacs[0x4c58b6] emacs[0x4c593b] /lib64/libX11.so.6(_XError+0x12d)[0x2b5baa0ff57d] /lib64/libX11.so.6(+0x413e7)[0x2b5baa0fc3e7] /lib64/libX11.so.6(+0x414ad)[0x2b5baa0fc4ad] /lib64/libX11.so.6(_XReply+0x238)[0x2b5baa0fd478] /lib64/libX11.so.6(XQueryPointer+0x91)[0x2b5baa0f3351] /lib64/libgdk-3.so.0(+0x4da2a)[0x2b5ba8150a2a] /lib64/libgdk-3.so.0(+0x6a605)[0x2b5ba816d605] /lib64/libgdk-3.so.0(gdk_window_get_device_position_double+0x10b) [0x2b5ba8143d1b] /lib64/libgdk-3.so.0(gdk_window_get_device_position+0x2d) [0x2b5ba8143e1d] /lib64/libgtk-3.so.0(+0x321199)[0x2b5ba7b48199] /lib64/libgtk-3.so.0(+0x3216f4)[0x2b5ba7b486f4] /lib64/libgdk-3.so.0(+0x253d8)[0x2b5ba81283d8] /lib64/libglib-2.0.so.0(+0x4a173)[0x2b5ba97d0173] /lib64/libglib-2.0.so.0(g_main_context_dispatch+0x163)[0x2b5ba97cf703] emacs[0x5e0b78] emacs[0x5a6025] emacs[0x4fc1bc] emacs[0x4fdfdd] emacs[0x4ffc24] emacs[0x564642] emacs[0x4f16b4] emacs[0x5645e3] emacs[0x4f1670] emacs[0x4f5e6b] emacs[0x4f61c8] emacs[0x419b52] /lib64/libc.so.6(__libc_start_main+0xf1)[0x2b5bb17db731] emacs[0x41a639] Aborted (core dumped)
x2go-user mailing list x2go-user@lists.x2go.org http://lists.x2go.org/listinfo/x2go-user
No, maybe an update to gtk?
Dear all,
Have there been any further developments regarding the problem of Emacs crashing when run over x2go? I'm experiencing the same issue and would love to know if there is any workaround that doesn't involve recompiling Emacs or running it in text mode (as mentioned in the Fedora bug report at <https://bugzilla.redhat.com/show_bug.cgi?id=1349412>).
Regards, Tristan
Tristan Miller
I have run into some random problems with the x2go server crashing
when I invoke programs, sometimes vi, sometimes synaptic.
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting. Knowledgeable human assistance, not telephone trees or script readers. See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.
On Wed, 9 Nov 2016, Tristan Miller wrote:
Date: Wed, 9 Nov 2016 16:36:18 +0100 From: Tristan Miller <psychonaut@nothingisreal.com> To: x2go-user@lists.x2go.org Subject: Re: [X2Go-User] Emacs crashes on start
Dear all,
Have there been any further developments regarding the problem of Emacs crashing when run over x2go? I'm experiencing the same issue and would love to know if there is any workaround that doesn't involve recompiling Emacs or running it in text mode (as mentioned in the Fedora bug report at <https://bugzilla.redhat.com/show_bug.cgi?id=1349412>).
Regards, Tristan
--
Tristan Miller
Free Software developer, ferret herder, logologist https://logological.org/
Does this happen with other Gtk apps? Are you running with an Nvidia card? I had to install VirtualGL and run some application through a proxy to get them to work.
vglrun -c proxy xterm -ls
-----Original Message----- From: x2go-user-bounces@lists.x2go.org [mailto:x2go-user-bounces@lists.x2go.org] On Behalf Of Robert Dinse Sent: Wednesday, November 09, 2016 1:47 PM To: Tristan Miller <psychonaut@nothingisreal.com> Cc: x2go-user@lists.x2go.org Subject: Re: [X2Go-User] Emacs crashes on start
I have run into some random problems with the x2go server crashing when I invoke programs, sometimes vi, sometimes synaptic.
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting. Knowledgeable human assistance, not telephone trees or script readers. See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.
On Wed, 9 Nov 2016, Tristan Miller wrote:
Date: Wed, 9 Nov 2016 16:36:18 +0100 From: Tristan Miller <psychonaut@nothingisreal.com> To: x2go-user@lists.x2go.org Subject: Re: [X2Go-User] Emacs crashes on start
Dear all,
Have there been any further developments regarding the problem of Emacs crashing when run over x2go? I'm experiencing the same issue and would love to know if there is any workaround that doesn't involve recompiling Emacs or running it in text mode (as mentioned in the Fedora bug report at <https://bugzilla.redhat.com/show_bug.cgi?id=1349412>).
Regards, Tristan
--
Tristan Miller
Free Software developer, ferret herder, logologist https://logological.org/
x2go-user mailing list x2go-user@lists.x2go.org http://lists.x2go.org/listinfo/x2go-user
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
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
A bug was filed a while ago: https://bugzilla.redhat.com/show_bug.cgi?id=1349412 <https://bugzilla.redhat.com/show_bug.cgi?id=1349412> and a couple work arounds are listed there including rebuild with --with-x-toolkit=gtk2 --without-xwidgets or use xemacs
On Nov 10, 2016, at 4:22 PM, Thackeray, Neil L <neilt@illinois.edu> wrote:
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> [mailto: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 <mailto: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
Free Software developer, ferret herder, logologist https://urldefense.proofpoint.com/v2/url?u=https-3A__logological.org_&d=DQICAg&c=aqMfXOEvEJQh2iQMCb7Wy8l0sPnURkcqADc2guUW8IM&r=X0jL9y0sL4r4iU_qVtR3lLNo4tOL1ry_m7-psV3GejY&m=iEzY9axsYeUMah8mvFijUqWhRFw6W3LggeovgbiU66o&s=VrqDZAXzAVNN_xdPEkngD422CwNcmqYbn2WYJPq6J4U&e= <https://urldefense.proofpoint.com/v2/url?u=https-3A__logological.org_&d=DQICAg&c=aqMfXOEvEJQh2iQMCb7Wy8l0sPnURkcqADc2guUW8IM&r=X0jL9y0sL4r4iU_qVtR3lLNo4tOL1ry_m7-psV3GejY&m=iEzY9axsYeUMah8mvFijUqWhRFw6W3LggeovgbiU66o&s=VrqDZAXzAVNN_xdPEkngD422CwNcmqYbn2WYJPq6J4U&e=>
x2go-user mailing list x2go-user@lists.x2go.org <mailto:x2go-user@lists.x2go.org> https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.x2go.org_listinfo_x2go-2Duser&d=DQICAg&c=aqMfXOEvEJQh2iQMCb7Wy8l0sPnURkcqADc2guUW8IM&r=X0jL9y0sL4r4iU_qVtR3lLNo4tOL1ry_m7-psV3GejY&m=iEzY9axsYeUMah8mvFijUqWhRFw6W3LggeovgbiU66o&s=_Jf6au-ociJPFX8lAX1hud6qo-HDRBqnwHSD62sj_LE&e= <https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.x2go.org_listinfo_x2go-2Duser&d=DQICAg&c=aqMfXOEvEJQh2iQMCb7Wy8l0sPnURkcqADc2guUW8IM&r=X0jL9y0sL4r4iU_qVtR3lLNo4tOL1ry_m7-psV3GejY&m=iEzY9axsYeUMah8mvFijUqWhRFw6W3LggeovgbiU66o&s=_Jf6au-ociJPFX8lAX1hud6qo-HDRBqnwHSD62sj_LE&e=>
Greetings.
On Thu, 10 Nov 2016 16:31:53 -0500, Robert Kudyba <rkudyba@fordham.edu> wrote:
A bug was filed a while ago: https://bugzilla.redhat.com/show_bug.cgi?id=1349412 <https://bugzilla.redhat.com/show_bug.cgi?id=1349412> and a couple work arounds are listed there including rebuild with --with-x-toolkit=gtk2 --without-xwidgets or use xemacs
Yes, that was the workaround referenced in my original post. As I said, I'm not particularly keen on recompiling from source. This isn't even possible for users who connect to a remote system on which there are no development tools and no root access to install them.
Regards, Tristan
Tristan Miller
Tristan Miller wrote:
Greetings.
On Thu, 10 Nov 2016 16:31:53 -0500, Robert Kudyba <rkudyba@fordham.edu> wrote:
A bug was filed a while ago: https://bugzilla.redhat.com/show_bug.cgi?id=1349412 <https://bugzilla.redhat.com/show_bug.cgi?id=1349412> and a couple work arounds are listed there including rebuild with --with-x-toolkit=gtk2 --without-xwidgets or use xemacs
Yes, that was the workaround referenced in my original post. As I said, I'm not particularly keen on recompiling from source. This isn't even possible for users who connect to a remote system on which there are no development tools and no root access to install them.
Regards, Tristan
I'm setting up a patched emacs on copr, I'll have builds for f24/f25 x86_64 shortly
On Fri, Nov 11, 2016 at 1:55 PM, Neal Becker <ndbecker2@gmail.com> wrote:
On Thu, 10 Nov 2016 16:31:53 -0500, Robert Kudyba <rkudyba@fordham.edu> wrote:
A bug was filed a while ago: https://bugzilla.redhat.com/show_bug.cgi?id=1349412 <https://bugzilla.redhat.com/show_bug.cgi?id=1349412> and a couple work arounds are listed there including rebuild with --with-x-toolkit=gtk2 --without-xwidgets or use xemacs
Yes, that was the workaround referenced in my original post. As I said, I'm not particularly keen on recompiling from source. This isn't even possible for users who connect to a remote system on which there are no development tools and no root access to install them.
I'm setting up a patched emacs on copr, I'll have builds for f24/f25 x86_64 shortly
While is certainly helps this is only a workaround. The real problem for me ist gtk3 nor working with NX. https://bugzilla.redhat.com/show_bug.cgi?id=903410 suggests a downgrade of cairo might help. Can someone pelase test this?
Uli
On Fri, Nov 11, 2016 at 2:48 PM, Ulrich Sibiller <uli42@gmx.de> wrote:
While is certainly helps this is only a workaround. The real problem for me ist gtk3 nor working with NX. https://bugzilla.redhat.com/show_bug.cgi?id=903410 suggests a downgrade of cairo might help. Can someone pelase test this?
This is rather old, I missed that when reading it, sorry.
But here's a small example code that might trigger the problem:
http://stackoverflow.com/questions/36486685/gtk3-crash-when-opening-a-popup-...
Can anyone confirm?
Uli
Greetings.
On Fri, 11 Nov 2016 14:48:53 +0100, Ulrich Sibiller <uli42@gmx.de> wrote:
While is certainly helps this is only a workaround. The real problem for me ist gtk3 nor working with NX. https://bugzilla.redhat.com/show_bug.cgi?id=903410 suggests a downgrade of cairo might help. Can someone pelase test this?
My client (openSUSE 13.2) and server (openSUSE Tumbleweed) are both running Cairo 1.15.2. I had an old Cairo 1.10.2 lying around, but setting LD_LIBRARY_PATH to use it on the client, as suggested in the bug report you posted, results in undefined from various other libraries. I tried using older versions of these libraries too, but eventually hit a dead-end -- the current version of Emacs depends on some symbol that doesn't exist in the older version of libgdk that the older version of libcario indirectly requires.
Regards, Tristan
Tristan Miller
Greetings.
On Fri, 11 Nov 2016 07:55:55 -0500, Neal Becker <ndbecker2@gmail.com> wrote:
I'm setting up a patched emacs on copr, I'll have builds for f24/f25 x86_64 shortly
Great news for Fedora users. If there's no fix or workaround coming in the near future, I might do the same for openSUSE, if I can wrap my head around OBS.
Incidentally, here's a similar bug report for openSUSE:
http://bugzilla.suse.com/show_bug.cgi?id=1007912
Regards, Tristan
Tristan Miller
Greetings.
On Thu, 10 Nov 2016 21:22:19 +0000, "Thackeray, Neil L" <neilt@illinois.edu> wrote:
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.
Well, I think the problem with running it as the x2go single application might be the same problem with running it from a terminal -- it can't find the display. I tried launching an xterm from x2go as usual, and then manually passed the display value to vglrun:
$ vglrun -c proxy -d $DISPLAY emacs
This works somewhat better in that Emacs actually gets launched. However, it still crashes on mouseover (albeit with a somewhat longer delay).
Regards, Tristan
Tristan Miller
I am having it happen with synaptic under Mate and I do have an old nvidia
card, 7900 GT.
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting. Knowledgeable human assistance, not telephone trees or script readers. See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.
On Thu, 10 Nov 2016, Thackeray, Neil L wrote:
Date: Thu, 10 Nov 2016 15:26:15 +0000 From: "Thackeray, Neil L" <neilt@illinois.edu> To: "x2go-user@lists.x2go.org" <x2go-user@lists.x2go.org> Subject: Re: [X2Go-User] Emacs crashes on start
Does this happen with other Gtk apps? Are you running with an Nvidia card? I had to install VirtualGL and run some application through a proxy to get them to work.
vglrun -c proxy xterm -ls
-----Original Message----- From: x2go-user-bounces@lists.x2go.org [mailto:x2go-user-bounces@lists.x2go.org] On Behalf Of Robert Dinse Sent: Wednesday, November 09, 2016 1:47 PM To: Tristan Miller <psychonaut@nothingisreal.com> Cc: x2go-user@lists.x2go.org Subject: Re: [X2Go-User] Emacs crashes on start
I have run into some random problems with the x2go server crashing when I invoke programs, sometimes vi, sometimes synaptic.
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting. Knowledgeable human assistance, not telephone trees or script readers. See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.
On Wed, 9 Nov 2016, Tristan Miller wrote:
Date: Wed, 9 Nov 2016 16:36:18 +0100 From: Tristan Miller <psychonaut@nothingisreal.com> To: x2go-user@lists.x2go.org Subject: Re: [X2Go-User] Emacs crashes on start
Dear all,
Have there been any further developments regarding the problem of Emacs crashing when run over x2go? I'm experiencing the same issue and would love to know if there is any workaround that doesn't involve recompiling Emacs or running it in text mode (as mentioned in the Fedora bug report at <https://bugzilla.redhat.com/show_bug.cgi?id=1349412>).
Regards, Tristan
--
Tristan Miller
Free Software developer, ferret herder, logologist https://logological.org/
x2go-user mailing list x2go-user@lists.x2go.org http://lists.x2go.org/listinfo/x2go-user
x2go-user mailing list x2go-user@lists.x2go.org http://lists.x2go.org/listinfo/x2go-user
Dear all,
On Wed, 9 Nov 2016 16:36:18 +0100, Tristan Miller <psychonaut@nothingisreal.com> wrote:
Have there been any further developments regarding the problem of Emacs crashing when run over x2go?
Apparently this problem still exists, and is caused by the GTK+ bug described at <https://bugzilla.gnome.org/show_bug.cgi?id=85715>. Here are the various workarounds I know about:
Run Emacs in text mode (emacs -nw). This is fine if you don't need pull-down menus, mouse support, etc.
Run Emacs over SSH instead of over x2go (ssh -f MYHOST emacs). On a fast connection, this is fine if you're just editing text. If you need to launch graphics-intensive programs such as web browsers or PDF viewers, etc., then this should be done separately from an x2go session rather than directly from Emacs.
Use a version of Emacs compiled with a different X toolkit, such as Lucid. You can compile such an Emacs yourself by passing --with-x-toolkit=lucid to the configure script. Some GNU/Linux distribution provide binary packages for this:
In Fedora, use the emacs-lucid package.
In openSUSE, the default emacs package includes both the GTK+ and Lucid versions. To use the Lucid version, call Emacs as follows: EMACS_TOOLKIT=x11 emacs
Regards, Tristan
Tristan Miller
Am 13.09.2017 um 12:38 schrieb Tristan Miller:
- In Fedora, use the emacs-lucid package.
I'm not affected by this bug, as I'm not an Emacs user myself, but I recently discovered: <https://copr.fedorainfracloud.org/coprs/nbecker/emacs-x2go/>
I'm assuming this "nbecker" is the Neal Becker <ndbecker2@gmail.com> who chimed in on this thread before.
(Just leaving this here in case it helps someone.)
-Stefan
-- 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
Stefan Baur wrote:
Am 13.09.2017 um 12:38 schrieb Tristan Miller:
- In Fedora, use the emacs-lucid package.
I'm not affected by this bug, as I'm not an Emacs user myself, but I recently discovered: <https://copr.fedorainfracloud.org/coprs/nbecker/emacs-x2go/>
I'm assuming this "nbecker" is the Neal Becker <ndbecker2@gmail.com> who chimed in on this thread before.
(Just leaving this here in case it helps someone.)
-Stefan
Yes, when I first ran into this bug I built an emacs version with gtk2 instead of gtk3 which provided a workaround, and then setup emacs-x2go to help out others.
But since fedora now supplies emacs-lucid I just use that instead, and won't be updating emacs-x2go.