Version: (using KDE KDE 3.5.2) Installed from: Gentoo Packages Compiler: gcc version 3.4.5 (Gentoo 3.4.5-r1, ssp-3.4.5-1.0, pie-8.7.9) OS: Linux I like to set Ctrl+Tab to Activate Next Tab in my programs. This works like a charm. However, when trying to set Ctrl+Shift+Tab to Activate Previous Tab, it will be interpreted as "Ctrl+Shift+Backtab" which will not work. I have to manually edit my kdeglobals file to replace this with Ctrl+Shift+Tab, which does work.
I have the same problem. And when I try to switch tasks using Alt+Tab and Alt+Shift+Tab, the Alt+Shift+Tab doesn't work even though it's set as shortcut, just because KDE gets it as "Backtab", which doesn't match the defined shortcut. To make it work, I have to change the default shortcut to Alt+Backtab manually. I think it should work out of the box.
*** Bug 196009 has been marked as a duplicate of this bug. ***
Still the case for KDE4.
KDE 4.3.0, i686, pld-linux.org When I add shortcut for previous desktop as meta+shift+tab, it is saved as "Meta+Shift+Tab", and it does not work. When I manually edit ~/.kde/share/config/kglobalshortcutsrc and change Tab to Backtab, shortcut works.
Tried that, too. Unfortunately that doesn't for me.
This is weird. It works now for me. I changed the kglobalshortcutsrc a few days ago and now it just works? Maybe kde needed a restart and not just kwin.
Works for me out of the box with Qt-4.6 and kdelibs-4.5.2. I tested using "Configure Shortcuts" in konqueror. When typing the shortcut, the shortcut editor shows Ctrl+Shift+Tab, not Ctrl+Backtab. xev still shows ISO_Left_Tab, so this isn't due to a different Xorg configuration. I assume it has been fixed in Qt. Please reopen if you still experience the bug with Qt >= 4.6 and kdelibs >= 4.5.
Well, that's one way to fix bugs -- give it four and a half years and see if it gets fixed on its own in the interim. :-) Seems like the wrong resolution status though.
If you have any other suggestion on how to handle 2000 open bug reports, I'm all ears :-) I don't think the resolution status is wrong: I use FIXED when I know the commit that fixed the bug for sure. I use WORKSFORME when, well, it works for me, but I have no way of knowing if that's because something in my setup is different, or because it indeed got fixed meanwhile. If you confirm that it works for you too nowadays, then indeed it sounds like it got fixed (most probably in Qt, btw, which also explains the delay...)