On Sat, 28 Mar 2015, Scott Kitterman wrote:
On Sunday, March 15, 2015 12:43:51 PM Scott Kitterman wrote:
I've poked around in core/libs/database/collectionmanager.cpp and it appears
that the digikam code tries to do the right thing and the most likely issue
is something about how solid handles these cases, so reassigning.
For the cases in question for this bug, please try running:
$ solid-hardware list
Then find the UID of the mount point in question and run:
$ solid-hardware details '$UID'
I have tried to re-create a situation where solid-hardware would complain
in any way, but have failed to.
No matter what I do to recreate the problematic situation "solid-hardware
list" would stay the same.
The problem wrt solid-hardware is that it is concerned with *real*
hardware only as far as I can see. The problem I saw, when first
contributing to this bug report was completely with "virtual
resources" though - that is, I did not mount any real hardware but only
stuff like /var/lib/dbus, ~/.pulse, /run/shm, /dev/, /proc under the
chroot which apparently caused problems in digiKam. All the listed
devices/filesystems is stuff that solid-hardware should be unconcerned
with...
So I'm not sure if I there's any further useful insight wrt solid-hardware
I'd be able to provide...
*t
--
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/alpine.DEB.2.11.1505051033490.2644@hier
