Bug 68685 - Desktop receives input when not focused.
Summary: Desktop receives input when not focused.
Status: RESOLVED WORKSFORME
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Slackware Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-11-20 20:03 UTC by Dylan Griffiths
Modified: 2003-11-23 03:39 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dylan Griffiths 2003-11-20 20:03:38 UTC
Version:            (using KDE KDE 3.1.4)
Installed from:    Slackware Packages
Compiler:          Slackware 9.1 GCC. 
OS:          Linux

I recently upgraded from Slackware 9.0 (KDE 3.1.0) to Slackware 9.1 (KDE 3.1.4), mainly to upgrade KDE as 3.1.0 contained several irritating bugs (I was hoping they'd all be squished).  Unfortunately, there is a new bug in 3.1.4 -- input going to the desktop when the desktop is not in focus.

Detailed reproduction test case will be added when I can pin down the cause better.

So, for example, I'll go to type a search query into Mozilla, and see all my typing mirrored on the desktop.  When I hit enter, all of a sudden a window will pop up because the desktop was still accepting input -- even though it wasn't focused.

I have click raise turned on with focus following the mouse in the wm settings.
Comment 1 Dylan Griffiths 2003-11-21 09:09:04 UTC
It appears that every time I click between two tabs in a konsole window, or open a new console, or close a console, input goes to both console, and the desktop.

It also happens when I've minimized the konsole and switched to something else (like Mozilla).

It's very disturbing :-/
Comment 2 Lubos Lunak 2003-11-21 17:59:02 UTC
Should be already fixed for KDE3.2. You can turn off screensaver as a temporary solution.
Comment 3 Dylan Griffiths 2003-11-23 03:39:58 UTC
I disabled the screensaver.  A few minutes ago, the bug triggered again.  Perhaps it's only harder to trigger when that's off, but it's still there.