When I plug my IRiver LPlayer, it appears in UDisks DBus interface as /org/freedesktop/UDisks/devices/sdc. It has property "IdUUID" which should return UUID of the device. But instead of returning UUID it returns just an empty string. This leads to the fact that it has empty UUID in Solid in KDE, and this leads to the fact that Amarok can't use it as external media device (it shows an '[MassStorageDeviceHandler] has empty uuid' error) Reproducible: Always Steps to Reproduce: 1. Plug IRiver LPlayer to USB. 2. Run "qdbusviewer" 3. Open "org.freedesktop.UDisks" interface in "System Bus". 4. Check property "IdUUID" of /org/freedesktop/UDisks/devices/DEVICE_ID (where DEVICE_ID is the id of your player in UDisks). Actual Results: It returns an empty string. Expected Results: It should return some UUID.
Created attachment 270997 [details] cave info sys-fs/udisks
That's what I get for my main hdd (empty uuid), only partitions have uuid. Same as for cdrom with no disc in it (empty uuid). Try creating a partition for your sdc first? :)
I bet you won't get a uuid even with `blkid /dev/sdc`
Yep, you're right, it shows only LABEL and TYPE. But this device doesn't have partition table, and all data is stored on /dev/sdc. And I don't want to create partition table with 1 partition in order to don't break anything (I don't know how the internal firmware will react on it; I guess, it should work, but I don't want to experiment). So, if you're right and this device shouldn't have a UUID, whose bug is it? UDisks? Solid? Amarok?
Propably amarok, or more likely solid shouldn't be expecting a uuid... Reassigning to KDE maintainers
I'd suggest you file an upstream bug against amarok. It may not be an amarok problem, but then these guys will know the codepaths better and be able to trace it to its origin.
Done. Link is https://bugs.kde.org/show_bug.cgi?id=275978. I guess this one should be 'RESOLVED' as 'UPSTREAM' then?
(In reply to comment #7) > Done. Link is https://bugs.kde.org/show_bug.cgi?id=275978. I guess this one > should be 'RESOLVED' as 'UPSTREAM' then? We'll keep it open for tracking.
Looks like this bug disappeared in Amarok 2.4.3. I reported about it to upstream and closed upstream bug. You can close this too.
(In reply to comment #9) > Looks like this bug disappeared in Amarok 2.4.3. I reported about it to > upstream and closed upstream bug. You can close this too. Cheers! :)
