Version: (using KDE KDE 3.5.7) Installed from: Unlisted Binary Package Compiler: GCC 4.1.2 OS: Linux When clicking on headlines at digg.com, mouse cursor becomes unresponsive and won't accept mouse click events (still moves though). CPU usage stays normal. This only happens when logged in and "Opening Links to External Pages" is set to "Always Open in a New Window" in digg profile settings. A quick look at digg html souce reveals: a href="url" target="_blank" onclick="gotoLink('2074557');" so maybe it has something to do with that javascript onclick event. Only way to make the mouse cursor functional again is to kill the konqueror process. Keyboard shorcuts like ctrl+w or alt+f4 do not work.
Created attachment 20690 [details] Screenshot Screenshot of bug in action. Also, I'm using Acrh Linux KDE packages.
Could it be that this is somehow related to bug 145894? I know different things happen, both have in common it's KDE 3.5.7 with the new feature for showing a new window icon near the mouse cursor.
I remember this happening occasionally on 3.5.6 too (didn't have the motivation to hunt it down at that time) so I think this has no relation to the new window indicator in 3.5.7.
Can't confirm. But it sounds like synchronous XHR junk again
OK just tried changing "Opening Links to External Pages" to "Never Open in a New Window" in digg profile settings and still showing same behaviour. So most likely the onclick="gotoLink('XXXXXXX'); function is causing the freeze.
Created attachment 20711 [details] Backtrace Summing up steps to reproduce: 1. Have javascript enabled 2. Go to digg.com and log in 3. Click on any of the headlines and slightly move mouse cursor to some direction at the same time. Will not reproduce if: -Javascript turned off -Not logged in (digg) -Link opened with middle mouse button (new tab) -Mouse cursor held steady while clicking Backtrace attached.
Thanks for noting that one needs an account. That helps... And yep, it looks like it's synchronous XMLHttpRequest. Hopefully it's not as bad as what cisco.com used to have, that one was bordering on impossible to fix :(
Oh, one question for you, reporter: do scrollbars on the window work or not?
And, please forgive me, I am going to record some technical advice from David which may be useful if my intuition is right here: "no, you'd need to combine an enter loop and a qtimer"
Created attachment 20733 [details] Cursor Scrollbars are not working, as the mouse cursor doesn't accept any click events. Also, mouse wheel is not functional. The cursor changes to something like in the attached screenshot. Trying to click on kicker or the desktop has no effect either.
Thanks, so it does get stuck in an inner event loop w/o timeout... Unfortunately, I still can't reproduce it, so it's hard to say why that happens :(
Similar problem here with Konqueror 3.5.7, but I can use the cursor again when I press Escape. Happens on comment ratings (digg up/down) and links that don't open in a new window too.
This bug is still there and has been a very difficult one to live with. I've been reading Digg for about five hours straight now and I've had the freeze four or five times already. Nope, pressing Escape doesn't do anything, neither does pretty much anything I could think of, so therefore I've always pressed Alt+F2 and took konsole up for a quick "sudo kill"-session. Anyways, it seems like the bug has something to do with javascript and images. This is just a bit more than a gut feeling, but apparently the browser goes nuts, when trying to open the page in a new tab, when there's a certain type of image around. My cursor turns into showing the generic file icon for some reason, when this happens, by the way.
Ah, sorry, I should've read all of the comments before writing that. Anyways, I'm using Arch Linux ("Don't Panic") with the latest patches from testing included (just had an update couple of hours ago), for your knowledge, that is.
Same problem here on a gentoo box and a redhat box. Esc is useful so far.
*** Bug 157188 has been marked as a duplicate of this bug. ***
Is it still happening to you in any recent version of KDE? We won't fix KDE 3.5 anymore, so please test with KDE 4.0.5 or KDE 4.1 when it's out.
It works fine on current truk.