Bug 54174 - kwin eats all Ctrl b characters, prevents Ctrl B from working in any app.
Summary: kwin eats all Ctrl b characters, prevents Ctrl B from working in any app.
Status: RESOLVED DUPLICATE of bug 45312
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Solaris
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-02-05 23:12 UTC by Aaron Williams
Modified: 2003-02-06 12:03 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 Aaron Williams 2003-02-05 23:12:37 UTC
Version:            (using KDE KDE 3.1)
Installed from:    Compiled From Sources
Compiler:          gcc 2.95.3 sparc solaris 2.7
OS:          Solaris

For some reasin, kwin is consuming all Ctrl B keystrokes preventing them from reaching any other apps.  It blocks it for non-KDE apps as well, like xterm and xemacs.

I tried changing the hotkey assignment for bookmarks from Ctrl B to Alt B and later tried disabling the bookmark accelerator all together, but it made no difference.

When running kwin with debugging enabled I see the following when I hit Ctrl B in any application:

 kdecore (KAccel): Workspace::keyPress( Ctrl+B ) 

I do not see this for other keystrokes that are not captured (i.e. Ctrl A, Ctrl F).
 
I have tried running twm instead of kwin.  When I do this Ctrl B works.  Obviously this isn't a solution, though.

After browsing all the kwin code I cannot see where the hook is being added for Ctrl B.  I also have been going through the kdelibs/kdecore files to see if anything there could explain the problem.

This was previously marked as bug 54046 (http://bugs.kde.org/show_bug.cgi?id=54046).  I am reentering the bug here since it appears to be kwin related rather than kdelibs related.

-Aaron
Comment 1 Aaron Williams 2003-02-06 05:18:31 UTC
Actually, this is a duplicate of bug 45312 which still exists, BTW. 
Comment 2 Stephan Binner 2003-02-06 12:03:28 UTC

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