https://bugs.kde.org/show_bug.cgi?id=387454
--- Comment #22 from Stephan Wezel <s.we...@web.de> ---
I quess not that is a kernel error.
As stated in comment 11 the kernel (4.14+) now sends bind uvents when the
driver gets bound to a physical device.
It seems that the add uvents are now send earlier then before this change (when
the device get plugged in). Before any device specific properties/attributes
could be read.
Before my change the /dev/libmtp* symlink was created when i ran
udevadm test <path to usb device under dev>
after the device was plugged in.
The question is why can pcmanfm access the mtp device and dolphin (via solid)
not.
Does Solid depend on the /dev/libmtp* symlink? Or which information are needed
to mark an usb device as mtp device by solid?
Maybe solid depends on following two udev env variables?
ENV{ID_MTP_DEVICE}="1"
ENV{ID_MEDIA_PLAYER}="1"
Those ENV vars get setup by the libmtp udev rules, which also setup the
/dev/libmtp* symlink.
Maybe pcmanfm doesn't depend on udev properties to access/mark a device as mtp
device. It could directly query libmtp for available devices. And libmtp
reports it correctly after the device was plugged in.
--
You are receiving this mail because:
You are watching all bug changes.
