Bug 216959 - crashing of dolphin application
Summary: crashing of dolphin application
Status: RESOLVED DUPLICATE of bug 208921
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 16.12.2
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: Peter Penz
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-12-01 17:23 UTC by gdr.root
Modified: 2009-12-01 17:53 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 gdr.root 2009-12-01 17:23:24 UTC
Application that crashed: dolphin
Version of the application: 1.3
KDE Version: 4.3.3 (KDE 4.3.3)
Qt Version: 4.5.3
Operating System: Linux 2.6.27.38-170.2.113.fc10.i686 i686
Distribution: "Fedora release 10 (Cambridge)"

What I was doing when the application crashed:
Dolphin crash randomly.
For several days work without any problems, and randomly crash withoutn any apparently cause 
Can occour at the startup of the applications or when is in use after browse a directory

 -- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
[KCrash Handler]
#6  QMutex::lock (this=0x8758b0c) at thread/qmutex.cpp:152
#7  0x00c216ad in mutex_lock (mutex=0x8758b0c) at qdbusthread.cpp:69
#8  0x0093f53f in _dbus_mutex_lock (mutex=0x8758b0c) at dbus-threads.c:150
#9  0x009270c5 in _dbus_connection_lock (connection=0x6f006e) at dbus-connection.c:355
#10 0x00939e35 in _dbus_pending_call_get_connection_and_lock (pending=0x9de0b50) at dbus-pending-call.c:309
#11 0x0092c085 in reply_handler_timeout (data=0x9de0b50) at dbus-connection.c:3116
#12 0x0093f0e2 in dbus_timeout_handle (timeout=0x9d62240) at dbus-timeout.c:473
#13 0x00bf7fa7 in q_dbus_timeout_handle () at ./qdbus_symbols_p.h:172
#14 QDBusConnectionPrivate::timerEvent (this=0x9a88828, e=0xbf8393ac) at qdbusintegrator.cpp:1023
#15 0x0441370f in QObject::event (this=0x9a88828, e=0xbf8393ac) at kernel/qobject.cpp:1074
#16 0x05be89ec in QApplicationPrivate::notify_helper (this=0x9a99fd0, receiver=0x9a88828, e=0xbf8393ac) at kernel/qapplication.cpp:4065
#17 0x05bf0cfe in QApplication::notify (this=0xbf839644, receiver=0x9a88828, e=0xbf8393ac) at kernel/qapplication.cpp:3605
#18 0x0332ffad in KApplication::notify (this=0xbf839644, receiver=0x9a88828, event=0xbf8393ac) at /usr/src/debug/kdelibs-4.3.3/kdeui/kernel/kapplication.cpp:302
#19 0x0440301b in QCoreApplication::notifyInternal (this=0xbf839644, receiver=0x9a88828, event=0xbf8393ac) at kernel/qcoreapplication.cpp:610
#20 0x04432351 in QCoreApplication::sendEvent () at kernel/qcoreapplication.h:213
#21 QTimerInfoList::activateTimers (this=0x9a90bec) at kernel/qeventdispatcher_unix.cpp:580
#22 0x0442e950 in timerSourceDispatch (source=0x9a90bb8) at kernel/qeventdispatcher_glib.cpp:165
#23 0x005a9258 in g_main_dispatch () at gmain.c:2144
#24 IA__g_main_context_dispatch (context=0x9a97670) at gmain.c:2697
#25 0x005ac903 in g_main_context_iterate (context=0x9a97670, block=1, dispatch=1, self=0x9a9cc58) at gmain.c:2778
#26 0x005acac1 in IA__g_main_context_iteration (context=0x9a97670, may_block=1) at gmain.c:2841
#27 0x0442e8a8 in QEventDispatcherGlib::processEvents (this=0x9a72840, flags={i = 36}) at kernel/qeventdispatcher_glib.cpp:327
#28 0x05c88cf5 in QGuiEventDispatcherGlib::processEvents (this=0x9a72840, flags={i = 36}) at kernel/qguieventdispatcher_glib.cpp:202
#29 0x0440164a in QEventLoop::processEvents (this=0xbf8395d0, flags={i = 36}) at kernel/qeventloop.cpp:149
#30 0x04401a92 in QEventLoop::exec (this=0xbf8395d0, flags={i = 0}) at kernel/qeventloop.cpp:201
#31 0x04403f39 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#32 0x05be8867 in QApplication::exec () at kernel/qapplication.cpp:3525
#33 0x0807862f in main (argc=5, argv=0xbf8397f4) at /usr/src/debug/kdebase-4.3.3/apps/dolphin/src/main.cpp:94

Reported using DrKonqi
Comment 1 Frank Reininghaus 2009-12-01 17:53:27 UTC
Thanks for the bug report! Crashes of this kind (crash in DBus code, apparently related to Nepomuk) have been reported already.

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