[frameworks-solid] [Bug 345871] Baloo Crash - Solid UDisks2

[Joshua Clayton via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=345871

--- Comment #11 from Joshua Clayton  ---
Situation:
partitioning an SD card from a script using parted.
Interestingly the new partition layout is usually the same as the old partition
layout
I can crash plasma repeatedly with this trick. (thankfully plasma restarts)

Looks like soid tries to create a QVariant for something whose name is still
valid, but
whose file handle has been destroyed.

Application: kded5 (kded5), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f73807f68c0 (LWP 15223))]

Thread 1 (Thread 0x7f73807f68c0 (LWP 15223)):
[KCrash Handler]
#6  0x7f73801ab418 in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:54
#7  0x7f73801ad01a in __GI_abort () at abort.c:89
#8  0x7f737e5c8ff1 in qt_message_fatal (context=..., message=) at global/qlogging.cpp:1578
#9  QMessageLogger::fatal (this=this@entry=0x7ffcd4427940,
msg=msg@entry=0x7f738093cd28 "Cannot construct placeholder type QDBusRawType")
at global/qlogging.cpp:781
#10 0x7f7380919552 in QDBusRawTypeHandler::construct () at
qdbusmetaobject.cpp:133
#11 0x7f737e7fc9c0 in QMetaType::construct (copy=0x0, where=0x7ffcd4427a60,
this=0x7ffcd44279a0) at
../../include/QtCore/../../src/corelib/kernel/qmetatype.h:2141
#12 (anonymous namespace)::customConstruct (d=0x7ffcd4427a60, copy=0x0) at
kernel/qvariant.cpp:1019
#13 0x7f737e7fd8bf in QVariant::QVariant (this=0x7ffcd4427a60,
typeId=, copy=) at kernel/qvariant.cpp:1660
#14 0x7f737e7c9cf2 in QMetaProperty::read (this=this@entry=0x7ffcd4427b00,
object=object@entry=0x29a7c00) at kernel/qmetaobject.cpp:3010
#15 0x7f737e7e9b0f in QObject::property (this=0x29a7c00, name=0x29e2868
"MountPoints") at kernel/qobject.cpp:3893
#16 0x7f73708d4664 in Solid::Backends::UDisks2::DeviceBackend::checkCache
(this=0x29d0ed0, key=...) at
../../../src/solid/devices/backends/udisks2/udisksdevicebackend.cpp:185
#17 0x7f73708d4883 in
Solid::Backends::UDisks2::DeviceBackend::propertyExists (this=0x29d0ed0,
key=...) at
../../../src/solid/devices/backends/udisks2/udisksdevicebackend.cpp:132
#18 0x7f73708cc5be in Solid::Backends::UDisks2::Device::propertyExists
(this=this@entry=0x29cf040, key=...) at
../../../src/solid/devices/backends/udisks2/udisksdevice.cpp:126
#19 0x7f73708ce37f in Solid::Backends::UDisks2::Device::isMounted
(this=0x29cf040) at
../../../src/solid/devices/backends/udisks2/udisksdevice.cpp:818
#20 0x7f73708e7711 in Solid::Backends::UDisks2::StorageAccess::isAccessible
(this=0x297e170) at
../../../src/solid/devices/backends/udisks2/udisksstorageaccess.cpp:75
#21 0x7f73708e7944 in Solid::Backends::UDisks2::StorageAccess::updateCache
(this=0x297e170) at
../../../src/solid/devices/backends/udisks2/udisksstorageaccess.cpp:138
#22 Solid::Backends::UDisks2::StorageAccess::StorageAccess (this=0x297e170,
device=0x29cf040, __in_chrg=, __vtt_parm=) at
../../../src/solid/devices/backends/udisks2/udisksstorageaccess.cpp:36
#23 0x7f73708cc780 in
Solid::Backends::UDisks2::Device::createDeviceInterface (this=0x29cf040,
type=) at
../../../src/solid/devices/backends/udisks2/udisksdevice.cpp:174
#24 0x7f737089668f in Solid::Device::asDeviceInterface (this=0x29db2c0,
type=@0x7ffcd4427e10: Solid::DeviceInterface::StorageAccess) at
../../../src/solid/devices/frontend/device.cpp:154
#25 0x7f73727d7353 in ?? () from
/usr/lib/x86_64-linux-gnu/libKF5KIOFileWidgets.so.5
#26 0x7f73727d9d67 in KFilePlacesModel::Private::loadBookmarkList() () from
/usr/lib/x86_64-linux-gnu/libKF5KIOFileWidgets.so.5
#27 0x7f73727db933 in KFilePlacesModel::Private::_k_reloadBookmarks() ()
from /usr/lib/x86_64-linux-gnu/libKF5KIOFileWidgets.so.5
#28 0x7f73727dd08d in KFilePlacesModel::Private::_k_deviceAdded(QString
const&) () from /usr/lib/x86_64-linux-gnu/libKF5KIOFileWidgets.so.5
#29 0x7f73727dda25 in ?? () from
/usr/lib/x86_64-linux-gnu/libKF5KIOFileWidgets.so.5
#30 0x7f737e7eafca in QMetaObject::activate (sender=0x1129c30,
signalOffset=, local_signal_index=local_signal_index@entry=0,
argv=argv@entry=0x7ffcd4428190) at kernel/qobject.cpp:3713
#31 0x7f737e7eb7d7 in QMetaObject::activate (sender=,
m=m@entry=0x7f7370b23e60 ,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffcd4428190)
at kernel/qobject.cpp:3578
#32 0x7f7370896bb2 in Solid::DeviceNotifier::deviceAdded (this=, _t1=...) at ./moc_devicenotifier.cpp:136
#33 0x7f737e7eafca in QMetaObject::activate (sender=sender@entry=0x112bfb0,
signalOffset=, local_signal_index=local_signal_index@entry=0,
argv=argv@entry=0x7ffcd44282c0) at kernel/qobject.cpp:3713
#34 0x7f737e7eb7d7 in QMetaObject::activate (sender=sender@entry=0x112bfb0,
m=m@entry=0x7f7370b2c540 ,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffcd44282c0)
at kernel/qobject.cpp:3578
#35 0x7f73708f2262 in Solid::Ifaces::DeviceManager::deviceAdded

[kscreenlocker] [Bug 363749] New: kscreenlocker_greet will not accept password and taking 4.9 GiB

[Joshua Clayton via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=363749

Bug ID: 363749
   Summary: kscreenlocker_greet will not accept password and
taking 4.9 GiB
   Product: kscreenlocker
   Version: 5.5.5
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: greeter
  Assignee: plasma-b...@kde.org
  Reporter: stillcompil...@gmail.com
CC: bhus...@gmail.com, mgraess...@kde.org

After a weekend away, kscreenlocker_greet allows me to type my password, but
will not accept the correct password. switching to a console terminal, I notice
the process is taking 41% of the systme memory, which is about 4.92 GiB.

When I kill the kscreenlocker_greet process, another is spawned. This new
kcscreenlocker_greet process accepts the password and I am able to log in.

Reproducible: Always

Steps to Reproduce:
1. Leave for several days
2. Try to log in
3.

Actual Results:  
Unable to log in

Expected Results:  
Password accepted, process taking very little memory

The first time this happened, I changed my password, thinking that something
had happened. I would like to troubleshoot this more, but not sure how to
proceed. This has happened for three weeks now, and the process is still
running when I come back in to work. Is there a way to run ksceenlocker_greet
on valgrind or something?

-- 
You are receiving this mail because:
You are watching all bug changes.