Bug 234631 - KFilePlacesModel/Solid crashes when external drive has suddenly been disconnected
Summary: KFilePlacesModel/Solid crashes when external drive has suddenly been disconne...
Status: RESOLVED UNMAINTAINED
Alias: None
Product: solid
Classification: Unmaintained
Component: libsolid-hal (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Alberto Villa
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-04-17 17:53 UTC by Stefan Majewsky
Modified: 2015-04-26 22:41 UTC (History)
0 users

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 Stefan Majewsky 2010-04-17 17:53:24 UTC
Application: kate (3.4.2)
KDE Platform Version: 4.4.2 (KDE 4.4.2) "release 239"
Qt Version: 4.6.2
Operating System: Linux 2.6.31.12-0.2-desktop i686
Distribution: "openSUSE 11.2 (i586)"

-- Information about the crash:
I ran into this crash when I tried to launch Kate. The backtrace shows that the crash is inside Solid's volume handling. It might be caused by the fact that I had unplugged my (LUKS-encrypted) external HDD while having suspended the system. The output of `mount` suggests that the device is still mounted:

/dev/mapper/externaldrive on /externaldrive type ext3 (rw)

The crash can be reproduced every time.

 -- Backtrace:
Application: Kate (kate), signal: Segmentation fault
[KCrash Handler]
#6  Solid::GenericInterface::property (this=0x0, key=...) at /usr/src/debug/kdelibs-4.4.2/solid/solid/genericinterface.cpp:47
#7  0xb5286fd8 in Solid::Backends::Hal::Volume::isIgnored (this=0x8300610) at /usr/src/debug/kdelibs-4.4.2/solid/solid/backends/hal/halvolume.cpp:61
#8  0xb523faa0 in Solid::StorageVolume::isIgnored (this=0x8c59008) at /usr/src/debug/kdelibs-4.4.2/solid/solid/storagevolume.cpp:45
#9  0xb523fd50 in Solid::StorageVolume::qt_metacall (this=0x8c59008, _c=ReadProperty, _id=0, _a=0xbfdd7ba0) at /usr/src/debug/kdelibs-4.4.2/build/solid/solid/storagevolume.moc:94
#10 0xb62c114d in QMetaObject::metacall (object=0x8c59008, cl=101, idx=1, argv=0xbfdd7ba0) at kernel/qmetaobject.cpp:237
#11 0xb62c3e0d in QMetaProperty::read (this=0xbfdd7c04, object=0x8c59008) at kernel/qmetaobject.cpp:2174
#12 0xb5244668 in Solid::Predicate::matches (this=0x828ff68, device=...) at /usr/src/debug/kdelibs-4.4.2/solid/solid/predicate.cpp:208
#13 0xb52444ef in Solid::Predicate::matches (this=0x8299360, device=...) at /usr/src/debug/kdelibs-4.4.2/solid/solid/predicate.cpp:199
#14 0xb5244527 in Solid::Predicate::matches (this=0x8280650, device=...) at /usr/src/debug/kdelibs-4.4.2/solid/solid/predicate.cpp:196
#15 0xb5244527 in Solid::Predicate::matches (this=0x832a568, device=...) at /usr/src/debug/kdelibs-4.4.2/solid/solid/predicate.cpp:196
#16 0xb523af1b in Solid::Device::listFromQuery (predicate=..., parentUdi=...) at /usr/src/debug/kdelibs-4.4.2/solid/solid/devicemanager.cpp:144
#17 0xb3043917 in KFilePlacesModel::Private::_k_initDeviceList (this=0x832a558) at /usr/src/debug/kdelibs-4.4.2/kfile/kfileplacesmodel.cpp:303
#18 0xb3043d5f in KFilePlacesModel::qt_metacall (this=0x8305e18, _c=InvokeMetaMethod, _id=26, _a=0xbfdd808c) at /usr/src/debug/kdelibs-4.4.2/build/kfile/kfileplacesmodel.moc:91
#19 0xb62c114d in QMetaObject::metacall (object=0x8305e18, cl=101, idx=26, argv=0xbfdd808c) at kernel/qmetaobject.cpp:237
#20 0xb62cffaa in QMetaObject::activate (sender=0x8333708, m=0xb63d1188, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3293
#21 0xb62d7c95 in QSingleShotTimer::timeout (this=0x8333708) at .moc/release-shared/qtimer.moc:82
#22 0xb62d7dcc in QSingleShotTimer::timerEvent (this=0x8333708) at kernel/qtimer.cpp:308
#23 0xb62ccab4 in QObject::event (this=0x8333708, e=0xbfdd7a94) at kernel/qobject.cpp:1212
#24 0xb6c9b3fc in QApplicationPrivate::notify_helper (this=0x806c0a8, receiver=0x8333708, e=0xbfdd85e4) at kernel/qapplication.cpp:4300
#25 0xb6ca2248 in QApplication::notify (this=0xbfdd8984, receiver=0x8333708, e=0xbfdd85e4) at kernel/qapplication.cpp:4183
#26 0xb65c7c01 in KApplication::notify (this=0xbfdd8984, receiver=0x8333708, event=0xbfdd85e4) at /usr/src/debug/kdelibs-4.4.2/kdeui/kernel/kapplication.cpp:302
#27 0xb62bbdde in QCoreApplication::notifyInternal (this=0xbfdd8984, receiver=0x8333708, event=0xbfdd85e4) at kernel/qcoreapplication.cpp:704
#28 0xb62ebffe in sendEvent (event=<value optimized out>, receiver=<value optimized out>) at kernel/qcoreapplication.h:215
#29 QTimerInfoList::activateTimers (event=<value optimized out>, receiver=<value optimized out>) at kernel/qeventdispatcher_unix.cpp:617
#30 0xb62e8c62 in timerSourceDispatch (source=0x8072090) at kernel/qeventdispatcher_glib.cpp:184
#31 0xb5fb04c2 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#32 0xb5fb3d98 in ?? () from /usr/lib/libglib-2.0.so.0
#33 0xb5fb3ebe in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#34 0xb62e8931 in QEventDispatcherGlib::processEvents (this=0x8051ef8, flags=...) at kernel/qeventdispatcher_glib.cpp:412
#35 0xb6d5be0a in QGuiEventDispatcherGlib::processEvents (this=0x8051ef8, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#36 0xb62ba44d in QEventLoop::processEvents (this=0xbfdd8894, flags=) at kernel/qeventloop.cpp:149
#37 0xb62ba899 in QEventLoop::exec (this=0xbfdd8894, flags=...) at kernel/qeventloop.cpp:201
#38 0xb62bea10 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:981
#39 0xb6c9b4a4 in QApplication::exec () at kernel/qapplication.cpp:3579
#40 0xb7769ac5 in kdemain () from /usr/lib/libkdeinit4_kate.so
#41 0x080485fb in _start ()

Reported using DrKonqi
Comment 1 Stefan Majewsky 2010-04-17 17:55:36 UTC
Yes, this is the reason. `umount /media/externaldrive` solves the problem.
Comment 2 Stefan Majewsky 2010-09-06 15:55:52 UTC
Still reproducible in KDE 4.5.1.
Comment 3 Jonathan Riddell 2015-03-11 19:11:07 UTC
This bug is reported on libsolid which is the kdelibs4 version of the solid library.  It is now in maintenance mode.  If you think it should still be fixed in the KDE Frameworks 5 version of solid please move it to or report a bug on frameworks-solid.
Comment 4 Stefan Majewsky 2015-04-26 22:41:47 UTC
I shall close this now, since I cannot reproduce this right now.