Bug 81081

Summary:	tip of the day close window manager button not responding warning dialog
Product:	[Plasma] kwin	Reporter:	Roman Fietze <kde>
Component:	general	Assignee:	KWin default assignee <kwin-bugs-null>
Status:	RESOLVED INTENTIONAL
Severity:	normal
Priority:	NOR
Version:	0.2
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Roman Fietze 2004-05-07 11:40:29 UTC

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

When closing "Tip of the Day" using the WM's close button at the moment that window appears, kdevelop pops up a warning dialog that this window is not responding and gives me the "chance" to exit kdevelop for a few seconds. When I wait for these seconds without clicking anywhere the warning dialog disappears and kdevelop comes up w/o problems.

Comment 1 Roman Fietze 2004-05-07 11:42:40 UTC

Kdevelop Version 3.0.2 and 3.0.3. Sorry, forgot to specify that when opening the bug.

Comment 2 Jens Dagerbo 2004-05-14 19:56:25 UTC

Can't reproduce. Does this really happen every time? What kind of machine is it? (CPU, RAM)

Btw, it's KWin, not KDevelop that shows that dialog. It shouldn't happen in normal circumstances, but can happen if lack of RAM has an app swapped out. This should be true of any dialog in any app, not just KDevelop.

Comment 3 Roman Fietze 2004-05-14 21:41:09 UTC

Hallo,

On Fri, May 14, 2004 at 05:56:26PM -0000, Jens Dagerbo wrote:

> Can't reproduce. Does this really happen every time? What kind of
> machine is it? (CPU, RAM)

Reproduced it on the following machine:

- relatively new HP 2.8GHz PC with 1GB RAM
- SuSE 9.0 out of the box
- Kernel 2.4.26 with backported GBit Ethernet driver
- KDE 3.2.2 from SuSE RPM's including kdevelop 3.0.3
- X Server on the console

> Btw, it's KWin, not KDevelop that shows that dialog. It shouldn't
> happen in normal circumstances, but can happen if lack of RAM has an
> app swapped out. This should be true of any dialog in any app, not
> just KDevelop.

Only saw that with kdevelop 3.0.3 (and I think with 3.0.2 as well), no
other KDE or non KDE app, even on a very loaded box. Repeatable 100%
using the display mode with seperate X11 windows for every display
plus the kontrol window. Maybe I can create a snapshot of that
situation and add it to the bug if it's worth the bandwidth and disk
space and if it's required or requested.

Roman

Comment 4 Lubos Lunak 2004-07-02 13:34:54 UTC

You can increase the timeout value in kwinrc, group Windows, key KillPingTimeout, value is in ms, 0 for disabling. Other than that, there's nothing that can be done - the app is not responding, so it's not responding. KWin has no crystal ball to find out it's just way too busy.