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 563460 - incorrect mapping of gtk_text_view shortcuts
incorrect mapping of gtk_text_view shortcuts
Status: RESOLVED DUPLICATE of bug 162726
Product: gtk+
Classification: Platform
Component: Widget: GtkTextView
2.14.x
Other All
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2008-12-06 15:12 UTC by tim
Modified: 2008-12-06 15:28 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24



Description tim 2008-12-06 15:12:38 UTC
Please describe the problem:
some shortcuts are not working correctly in gedit's text view. i could reproduce the following incorrect mapping on my system:

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

doing some debugging of the ctrl+q issue, i found the following, considering the following backtrace:
  • #0 gtk_text_view_select_all
    at /build/buildd/gtk+2.0-2.14.4/gtk/gtktextview.c line 7452
  • #1 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #2 ??
    from /usr/lib/libgobject-2.0.so.0
  • #3 gtk_binding_entry_activate
    at /build/buildd/gtk+2.0-2.14.4/gtk/gtkbindings.c line 537
  • #4 binding_match_activate
    at /build/buildd/gtk+2.0-2.14.4/gtk/gtkbindings.c line 1109
  • #5 gtk_bindings_activate_list
    at /build/buildd/gtk+2.0-2.14.4/gtk/gtkbindings.c line 1254
  • #6 IA__gtk_bindings_activate_event
    at /build/buildd/gtk+2.0-2.14.4/gtk/gtkbindings.c line 1347
  • #7 gtk_text_view_key_press_event
    at /build/buildd/gtk+2.0-2.14.4/gtk/gtktextview.c line 4113
  • #8 ??
    from /usr/lib/libgtksourceview-2.0.so.0
  • #9 _gtk_marshal_BOOLEAN__BOXED

in frame 6, event has the value:
(gdb) print *event
$11 = {type = GDK_KEY_PRESS, window = 0x1ea5520, send_event = 0 '\0', 
  time = 9579906, state = 22, keyval = 81, length = 1, 
  string = 0x2400dd0 "\021", hardware_keycode = 24, group = 0 '\0', 
  is_modifier = 0}

the keyval 81 has the correct ascii value for `q'. it is resolved to the entry of `a', though. at frame 3:
(gdb) print *entry
$12 = {keyval = 97, modifiers = GDK_CONTROL_MASK, binding_set = 0x1e04bf0, 
  destroyed = 0, in_emission = 1, marks_unbound = 0, set_next = 0x1e1cc70, 
  hash_next = 0x1bfdbb0, signals = 0x1e03950}

i been able to reproduce it with the gtk applications evolution and gedit

Steps to reproduce:
hard. pbor and jessevdk from the #gedit irc chat haven't been able to reproduce the issue.
there are some bug reports on the ubuntu tracker, though:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/305287
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/303710
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/294351

Actual results:


Expected results:


Does this happen every time?
yes

Other information:
Comment 1 Christian Persch 2008-12-06 15:28:38 UTC
QWERTY
AZERTY

-> bug 162726 

*** This bug has been marked as a duplicate of 162726 ***