Bug 132688

Summary:	google docs doesn't work
Product:	[Applications] konqueror	Reporter:	Milan Avramovic <chomee>
Component:	khtml ecma	Assignee:	Konqueror Developers <konq-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	normal	CC:	robin, rpogomes, zahl
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	backtrace

Description Milan Avramovic 2006-08-20 15:35:34 UTC

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.

Comment 1 Virgil Nisly 2006-08-21 03:55:57 UTC

Created attachment 17437 [details]
backtrace

Comment 2 Virgil Nisly 2006-08-21 03:57:34 UTC

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.

Comment 3 Rui G. 2008-07-13 00:52:30 UTC

Can you still reproduce it in recent versions?

Comment 4 A. Spehr 2008-08-25 13:10:14 UTC

I guess google bought them? It redirects to docs.google.com, which doesn't even support Safari... Cloaking doesn't help either.

Comment 5 Rui G. 2008-08-26 10:13:45 UTC

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.

Comment 6 Robin Appelman 2010-02-18 22:59:14 UTC

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

Comment 7 Justin Zobel 2021-03-21 00:25:07 UTC

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.

Comment 8 Christoph Cullmann 2024-05-06 20:51:24 UTC

Dear user,

KHTML (and KJS) was a long time more or less unmaintained and got removed in KF6.

Please migrate to use a QWebEngine based HTML component.

We will do no further fixes or improvements to the KF5 branches of these components beside important security fixes.

For security issues, please see:

https://kde.org/info/security/

Sorry that we did not fix this issue during the life-time of KHTML.

Greetings
Christoph Cullmann