Bug 210282

Summary:	konqueror crashed when I made clic on a folder
Product:	[Applications] konqueror	Reporter:	Gatoso <gatoso>
Component:	general	Assignee:	Konqueror Developers <konq-bugs>
Status:	RESOLVED DUPLICATE
Severity:	crash	CC:	frank78ac
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Unlisted Binaries
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Gatoso 2009-10-12 09:34:23 UTC

Application that crashed: konqueror
Version of the application: 4.3.2 (KDE 4.3.2)
KDE Version: 4.3.2 (KDE 4.3.2)
Qt Version: 4.5.3
Operating System: Linux 2.6.31-ARCH i686

What I was doing when the application crashed:
I had three open tabs, one in the photobucket.com web site , another one in the comunidadconce.cl web site and the another one in my home folder. I made clic on a directory conten in my home folder and konqueror crashed.

I can't reproduce this issue, sorry

Thanks a lot

 -- Backtrace:
Application: Konqueror (kdeinit4), signal: Segmentation fault
[KCrash Handler]
#6  0xb76c6d2d in QUrl::QUrl(QUrl const&) () from /usr/lib/libQtCore.so.4
#7  0xb74109a9 in KUrl::KUrl(KUrl const&) () from /usr/lib/libkdecore.so.5
#8  0xb701f639 in KDirListerCache::findByUrl(KDirLister const*, KUrl const&) const () from /usr/lib/libkio.so.5
#9  0xb701f98e in KDirLister::findByUrl(KUrl const&) const () from /usr/lib/libkio.so.5
#10 0xb1800252 in KHTMLPart::htmlDocument() const () from /usr/lib/libkhtml.so.5
#11 0xb1d6ba1b in SearchBarPlugin::HTMLDocLoaded() () from /usr/lib/kde4/searchbarplugin.so
#12 0xb1d717a3 in SearchBarPlugin::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/kde4/searchbarplugin.so
#13 0xb7727fdc in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQtCore.so.4
#14 0xb7728c12 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4
#15 0xb73193a7 in KParts::ReadOnlyPart::completed() () from /usr/lib/libkparts.so.4
#16 0xb17eb435 in KHTMLView::timerEvent(QTimerEvent*) () from /usr/lib/libkhtml.so.5
#17 0xb772218f in QObject::event(QEvent*) () from /usr/lib/libQtCore.so.4
#18 0xb633bac6 in QWidget::event(QEvent*) () from /usr/lib/libQtGui.so.4
#19 0xb66e2253 in QFrame::event(QEvent*) () from /usr/lib/libQtGui.so.4
#20 0xb67804ca in QAbstractScrollArea::event(QEvent*) () from /usr/lib/libQtGui.so.4
#21 0xb67854bd in QScrollArea::event(QEvent*) () from /usr/lib/libQtGui.so.4
#22 0xb17ed6dc in KHTMLView::event(QEvent*) () from /usr/lib/libkhtml.so.5
#23 0xb62e7924 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#24 0xb62eef5a in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#25 0xb6d2a0da in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#26 0xb77125bb in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4
#27 0xb773fefe in ?? () from /usr/lib/libQtCore.so.4
#28 0xb773d007 in ?? () from /usr/lib/libQtCore.so.4
#29 0xb5ef1d98 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#30 0xb5ef53e0 in g_main_context_iterate () from /usr/lib/libglib-2.0.so.0
#31 0xb5ef5513 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#32 0xb773cd25 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#33 0xb6385705 in ?? () from /usr/lib/libQtGui.so.4
#34 0xb7710ba9 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#35 0xb7710ffa in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#36 0xb771346f in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#37 0xb62e77a7 in QApplication::exec() () from /usr/lib/libQtGui.so.4
#38 0xb40c9dff in kdemain (argc=2, argv=0x8c844c8) at /home/phil/kdemod/core/kdebase/src/kdebase-4.3.2/apps/konqueror/src/konqmain.cpp:271
#39 0x0804de42 in _start ()

Reported using DrKonqi

Comment 1 Frank Reininghaus 2009-10-12 10:21:11 UTC

Thanks for the report!

If you get crashes with the same backtrace over and over again, there's no need to file a bug report every time ;-)

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

Comment 2 Gatoso 2009-10-12 17:59:13 UTC

Sorry, I didn't know this was the same bracktrace that the another one.

Comment 3 Frank Reininghaus 2009-10-12 20:15:39 UTC

(In reply to comment #2)
> Sorry, I didn't know this was the same bracktrace that the another one.

No problem at all! If you're unsure, you can always file a new report - marking crash duplicates doesn't take much time for us. I just meant that you can save *yourself* the time you need for reporting some known issue again (but only if you see that the backtrace is the same, of course).