http://bugzilla.suse.com/show_bug.cgi?id=927677 http://bugzilla.suse.com/show_bug.cgi?id=927677#c34 Thomas Blume <thomas.blume@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(dimesio@earthlink | |.net) --- Comment #34 from Thomas Blume <thomas.blume@suse.com> --- (In reply to Rosanne DiMesio from comment #33)
The problem stick doesn't appear in the output at all, whether it's mounted or not:
node /org/freedesktop/UDisks2/drives { node ASUS____DRW_24B1ST___j_FCD0CL043645 { }; node SanDisk_SDSSDA24_161627400789 { }; node SanDisk_SDSSDH21_130667401722 { }; node ST1000DM003_9YN1_S1D0FQMJ { }; };
Ok, thanks. If the device information is missing completely on the udisks2 bus, the sysfs representation of the stick might lack some properties that udisks2 needs for proper indentification. Please provide the output of: udevadm info -a /sys/$SYSFS_PATH where $SYSFS_PATH is the path to the usb device below /sys. For example in comment#19 you showed your devices sysfs path as: dimesio@linux-prda:~> udevadm info /dev/sdd P: /devices/pci0000:00/0000:00:16.2/usb5/5-3/5-3:1.0/host10/target10:0:0/10:0:0:0/block/sdd So the command would be: udevadm info -a /sys/devices/pci0000:00/0000:00:16.2/usb5/5-3/5-3:1.0/host10/target10:0:0/10:0:0:0/block/sdd -- You are receiving this mail because: You are on the CC list for the bug.