Description of problem: It's not possible to use keyboard shortcuts mapped to sequence including <Control>. For example, default shortcut for menu is mapped to <Control>Escape, but that doesn't work. I need to assign the key again, however pressing Ctrl+Escape will map the sequence to <Primary>Escape. This is caused by a change in gtk: http://git.gnome.org/browse/gtk+/commit/?h=gtk-2-24&id=1f6a921158b5a4fa80ea2e844ce25aad04101aaf gnome-control-center has a workaround for the problem: http://git.gnome.org/browse/gnome-control-center/commit/?h=gnome-3-2&id=e46180ec18192a7954b4e75bca1594ec3ca3ae62 Version-Release number of selected component (if applicable): xfce4-settings-4.8.3-1.fc16.i686 gtk2-2.24.7-3.fc16.i686 How reproducible: always Steps to Reproduce: 1. use a key which includes <Control> in the key sequence 2. 3. Actual results: the shortcut doesn't work Expected results: it works Additional info:
This is upstream: https://bugzilla.xfce.org/show_bug.cgi?id=8056 Perhaps we can adapt the workaround.
This bug exists in F16, Gnome 3.2 as well. I myself and apparently some others are experiencing the same problem. http://ask.fedoraproject.org/question/260/ctrl-key-does-not-work-for-setting-shortcuts The link to the workaround you've posted here does not work, do you mind posting the workaround here or sending a working link ?
This is relevant to bug 752591
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. 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 '16'. 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 16'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 16 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, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. 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
I kinda still see the problem on Fedora 17 with xfce4-settings-4.10.0-3.fc17.x86_64. I can set Control + Alt (even if it turns into <Primary><Alt>something) but not Control + Shift. Is Control + Shift supposed to work?
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. 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 '17'. 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 17'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 17 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, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. 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.
(In reply to Jan Pazdziora from comment #5) > I kinda still see the problem on Fedora 17 with > xfce4-settings-4.10.0-3.fc17.x86_64. I can set Control + Alt (even if it > turns into <Primary><Alt>something) but not Control + Shift. Is Control + > Shift supposed to work? This behaviour is still the same with $ rpm -q xfce4-settings xfce4-settings-4.10.1-2.fc19.x86_64 Setting version 19.
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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.
I no longer see the problem with xfce4-settings-4.10.1-5.fc21.x86_64. I can create Ctrl + Shift + P, it's stored as <Primary><Shift>P and it works. Can you check on your installation?
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.