Bug 193003

Summary:	KDE 4.3b1 blocks Ctrl-W for all apps
Product:	[I don't know] kde	Reporter:	markuss <kamikazow>
Component:	general	Assignee:	Michael Jansen <kde>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	andresbajotierra, kvalko
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	openSUSE
OS:	Unspecified
Latest Commit:		Version Fixed In:

Description markuss 2009-05-17 14:19:07 UTC

Version:            (using KDE 4.2.85)
Installed from:    SuSE RPMs

Ever since I installed KDE 4.3b1 yesterday, I can't use Ctrl-W anymore.
Ctrl-W no longer closes tabs in either Dolphin, Firefox, Kopete, or Songbird.
Some other KDE component I failed to identify intercepts this shortcut. 
As far as I can see, no other shortcuts are affected.

Comment 1 Dario Andres 2009-05-17 16:43:15 UTC

Can you check if you can reassign this shorcut? (may be it appeared an internal conflict with a global Ctrl+W action)
Try going to Dolphin.. Settings/Configure Shortcuts... and configuring the Close Tab shortcut to another keyshortcut and then back to Ctrl+W
Thanks

Comment 2 Kevin Valko 2009-05-18 01:24:57 UTC

I can confirm the bug with the opensuse 4.3B1 packages.

I worked around it by disabling the shortcut for "Remap Ctrl+W to Ctrl+F4 in Qt Designer" under System Settings -> Keyboard & Mouse -> Global Keyboard Shortcuts -> khotkeys.  It was set to Ctrl+W, so I assume it was intercepting the shortcut.

Ctrl+W now works as expected for closing tabs; I don't use Qt Designer so I'm not sure if there is an unexpected impact from this, though.

Comment 3 markuss 2009-05-18 10:36:08 UTC

Indeed, it's the Qt Designer thingie. According to the description on that action, KHotKeys searches for "Qt Designer by Trolltech" in the window title and only when that one is active rerouts Ctrl-W.
I'm only guessing, but maybe someone modified the action, because Trolltech is no longer called Trolltech and accidentally applied the action to all windows instead of only that specific Qt Designer one.

Comment 4 Michael Jansen 2009-05-18 14:08:28 UTC


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