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 412970 - ctrl-a becomes ctrl-q under azerty keyboard?
ctrl-a becomes ctrl-q under azerty keyboard?
Status: RESOLVED DUPLICATE of bug 162726
Product: gnome-control-center
Classification: Core
Component: [obsolete] Keybinding
unspecified
Other Linux
: Normal major
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-02-28 06:57 UTC by Pascal Terjan
Modified: 2007-03-01 10:02 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Pascal Terjan 2007-02-28 06:57:20 UTC 
Ctrl+A is used in most graphical applications for "Select all" but trying it in Pan will quit !
Comment 1 Charles Kerr 2007-02-28 18:54:03 UTC 
That's strange.  Ctrl+A isn't mapped to anything at all in Pan.

GtkTreeView's internal mappings seem to pick it up as "Select all"
if a GtkTreeView has focus, but otherwise Ctrl+A should have no
effect at all.

* What version of Pan are you using?
* Is <Control>a mapped to anything in ~/.pan2/accels.txt?
Comment 2 Pascal Terjan 2007-02-28 20:40:24 UTC 
I'm using 0.125 and <Control>a does not appear in ~/.pan2/accels.txt

<Control>a and <Control>q both exit but I have no idea why...
Comment 3 Pascal Terjan 2007-02-28 21:21:27 UTC 
I added (gtk_accel_path "<Actions>/Actions/show-header-pane" "<Control>a") to ~/.pan2/accels.txt, just to test, and it correctly shows/hides the pane.
If I remove it, it quits again...
Comment 4 Charles Kerr 2007-02-28 23:24:49 UTC 
very strange, I can't reproduce this.  Could you run Pan in gdb 
with a breakpoint at mainloop_quit() and get a backtrace when
Pan exits on ctrl-a?
Comment 5 Pascal Terjan 2007-02-28 23:37:30 UTC 
mainloop_quit was not resolved by gdb so I set it on gtk_main_quit :

+ Trace 114773

  • #0 IA__gtk_main_quit
    at gtkmain.c line 1209
  • #1 IA__g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 77
  • #2 IA__g_closure_invoke
    at gclosure.c line 490
  • #3 signal_emit_unlocked_R
    at gsignal.c line 2440
  • #4 IA__g_signal_emit_valist
    at gsignal.c line 2199
  • #5 IA__g_signal_emit
    at gsignal.c line 2243
  • #6 _gtk_action_emit_activate
    at gtkaction.c line 835
  • #7 closure_accel_activate
    at gtkaction.c line 1602
  • #8 IA__g_closure_invoke
    at gclosure.c line 490
  • #9 signal_emit_unlocked_R
    at gsignal.c line 2440
  • #10 IA__g_signal_emit_valist
    at gsignal.c line 2209
  • #11 IA__g_signal_emit
    at gsignal.c line 2243
  • #12 IA__gtk_accel_group_activate
    at gtkaccelgroup.c line 736
  • #13 IA__gtk_accel_groups_activate
    at gtkaccelgroup.c line 774
  • #14 IA__gtk_window_activate_key
    at gtkwindow.c line 7706
  • #15 gtk_window_key_press_event
    at gtkwindow.c line 4697
  • #16 _gtk_marshal_BOOLEAN__BOXED
    at gtkmarshalers.c line 84
  • #17 g_type_class_meta_marshal
    at gclosure.c line 567
  • #18 IA__g_closure_invoke
    at gclosure.c line 490
  • #19 signal_emit_unlocked_R
    at gsignal.c line 2478
  • #20 IA__g_signal_emit_valist
    at gsignal.c line 2209
  • #21 IA__g_signal_emit
    at gsignal.c line 2243
  • #22 gtk_widget_event_internal
    at gtkwidget.c line 3915
  • #23 IA__gtk_propagate_event
    at gtkmain.c line 2309
  • #24 IA__gtk_main_do_event
    at gtkmain.c line 1569
  • #25 gdk_event_dispatch
    at gdkevents-x11.c line 2318
  • #26 IA__g_main_context_dispatch
    at gmain.c line 2045
  • #27 g_main_context_iterate
    at gmain.c line 2677
  • #28 IA__g_main_loop_run
    at gmain.c line 2881
  • #29 IA__gtk_main
    at gtkmain.c line 1148
  • #30 (anonymous namespace)::run_pan_in_window
  • #31 main 






Comment 6


Pascal Terjan





          2007-02-28 23:41:07 UTC
        



Does accel_key=113 mean it receives my 'a' as a 'q' ?






Comment 7


Pascal Terjan





          2007-02-28 23:55:30 UTC
        



This may be related to my keyboard layout (azerty) but the strange part is that when pressing Ctrl+q, the code is the same...

(gdb) bt




+
Trace
    114781






    

  • 
#0
IA__gtk_main_quit

    
                at gtkmain.c
                  line
                  1209

    

    • 

  • 
#1
IA__g_cclosure_marshal_VOID__VOID

    
                at gmarshal.c
                  line
                  77

    

    • 

  • 
#2
IA__g_closure_invoke

    
                at gclosure.c
                  line
                  490

    

    • 

  • 
#3
signal_emit_unlocked_R

    
                at gsignal.c
                  line
                  2440

    

    • 

  • 
#4
IA__g_signal_emit_valist

    
                at gsignal.c
                  line
                  2199

    

    • 

  • 
#5
IA__g_signal_emit

    
                at gsignal.c
                  line
                  2243

    

    • 

  • 
#6
_gtk_action_emit_activate

    
                at gtkaction.c
                  line
                  835

    

    • 

  • 
#7
closure_accel_activate

    
                at gtkaction.c
                  line
                  1602

    

    • 

  • 
#8
IA__g_closure_invoke

    
                at gclosure.c
                  line
                  490

    

    • 

  • 
#9
signal_emit_unlocked_R

    
                at gsignal.c
                  line
                  2440

    

    • 

  • 
#10
IA__g_signal_emit_valist

    
                at gsignal.c
                  line
                  2209

    

    • 

  • 
#11
IA__g_signal_emit

    
                at gsignal.c
                  line
                  2243

    

    • 

  • 
#12
IA__gtk_accel_group_activate

    
                at gtkaccelgroup.c
                  line
                  736

    

    • 

  • 
#13
IA__gtk_accel_groups_activate

    
                at gtkaccelgroup.c
                  line
                  774

    

    • 

  • 
#14
IA__gtk_window_activate_key

    
                at gtkwindow.c
                  line
                  7706

    

    • 

  • 
#15
gtk_window_key_press_event

    
                at gtkwindow.c
                  line
                  4697

    

    • 

  • 
#16
_gtk_marshal_BOOLEAN__BOXED

    
                at gtkmarshalers.c
                  line
                  84

    

    • 

  • 
#17
g_type_class_meta_marshal

    
                at gclosure.c
                  line
                  567

    

    • 

  • 
#18
IA__g_closure_invoke

    
                at gclosure.c
                  line
                  490

    

    • 

  • 
#19
signal_emit_unlocked_R

    
                at gsignal.c
                  line
                  2478

    

    • 

  • 
#20
IA__g_signal_emit_valist

    
                at gsignal.c
                  line
                  2209

    

    • 

  • 
#21
IA__g_signal_emit

    
                at gsignal.c
                  line
                  2243

    

    • 

  • 
#22
gtk_widget_event_internal

    
                at gtkwidget.c
                  line
                  3915

    

    • 

  • 
#23
IA__gtk_propagate_event

    
                at gtkmain.c
                  line
                  2309

    

    • 

  • 
#24
IA__gtk_main_do_event

    
                at gtkmain.c
                  line
                  1569

    

    • 

  • 
#25
gdk_event_dispatch

    
                at gdkevents-x11.c
                  line
                  2318

    

    • 

  • 
#26
IA__g_main_context_dispatch

    
                at gmain.c
                  line
                  2045

    

    • 

  • 
#27
g_main_context_iterate

    
                at gmain.c
                  line
                  2677

    

    • 

  • 
#28
IA__g_main_loop_run

    
                at gmain.c
                  line
                  2881

    

    • 

  • 
#29
IA__gtk_main

    
                at gtkmain.c
                  line
                  1148

    

    • 

  • 
#30
(anonymous namespace)::run_pan_in_window

    
                at pan.cc
                  line
                  154

    

    • 

  • 
#31
main

    
                at pan.cc
                  line
                  294

    

    • 













Comment 8


Pascal Terjan





          2007-03-01 00:19:51 UTC
        



So here is where I am :

- I start GNOME
- pan get the same key for Ctrl+a and Ctrl+q
- xev see correct keys for Ctrl+a and Ctrl+q
- I add the GNOME keyboard layout applet
- I switch to us layout using the applet
- pan only quits with Ctrl+q
- I switch to fr layout using the applet
- pan get the same key for Ctrl+a and Ctrl+q
- I change the layout to what is in my xorg.conf using setxkbmap (setxkbmap -layout fr -model pc105) and then keys get correct in pan but I can no longer change layout using the applet
- I try setxkbmap -layout fr,us and the I can switch again between both using the applet but pan gets again the same key for Ctrl+a and Ctrl+q







Comment 9


Charles Kerr





          2007-03-01 02:50:50 UTC
        



Re comment #6: 0x113 == 161 == 'q', so yes the 113 in

> #12 0xb7aca3a6 in IA__gtk_accel_group_activate (accel_group=0x8540e80,
> accel_quark=1253, acceleratable=0x853c000, accel_key=113,
> accel_mods=GDK_CONTROL_MASK)
>     at gtkaccelgroup.c:736
> #13 0xb7aca4ae in IA__gtk_accel_groups_activate (object=0x853c000,
> accel_key=113, accel_mods=GDK_CONTROL_MASK) at gtkaccelgroup.c:774

indicates that gtk+ thinks that ctrl-q has been pressed.

What version of gtk do you have installed?






Comment 10


Charles Kerr





          2007-03-01 03:11:51 UTC
        



Given that Pan doesn't do anything with <control>a,
and judging from the backtraces and comment #8, I suspect this
is a bug in either gnome-keyboard-properties or in gtk+ itself.

I'm bumping this over to the control-center keyboard people
to get another pair of eyes to look at this.  Feel free to
bump it back if you feel this is a bug in Pan.






Comment 11


Sebastien Bacher





          2007-03-01 10:02:30 UTC
        



Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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