Bug 262196 - Ctrl+Shift+Tab not used as keybord shortcut
Summary: Ctrl+Shift+Tab not used as keybord shortcut
Status: RESOLVED DUPLICATE of bug 179562
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-05 15:08 UTC by tnemeth
Modified: 2011-01-05 15:18 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description tnemeth 2011-01-05 15:08:05 UTC
Version:           unspecified (using KDE 4.5.4) 
OS:                Linux

Hi!

I like using Ctrl+Tab to switch to the next workspace and Ctrl+Shit+Tab to shift to
the previous one. However, when trying to insert this last shortcut in the KWin
configuration, nothing happens when I use the shortcut. After looking at the other
entries, I noticed that some shortcuts used "xxx+Shift+Backtab".

So I edited the kglobalshortcutsrc file and replaced the "Tab" entry in the wanted
section by "Backtab" (ie: "Ctrl+shift+Tab" -> "Ctrl+Shift+Backtab") and restarted
KDE.

After the restart, the shortcut worked as intended.

Thomas.

Reproducible: Always

Steps to Reproduce:
Set the Ctrl+Shift+Tab shortcut for the "Switch to Previous Desktop", try it.
Edit, the same shortcut entry in the configuration file, to replace "Tab" by "Backtab",
restart KDE and try again.

Actual Results:  
With the automatically inserted shortcut, the shortcut doesn't work. With the edited
one, the shortcut works as intended.

Expected Results:  
Either the shortcut should work out of the box or the inserted keys in the entry field
should be right, using "Backtab" instead of "Tab"...
Comment 1 Thomas Lübking 2011-01-05 15:18:31 UTC
... and it probably /is/ a dupe of bug #179504, can't assign ctrl+alt+shif+1 to anything - probably a bug in the "keys" kcm dialog.

*** This bug has been marked as a duplicate of bug 179562 ***