Bug 245872

Summary: PC-BSD updating Firefox caused KDE crash
Product: [Unmaintained] kdelibs Reporter: William Read <william_d_read>
Component: kdedAssignee: David Faure <faure>
Status: RESOLVED DUPLICATE    
Severity: crash    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: FreeBSD Ports   
OS: FreeBSD   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description William Read 2010-07-27 09:44:45 UTC
Application: kded4 ($Id: kded.cpp 1031637 2009-10-05 16:58:19Z lunakl $)
KDE Platform Version: 4.4.5 (KDE 4.4.5)
Qt Version: 4.6.3
Operating System: FreeBSD 8.1-RELEASE i386
Distribution (Platform): FreeBSD Ports

-- Information about the crash:
PC-BSD Software and Updates application was updating Firefox to 3.6.7 after update finished
kde crashed.

 -- Backtrace:
Application: KDE Daemon (kdeinit4), signal: Segmentation fault: 11
[KCrash Handler]
#6  0x29101cef in QResourceFileEngineHandler::create () from /usr/local/lib/qt4/libQtCore.so.4
#7  0x290d00cf in QAbstractFileEngine::create () from /usr/local/lib/qt4/libQtCore.so.4
#8  0x290e59f4 in QFileInfoPrivate::initFileEngine () from /usr/local/lib/qt4/libQtCore.so.4
#9  0x290e62fc in QFileInfo::QFileInfo () from /usr/local/lib/qt4/libQtCore.so.4
#10 0x286a25ec in KDirWatch::addDir () from /usr/local/kde4/lib/libkio.so.7
#11 0x286a29e7 in KDirWatch::addDir () from /usr/local/kde4/lib/libkio.so.7
#12 0x2915a1a3 in QMetaObject::metacall () from /usr/local/lib/qt4/libQtCore.so.4
#13 0x29167336 in QMetaObject::activate () from /usr/local/lib/qt4/libQtCore.so.4
#14 0x29126c93 in QFileSystemWatcher::directoryChanged () from /usr/local/lib/qt4/libQtCore.so.4
#15 0x29127b3d in QFileSystemWatcherPrivate::_q_directoryChanged () from /usr/local/lib/qt4/libQtCore.so.4
#16 0x29127c61 in QFileSystemWatcher::qt_metacall () from /usr/local/lib/qt4/libQtCore.so.4
#17 0x2915a1a3 in QMetaObject::metacall () from /usr/local/lib/qt4/libQtCore.so.4
#18 0x29164036 in QMetaCallEvent::placeMetaCall () from /usr/local/lib/qt4/libQtCore.so.4
#19 0x29165579 in QObject::event () from /usr/local/lib/qt4/libQtCore.so.4
#20 0x294aa97c in QApplicationPrivate::notify_helper () from /usr/local/lib/qt4/libQtGui.so.4
#21 0x294b1b64 in QApplication::notify () from /usr/local/lib/qt4/libQtGui.so.4
#22 0x28c7b483 in KApplication::notify () from /usr/local/kde4/lib/libkdeui.so.7
#23 0x29153efb in QCoreApplication::notifyInternal () from /usr/local/lib/qt4/libQtCore.so.4
#24 0x29155406 in QCoreApplicationPrivate::sendPostedEvents () from /usr/local/lib/qt4/libQtCore.so.4
#25 0x2915562d in QCoreApplication::sendPostedEvents () from /usr/local/lib/qt4/libQtCore.so.4
#26 0x291816af in postEventSourceDispatch () from /usr/local/lib/qt4/libQtCore.so.4
#27 0x2a2f5817 in g_main_context_dispatch () from /usr/local/lib/libglib-2.0.so.0
#28 0x2a2f905e in g_main_context_check () from /usr/local/lib/libglib-2.0.so.0
#29 0x2a2f9685 in g_main_context_iteration () from /usr/local/lib/libglib-2.0.so.0
#30 0x291819fb in QEventDispatcherGlib::processEvents () from /usr/local/lib/qt4/libQtCore.so.4
#31 0x29564e55 in QGuiEventDispatcherGlib::processEvents () from /usr/local/lib/qt4/libQtGui.so.4
#32 0x29152f03 in QEventLoop::processEvents () from /usr/local/lib/qt4/libQtCore.so.4
#33 0x2915327a in QEventLoop::exec () from /usr/local/lib/qt4/libQtCore.so.4
#34 0x291556f6 in QCoreApplication::exec () from /usr/local/lib/qt4/libQtCore.so.4
#35 0x294aa157 in QApplication::exec () from /usr/local/lib/qt4/libQtGui.so.4
#36 0x2a6d0ca6 in kdemain () from /usr/local/kde4/lib/libkdeinit4_kded4.so
#37 0x0804dff1 in ?? ()
#38 0x08050357 in ?? ()
#39 0x0804b3a7 in ?? ()
#40 0x00000002 in ?? ()
#41 0xbfbfe890 in ?? ()
#42 0xbfbfe89c in ?? ()
#43 0xbfbfe870 in ?? ()
#44 0xbfbfe88c in ?? ()
#45 0x00000000 in ?? ()
#46 0xbfbfe888 in ?? ()
#47 0x0804b315 in ?? ()
#48 0x28057f40 in dlclose () from /libexec/ld-elf.so.1

This bug may be a duplicate of or related to bug 245643.

Possible duplicates by query: bug 245692, bug 245643.

Reported using DrKonqi
Comment 1 Christoph Feck 2010-07-27 10:59:35 UTC

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