Bug 982695 - Regression: Unable to disable or change workspace navigation shortcuts
Summary: Regression: Unable to disable or change workspace navigation shortcuts
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: control-center
Version: 28
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Control Center Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-07-09 15:19 UTC by Mat Booth
Modified: 2019-05-28 19:24 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-05-28 19:24:33 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Mat Booth 2013-07-09 15:19:20 UTC
I am unable to change or disable the "Move to workspace above/below" shortcuts in Gnome 3. If I change or disable the shortcut, I can still use Ctrl+Alt+Up/Down to switch workspaces.

Another application (Eclipse) has shortcuts that clash with the default Gnome 3 shortcuts for switching workspaces, so I wish to disable the Gnome 3 shortcuts.

This used to work in Fedora 18/Gnome 3.6 so it appears to be a regression.


Version-Release number of selected component (if applicable):
control-center-3.8.3-2.fc19.x86_64
gnome-settings-daemon-3.8.3-3.fc19.x86_64
gnome-settings-daemon-updates-3.8.3-3.fc19.x86_64
gnome-shell-3.8.3-3.fc19.x86_64


Steps to Reproduce:
1. Open Settings-->Keyboard-->Shortcuts-->Navigation
2. Disable shortcuts for "Move to workspace above/below" or change the shortcuts away from the defaults
3. Still able to use Ctrl+Alt+Up/Down to change workspaces

Comment 1 peereken 2013-07-30 12:05:33 UTC
I had the same problem. The new keybinding you can define in 'Settings-->Keyboard-->Shortcuts-->Navigation' is appended to the previous/default one. 

for example:
gsettings get org.gnome.desktop.wm.keybindings switch-to-workspace-down
['<Primary><Shift>Down', '<Control><Alt>Down']


I managed to remove the default keybinding using the following commands
gsettings set org.gnome.desktop.wm.keybindings switch-to-workspace-down "['']"
gsettings set org.gnome.desktop.wm.keybindings switch-to-workspace-up "['']"

This clears all defined shortcuts for those tasks. And then just use 'Settings-->Keyboard-->Shortcuts-->Navigation' to define the desired shortcuts.

Comment 2 Mat Booth 2013-07-30 13:05:34 UTC
I had not figured out the workaround so this is extremely helpful!

Thank-you, anonymous hero!

Comment 3 Mat Booth 2014-04-02 10:21:11 UTC
This is still a problem in F20

Comment 4 Fedora End Of Life 2015-05-29 09:10:06 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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 EOL if it remains open with a Fedora  'version'
of '20'.

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 20 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.

Comment 5 Fedora End Of Life 2015-06-29 12:03:49 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.

Comment 6 Rik 2017-06-17 15:06:56 UTC
This is still a problem in Fedora 26 beta. Also the workaround does not work. 

I have disabled the navigation shortcut to switch workspace. So this shortcut has no function anymore in Gnome but still this shortcut is "swallowed". Btw, I have disabled allmost all navigation shorcuts which have something to do with workspaces/windows.

Comment 7 Rik 2017-06-17 16:02:34 UTC
I do not see a way to reopen this issue.

Comment 8 Mat Booth 2017-08-25 15:07:07 UTC
Still a problem on fresh installs of F26 -- still interferes with Eclipse's default shortcuts because it's impossible to unset the default gnome shortcut.

Comment 9 Mat Booth 2017-08-25 15:11:23 UTC
By default the switch workspace actions still have two shortcuts, but the gnome shortcut settings panel still only shows the first one in the list:

$ gsettings get org.gnome.desktop.wm.keybindings switch-to-workspace-down
['<Super>Page_Down', '<Control><Alt>Down']

The workaround of clobbering these settings manually still works for me:

$ gsettings set org.gnome.desktop.wm.keybindings switch-to-workspace-down "['<Super>Page_Down']"
$ gsettings set org.gnome.desktop.wm.keybindings switch-to-workspace-up "['<Super>Page_Up']"

Comment 10 karlp 2017-12-07 23:31:50 UTC
There seems to be an alias (On my old FC23 at least)

switch-to-workspace-down/up _and_ move-to-workspace-down/up.

These _both_ need to be cleared out via the workaround to make this all go away properly.

Comment 11 Fedora End Of Life 2018-05-03 08:56:34 UTC
This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. 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 EOL if it remains open with a Fedora  'version'
of '26'.

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 26 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.

Comment 12 karlp 2018-05-03 10:03:28 UTC
This is still a problem on FC27. I can't change the version though.

$ gsettings get org.gnome.desktop.wm.keybindings switch-to-workspace-down
['<Super>Page_Down', '<Control><Alt>Down']

The second "ctrl-alt-down" isn't show in the ui, so even though you've disabled everything that was using the ctrl-alt-down, it's still broken.

(and of course, same for up)

Comment 13 Mat Booth 2018-05-03 12:48:17 UTC
(In reply to karlp from comment #12)
> This is still a problem on FC27. I can't change the version though.
> 
> $ gsettings get org.gnome.desktop.wm.keybindings switch-to-workspace-down
> ['<Super>Page_Down', '<Control><Alt>Down']
> 
> The second "ctrl-alt-down" isn't show in the ui, so even though you've
> disabled everything that was using the ctrl-alt-down, it's still broken.
> 
> (and of course, same for up)

Thanks for testing it's still a problem -- I altered the version accordingly.

Comment 14 Mat Booth 2018-08-15 10:18:45 UTC
Looks still a problem in F28.

Comment 15 Ben Cotton 2019-05-02 21:05:44 UTC
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. 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
EOL if it remains open with a Fedora 'version' of '28'.

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 28 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.

Comment 16 karlp 2019-05-03 09:15:58 UTC
I can't speak for fedora 28, but on Fedora 29, this appears fixed, or at least, the original core of this issue.  The keyboard shortcuts UI shows meta-pageup/down, and deleting those shortcuts (via backspace) successfully clears out the ctrl-alt-up/down shortcuts.

There doesn't appear to be a way to leave meta-pageup/down in place and remove only the ctrl-alt-up/down shortcuts, but that can be a different bug if anyone cares about that.

Comment 17 Ben Cotton 2019-05-28 19:24:33 UTC
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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.


Note You need to log in before you can comment on or make changes to this bug.