Application that crashed: dolphin Version of the application: 1.2.80 KDE Version: 4.2.90 (KDE 4.2.90 (KDE 4.3 Beta2)) Qt Version: 4.5.1 Operating System: Linux 2.6.29.5-186.fc11.i586 i686 Distribution: "Fedora release 11 (Leonidas)" -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault [KCrash Handler] #6 QWidget::height (this=<value optimized out>) at /usr/include/QtGui/qwidget.h:985 #7 KTreeView::KTreeViewPrivate::startScrolling (this=<value optimized out>) at /usr/src/debug/kdebase-4.2.90/apps/dolphin/src/panels/folders/ktreeview.cpp:61 #8 0x08083156 in KTreeView::KTreeViewPrivate::qt_metacall (this=0x916d540, _c=QMetaObject::InvokeMetaMethod, _id=4, _a=0xbfdd0c4c) at /usr/src/debug/kdebase-4.2.90/i586-redhat-linux-gnu/apps/dolphin/src/ktreeview_p.moc:69 #9 0x024f7fc3 in QMetaObject::activate (sender=0x916d230, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3120 #10 0x024f8c12 in QMetaObject::activate (sender=0x916d230, m=0x25d3344, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3194 #11 0x02532287 in QTimer::timeout (this=0x916d230) at .moc/release-shared/moc_qtimer.cpp:128 #12 0x024fd6de in QTimer::timerEvent (this=0x916d230, e=0xbfdd10e0) at kernel/qtimer.cpp:261 #13 0x024f202f in QObject::event (this=0x916d230, e=0xbfdd10e0) at kernel/qobject.cpp:1082 #14 0x02970444 in QApplicationPrivate::notify_helper (this=0x91647d0, receiver=0x916d230, e=0xbfdd10e0) at kernel/qapplication.cpp:4057 #15 0x02977abe in QApplication::notify (this=0xbfdd144c, receiver=0x916d230, e=0xbfdd10e0) at kernel/qapplication.cpp:4022 #16 0x03f4f3da in KApplication::notify (this=0xbfdd144c, receiver=0x916d230, event=0xbfdd10e0) at /usr/src/debug/kdelibs-4.2.90/kdeui/kernel/kapplication.cpp:302 #17 0x024e1fdb in QCoreApplication::notifyInternal (this=0xbfdd144c, receiver=0x916d230, event=0xbfdd10e0) at kernel/qcoreapplication.cpp:610 #18 0x0250f35e in QCoreApplication::sendEvent (event=<value optimized out>, receiver=<value optimized out>) at kernel/qcoreapplication.h:213 #19 QTimerInfoList::activateTimers (event=<value optimized out>, receiver=<value optimized out>) at kernel/qeventdispatcher_unix.cpp:572 #20 0x0250cd90 in timerSourceDispatch (source=0x9166ab0) at kernel/qeventdispatcher_glib.cpp:164 #21 0x00d44d78 in g_main_dispatch (context=<value optimized out>) at gmain.c:1814 #22 IA__g_main_context_dispatch (context=<value optimized out>) at gmain.c:2367 #23 0x00d48310 in g_main_context_iterate (context=0x9166890, block=<value optimized out>, dispatch=1, self=0x9164018) at gmain.c:2445 #24 0x00d48443 in IA__g_main_context_iteration (context=0x9166890, may_block=1) at gmain.c:2508 #25 0x0250ccdc in QEventDispatcherGlib::processEvents (this=0x913cb60, flags={i = 36}) at kernel/qeventdispatcher_glib.cpp:324 #26 0x02a0f305 in QGuiEventDispatcherGlib::processEvents (this=0x913cb60, flags={i = 36}) at kernel/qguieventdispatcher_glib.cpp:202 #27 0x024e05c9 in QEventLoop::processEvents (this=0xbfdd13a4, flags={i = 36}) at kernel/qeventloop.cpp:149 #28 0x024e0a12 in QEventLoop::exec (this=0xbfdd13a4, flags={i = 0}) at kernel/qeventloop.cpp:200 #29 0x024e2d6f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888 #30 0x029702c7 in QApplication::exec () at kernel/qapplication.cpp:3526 #31 0x0807804f in main (argc=3, argv=0xbfdd1624) at /usr/src/debug/kdebase-4.2.90/apps/dolphin/src/main.cpp:94 Reported using DrKonqi
This reminds me bug 167044 which was fixed long time ago. Does this happen every time? I'm assuming you have the Folders panel enabled. Did you tried to browse an specific folder when running Dolphin, or did you just run it without any special parameter? Thanks
This happened once during kde startup, it was starting a couple of dolphin windows as part of my session. I have the places and folders panels enabled. Sorry I can't provide any more info as it was a one-off. Will let you know if I get it again.
*** Bug 200326 has been marked as a duplicate of this bug. ***
- Did you experienced this again with an updated KDE? Thanks
I cannot reproduce this issue in trunk. I've set it to fixed, please reopen it if the issue still is reproducible in your system. Thanks!
*** This bug has been marked as a duplicate of bug 199219 ***