Bug 242725 - dolphin crashes during connecting a usb memory device
Summary: dolphin crashes during connecting a usb memory device
Status: RESOLVED DUPLICATE of bug 226725
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-06-24 22:00 UTC by Karsten Roch
Modified: 2010-06-25 00:10 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Karsten Roch 2010-06-24 22:00:11 UTC
Application: dolphin (1.4.9)
KDE Platform Version: 4.4.85 (KDE 4.4.85 (KDE 4.5 Beta2))
Qt Version: 4.7.0
Operating System: Linux 2.6.35-0.2.rc3.git0.fc14.i686 i686
Distribution: "Fedora release 14 (Rawhide)"

-- Information about the crash:
- What I was doing when the application crashed:

I opened dolphin, connected by usb my digital camera (4GB SD card) and switched on my camera. Crash happened immediatelity.

The crash can be reproduced some of the time.

-- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
[KCrash Handler]
#7  _dbus_connection_lock (connection=0x2f6960) at dbus-connection.c:355
#8  0x008e1026 in _dbus_pending_call_get_connection_and_lock (pending=0xb4006510) at dbus-pending-call.c:307
#9  0x008d1956 in reply_handler_timeout (data=0xb4006510) at dbus-connection.c:3163
#10 0x008e5f33 in dbus_timeout_handle (timeout=0xb4004310) at dbus-timeout.c:473
#11 0x0315dfe0 in q_dbus_timeout_handle (this=0x9a2cf08, e=0xbff8e580) at qdbus_symbols_p.h:174
#12 QDBusConnectionPrivate::timerEvent (this=0x9a2cf08, e=0xbff8e580) at qdbusintegrator.cpp:1040
#13 0x035c2fc4 in QObject::event (this=0x9a2cf08, e=0xbff8e580) at kernel/qobject.cpp:1208
#14 0x0611f85c in QApplicationPrivate::notify_helper (this=0x9a3a750, receiver=0x9a2cf08, e=0xbff8e580) at kernel/qapplication.cpp:4345
#15 0x061261d6 in QApplication::notify (this=0xbff8e8f0, receiver=0x9a2cf08, e=0xbff8e580) at kernel/qapplication.cpp:3749
#16 0x0484a8cb in KApplication::notify (this=0xbff8e8f0, receiver=0x9a2cf08, event=0xbff8e580) at /usr/src/debug/kdelibs-4.4.85/kdeui/kernel/kapplication.cpp:302
#17 0x035b0c73 in QCoreApplication::notifyInternal (this=0xbff8e8f0, receiver=0x9a2cf08, event=0xbff8e580) at kernel/qcoreapplication.cpp:726
#18 0x035ddd0e in sendEvent (this=0x9a3bb3c) at kernel/qcoreapplication.h:215
#19 QTimerInfoList::activateTimers (this=0x9a3bb3c) at kernel/qeventdispatcher_unix.cpp:602
#20 0x035db478 in timerSourceDispatch (source=0x9a3bb70) at kernel/qeventdispatcher_glib.cpp:184
#21 idleTimerSourceDispatch (source=0x9a3bb70) at kernel/qeventdispatcher_glib.cpp:231
#22 0x00959da5 in g_main_dispatch (context=0x9a396c0) at gmain.c:2044
#23 IA__g_main_context_dispatch (context=0x9a396c0) at gmain.c:2597
#24 0x0095dbe8 in g_main_context_iterate (context=0x300a80, block=1, dispatch=1, self=0x9a35cd8) at gmain.c:2675
#25 0x0095ddc9 in IA__g_main_context_iteration (context=0x9a396c0, may_block=1) at gmain.c:2738
#26 0x035db126 in QEventDispatcherGlib::processEvents (this=0x9a16c18, flags=...) at kernel/qeventdispatcher_glib.cpp:412
#27 0x061cfab6 in QGuiEventDispatcherGlib::processEvents (this=0x9a16c18, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#28 0x035af80a in QEventLoop::processEvents (this=0xbff8e844, flags=...) at kernel/qeventloop.cpp:149
#29 0x035afb4a in QEventLoop::exec (this=0xbff8e844, flags=...) at kernel/qeventloop.cpp:201
#30 0x035b4177 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1003
#31 0x0611e838 in QApplication::exec () at kernel/qapplication.cpp:3624
#32 0x041f8353 in kdemain () from /usr/lib/libkdeinit4_dolphin.so
#33 0x0804872c in _start ()

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

Possible duplicates by query: bug 242574, bug 241480, bug 240458, bug 238659, bug 238532.

Reported using DrKonqi
Comment 1 Frank Reininghaus 2010-06-25 00:10:51 UTC
Thanks for the bug report! This crash is known already - it's due to a bug in the D-Bus library.

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