After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 628932 - key typing causes core dump in VNC environment
key typing causes core dump in VNC environment
Status: RESOLVED FIXED
Product: gtk+
Classification: Platform
Component: Backend: X11
2.21.x
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2010-09-07 02:15 UTC by VDR dai (bugzilla)
Modified: 2010-09-07 04:12 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
sylpheed's core backtrace log (4.04 KB, text/plain)
2010-09-07 02:15 UTC, VDR dai (bugzilla) 		Details

Description VDR dai (bugzilla) 2010-09-07 02:15:19 UTC 
Created attachment 169637 [details]
sylpheed's core backtrace log

key typing causes core dump in VNC environment.
For example, GTK+ MUA Sylpheed crashes if I type a key on it.

% sylpheed
Xlib:  extension "RANDR" missing on display ":1.0".

Gdk-ERROR **: Failed to get keymap
aborting...
zsh: trace trap (core dumped)  sylpheed
%

It occurs in only VNC environment, not plain X.
It is caused by below patch. It is included in 2.21.7.

Make gdk_keymap_map_virtual_modifiers work early
http://git.gnome.org/browse/gtk+/commit/?id=d5a8a3c9bc2a5dc30c1f16f2ac38869299aa86b9

gtk+ 2.21.6            : not crash
gtk+ 2.21.6 applied it : crash
gtk+ 2.21.7            : crash
gtk+ 2.21.7 revert it  : not crash

GDB backtrace log attached.

Regards,
        dai
--