Summary: | Removing memory card causes device to disappear from the system. | ||
---|---|---|---|
Product: | [Frameworks and Libraries] frameworks-solid | Reporter: | S.Trzmiel <xeno> |
Component: | general | Assignee: | Lukáš Tinkl <lukas> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | kde, kdelibs-bugs, nate, stefan.bruens |
Priority: | NOR | ||
Version: | 5.53.0 | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | https://cgit.kde.org/solid.git/commit/?id=6d260195cf75604d835235d2a1b02166ee8b514a | Version Fixed In: | 5.54 |
Attachments: |
udev info of SDCard
udev info of SDcard partition 1 of 1 udisk mmcblk0 info udisk SU02G info |
Description
S.Trzmiel
2018-12-13 15:40:51 UTC
It is probably powered down by Solid because people wanted us to power down external hard drives... (In reply to Kai Uwe Broulik from comment #1) > It is probably powered down by Solid because people wanted us to power down > external hard drives... I guess so, would it be possible to offer different actions for different media types? Ie 'safe removal' for external hard drives/pendrives and 'eject' for memory cards? Hardware vendors are unfortunately to dumb to properly implement standards ... Therefor, UDisks adds a list of quirks for known devices. Try adding a file "/etc/udev/rules.d/80-udisks2-local.rule" with the following contents to your system: --- >8 --- SUBSYSTEMS=="usb", ENV{ID_VENDOR_ID}=="0bda",ENV{ID_MODEL_ID}=="0129", ENV{ID_DRIVE_FLASH_CF}="1" --- 8< --- Also please provide the output of the following commands: $> udevadm info -n /dev/sdX > /tmp/udev_info_sdX.txt $> udevadm info -n /dev/sdXN > /tmp/udev_info_sdXN.txt replace sdX with the correct device name for your card reader, e.g. sdb, sdc ... replace N in sdXN with the number(s) of the partitions. Created attachment 116902 [details]
udev info of SDCard
Created attachment 116903 [details]
udev info of SDcard partition 1 of 1
(In reply to Stefan Brüns from comment #3) > Hardware vendors are unfortunately to dumb to properly implement standards > ... > > Therefor, UDisks adds a list of quirks for known devices. > > Try adding a file "/etc/udev/rules.d/80-udisks2-local.rule" with the > following contents to your system: > --- >8 --- > SUBSYSTEMS=="usb", ENV{ID_VENDOR_ID}=="0bda",ENV{ID_MODEL_ID}=="0129", > ENV{ID_DRIVE_FLASH_CF}="1" > --- 8< --- > > Also please provide the output of the following commands: > $> udevadm info -n /dev/sdX > /tmp/udev_info_sdX.txt > $> udevadm info -n /dev/sdXN > /tmp/udev_info_sdXN.txt > > replace sdX with the correct device name for your card reader, e.g. sdb, sdc > ... > replace N in sdXN with the number(s) of the partitions. udevdm output provided. I've created udev rule, even rebooted OS to be sure it's loaded (most likely unnessesary) but it made no difference, removing SDcard still power downs the reader Right now it loks like this: #--- >8 --- SUBSYSTEMS=="usb", ENV{ID_VENDOR_ID}=="0bda",ENV{ID_MODEL_ID}=="0129", ENV{ID_DRIVE_FLASH_CF}="1" #--- 8< --- I've tried with header footer/commented out, not commented and not present, still no difference Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! As posted above, workaround didn't make a difference, udevadm output provided as attachements. The malfunction is likely caused by the device identifying itself as a MMC block device, contrary to the typical USB cardreader using the SCSI/SATA command set. Can you provide the output of: $> udisksctl info -b /dev/mmcblk0 $> udisksctl info -d FooBar Replace FooBar with the value from the block device "Drive" property, like: $> udisksctl info -b /dev/sdb | grep Drive Drive: '/org/freedesktop/UDisks2/drives/FooBar' Created attachment 117229 [details]
udisk mmcblk0 info
output of udisksctl info -b /dev/mmcblk0
Created attachment 117230 [details]
udisk SU02G info
output of udisksctl info -d SU02G_0x0eea8c36
Requested info provided |