Bug 209774 - Keyboard input focus is lost after closing a window
Summary: Keyboard input focus is lost after closing a window
Status: RESOLVED WORKSFORME
Alias: None
Product: kde
Classification: I don't know
Component: general (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-10-07 17:33 UTC by Hulahup
Modified: 2011-09-28 08:55 UTC (History)
2 users (show)

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 Hulahup 2009-10-07 17:33:05 UTC
Version:            (using KDE 4.3.1)
OS:                Linux
Installed from:    Fedora RPMs

When I close a window, the input focus is not restored to the window that kwin decorates as the new active window. 

Scenario:
- open a konsole
- from konsole, start kate
- close kate: kwin decorates konsole as active - as expected - but keystrokes result in nothing.

However, ALT+F2 ALT+TAB ... still work. Indeed, switching back and forth to another application restores the input focus. If no other application is open, opening a new kate with ALT+F2, then switching back to konsole with ALT+TAB also restores the keyboard input.

The problem is not specifically related to konsole or kate: I observe the same behavior with whatever KDE application I've tried till now, namely konqueror and kmail. If I open konqueror, type in something in the URL input, then close konqueror, the keyboard is lost. However, if I open konqueror and just close it (without typing in an input field), there is no problem, and the focus is correctly restored.

This might be related to the X server, but it's definitely specific to KDE (or maybe QT). I could not find any other application where closing does the same thing.


My install comes from a fedora 11 x86_64, with updates:
  kdebase-4.3.1-2.fc11.x86_64
  xorg-x11-server-common-1.6.4-0.1.fc11.x86_64

I've used X drivers NV and VESA, both with the same result.

Yours for further investigation.

Bruno
Comment 1 Jekyll Wu 2011-09-23 03:29:56 UTC
I can't reproduce this. Is this still a problem for the reporter?