Bug 170288 - dolphin crashed on first use
Summary: dolphin crashed on first use
Status: RESOLVED DUPLICATE of bug 163171
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 16.12.2
Platform: FreeBSD Ports FreeBSD
: NOR crash
Target Milestone: ---
Assignee: Peter Penz
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-09-03 02:23 UTC by Tom Dailey
Modified: 2008-11-17 21:56 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tom Dailey 2008-09-03 02:23:17 UTC
Version:            (using KDE 4.1.0)
OS:                FreeBSD
Installed from:    FreeBSD Ports

Application: Dolphin (dolphin), signal SIGSEGV
[New Thread 0x8101100 (LWP 100130)]
[Switching to Thread 0x8101100 (LWP 100130)]
[KCrash handler]
#6  0x28d2f322 in QUrl::host () from /usr/local/lib/qt4/libQtCore.so.4
#7  0x282f3f34 in searchIdleList (idleSlaves=@0x8145704, url=@0x8523b50, 
    protocol=@0xbfbfdfcc, exact=@0xbfbfe06b)
    at /usr/ports/x11/kdelibs4/work/kdelibs-4.1.0/kio/kio/scheduler.cpp:608
#8  0x282f4a33 in KIO::SchedulerPrivate::findIdleSlave (this=0x81456b0, 
    job=0x851fae0, exact=@0xbfbfe06b)
    at /usr/ports/x11/kdelibs4/work/kdelibs-4.1.0/kio/kio/scheduler.cpp:682
#9  0x282f729e in KIO::SchedulerPrivate::startJobDirect (this=0x81456b0)
    at /usr/ports/x11/kdelibs4/work/kdelibs-4.1.0/kio/kio/scheduler.cpp:587
#10 0x282f73bb in KIO::SchedulerPrivate::startStep (this=0x81456b0)
    at /usr/ports/x11/kdelibs4/work/kdelibs-4.1.0/kio/kio/scheduler.cpp:432
#11 0x282f7569 in KIO::Scheduler::qt_metacall (this=0x8269cf0, 
    _c=QMetaObject::InvokeMetaMethod, _id=6, _a=0xbfbfe158)
    at scheduler.moc:101
#12 0x28d779ec in QMetaObject::activate ()
   from /usr/local/lib/qt4/libQtCore.so.4
#13 0x28d77e22 in QMetaObject::activate ()
   from /usr/local/lib/qt4/libQtCore.so.4
#14 0x28db0df7 in QTimer::timeout () from /usr/local/lib/qt4/libQtCore.so.4
#15 0x28d804ee in QTimer::timerEvent () from /usr/local/lib/qt4/libQtCore.so.4
#16 0x28d76894 in QObject::event () from /usr/local/lib/qt4/libQtCore.so.4
#17 0x2945bafc in QApplicationPrivate::notify_helper ()
   from /usr/local/lib/qt4/libQtGui.so.4
#18 0x294624be in QApplication::notify ()
   from /usr/local/lib/qt4/libQtGui.so.4
#19 0x28619ab3 in KApplication::notify (this=0xbfbfe7ac, receiver=0x81456b4, 
    event=0xbfbfe54c)
    at /usr/ports/x11/kdelibs4/work/kdelibs-4.1.0/kdeui/kernel/kapplication.cpp:311
#20 0x28d67459 in QCoreApplication::notifyInternal ()
   from /usr/local/lib/qt4/libQtCore.so.4
#21 0x28d90188 in QTimerInfoList::activateTimers ()
   from /usr/local/lib/qt4/libQtCore.so.4
#22 0x28d8de30 in timerSourceDispatch ()
   from /usr/local/lib/qt4/libQtCore.so.4
#23 0x29ea2276 in g_main_context_dispatch ()
   from /usr/local/lib/libglib-2.0.so.0
#24 0x29ea5612 in g_main_context_check () from /usr/local/lib/libglib-2.0.so.0
#25 0x29ea5b95 in g_main_context_iteration ()
   from /usr/local/lib/libglib-2.0.so.0
#26 0x28d8e4be in QEventDispatcherGlib::processEvents ()
   from /usr/local/lib/qt4/libQtCore.so.4
#27 0x294e0475 in QGuiEventDispatcherGlib::processEvents ()
   from /usr/local/lib/qt4/libQtGui.so.4
#28 0x28d665d3 in QEventLoop::processEvents ()
   from /usr/local/lib/qt4/libQtCore.so.4
#29 0x28d66761 in QEventLoop::exec () from /usr/local/lib/qt4/libQtCore.so.4
#30 0x28d6894a in QCoreApplication::exec ()
   from /usr/local/lib/qt4/libQtCore.so.4
#31 0x2945b097 in QApplication::exec () from /usr/local/lib/qt4/libQtGui.so.4
#32 0x0808550b in main (argc=6, argv=0xbfbfe900)
    at /usr/ports/x11/kdebase4/work/kdebase-4.1.0/apps/dolphin/src/main.cpp:94
Comment 1 Frank Reininghaus 2008-09-03 22:09:02 UTC
Thanks for the bug report. The backtrace looks very similar to the ones in bug 169105, bug 170115, it might be a duplicate.
Comment 2 Frank Reininghaus 2008-11-17 21:56:35 UTC
I think this is indeed a duplicate of the issue that was reported a couple of times. The developers worked on it, but it's not entirely sure if it is fixed. If you get this crash again in KDE 4.1.3 or later, please add a comment to bug 163171. Thanks!

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