Bug 317485

Uh, this is really weird, is that  bug reproducible all the times? if so, can you point us tot he file where this code comes from?

If you list all devices, are udisk2 devices included?

(In reply to comment #1)
> Uh, this is really weird, is that  bug reproducible all the times?

Yes.

> if so, can you point us tot he file where this code comes from?

http://quickgit.kde.org/?p=amarok.git&a=blob&f=src%2Fcore-impl%2Fcollections%2Fipodcollection%2FIpodCollectionFactory.cpp#45 - for debugging I apply patch below.

> If you list all devices, are udisk2 devices included?

Yes. Solid::Device::allDevices() includes UDisks2 devices; I get following ouput using the debugging patch below:

BEGIN: virtual void IpodCollectionFactory::init() 
  [IpodCollectionFactory] ::allDevices(): 
  [IpodCollectionFactory] "/org/kde/solid/udev/sys/devices/LNXSYSTM:00/LNXCPU:00" 
(...)
  [IpodCollectionFactory] "/org/freedesktop/UDisks2/block_devices/sdc1" 
  [IpodCollectionFactory] "/org/freedesktop/UDisks2/block_devices/sdc2" 
(...)
  [IpodCollectionFactory] ::listFromQuery(): 
  [IpodCollectionFactory] "/org/kde/solid/udev/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1.1/1-1.1.1:1.0/host6/target6:0:0/6:0:0:0/block/sdc/sdc1" 
  [IpodCollectionFactory] "/org/kde/solid/udev/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1.1/1-1.1.1:1.0/host6/target6:0:0/6:0:0:0/block/sdc/sdc2" 
  [IpodCollectionFactory] "/org/kde/solid/udev/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1.1/1-1.1.1:1.0/host6/target6:0:0/6:0:0:0/block/sdc" 
  [IpodCollectionFactory] "/org/kde/fstab/esprimo.local:/" 
  [IpodCollectionFactory] "/org/kde/fstab/roundy.local:/" 
END__: virtual void IpodCollectionFactory::init() [Took: 0.33s]

The same thing also happens USB Mass Storage Collection which uses nearly identical code with simpler query: "IS StorageAccess"

diff --git a/src/core-impl/collections/ipodcollection/IpodCollectionFactory.cpp b/src/core-impl/collections/ipodcollection/IpodCollectionFactory.cpp
index 7ecdcfa..bb6f12b 100644
--- a/src/core-impl/collections/ipodcollection/IpodCollectionFactory.cpp
+++ b/src/core-impl/collections/ipodcollection/IpodCollectionFactory.cpp
@@ -16,6 +16,8 @@
 
 #include "IpodCollectionFactory.h"
 
+#define DEBUG_PREFIX "IpodCollectionFactory"
+
 #include "IpodCollection.h"
 #include "core/support/Debug.h"
 
@@ -42,14 +44,20 @@ IpodCollectionFactory::~IpodCollectionFactory()
 void
 IpodCollectionFactory::init()
 {
+    DEBUG_BLOCK
     connect( Solid::DeviceNotifier::instance(), SIGNAL(deviceAdded(QString)),
              SLOT(slotAddSolidDevice(QString)) );
     connect( Solid::DeviceNotifier::instance(), SIGNAL(deviceRemoved(QString)),
              SLOT(slotRemoveSolidDevice(QString)) );
 
+    debug() << "::allDevices():";
+    foreach( const Solid::Device &d, Solid::Device::allDevices() ) { debug() << d.udi(); }
+
     // detect iPods that were already connected on startup
     QString query( "[IS StorageAccess OR IS PortableMediaPlayer]" );
     QList<Solid::Device> ipodDevices = Solid::Device::listFromQuery( query );
+    debug() << "::listFromQuery():";
+    foreach( const Solid::Device &d, ipodDevices ) { debug() << d.udi(); }
     foreach( Solid::Device device, ipodDevices )
     {
         if( identifySolidDevice( device.udi() ) )

I'm quite certain that the bug is in udisk2 backend, method:

devicemanager.cpp
QStringList Manager::devicesFromQuery

Can you do some debugging around there?

Since parenetUdi is empty, I'm thinking that either:
deviceCache() is returning an empty stringlist

or we are failing to detect the type properly for some weird reason :/

Udisks2 backend do weird things also when detecting hard disks: see bug 311408 , could be related?

Created attachment 81261 [details]
amarok-debugging-for-afiestas.patch

Created attachment 81262 [details]
kdelibs-debugging-for-afiestas.patch

Hi Àlex,
please find the 2 debugging patches to identify the problem we've worked on at 
Akademy on bug https://bugs.kde.org/show_bug.cgi?id=317485

After applying both amarok and kdelibs patch, reproducing is as easy as 
plugging in and mounting a USB drive, starting Amarok from console as
amarok --debug --nofork
and watching for UmsCollection string.

Interesting observations:
 * The exact solid device is instantiated earlier and in that case it prints 
out product just fine.
 * Messages like 
`"/org/freedesktop/UDisks2/drives/Corsair_Flash_Voyager_A400000000025639" : 
property "Drive" does not exist` seem to be root of the cause
 * my udisks version is 2.1.0

	Matěj

*** Bug 322980 has been marked as a duplicate of this bug. ***

Git commit cfaa48278274f70fab3f6e1b610660edafbf7bbc by Matěj Laitl.
Committed on 30/07/2013 at 17:51.
Pushed by laitl into branch 'master'.

MediaDeviceCache: work-around Solid UDisks2 bug by not calling allDevices()

Kudos go to Alex Fiestas for extensive debugging and finding out the
root of the problem.

BUGFIXES:
 * Work-around Solid UDisks2 backend bug that caused USB Mass Storage
   devices and iPods not being recognized when connected before Amarok
   was started. Also fixes a bug where blank devices would appear in
   Play Media dialog. (BR 322980)

We don't need to call Solid::Device::allDevices() at all because that
was only needed for Apple iPhone support for the *old* iPod collection
that was replaced in Amarok 2.6.
Related: bug 322980
FIXED-IN: 2.8

M  +3    -0    ChangeLog
M  +0    -23   src/MediaDeviceCache.cpp

http://commits.kde.org/amarok/cfaa48278274f70fab3f6e1b610660edafbf7bbc

Git commit b92df2769477f48102ccc215f5d5eae5c4a6e5a5 by Àlex Fiestas.
Committed on 01/08/2013 at 19:24.
Pushed by afiestas into branch 'master'.

Do not clean the cache in UDisks2 backend

By deleting DeviceBackend we are invalidating all UDisks2::Devices that
are in libsolid frontend, since their m_backend will be 0
Related: bug 314544

REVIEW:111802

M  +0    -6    solid/solid/backends/udisks2/udisksmanager.cpp

http://commits.kde.org/kdelibs/b92df2769477f48102ccc215f5d5eae5c4a6e5a5

Git commit 9d7a02f3af96551eaed0bd97e9fb9ccd03d54650 by Àlex Fiestas.
Committed on 01/08/2013 at 19:24.
Pushed by afiestas into branch 'KDE/4.11'.

Do not clean the cache in UDisks2 backend

By deleting DeviceBackend we are invalidating all UDisks2::Devices that
are in libsolid frontend, since their m_backend will be 0
Related: bug 314544

REVIEW:111802
(cherry picked from commit b92df2769477f48102ccc215f5d5eae5c4a6e5a5)

M  +0    -6    solid/solid/backends/udisks2/udisksmanager.cpp

http://commits.kde.org/kdelibs/9d7a02f3af96551eaed0bd97e9fb9ccd03d54650