Version: (using KDE 4.2.0) OS: Linux Installed from: SuSE RPMs Told YAST (under openSUSE 11.1) to format a 500GB disk connected to eSATA on a SiI3132 controller. Almost immediately, saw SIGABRT from krunner process. Not 100% sure that the crash was caused by the format operation, as that continued, but YAST and format were the only things running on the desktop at the time. BACKTRACE: Application: Run Command Interface (krunner), signal SIGABRT [Current thread is 1 (Thread 0xb52ad700 (LWP 5661))] Thread 1 (Thread 0xb52ad700 (LWP 5661)): [KCrash Handler] #6 0xffffe430 in __kernel_vsyscall () #7 0xb67ea990 in raise () from /lib/libc.so.6 #8 0xb67ec2c8 in abort () from /lib/libc.so.6 #9 0xb560a245 in ?? () from /lib/libdbus-1.so.3 #10 0xb5605c59 in ?? () from /lib/libdbus-1.so.3 #11 0xb55f97fe in dbus_message_new_method_call () from /lib/libdbus-1.so.3 #12 0xb7748bb4 in ?? () from /usr/lib/libQtDBus.so.4 #13 0xb7744a4b in ?? () from /usr/lib/libQtDBus.so.4 #14 0xb7730a81 in QDBusConnection::call(QDBusMessage const&, QDBus::CallMode, int) const () from /usr/lib/libQtDBus.so.4 #15 0xb774da2b in QDBusAbstractInterface::callWithArgumentList(QDBus::CallMode, QString const&, QList<QVariant> const&) () from /usr/lib/libQtDBus.so.4 #16 0xb774f8dd in QDBusAbstractInterface::call(QDBus::CallMode, QString const&, QVariant const&, QVariant const&, QVariant const&, QVariant const&, QVariant const&, QVariant const&, QVariant const&, QVariant const&) () from /usr/lib/libQtDBus.so.4 #17 0xb774fb3c in QDBusAbstractInterface::call(QString const&, QVariant const&, QVariant const&, QVariant const&, QVariant const&, QVariant const&, QVariant const&, QVariant const&, QVariant const&) () from /usr/lib/libQtDBus.so.4 #18 0xb5aedf36 in ?? () from /usr/lib/libsolid.so.4 #19 0xb5afb372 in ?? () from /usr/lib/libsolid.so.4 #20 0xb5abcd96 in Solid::StorageVolume::isIgnored() const () from /usr/lib/libsolid.so.4 #21 0xb5abd4a3 in Solid::StorageVolume::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libsolid.so.4 #22 0xb763e4b4 in QMetaProperty::read(QObject const*) const () from /usr/lib/libQtCore.so.4 #23 0xb7649021 in QObject::property(char const*) const () from /usr/lib/libQtCore.so.4 #24 0xb5ac1609 in Solid::Predicate::matches(Solid::Device const&) const () from /usr/lib/libsolid.so.4 #25 0xb5ac152a in Solid::Predicate::matches(Solid::Device const&) const () from /usr/lib/libsolid.so.4 #26 0xb5ac157f in Solid::Predicate::matches(Solid::Device const&) const () from /usr/lib/libsolid.so.4 #27 0xb65123e4 in KFilePlacesModel::Private::_k_deviceAdded(QString const&) () from /usr/lib/libkfile.so.4 #28 0xb65148c0 in KFilePlacesModel::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libkfile.so.4 #29 0xb764b580 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQtCore.so.4 #30 0xb764c302 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4 #31 0xb5ab7723 in Solid::DeviceNotifier::deviceAdded(QString const&) () from /usr/lib/libsolid.so.4 #32 0xb5ab978f in ?? () from /usr/lib/libsolid.so.4 #33 0xb5ab99af in ?? () from /usr/lib/libsolid.so.4 #34 0xb764b580 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQtCore.so.4 #35 0xb764c302 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4 #36 0xb5acb163 in ?? () from /usr/lib/libsolid.so.4 #37 0xb5aefe3e in ?? () from /usr/lib/libsolid.so.4 #38 0xb5aefeda in ?? () from /usr/lib/libsolid.so.4 #39 0xb7740e6f in ?? () from /usr/lib/libQtDBus.so.4 #40 0xb77481f7 in ?? () from /usr/lib/libQtDBus.so.4 #41 0xb7646281 in QObject::event(QEvent*) () from /usr/lib/libQtCore.so.4 #42 0xb6d0f8fc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #43 0xb6d1775e in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #44 0xb7bd7a3d in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5 #45 0xb7636961 in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4 #46 0xb76375d5 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/libQtCore.so.4 #47 0xb76377cd in QCoreApplication::sendPostedEvents(QObject*, int) () from /usr/lib/libQtCore.so.4 #48 0xb766136f in ?? () from /usr/lib/libQtCore.so.4 #49 0xb567f9a8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #50 0xb5683063 in ?? () from /usr/lib/libglib-2.0.so.0 #51 0xb5683221 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #52 0xb7660fb8 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #53 0xb6da87c5 in ?? () from /usr/lib/libQtGui.so.4 #54 0xb763501a in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #55 0xb76351da in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #56 0xb7637895 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4 #57 0xb6d0f777 in QApplication::exec() () from /usr/lib/libQtGui.so.4 #58 0xb80718e6 in kdemain () from /usr/lib/libkdeinit4_krunner.so #59 0x08048792 in _start ()
Not sure if this is the right spot, but this does have lots of solid lines.
Created attachment 32519 [details] stack trace from crash with all symbols loaded I had what seems to be a similar crash - this time in plasma while messing with the partitions on a usb stick - but Solid and QDBus are also referenced in the stack trace (attached). I was using gparted on Fedora 10 to resize a fat32 partition on a usb stick, and add a second fat32 partition in the freed space. During the process the Device Notifier plasmoid popped up a couple of times (it had already popped up to show unmounted partitions on my HD when gparted started and scanned the partition tables, or whatever it does). Early on in the process the panel disappeared and the kcrash handler popped up. Gparted was still resizing the first partition at the time. When I looked at the detail output afterwards it looked like gparted not only resized the partition but also moved the partition boundaries a couple of times and checked the disk 2-3 times (I think it thought that the partition was mis-aligned or not matching the boot backup - could be something to do with U3, which I'd already removed). I suspect that this is why the device notifier kept popping up with device attached notifications. Unfortunately, I didn't think to save the detailed gparted logs. Packages installed: gparted-0.4.3-1.fc10.i386 parted-1.8.8-8.fc10.i386 kdebase-workspace-4.2.1-7.fc10.i386 kdebase-runtime-4.2.1-2.fc10.i386 kdebase-4.2.1-2.fc10.i386 hal-0.5.12-14.20081027git.fc10.i386
do you still reproduce with kde 4.4 ?
No reply to Nicolas.
Nicolas, who's your question directed at? I didn't get an email update on this for some reason when you posted. I've not reproduced it, but have stopped using eSATA external disks because I had to move the drive too far from the machine, so switched to the USB interface.
Hello! Sorry to be the bearer of bad news, but this project has been unmaintained for many years so I am closing this bug. Please try again with the latest version and submit a new bug to frameworks-solid if your issue persists. Thank you!