Created attachment 374590 [details] Duplicate Actions The Keyboard Shortcuts tool has duplicate actions under the "Window Management" section. The only difference seems to be the capitalization style, like "Maximize Window Vertically" vs "Maximize window vertically". They also seem to not sync up, for example, I can set a key binding for one and the other is unaffected. If I choose the wrong one, then my keybinding doesn't work, which adds to the confusion. How reproducible: Happens every time. Steps to Reproduce: 1. System -> Preferences -> Keyboard Shortcits 2. Scroll down to Window Management section 3. See duplicate actions Expected results: Only show one item per real window management action.
You probably have both compiz and metacity installed ? Bastien, I thought we had this fixed ?
Yes, although I don't remember installing compiz manually, it seems that I do have both compiz and metacity installed. This issue seems similar to this bug (which was just recently fixed): https://bugzilla.gnome.org/show_bug.cgi?id=600531 Although that one seems to suggest that I should only see other WM's keybindings and not metacity's, but in my case I see both metacity's and compiz's keybindings. Thanks, -Damien
control-center-2.28.1-10.fc12 has been pushed to the Fedora 12 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update control-center'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F12/FEDORA-2009-12983
The update removed the duplicates, but now I am only seeing the Compiz actions when I should be seeing the Metacity ones (since that's my active WM). To confirm this, I tried changing the "Maximize Window Vertically" shortcut while observing both of these keys in gconf-editor: /apps/metacity/window_keybindings/maximize_vertically /apps/compiz/general/allscreens/options/maximize_window_vertically_key When I modify the shortcut in the keybinding tool, the Compiz value changes but not the Metacity one.
I believe what I'm seeing is the bug referred earlier on the Gnome Bugzilla: https://bugzilla.gnome.org/show_bug.cgi?id=600531 It was committed upstream about a month ago, but wasn't applied to the 2.28 branch: http://git.gnome.org/cgit/gnome-control-center/commit/?id=7c82b5b5cc89c0934f13e66175f3881b8f5528f4 I'm not sure how to check if Fedora's version has this patch though.
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.