Bug 88771 - xclock never gets focus, causes problems with "No border" setting
Summary: xclock never gets focus, causes problems with "No border" setting
Status: RESOLVED DUPLICATE of bug 101019
Alias: None
Product: kwin
Classification: Plasma
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Compiled Sources Linux
: LO normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-09-03 14:57 UTC by Christopher Neufeld
Modified: 2005-03-17 16:42 UTC (History)
0 users

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christopher Neufeld 2004-09-03 14:57:55 UTC
Version:            (using KDE KDE 3.3.0)
Installed from:    Compiled From Sources
Compiler:          gcc-3.2.2 Compiler compiled from sources.

I've noticed this in previous versions of KDE, an xclock window never gets focus.  I can put the mouse in the window, click the border, nothing causes the border to change colours to indicate that it has focus.  This is not a big deal, the control buttons still work, such as the window-kill button rightmost in the title bar.

When the new "No border" advanced setting is used, the xclock window loses its border, but still can't grab focus, so putting the mouse pointer into the xclock window and pressing ALT-F3 does not bring up the menu which would allow one to restore the border, or close the window.  The process has to be killed by hand from the shell.

I have no special window settings for xclock, and no unusual resources:
XClock*font:            7x13bold
XClock*analog:          False
XClock*update:          1
Comment 1 Lubos Lunak 2004-09-22 16:37:15 UTC
xclock asks not to get focus, so there's nothing strange about it not receiving the focus. Not being able to use Alt+F3 is a problem though.
Comment 2 Lubos Lunak 2005-03-17 16:42:46 UTC

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