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.30-ARCH i686 What I was doing when the application crashed: Just I was browsing in the web and konqueror crahed. I think this happened becouse the flash plugin was being used (flash spam), I guess... Thanks -- Backtrace: Application: Konqueror (kdeinit4), signal: Segmentation fault [Current thread is 1 (Thread 0xb5de4700 (LWP 12026))] Thread 2 (Thread 0xae8feb70 (LWP 12965)): #0 0xb7fb4424 in __kernel_vsyscall () #1 0xb7d56ec2 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/libpthread.so.0 #2 0xb7db4fef in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQtCore.so.4 #3 0xb7daa83e in ?? () from /usr/lib/libQtCore.so.4 #4 0xb7db4052 in ?? () from /usr/lib/libQtCore.so.4 #5 0xb7d5265c in start_thread () from /lib/libpthread.so.0 #6 0xb67ec1fe in clone () from /lib/libc.so.6 Thread 1 (Thread 0xb5de4700 (LWP 12026)): [KCrash Handler] #6 0xb7e56d29 in QUrl::QUrl(QUrl const&) () from /usr/lib/libQtCore.so.4 #7 0xb7ba09a9 in KUrl::KUrl(KUrl const&) () from /usr/lib/libkdecore.so.5 #8 0xb77af639 in KDirListerCache::findByUrl(KDirLister const*, KUrl const&) const () from /usr/lib/libkio.so.5 #9 0xb77af98e in KDirLister::findByUrl(KUrl const&) const () from /usr/lib/libkio.so.5 #10 0xb1f91252 in KHTMLPart::htmlDocument() const () from /usr/lib/libkhtml.so.5 #11 0xb24fca1b in SearchBarPlugin::HTMLDocLoaded() () from /usr/lib/kde4/searchbarplugin.so #12 0xb25027a3 in SearchBarPlugin::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/kde4/searchbarplugin.so #13 0xb7eb7fdc in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQtCore.so.4 #14 0xb7eb8c12 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4 #15 0xb7aa93a7 in KParts::ReadOnlyPart::completed() () from /usr/lib/libkparts.so.4 #16 0xb1f7c435 in KHTMLView::timerEvent(QTimerEvent*) () from /usr/lib/libkhtml.so.5 #17 0xb7eb218f in QObject::event(QEvent*) () from /usr/lib/libQtCore.so.4 #18 0xb6acbac6 in QWidget::event(QEvent*) () from /usr/lib/libQtGui.so.4 #19 0xb6e72253 in QFrame::event(QEvent*) () from /usr/lib/libQtGui.so.4 #20 0xb6f104ca in QAbstractScrollArea::event(QEvent*) () from /usr/lib/libQtGui.so.4 #21 0xb6f154bd in QScrollArea::event(QEvent*) () from /usr/lib/libQtGui.so.4 #22 0xb1f7e6dc in KHTMLView::event(QEvent*) () from /usr/lib/libkhtml.so.5 #23 0xb6a77924 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #24 0xb6a7ef5a in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #25 0xb74ba0da in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5 #26 0xb7ea25bb in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4 #27 0xb7ecfefe in ?? () from /usr/lib/libQtCore.so.4 #28 0xb7ecd007 in ?? () from /usr/lib/libQtCore.so.4 #29 0xb6681d98 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #30 0xb66853e0 in g_main_context_iterate () from /usr/lib/libglib-2.0.so.0 #31 0xb6685513 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #32 0xb7eccd25 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #33 0xb6b15705 in ?? () from /usr/lib/libQtGui.so.4 #34 0xb7ea0ba9 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #35 0xb7ea0ffa in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #36 0xb7ea346f in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4 #37 0xb6a777a7 in QApplication::exec() () from /usr/lib/libQtGui.so.4 #38 0xb4859dff in kdemain (argc=2, argv=0x873a568) at /home/phil/kdemod/core/kdebase/src/kdebase-4.3.2/apps/konqueror/src/konqmain.cpp:271 #39 0x0804de42 in _start () Reported using DrKonqi
Thanks for the bug report! According to the backtrace, this is a bug that was reported earlier (and possibly related to bug 208397). *** This bug has been marked as a duplicate of bug 208039 ***