Bug 67309

Summary: gnome-panel panel_parse_accelerator not parsing <Modn>
Product: [Retired] Red Hat Linux Beta Reporter: Jens Petersen <petersen>
Component: gnome-panelAssignee: Havoc Pennington <hp>
Status: CLOSED RAWHIDE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 6.1.91   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2003-01-07 23:25:54 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 67218, 79579    

Description Jens Petersen 2002-06-22 03:57:19 UTC
Description of Problem:
When I bind "<mod4>F1" and "<mod4>F2" say to menu_key and "run_key"
respectively (with gconf-editor) the bindings do not work.  Only the
modifiers "<Control>", "<Alt>" and "<Shift>" seems to work, not those
for modN.

Version-Release number of selected component (if applicable):
gnome-panel-2.0.0-2
gtk2-2.0.5-1

How Reproducible:
every time

Steps to Reproduce:
1. change bindings to use "<Mod4>" modifier instead of the default
"<Alt>" in gconf-editor. 

Actual Results:
Menu and run bindings don't work with mod4 modifier.

Expected Results:
Using modN modifiers should work.

Additional Information:
"<ModN>" works in metacity and I note that `panel_parse_accelerator'
("panel_util.c") lacks some of the code in metacity's
`meta_ui_parse_accelerator' ("ui.c"), however looking at gtk's
`gtk_accelerator_parse', I don't see why `panel_parse_accelerator'
shouldn't work, or in other words why the extra modifier code in
`meta_ui_parse_accelerator' is necessary.

<grumble>WIBNI `gtk_accelerator_parse' could handle "<Meta>" too
(and "<Hyper>" perhaps).</grumble>  I'll try to file a separate
RFE for that though.

Comment 1 Havoc Pennington 2002-07-10 21:56:27 UTC
I don't think the bug can be in panel_parse_accelerator() - it just 
calls gtk_accelerator_parse, no strangeness there.

The problem is the IGNORED_MODS #define, see
http://bugzilla.gnome.org/show_bug.cgi?id=87876

Comment 2 Jens Petersen 2002-07-11 07:03:20 UTC
So in the mean time can the ModN keys be moved from IGNORED_MODS
to USED_MODS?

Metacity supports <Meta> now?


Comment 3 Havoc Pennington 2002-07-11 15:18:43 UTC
No, just moving from ignored mods to used mods doesn't work - you do need to
ignore numlock and scroll lock. This is why you have to dynamically sort out
which mods are which.

Metacity supports <ModN>, not <Meta>, it still uses gtk_accelerator_parse(). But
metacity doesn't hardcode the ignored mods, it dynamically locates numlock.

Comment 4 Havoc Pennington 2003-01-07 23:25:54 UTC
Should be fixed in rawhide, or if not in the next gnome-panel upstream 
version we get. But 90% sure fixed in rawhide.