Bug 234620

Summary:	konqueror infinite loop when opening a link from skype
Product:	[Applications] konqueror	Reporter:	Germano Massullo <germano.massullo>
Component:	general	Assignee:	Konqueror Developers <konq-bugs>
Status:	RESOLVED DUPLICATE
Severity:	crash	CC:	iform
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Fedora RPMs
OS:	Unspecified
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	Screen of showing konqueror bug + output in konsole

Description Germano Massullo 2010-04-17 15:20:19 UTC

Version:            (using KDE 4.4.1)
Installed from:    Fedora RPMs

I reported this bug like a crash severity because the final result is that you must reboot the machine to stop that.

It is not the first time I get this problem.
I clicked on a link from a conversation in Skype. Immediately konqueror started even if it is not the default browser. Even if konqueror tried to start, it did not open, but in the task bar I say A LOT of konquerors that started opening. This continued also when the task bar was full. To stop it I had to reboot the computer through the console.

Here an image of the taskbar
http://img227.imageshack.us/img227/8588/bugo.png

Comment 1 Germano Massullo 2010-04-17 15:21:11 UTC

I person in this forum had a similar problem
http://forums.opensuse.org/get-help-here/applications/413550-infinite-loop-starting-konqueror.html

Comment 2 iform 2010-06-03 16:45:12 UTC

Created attachment 47638 [details]
Screen of showing konqueror bug + output in konsole

Comment 3 iform 2010-06-03 16:48:59 UTC

Comment on attachment 47638 [details]
Screen of showing konqueror bug + output in konsole

I experience this same bug when opening a SAGE notebook.  The only way out is to kill X.

Also, this bug affects my kde settings so that the next time I am in kde, some shortcuts in the kde menu cease to function (most notably, log out, shutdown, restart).  The solution to that is to DELETE .kde directory.

KDE 4.4.3 on ArchLinux

Comment 4 iform 2010-06-04 03:20:54 UTC

https://bugs.kde.org/show_bug.cgi?id=240677

This is the bug that caused it all for me.

Comment 5 Dawit Alemayehu 2011-11-19 19:31:37 UTC


*** This bug has been marked as a duplicate of bug 240677 ***