[Kde-hardware-devel] Fwd: Trouble with udisks-daemon caused by solid

[Ben Cooksley]

Forwarding this to the solid list...

Regards,
Ben

---------- Forwarded message ----------
From: Andreas Roth <aroth at arsoft-online.com>
Date: Wed, Jul 27, 2011 at 5:48 AM
Subject: Trouble with udisks-daemon caused by solid
To: kde-core-devel at kde.org


Hi,

i stumbled over this issue when running amarok. When amarok is running, the
udisks-daemon is constantly active. It takes about 1-5% of CPU. At the same
time the dbus-daemon also takes the same amount of CPU.
The original post to amarok-devel can be found here:
http://mail.kde.org/pipermail/amarok-devel/2011-July/009273.html

I've run a strace against the udisks-daemon and writes the following message
to stderr:
write(2, "\n** (udisks-daemon:2797): WARNING **: Property get or set does not
have an interface string as first arg\n\n", 106)

With the help of the amarok developers is found the piece of code, which
triggers this issue. In amarok/src/MediaDeviceCache.cpp, function
MediaDeviceCache::slotTimeout() calls Solid::Device::listFromType, which does
some dbus/udisks magic and this causes the trouble. I haven't gone into the
solid code to check what might be wrong there.

I created a small test program, which does exactly what amarok does and also
triggers this issue. I've attach the program to this mail.

Hopefully someone could help me to track down this issue and fix it.

Thanks,
Andreas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: solidtest.zip
Type: application/zip
Size: 2750 bytes
Desc: not available
Url : http://mail.kde.org/pipermail/kde-hardware-devel/attachments/20110727/53a3d466/attachment-0001.zip