Bug 227952 - Dolphin crash when unplug the usb key which is open by dolphin
Summary: Dolphin crash when unplug the usb key which is open by dolphin
Status: RESOLVED DUPLICATE of bug 222204
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 16.12.2
Platform: Arch Linux Linux
: NOR crash
Target Milestone: ---
Assignee: Peter Penz
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-02-21 17:02 UTC by benpro
Modified: 2010-03-01 12:46 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 benpro 2010-02-21 17:02:41 UTC
Application: dolphin (1.4)
KDE Platform Version: 4.4.00 (KDE 4.4.0)
Qt Version: 4.6.2
Operating System: Linux 2.6.32-ARCH x86_64
Distribution (Platform): Archlinux Packages

-- Information about the crash:
I have keep my windows dolphin of my usb key then click unplug to eject the usb jey and dolphin crashed.

 -- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
[KCrash Handler]
#5  0x00007fbab629ec5d in QTextCodec::fromUnicode (this=0x18badf0, str=<value optimized out>) at codecs/qtextcodec.cpp:1195
#6  0x00007fbab61bf5a1 in QString::toLocal8Bit (this=0x2192f80) at tools/qstring.cpp:3511
#7  0x00007fbab61f8e09 in locale_encode (f=...) at io/qfile.cpp:66
#8  0x00007fbab61f8c8a in QFile::encodeName (fileName=...) at io/qfile.cpp:477
#9  0x00007fbab741c2c9 in ?? () from /usr/lib/libkio.so.5
#10 0x00007fbab7423fb4 in ?? () from /usr/lib/libkio.so.5
#11 0x00007fbab628295f in QMetaObject::activate (sender=0x222c1c0, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x1) at kernel/qobject.cpp:3293
#12 0x00007fbab628a17f in QSingleShotTimer::timerEvent (this=0x222c1c0) at kernel/qtimer.cpp:308
#13 0x00007fbab627f5b3 in QObject::event (this=0x222c1c0, e=0x7fffefd09b00) at kernel/qobject.cpp:1212
#14 0x00007fbab562c95c in QApplicationPrivate::notify_helper (this=0x19009a0, receiver=0x222c1c0, e=0x7fffefd09b00) at kernel/qapplication.cpp:4300
#15 0x00007fbab5632f4b in QApplication::notify (this=0x7fffefd09e50, receiver=0x222c1c0, e=0x7fffefd09b00) at kernel/qapplication.cpp:4183
#16 0x00007fbab6ed0d36 in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#17 0x00007fbab626fbfc in QCoreApplication::notifyInternal (this=0x7fffefd09e50, receiver=0x222c1c0, event=0x7fffefd09b00) at kernel/qcoreapplication.cpp:704
#18 0x00007fbab629c8a2 in QCoreApplication::sendEvent (this=0x1910940) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#19 QTimerInfoList::activateTimers (this=0x1910940) at kernel/qeventdispatcher_unix.cpp:603
#20 0x00007fbab62993c8 in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:184
#21 idleTimerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:231
#22 0x00007fbab0d2d26e in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#23 0x00007fbab0d30c28 in g_main_context_iterate () from /usr/lib/libglib-2.0.so.0
#24 0x00007fbab0d30d50 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#25 0x00007fbab6299093 in QEventDispatcherGlib::processEvents (this=0x18b5c40, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:412
#26 0x00007fbab56db30e in QGuiEventDispatcherGlib::processEvents (this=0x7fffefd09270, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#27 0x00007fbab626e522 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#28 0x00007fbab626e8fc in QEventLoop::exec (this=0x7fffefd09da0, flags=) at kernel/qeventloop.cpp:201
#29 0x00007fbab627263b in QCoreApplication::exec () at kernel/qcoreapplication.cpp:981
#30 0x000000000043acb5 in _start ()

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

Possible duplicates by query: bug 224766, bug 222479, bug 222204, bug 192328.

Reported using DrKonqi
Comment 1 Dario Andres 2010-03-01 12:46:43 UTC
This is fixed for KDE SC 4.4.1: bug 222204. Regards

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