GNOME Bugzilla – Bug 508751
gnome-terminal crashed with SIGSEGV after keypress
Last modified: 2008-08-26 11:07:19 UTC
This report has been filled here: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/180626 "after an emerald crash gnome-terminal showed very strange behaviour. i first opened a new gnome-terminal and the bash shell showed up. selecting the terminal window and pressing any key made gnome-terminal to segfault." ".
+ Trace 184932
Thread 1 (process 31736)
I just found several other crashes in Launchpad with the same stacktrace, so I think this is a real problem. See the duplicate list in https://launchpad.net/bugs/180626.
*** Bug 530491 has been marked as a duplicate of this bug. ***
This happens in all GTK apps when xmodmap has no modifiers at all. To reproduce: try deleteing all the modifiers like: xmodmap -e 'remove lock = Caps Lock' until 'xmodmap' returns an empty list. Then run NEW gtk apps, they'll all die with a keypress, in this _gdk_keymap_key_is_modifier function. Why would anyone have an empty list of modifiers? VMware bug causes deletion of modifiers : https://bugs.launchpad.net/bugs/195982 Still, non-gtk apps handle this situation well, so I think this issue should be solved.
This is an X bug. If the modifier map is empty, then XkbGetMap (display, XkbModifierMapMask, XkbUseCoreKbd) doesn't allocate the modmap member of the client map. This is because _XkbReadModifierMap only allocates if rep->totalModMapKeys>0. And totalModMapKeys is zero if there are no modifier keys. We can work around this inside GTK+, but it should probably be fixed in XKB.
* gdk/x11/gdkkeys-x11.c (_gdk_keymap_key_is_modifier): Protect against XKB being stupid. Reported by Pedro Villavicencio.
*** Bug 534430 has been marked as a duplicate of this bug. ***
*** Bug 485997 has been marked as a duplicate of this bug. ***