Bug 170452

Summary:	Crashes on CUPS configuration page
Product:	[Applications] konqueror	Reporter:	Michael Meier <mick22>
Component:	khtml	Assignee:	Plasma Bugs List <plasma-bugs>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	aseigo, lorenxo86
Priority:	NOR
Version:	SVN
Target Milestone:	---
Platform:	Gentoo Packages
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	Screenshot Screenshot (2) Konqueror crash log

Description Michael Meier 2008-09-05 13:47:49 UTC

Version:            (using KDE 4.1.1)
OS:                Linux
Installed from:    Gentoo Packages

There is a reproducible bug in recent plasma (KDE 4.1.1).

When I launch "Druckerverwaltung" (in English versions probably something like "Printer management"), KDE is for some reason automatically launching A LOT of konqueror instances. 

I doubt that konqueror is actually started. It seems, that the icons are generated but the konqueror processes are not actually there.

Therefore, the taskbar is getting flooded with task icons. After some seconds, the icons get so small to become unrecognisable.  After a while, the icons start overflowing and slowly to the right, covering the systray, the clock, and even my second screen.

I'll attach two screenshots that show the situation after about 3-5 seconds and after about 30-45 seconds.

After about 1-2 minuates, a window appears saying "The process for the http://localhost" protocol died unexpectedly and the taskbar is reset to normal.

Comment 1 Michael Meier 2008-09-05 13:49:06 UTC

Created attachment 27251 [details]
Screenshot

Comment 2 Michael Meier 2008-09-05 13:49:26 UTC

Created attachment 27252 [details]
Screenshot (2)

Comment 3 Aaron J. Seigo 2008-12-05 03:47:25 UTC

can you test 4.2 beta 1 (or later?) for this problem?

Comment 4 Michael Meier 2008-12-05 22:01:58 UTC

I have been using weekly KDE snapshots for a couple of months now. Never saw this bug again. I have not been able to reproduce it today with 4.1.81.

If cupsd is stopped and I launch "Manage printing", an error message pops up and tells me that a connection to localhost cannot be made. That's fine.

If cupsd is running, however, konqueror crashes! That's probably a completely different bug. See the attached crash handler log.

Comment 5 Michael Meier 2008-12-05 22:02:35 UTC

Created attachment 29073 [details]
Konqueror crash log

Comment 6 Aaron J. Seigo 2008-12-05 22:21:02 UTC

yes, that's a completely different report. i'll send this one over the khtml team.

also, if you could, in future please put the backtrace right into the comments, that way they are searchable using bugzilla's search form =)

#5  0x00007fef90af63c5 in raise () from /lib64/libc.so.6
#6  0x00007fef90af773e in abort () from /lib64/libc.so.6
#7  0x00007fef9315e815 in qt_message_output () from /usr/lib64/qt4/libQtCore.so.4
#8  0x00007fef9315e947 in qFatal () from /usr/lib64/qt4/libQtCore.so.4
#9  0x00007fef8847eb8b in ?? () from /usr/kde/4.2/lib64/libkhtml.so.5
#10 0x00007fef8847f0e0 in ?? () from /usr/kde/4.2/lib64/libkhtml.so.5
#11 0x00007fef88490c68 in ?? () from /usr/kde/4.2/lib64/libkhtml.so.5
#12 0x00007fef883407f3 in ?? () from /usr/kde/4.2/lib64/libkhtml.so.5
#13 0x00007fef882ee6f7 in KHTMLPart::begin () from /usr/kde/4.2/lib64/libkhtml.so.5
#14 0x00007fef882e5483 in KHTMLPart::slotData () from /usr/kde/4.2/lib64/libkhtml.so.5
#15 0x00007fef882fe043 in KHTMLPart::qt_metacall () from /usr/kde/4.2/lib64/libkhtml.so.5
#16 0x00007fef93259007 in QMetaObject::activate () from /usr/lib64/qt4/libQtCore.so.4
#17 0x00007fef94a63714 in KIO::TransferJob::data () from /usr/kde/4.2/lib64/libkio.so.5
#18 0x00007fef94a685c8 in KIO::TransferJob::qt_metacall () from /usr/kde/4.2/lib64/libkio.so.5
#19 0x00007fef93259007 in QMetaObject::activate () from /usr/lib64/qt4/libQtCore.so.4
#20 0x00007fef94b10ba2 in KIO::SlaveInterface::data () from /usr/kde/4.2/lib64/libkio.so.5
#21 0x00007fef94b12ddc in KIO::SlaveInterface::dispatch () from /usr/kde/4.2/lib64/libkio.so.5
#22 0x00007fef94b10e91 in KIO::SlaveInterface::dispatch () from /usr/kde/4.2/lib64/libkio.so.5
#23 0x00007fef94b03b2e in KIO::Slave::gotInput () from /usr/kde/4.2/lib64/libkio.so.5
#24 0x00007fef94b03e2a in KIO::Slave::qt_metacall () from /usr/kde/4.2/lib64/libkio.so.5
#25 0x00007fef93259007 in QMetaObject::activate () from /usr/lib64/qt4/libQtCore.so.4
#26 0x00007fef94a3c2a7 in ?? () from /usr/kde/4.2/lib64/libkio.so.5
#27 0x00007fef94a3c332 in KIO::Connection::qt_metacall () from /usr/kde/4.2/lib64/libkio.so.5
#28 0x00007fef93254792 in QObject::event () from /usr/lib64/qt4/libQtCore.so.4
#29 0x00007fef9258755e in QApplicationPrivate::notify_helper () from /usr/lib64/qt4/libQtGui.so.4
#30 0x00007fef9258c09e in QApplication::notify () from /usr/lib64/qt4/libQtGui.so.4
#31 0x00007fef9405383b in KApplication::notify () from /usr/kde/4.2/lib64/libkdeui.so.5
#32 0x00007fef93244fe8 in QCoreApplication::notifyInternal () from /usr/lib64/qt4/libQtCore.so.4
#33 0x00007fef93245e4d in QCoreApplicationPrivate::sendPostedEvents () from /usr/lib64/qt4/libQtCore.so.4
#34 0x00007fef9260c62d in ?? () from /usr/lib64/qt4/libQtGui.so.4
#35 0x00007fef9324436d in QEventLoop::processEvents () from /usr/lib64/qt4/libQtCore.so.4
#36 0x00007fef932444c8 in QEventLoop::exec () from /usr/lib64/qt4/libQtCore.so.4
#37 0x00007fef932461ee in QCoreApplication::exec () from /usr/lib64/qt4/libQtCore.so.4
#38 0x00007fef959c7048 in kdemain () from /usr/kde/4.2/lib64/libkdeinit4_konqueror.so
#39 0x00007fef90ae3b74 in __libc_start_main () from /lib64/libc.so.6
#40 0x00000000004008d9 in _start ()

Comment 7 Lorenzo Masini 2009-04-03 09:41:43 UTC

*** Bug 188705 has been marked as a duplicate of this bug. ***