Bug 351825 - "Window to Screen" Shortcut doesn't work
Summary: "Window to Screen" Shortcut doesn't work
Status: VERIFIED DUPLICATE of bug 341959
Alias: None
Product: kwin
Classification: Plasma
Component: core (show other bugs)
Version: 5.3.2
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-08-26 19:56 UTC by tom
Modified: 2015-08-26 20:45 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description tom 2015-08-26 19:56:47 UTC 
When using two or more screens, it's very helpful to be able to move windows using a keyboard shortcut. This shortcut is provided by kwin in the "Global Keyboard Shortcuts" but since upgrading to plasma 5 it doesn't work anymore.

Reproducible: Always

Steps to Reproduce:
1. Configure the shortcut in "Global Keyboard Shortcuts"
2. Press the configured key combination

Actual Results:  
Nothing happens

Expected Results:  
Window moves to another screen
Comment 1 Thomas Lübking 2015-08-26 20:19:46 UTC 
a) Which action exactly ("window to screen #n" or "window to next/previous screen"
b) which shortcut exactly? (does it eg. include shift and a number)
c) does the "move to screen" entry in the titlebars context menu work for you?
d) does "kglobalaccel5" run ("ps ax | grep kglobalaccel5")
e) does restarting that ("pkill kglobalaccel5; sleep 1; kglobalaccel5 &") make it work™?
Comment 2 tom 2015-08-26 20:29:22 UTC 
a: "window to screen #n"
b: ctrl + shift + 123
c: yes, move to screen in the titlebar works
d: kglobalaccel5 is running
e: restarting it doesn't solve the issue
Comment 3 Thomas Lübking 2015-08-26 20:36:32 UTC 
(In reply to tom.zoehner from comment #2)
> a: "window to screen #n"
> b: ctrl + shift + 123

That's by 99.9% chance bug #341959 - try a shortcut that does NOT include shift (eg. meta+ctrl+123) or to assign this shortcut to any global action.

Pre-emptively duping.

*** This bug has been marked as a duplicate of bug 341959 ***
Comment 4 tom 2015-08-26 20:45:12 UTC 
That works around we issue, thank you very much.