Bug 129410 - faulty "window not responding"-message
Summary: faulty "window not responding"-message
Status: CLOSED REMIND
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
: 113145 126160 (view as bug list)
Depends on:
Blocks:
 
Reported: 2006-06-19 10:42 UTC by Marijn Schouten
Modified: 2007-07-17 11:00 UTC (History)
2 users (show)

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 Marijn Schouten 2006-06-19 10:42:43 UTC
Version:           3.5.3 (using KDE KDE 3.5.3)
Installed from:    Gentoo Packages
Compiler:          gcc-4.1.1 
OS:                Linux

I can reproducibly get a "window not responding"-message, while there is actually nothing wrong with konqueror.

Reproduce:
start Konqueror or use an already open window. Open a new tab. Click close window and get warning about closing multiple tabs. Click cancel. Click close tab (either tab). After a second or so a window not responding message pops up. Click keep running and observe a perfectly fine running window.
Comment 1 Marijn Schouten 2006-06-19 16:13:49 UTC
I just got the same behaviour with firefox.
Comment 2 Philip Rodrigues 2006-06-19 23:55:28 UTC
I can't reproduce this with SVN r548321 on FreeBSD
Comment 3 Thiago Macieira 2006-06-27 01:14:11 UTC
I can't reproduce with SVN r548000 on Linux.

Luboš, any ideas?
Comment 4 Lubos Lunak 2006-06-28 15:04:36 UTC
Cannot reproduce (and the delay should be 5 seconds by default). There have been already such problems caused by wrong 3rd party patches.
Comment 5 Marijn Schouten 2006-06-28 19:15:22 UTC
where can I check what the delay is on my system?
Comment 6 Lubos Lunak 2006-06-29 13:51:19 UTC
~/.kde/share/config/kwinrc, group [Windows], key KillPingTimeout= , value is in msec. By default 5000.
Comment 7 Marijn Schouten 2006-06-29 14:51:48 UTC
I don't have that entry under [Windows].
Comment 8 Marijn Schouten 2006-07-20 17:38:04 UTC
Actually I now (and possibly before as well) get it when I have multiple tabs open and I click on the close this window cross. The warning about closing multiple tabs pops up and if I wait a few seconds more the not responding message. Apparently kwin doesn't know about this warning and is assuming that the window is quitting regardless. When it doesn't do that, because it is waiting for user input kwin assumes it is not responding. I find it strange that you cannot reproduce this. Perhaps you didn't wait 5 seconds?
Comment 9 Lubos Lunak 2006-07-31 13:41:46 UTC
The feature works exactly as it should here with stock KDE. I suggest reporting the problem to wherever you got the packages from to check that it's not caused by some patch.
Comment 10 Lubos Lunak 2006-08-01 10:12:02 UTC
*** Bug 126160 has been marked as a duplicate of this bug. ***
Comment 11 Lubos Lunak 2006-08-10 16:11:17 UTC
*** Bug 113145 has been marked as a duplicate of this bug. ***
Comment 12 Marijn Schouten 2006-08-19 11:44:52 UTC
I no longer get the wrong behaviour. I'm on kde 3.5.4 now. Don't know if that is what fixed it.
Comment 13 Jonathan Ryshpan 2007-02-07 21:52:20 UTC
I get exactly this behavior running Firefox under FC6 KDE 3.5.5-0.4.  
To reproduce:
(1) Start Firefox
(2) Set: Edit->Preferences->Tabs->"Warn me when closing multiple tabs"
(3) Open at least two tabs in the current window
(4) Click the Close Window decoration (the X at the upper right corner 
    of the window.)
(5) Wait six seconds.

The error warning sounds and a "window not responding"-message appears.
Comment 14 Marijn Schouten 2007-02-08 11:48:16 UTC
I remember some regressions, but I cannot reproduce at the moment with kde 3.5.6 with konqueror or firefox-2.0.0.1
Comment 15 ivan-kde 2007-02-10 08:10:43 UTC
same problem observed with Debian KDE 3.5.5 (4:3.5.5a.dfsg.1-5) and iceweasel (firefox codebase) 2.0.0.1 (2.0.0.1+dfsg-2).  Steps in #13 reproduce this bug precisely.

Is this bug present in upstream 3.5.5 or was it introduced independently by the Debian and Fedora distribution-specific changes?
Comment 16 Thomas Zander 2007-02-10 09:24:45 UTC
reopened by popular request.

on kubuntu-edgy with kde 355 I can also reproduce 100%.
Comment 17 Raymond Lewis Rebbeck 2007-02-18 18:28:00 UTC
I can reproduce this in Konqueror every time on both 64-bit and 32-bit gentoo systems running KDE 3.5.5
Comment 18 Lubos Lunak 2007-06-01 15:47:03 UTC
Can somebody reproduce this problem with KDE3.5.7?
Comment 19 Lubos Lunak 2007-07-17 10:54:33 UTC
No response, assuming fixed.
Comment 20 Thomas Zander 2007-07-17 11:00:24 UTC
I used to be able to 100% reproduce; not anymore. So I'm with you; its fixed. Thanks!