[X2Go-User] Emacs crashes on start

[Neal Becker]

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 at lists.x2go.org
>> http://lists.x2go.org/listinfo/x2go-user
>>

No, maybe an update to gtk?