Custom workspaces keybindings do not work

Bug #1624654 reported by Sondre
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Switchboard Keyboard Plug
New
Undecided
Unassigned

Bug Description

Custom workspaces keybindings do not work. See comments 2 and 6.

Tags: loki
Sondre (sondrer)
tags: added: loki
Revision history for this message
Danielle Foré (danrabbit) wrote :

OP, please be more specific about what you mean by "don't work". What exactly are the steps to report the problem? What did you expect to happen? What happens instead?

Changed in elementaryos:
status: New → Incomplete
Revision history for this message
Sondre (sondrer) wrote :

These were my steps:
1. Assign Super+Alt+Right arrow to switch to next workspace.
2. Assign Super+Alt+Shift+Right arrow to move selected application to next workspace.
3. Open two or more windows.
4. Press Super+Alt+Shift+Right arrow.

Now I expected the current window to be moved to the next workspace, but nothing happened.

5. Restart the computer and log in.
6. Open a program.
7. Press Super+Alt+Right arrow.

Now I expect it to change workspace to the next one. It did this, however the window followed into workspace 2. Now pressing Super+Alt+Shift+Left and Right arrow one after another, the workspace just bounces showing that there are no more than one workspace.

8. Assign Super+q to Show workspace switcher.
9. Press Super+q.

Now I expect to see my open windows and only one workspace (because creating a new one doesn't work). However only a tab showing a plus is showing at the bottom, and an empty screen with the background picture in the middle of the screen.

Revision history for this message
Sondre (sondrer) wrote :

@danrabbit

Additionally this was all done with a secondary display connected.

Revision history for this message
Sondre (sondrer) wrote :

With the laptop primary display disabled.

Revision history for this message
Zisu Andrei (matzipan) wrote :

Hello,

I'm not sure why you expected those key bindings to work. In Switchboard, under Keyboard -> Shortcuts -> Workspaces you will see a full list.

Revision history for this message
Sondre (sondrer) wrote :

@matzipan I expected them to work because I assigned them like that in Keyboard -> Shortcuts -> Workspaces.

@danrabbit Is this still incomplete. Note that this bug only happens when connecting a secondary display (even though the primary is disabled).

Revision history for this message
Zisu Andrei (matzipan) wrote :

If you set them. It means that the issue is not that "workspaces do not work", but that "key bindings do not work as set".

summary: - Workspaces don't work
+ Custom workspaces keybindings do not work
affects: elementaryos → switchboard-plug-keyboard
Changed in switchboard-plug-keyboard:
status: Incomplete → New
description: updated
Revision history for this message
Sondre (sondrer) wrote :

@matzipan Have you tried this with an external monitor using the default keybindings? I cannot try it because I have changed the keybindings from the default. It works on my computer when an external monitor is not connected. The only time it doesn't work is with the external display connected. The main monitor is disabled.

Revision history for this message
Sasa Savic (sale4one) wrote :

@sonder I was struggling for a long time about this, never looked in the bugs until now, as I am really angry. When I am using an external monitor the keybindings for changing workspaces don't work (default keybindings). It looks like that eOS loses workspace functionality completely as I can't even move the windows to another workspace by right-clicking on the title bar and calling "Move to Workspace left". As soon as I disconnect the monitor everything works as expected.

Woohoo, I just found a nice quick fix for this, until this bug gets a patch. If you are disabling the main monitor on your laptop and using an external monitor (docking the laptop or similar), make sure that you set the external monitor as "Primary monitor" by clicking on the star in the Displays section in Settings. I guess the problem here is that eOS thinks this is a secondary monitor even when the primary is disabled, should be fixable?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.