GNOME Bugzilla – Bug 165958
Disappearing Keyboard Shortcut
Last modified: 2005-02-09 03:47:06 UTC
Distribution: Debian 3.1 Package: metacity Severity: normal Version: GNOME2.8.1 unspecified Gnome-Distributor: Debian Synopsis: Disappearing Keyboard Shortcut Bugzilla-Product: metacity Bugzilla-Component: general Bugzilla-Version: unspecified Description: Description of Problem: After restarting Gnome, a specific keyboard shortcut no longer works. The problem involves xmodmap, but this specific problem is NOT about xmodmap startup.(I know there have been a lot of complaints). I have xmodmap executed in session startup and it works ok. Steps to reproduce the problem: 1. Set /apps/metacity/global_keybindings/run_command_1 to the key "F13", (a non-existant key on my keyboard). 2. Set /apps/metacity/keybinding_commands/command_1 to /usr/bin/sudo /usr/bin/apm -s 3. Find the "sleep" key on the keyboard using xev. Link the key to "F13" in ~/.Xmodmap ('keycode 223 = F13') 4. Place "xmodmap /home/<user>/.Xmodmap" in session startup. 5. Test out the sleep key. (It should successfully run "sudo apm -s" and put the computer in a low power state.) 6. Logout of Gnome, then back in. 7. Test out the sleep key. (It doesn't want to work.) 8. Set /apps/metacity/global_keybindings/run_command_1 to something other than key "F13". 9. Set /apps/metacity/global_keybindings/run_command_1 back to the key "F13". 10. Go to step 5 Actual Results: Reproducable Always Expected Results: How often does this happen? Additional Information: ------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-02-01 13:41 ------- Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "metacity". Setting to default milestone for this product, '---' The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@bugzilla.gnome.org. Previous reporter was stephenpinker@hotpop.com. Setting to default status "UNCONFIRMED". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
Probably an issue with handling of MappingNotify
Havoc: could you explain? I don't see the connection. I believe this is a dupe of bug 164082, but Havoc's comment confuses me so I'm leaving it alone for now.
It does look like a dup. My theory is just that metacity starts up before the keymap changes are loaded, and then metacity fails to handle the mappingnotify correctly. If that were true you'd probably expect any dynamic change to the keymap to fail to take effect though, and I guess this bug says that it works, just not at login. So, I don't really know what could be wrong.
Hehe, OOOOPS. I read "MappingNotify" as "MapNotify" and was thinking "what in the world do keyboard shortcuts have to do with windows appearing?" Reading what you said correctly makes a lot more sense. :-) Anyway, I'll go ahead and mark as a dupe... *** This bug has been marked as a duplicate of 164082 ***
Hello... I am the individual that sent in this bug report. I've been following the discusion here. After reading of "bug 164082", I immediately thought, "Wow yeah, his problem is almost exactly like mine". But here's the twist: When I tried the work-around he posted(killing metacity), it still didn't work. I can only conclude that this bug is different.
I was wrong. It's not a bug. It was a failure on my part. My apologies.
No worries; thanks for letting us know.