http://bugzilla.suse.com/show_bug.cgi?id=927677 http://bugzilla.suse.com/show_bug.cgi?id=927677#c40 --- Comment #40 from Thomas Blume <thomas.blume@suse.com> --- (In reply to Rosanne DiMesio from comment #39)
Created attachment 725273 [details] udevadm info -e
Since the investigation gets a bit confusing by now, lets summarize the findings to better visualize the problem. The dbus information shows: --> org/freedesktop/UDisks2/block_devices/sdd: org.freedesktop.UDisks2.Block: [...] HintAuto: false [...] HintSystem: true --< This indicates a system disk and is obviously wrong for an usb stick. The check for this is done in src/udiskslinuxblock.c: --> /* Provide easy access to _only_ the following devices * * - anything connected via known local buses (e.g. USB or Firewire, MMC or MemoryStick) * - any device with removable media * * Be careful when extending this list as we don't want to automount * the world when (inadvertently) connecting to a SAN. */ if (drive != NULL) { const gchar *connection_bus; gboolean removable; connection_bus = udisks_drive_get_connection_bus (drive); removable = udisks_drive_get_media_removable (drive); if (removable || (g_strcmp0 (connection_bus, "usb") == 0 || g_strcmp0 (connection_bus, "ieee1394") == 0) || (g_str_has_prefix (device_file, "/dev/mmcblk") || g_str_has_prefix (device_file, "/dev/mspblk"))) { hint_system = FALSE; hint_auto = TRUE; } } --< The property removable is set in the udev database as the udevadm -a output shows: --> looking at device '/devices/pci0000:00/0000:00:16.2/usb5/5-3/5-3:1.0/host10/target10:0:0/10:0:0:0/block/sdd': [...] ATTR{removable}=="1" --< That means the the condition (drive != NULL) must be false. Reason therefore is that the dbus drive object isn't found as stated in comment#33. The question is now, what is adding the drive objects to dbus? Continuing the investigation in this direction. -- You are receiving this mail because: You are on the CC list for the bug.