Bug 244586 - Dolphin crashed when restoring session
Summary: Dolphin crashed when restoring session
Status: RESOLVED DUPLICATE of bug 241733
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 16.12.2
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: Peter Penz
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-07-14 11:04 UTC by Philippe
Modified: 2010-07-14 14:51 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 Philippe 2010-07-14 11:04:37 UTC
Application: dolphin (1.4)
KDE Platform Version: 4.4.4 (KDE 4.4.4)
Qt Version: 4.6.3
Operating System: Linux 2.6.33.6-147.fc13.i686 i686
Distribution: "Fedora release 13 (Goddard)"

-- Information about the crash:
Just after log in, KDE was restoring the session (just Amarock playing, yakuake and dolphin).
Dolphin contained 2 tabs, each one splitted to display 2 directories.

 -- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
[KCrash Handler]
#6  link_before (list=0x6c7271, link=0x3c) at dbus-list.c:118
#7  _dbus_list_prepend_link (list=0x6c7271, link=0x3c) at dbus-list.c:312
#8  0x00c4361a in _dbus_list_append_link (list=0x6c7271, link=0x3c) at dbus-list.c:294
#9  0x00c291bd in _dbus_connection_queue_synthesized_message_link (connection=0x6c7255, link=0x3c) at dbus-connection.c:513
#10 0x00c399d1 in _dbus_pending_call_queue_timeout_error_unlocked (pending=0xb4704e68, connection=0x6c7255) at dbus-pending-call.c:215
#11 0x00c29964 in reply_handler_timeout (data=0xb4704e68) at dbus-connection.c:3165
#12 0x00c3df33 in dbus_timeout_handle (timeout=0xb4705ed0) at dbus-timeout.c:473
#13 0x00124c60 in q_dbus_timeout_handle (this=0x9020ef8, e=0xbfaedea0) at qdbus_symbols_p.h:172
#14 QDBusConnectionPrivate::timerEvent (this=0x9020ef8, e=0xbfaedea0) at qdbusintegrator.cpp:1035
#15 0x00e03bc4 in QObject::event (this=0x9020ef8, e=0xbfaedea0) at kernel/qobject.cpp:1212
#16 0x0102dbdc in QApplicationPrivate::notify_helper (this=0x902aaf8, receiver=0x9020ef8, e=0xbfaedea0) at kernel/qapplication.cpp:4306
#17 0x01034636 in QApplication::notify (this=0xbfaee204, receiver=0x9020ef8, e=0xbfaedea0) at kernel/qapplication.cpp:3710
#18 0x04712e2b in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#19 0x00df3e13 in QCoreApplication::notifyInternal (this=0xbfaee204, receiver=0x9020ef8, event=0xbfaedea0) at kernel/qcoreapplication.cpp:726
#20 0x00e1eede in sendEvent (this=0x903207c) at kernel/qcoreapplication.h:215
#21 QTimerInfoList::activateTimers (this=0x903207c) at kernel/qeventdispatcher_unix.cpp:603
#22 0x00e1c468 in timerSourceDispatch (source=0x90320b0) at kernel/qeventdispatcher_glib.cpp:184
#23 idleTimerSourceDispatch (source=0x90320b0) at kernel/qeventdispatcher_glib.cpp:231
#24 0x02222525 in g_main_dispatch (context=0x902d910) at gmain.c:1960
#25 IA__g_main_context_dispatch (context=0x902d910) at gmain.c:2513
#26 0x02226268 in g_main_context_iterate (context=0x18b490, block=1, dispatch=1, self=0x9030f00) at gmain.c:2591
#27 0x02226449 in IA__g_main_context_iteration (context=0x902d910, may_block=1) at gmain.c:2654
#28 0x00e1c126 in QEventDispatcherGlib::processEvents (this=0x900b330, flags=...) at kernel/qeventdispatcher_glib.cpp:412
#29 0x010dc796 in QGuiEventDispatcherGlib::processEvents (this=0x900b330, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#30 0x00df24ea in QEventLoop::processEvents (this=0xbfaee164, flags=...) at kernel/qeventloop.cpp:149
#31 0x00df282a in QEventLoop::exec (this=0xbfaee164, flags=...) at kernel/qeventloop.cpp:201
#32 0x00df64e7 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1003
#33 0x0102dc88 in QApplication::exec () at kernel/qapplication.cpp:3585
#34 0x080784e7 in _start ()

Possible duplicates by query: bug 242040, bug 241733.

Reported using DrKonqi
Comment 1 Frank Reininghaus 2010-07-14 14:51:33 UTC
Thanks for the bug report! This looks like an issue which is known already.

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