Version: (using KDE KDE 3.5.4) Installed from: Unlisted Binary Package Compiler: gcc 4.0.1 OS: Linux When trying to open new document on writely.com, konqueror reports a problem with process for kio_http suddenly dying. I noticed several dozen kio_http processes started - it's probably debatable why the would crash in the first place. Even killing all of them didn't clear the bug condition. The real problem is that this is displayed in a modal dialog box which you just can't get rid of. Neither konqueror nor the troublesome page can be closed, nor the transfers can be stopped, requiring user to manually kill konqueror. Please consider displaying all errors inline - on the actual page where the error occurred; possibly stopping all pending transfers qithout reporting further errors.
Created attachment 17437 [details] backtrace
Kills konqueror when I go to writely.com, login, and create new document. It says "working" in a dialog (in the window), and starts aprox 350 kio_http processes before it crashes.
Can you still reproduce it in recent versions?
I guess google bought them? It redirects to docs.google.com, which doesn't even support Safari... Cloaking doesn't help either.
I don't know why I didn't even try writely.com the time I replied, but you're right, it redirects to docs.google.com . However in Konqueror 3.5.9 and 4.1, if i change Identification to Firefox 2.0.0.8 (or 1.5.0.4 in the case of 3.5.9) the pages load as they should, but a lot of features don't work and it can be downright unusable.
I know this bug report is a bit old, but konqueror still crashes when trying to use google docs (using version 4.4.0). I don't know how to create a backtrace because no crash message appears, when running it from a console, I only get irrelevant messages from QPainter before a Segmentation Fault QPainter::setViewport: Painter not active QPainter::setViewTransformEnabled: Painter not active QPainter::setMatrixEnabled: Painter not active QPainter::setClipRegion: Painter not active QPainter::hasClipping: Painter not active QPainter::hasClipping: Painter not active QPainter::hasClipping: Painter not active QPainter::hasClipping: Painter not active Segmentation fault
Thank you for the bug report. As this report hasn't seen any changes in 10 years or more, we ask if you can please confirm that the issue still persists. If this bug is no longer persisting or relevant please change the status to resolved.