gedit keyboard shortcut problem

[mokabar]

Binary package hint: gedit

in the editor window, some keyboard shortcuts are not working correctly. they are working, if the side pane has the focus, though.

some issues:
ctrl+w: `undo' instead of `close'
ctrl+q: `select all' instead of `quit'

this bug may be related to 294351. however ctrl+s is working fine on my machine.

ProblemType: Bug
Architecture: amd64
DistroRelease: Ubuntu 8.10
Package: gedit 2.24.2-0ubuntu1
ProcEnviron:
 PATH=/home/username/monouml-0.1/bin/:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gedit
Uname: Linux 2.6.27.7 x86_64

[Pedro Villavicencio (pedro)]

Thank you for taking the time to report this issue and helping to make Ubuntu better. Examining the information you have given us, this does not appear to be a bug report so we are closing it and converting it to a question in the support tracker. We appreciate the difficulties you are facing, but it would make more sense to raise problems you are having in the support tracker at https://answers.launchpad.net/ubuntu if you are uncertain if they are bugs. For help on reporting bugs, see https://help.ubuntu.com/community/ReportingBugs.

[mokabar (tim-klingt)]

doing some debugging, i found, there is an issue in the resolution of the gtk_text_view key bindings:

considering the following backtrace:
(gdb) bt
#0 gtk_text_view_select_all (widget=0x1e281b0, select=1)
    at /build/buildd/gtk+2.0-2.14.4/gtk/gtktextview.c:7452
#1 0x00007fad4e59625d in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
#2 0x00007fad4e5abc3b in ?? () from /usr/lib/libgobject-2.0.so.0
#3 0x00007fad5139d83c in gtk_binding_entry_activate (entry=0x1e1ccb0,
    object=0x1e281b0) at /build/buildd/gtk+2.0-2.14.4/gtk/gtkbindings.c:537
#4 0x00007fad5139dd21 in binding_match_activate (
    pspec_list=<value optimized out>, object=0x1e281b0, path_length=11,
    path=0x1ea3fe0 "GtkTextView", path_reversed=0x1c75640 "weiVtxeTktG",
    unbound=0x7fff5a4cc8e0)
    at /build/buildd/gtk+2.0-2.14.4/gtk/gtkbindings.c:1109
#5 0x00007fad5139df9a in gtk_bindings_activate_list (object=0x1e281b0,
    entries=<value optimized out>, is_release=<value optimized out>)
    at /build/buildd/gtk+2.0-2.14.4/gtk/gtkbindings.c:1254
#6 0x00007fad5139e105 in IA__gtk_bindings_activate_event (object=0x1e281b0,
    event=0x204f6e0) at /build/buildd/gtk+2.0-2.14.4/gtk/gtkbindings.c:1347
#7 0x00007fad514ffff0 in gtk_text_view_key_press_event (widget=0x1e281b0,
    event=0x204f6e0) at /build/buildd/gtk+2.0-2.14.4/gtk/gtktextview.c:4113
#8 0x00007fad5191a9d2 in ?? () from /usr/lib/libgtksourceview-2.0.so.0
#9 0x00007fad5144c908 in _gtk_marshal_BOOLEAN__BOXED (closure=0x19b5750,
    return_value=0x7fff5a4ccdc0, n_param_values=<value optimized out>,
    param_values=0x2052640, invocation_hint=<value optimized out>,
    marshal_data=0x7fad5191a8a0)

in frame 7, event->keyval has the value 81 (`q')
in frame 3, entry->keyval has the value 97 (`a')

so somehow the event `q' is mapped to the entry for the of shortcut `a' on the way from frame 7 to frame 3.

[mokabar (tim-klingt)]

bug #303710 seems to be related as well

[mokabar (tim-klingt)]

possibly related upstream bug: http://bugzilla.gnome.org/show_bug.cgi?id=162726