Bug #452768 “USB flash drive does not mount automatically” : Bugs : devicekit-disks package : Ubuntu

Revision history for this message

LarryGrover (lgrover) wrote on 2009-10-16:

#1

Dependencies.txt Edit (4.4 KiB, text/plain; charset="utf-8")
ProcMaps.txt Edit (42.3 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (760 bytes, text/plain; charset="utf-8")
XsessionErrors.txt Edit (188.9 KiB, text/plain; charset="utf-8")
usr_lib_nautilus.txt Edit (268 bytes, text/plain; charset="utf-8")

Revision history for this message

LarryGrover (lgrover) wrote on 2009-10-16:

#2

dmesg_usb_no_automount.txt Edit (67.5 KiB, text/plain)

dmesg output immediately after USB flash drive is inserted. The system is recognizing the USB drive (sdb), but it is not mounting it.

Revision history for this message

xgong (xgong) wrote on 2009-10-16:

#3

Try this:

1.backup this file to somewhere else /usr/share/hal/fdi/policy/10osvendor/20-storage-methods.fdi

2.delete it in the terminal:
sudo rm /usr/share/hal/fdi/policy/10osvendor/20-storage-methods.fdi

3.restart HAL service:
sudo service hal restart

Then re-plug USB drive

Revision history for this message

LarryGrover (lgrover) wrote on 2009-10-16:

#4

jackallen: I moved /usr/share/hal/fdi/policy/10osvendor/20-storage-methods.fdi to a different location and restarted hal. This had no effect. When I plug in my USB flash drive, it still fails to mount.

Brian Murray (brian-murray) on 2009-10-19

affects:

ubuntu → devicekit-disks (Ubuntu)

Revision history for this message

Busby (mobusby) wrote on 2009-10-20:

#5

Download full text (10.2 KiB)

This happens on stock Karmic Beta as well. Any USB drive plugged in after booting will not automount. Mounting manually works as usual.

as can be seen below, the devices are recognized, but automounting fails due to an I/O error.

before plugging in devices, after restarting:
$ lsusb
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 005: ID 0bc2:3001 Seagate RSS LLC
Bus 001 Device 004: ID 0b38:0010
Bus 001 Device 003: ID 046d:c521 Logitech, Inc. MX620 Laser Cordless Mouse
Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

after plugging in two devices:
$ lsusb
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 011: ID 0781:5530 SanDisk Corp.
Bus 001 Device 010: ID 0fca:8004 Research In Motion, Ltd.
Bus 001 Device 005: ID 0bc2:3001 Seagate RSS LLC
Bus 001 Device 004: ID 0b38:0010
Bus 001 Device 003: ID 046d:c521 Logitech, Inc. MX620 Laser Cordless Mouse
Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

$ dmesg | tail -120
[ 3237.672088] usb 1-7: new high speed USB device using ehci_hcd and address 10
[ 3237.817510] usb 1-7: configuration #1 chosen from 1 choice
[ 3237.824268] scsi7 : SCSI emulation for USB Mass Storage devices
[ 3237.824505] usb-storage: device found at 10
[ 3237.824509] usb-storage: waiting for device to settle before scanning
[ 3238.368109] usb 1-8: new high speed USB device using ehci_hcd and address 11
[ 3238.505256] usb 1-8: configuration #1 chosen from 1 choice
[ 3238.505575] scsi8 : SCSI emulation for USB Mass Storage devices
[ 3238.505797] usb-storage: device found at 11
[ 3238.505801] usb-storage: waiting for device to settle before scanning
[ 3242.821017] usb-storage: device scan complete
[ 3242.822116] scsi 7:0:0:0: Direct-Access RIM BlackBerry SD 0003 PQ: 0 ANSI: 4 CCS
[ 3242.823146] sd 7:0:0:0: Attached scsi generic sg3 type 0
[ 3242.839590] sd 7:0:0:0: [sdc] Attached SCSI removable disk
[ 3243.504424] usb-storage: device scan complete
[ 3243.505006] scsi 8:0:0:0: Direct-Access SanDisk SanDisk Cruzer 8.02 PQ: 0 ANSI: 0 CCS
[ 3243.505845] scsi 8:0:0:1: CD-ROM SanDisk SanDisk Cruzer 8.02 PQ: 0 ANSI: 0
[ 3243.506857] sd 8:0:0:0: Attached scsi generic sg4 type 0
[ 3243.508047] sd 8:0:0:0: [sdd] 15695871 512-byte logical blocks: (8.03 GB/7.48 GiB)
[ 3243.509141] sd 8:0:0:0: [sdd] Write Protect is off
[ 3243.509147] sd 8:0:0:0: [sdd] Mode Sense: 45 00 00 08
[ 3243.509152] sd 8:0:0:0: [sdd] Assuming drive cache: write through
[ 3243.510520] sr1: scsi3-mmc drive: 48x/48x tray
[ 3243.510720] sr 8:0:0:1: Attached scsi CD-ROM sr1
[ 3243.510829] sr 8:0:0:1: Attached scsi generic sg5 type 5...

This happens on stock Karmic Beta as well.  Any USB drive plugged in after booting will not automount.  Mounting manually works as usual.

as can be seen below, the devices are recognized, but automounting fails due to an I/O error.

before plugging in devices, after restarting:
$ lsusb
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 005: ID 0bc2:3001 Seagate RSS LLC 
Bus 001 Device 004: ID 0b38:0010  
Bus 001 Device 003: ID 046d:c521 Logitech, Inc. MX620 Laser Cordless Mouse
Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

after plugging in two devices:
$ lsusb
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 011: ID 0781:5530 SanDisk Corp. 
Bus 001 Device 010: ID 0fca:8004 Research In Motion, Ltd. 
Bus 001 Device 005: ID 0bc2:3001 Seagate RSS LLC 
Bus 001 Device 004: ID 0b38:0010  
Bus 001 Device 003: ID 046d:c521 Logitech, Inc. MX620 Laser Cordless Mouse
Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

$ dmesg | tail -120
[ 3237.672088] usb 1-7: new high speed USB device using ehci_hcd and address 10
[ 3237.817510] usb 1-7: configuration #1 chosen from 1 choice
[ 3237.824268] scsi7 : SCSI emulation for USB Mass Storage devices
[ 3237.824505] usb-storage: device found at 10
[ 3237.824509] usb-storage: waiting for device to settle before scanning
[ 3238.368109] usb 1-8: new high speed USB device using ehci_hcd and address 11
[ 3238.505256] usb 1-8: configuration #1 chosen from 1 choice
[ 3238.505575] scsi8 : SCSI emulation for USB Mass Storage devices
[ 3238.505797] usb-storage: device found at 11
[ 3238.505801] usb-storage: waiting for device to settle before scanning
[ 3242.821017] usb-storage: device scan complete
[ 3242.822116] scsi 7:0:0:0: Direct-Access     RIM      BlackBerry SD    0003 PQ: 0 ANSI: 4 CCS
[ 3242.823146] sd 7:0:0:0: Attached scsi generic sg3 type 0
[ 3242.839590] sd 7:0:0:0: [sdc] Attached SCSI removable disk
[ 3243.504424] usb-storage: device scan complete
[ 3243.505006] scsi 8:0:0:0: Direct-Access     SanDisk  SanDisk Cruzer   8.02 PQ: 0 ANSI: 0 CCS
[ 3243.505845] scsi 8:0:0:1: CD-ROM            SanDisk  SanDisk Cruzer   8.02 PQ: 0 ANSI: 0
[ 3243.506857] sd 8:0:0:0: Attached scsi generic sg4 type 0
[ 3243.508047] sd 8:0:0:0: [sdd] 15695871 512-byte logical blocks: (8.03 GB/7.48 GiB)
[ 3243.509141] sd 8:0:0:0: [sdd] Write Protect is off
[ 3243.509147] sd 8:0:0:0: [sdd] Mode Sense: 45 00 00 08
[ 3243.509152] sd 8:0:0:0: [sdd] Assuming drive cache: write through
[ 3243.510520] sr1: scsi3-mmc drive: 48x/48x tray
[ 3243.510720] sr 8:0:0:1: Attached scsi CD-ROM sr1
[ 3243.510829] sr 8:0:0:1: Attached scsi generic sg5 type 5
[ 3243.516270] sd 8:0:0:0: [sdd] Assuming drive cache: write through
[ 3243.516279]  sdd: sdd1
[ 3243.523502] sd 8:0:0:0: [sdd] Assuming drive cache: write through
[ 3243.523507] sd 8:0:0:0: [sdd] Attached SCSI removable disk
[ 3243.661638] sr 8:0:0:1: [sr1] Unhandled sense code
[ 3243.661646] sr 8:0:0:1: [sr1] Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE
[ 3243.661653] sr 8:0:0:1: [sr1] Sense Key : No Sense [current] 
[ 3243.661663] sr 8:0:0:1: [sr1] Add. Sense: No additional sense information
[ 3243.661672] end_request: I/O error, dev sr1, sector 196352
[ 3243.661680] __ratelimit: 11 callbacks suppressed
[ 3243.661686] Buffer I/O error on device sr1, logical block 49088
[ 3243.661693] Buffer I/O error on device sr1, logical block 49089
[ 3243.669986] sr 8:0:0:1: [sr1] Unhandled sense code
[ 3243.669995] sr 8:0:0:1: [sr1] Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE
[ 3243.670006] sr 8:0:0:1: [sr1] Sense Key : No Sense [current] 
[ 3243.670018] sr 8:0:0:1: [sr1] Add. Sense: No additional sense information
[ 3243.670031] end_request: I/O error, dev sr1, sector 196352
[ 3243.670042] Buffer I/O error on device sr1, logical block 49088
[ 3243.670051] Buffer I/O error on device sr1, logical block 49089
[ 3243.675629] sr 8:0:0:1: [sr1] Unhandled sense code
[ 3243.675635] sr 8:0:0:1: [sr1] Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE
[ 3243.675642] sr 8:0:0:1: [sr1] Sense Key : No Sense [current] 
[ 3243.675651] sr 8:0:0:1: [sr1] Add. Sense: No additional sense information
[ 3243.675661] end_request: I/O error, dev sr1, sector 196584
[ 3243.675668] Buffer I/O error on device sr1, logical block 49146
[ 3243.675674] Buffer I/O error on device sr1, logical block 49147
[ 3243.680628] sr 8:0:0:1: [sr1] Unhandled sense code
[ 3243.680634] sr 8:0:0:1: [sr1] Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE
[ 3243.680641] sr 8:0:0:1: [sr1] Sense Key : No Sense [current] 
[ 3243.680649] sr 8:0:0:1: [sr1] Add. Sense: No additional sense information
[ 3243.680658] end_request: I/O error, dev sr1, sector 196584
[ 3243.680665] Buffer I/O error on device sr1, logical block 49146
[ 3243.680670] Buffer I/O error on device sr1, logical block 49147
[ 3243.689500] sr 8:0:0:1: [sr1] Unhandled sense code
[ 3243.689507] sr 8:0:0:1: [sr1] Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE
[ 3243.689515] sr 8:0:0:1: [sr1] Sense Key : No Sense [current] 
[ 3243.689523] sr 8:0:0:1: [sr1] Add. Sense: No additional sense information
[ 3243.689533] end_request: I/O error, dev sr1, sector 196600
[ 3243.689541] Buffer I/O error on device sr1, logical block 49150
[ 3243.708503] sr 8:0:0:1: [sr1] Unhandled sense code
[ 3243.708510] sr 8:0:0:1: [sr1] Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE
[ 3243.708518] sr 8:0:0:1: [sr1] Sense Key : No Sense [current] 
[ 3243.708527] sr 8:0:0:1: [sr1] Add. Sense: No additional sense information
[ 3243.708537] end_request: I/O error, dev sr1, sector 196600
[ 3243.708544] Buffer I/O error on device sr1, logical block 49150
[ 3243.715374] sr 8:0:0:1: [sr1] Unhandled sense code
[ 3243.715379] sr 8:0:0:1: [sr1] Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE
[ 3243.715385] sr 8:0:0:1: [sr1] Sense Key : No Sense [current] 
[ 3243.715393] sr 8:0:0:1: [sr1] Add. Sense: No additional sense information
[ 3243.715402] end_request: I/O error, dev sr1, sector 196600
[ 3243.721748] sr 8:0:0:1: [sr1] Unhandled sense code
[ 3243.721753] sr 8:0:0:1: [sr1] Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE
[ 3243.721760] sr 8:0:0:1: [sr1] Sense Key : No Sense [current] 
[ 3243.721768] sr 8:0:0:1: [sr1] Add. Sense: No additional sense information
[ 3243.721777] end_request: I/O error, dev sr1, sector 196600
[ 3243.730008] sr 8:0:0:1: [sr1] Unhandled sense code
[ 3243.730015] sr 8:0:0:1: [sr1] Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE
[ 3243.730022] sr 8:0:0:1: [sr1] Sense Key : No Sense [current] 
[ 3243.730031] sr 8:0:0:1: [sr1] Add. Sense: No additional sense information
[ 3243.730040] end_request: I/O error, dev sr1, sector 196600
[ 3243.737628] sr 8:0:0:1: [sr1] Unhandled sense code
[ 3243.737635] sr 8:0:0:1: [sr1] Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE
[ 3243.737642] sr 8:0:0:1: [sr1] Sense Key : No Sense [current] 
[ 3243.737651] sr 8:0:0:1: [sr1] Add. Sense: No additional sense information
[ 3243.737661] end_request: I/O error, dev sr1, sector 196600
[ 3243.742499] sr 8:0:0:1: [sr1] Unhandled sense code
[ 3243.742505] sr 8:0:0:1: [sr1] Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE
[ 3243.742512] sr 8:0:0:1: [sr1] Sense Key : No Sense [current] 
[ 3243.742520] sr 8:0:0:1: [sr1] Add. Sense: No additional sense information
[ 3243.742529] end_request: I/O error, dev sr1, sector 196600
[ 3243.747999] sr 8:0:0:1: [sr1] Unhandled sense code
[ 3243.748029] sr 8:0:0:1: [sr1] Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE
[ 3243.748036] sr 8:0:0:1: [sr1] Sense Key : No Sense [current] 
[ 3243.748044] sr 8:0:0:1: [sr1] Add. Sense: No additional sense information
[ 3243.748054] end_request: I/O error, dev sr1, sector 196536
[ 3243.754872] sr 8:0:0:1: [sr1] Unhandled sense code
[ 3243.754878] sr 8:0:0:1: [sr1] Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE
[ 3243.754886] sr 8:0:0:1: [sr1] Sense Key : No Sense [current] 
[ 3243.754894] sr 8:0:0:1: [sr1] Add. Sense: No additional sense information
[ 3243.754904] end_request: I/O error, dev sr1, sector 196592
[ 3243.759624] sr 8:0:0:1: [sr1] Unhandled sense code
[ 3243.759630] sr 8:0:0:1: [sr1] Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE
[ 3243.759637] sr 8:0:0:1: [sr1] Sense Key : No Sense [current] 
[ 3243.759645] sr 8:0:0:1: [sr1] Add. Sense: No additional sense information
[ 3243.759654] end_request: I/O error, dev sr1, sector 196600
[ 3243.764372] sr 8:0:0:1: [sr1] Unhandled sense code
[ 3243.764377] sr 8:0:0:1: [sr1] Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE
[ 3243.764384] sr 8:0:0:1: [sr1] Sense Key : No Sense [current] 
[ 3243.764392] sr 8:0:0:1: [sr1] Add. Sense: No additional sense information
[ 3243.764401] end_request: I/O error, dev sr1, sector 196600
[ 3245.748505] sd 7:0:0:0: [sdc] 3862528 512-byte logical blocks: (1.97 GB/1.84 GiB)
[ 3245.749991] sd 7:0:0:0: [sdc] Assuming drive cache: write through
[ 3245.753520] sd 7:0:0:0: [sdc] Assuming drive cache: write through
[ 3245.753533]  sdc: sdc1

$ mount -l
/dev/sda8 on / type ext3 (rw,relatime,errors=remount-ro)
proc on /proc type proc (rw)
none on /sys type sysfs (rw,noexec,nosuid,nodev)
none on /sys/fs/fuse/connections type fusectl (rw)
none on /sys/kernel/debug type debugfs (rw)
none on /sys/kernel/security type securityfs (rw)
udev on /dev type tmpfs (rw,mode=0755)
none on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620)
none on /dev/shm type tmpfs (rw,nosuid,nodev)
none on /var/run type tmpfs (rw,nosuid,mode=0755)
none on /var/lock type tmpfs (rw,noexec,nosuid,nodev)
none on /lib/init/rw type tmpfs (rw,nosuid,mode=0755)
/dev/sda7 on /boot type ext3 (rw,relatime)
/dev/sda2 on /c type fuseblk (rw,nosuid,nodev,allow_other,default_permissions,blksize=4096)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,noexec,nosuid,nodev)
gvfs-fuse-daemon on /home/mobusby/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,user=mobusby)

Changed in devicekit-disks (Ubuntu):
status:	New → Confirmed

Revision history for this message

Busby (mobusby) wrote on 2009-10-20:

#6

Changed status to confirmed.

Revision history for this message

LarryGrover (lgrover) wrote on 2009-10-27:

#7

I am no longer experiencing this bug. I guess one of the updates I installed in the last couple of days must have fixed the problem.

Revision history for this message

oshunluvr (stuartksmith) wrote on 2009-10-27:

#8

lshal.txt Edit (215.3 KiB, text/plain)

I am still experiencing this bug.

Requested files below

Revision history for this message

oshunluvr (stuartksmith) wrote on 2009-10-27:

#9

ck-list-sessions.txt Edit (300 bytes, text/plain)

Revision history for this message

oshunluvr (stuartksmith) wrote on 2009-10-27:

#10

devices.txt Edit (2.2 KiB, text/plain)

Revision history for this message

oshunluvr (stuartksmith) wrote on 2009-10-27:

#11

dmesg.txt Edit (64.3 KiB, text/plain)

Revision history for this message

oshunluvr (stuartksmith) wrote on 2009-10-27:

#12

id_haldaemon.txt Edit (60 bytes, text/plain)

Revision history for this message

oshunluvr (stuartksmith) wrote on 2009-10-27:

#13

udevlog.txt Edit (16.0 KiB, text/plain)

Revision history for this message

oshunluvr (stuartksmith) wrote on 2009-10-27:

#14

uname.txt Edit (102 bytes, text/plain)

Revision history for this message

oshunluvr (stuartksmith) wrote on 2009-10-27:

#15

hallog.txt Edit (7.3 MiB, text/plain)

Revision history for this message

oshunluvr (stuartksmith) wrote on 2009-10-28:

#16

I am now seeing an additional udev/hal problem when using VirtualBox. I believe this is related to the above issue.

VitrualBox Error Message:
Could not access USB on the host system, because neither the USB file system (usbfs) nor the DBus and hal services are currently available. If you wish to use host USB devices inside guest systems, you must correct this and restart VirtualBox.
The USB Proxy Service could not be started, because neither the USB file system (usbfs) nor the hardware information service (hal) is available.

Revision history for this message

Oleg Blednov (blake-r) wrote on 2009-11-01:

#17

Jackallen, you method almost correct bug in my case. But need reboot, rather than just restart hal.

After that, I'm even reinstall hal and automount work correctly.

Revision history for this message

Martin Pitt (pitti) wrote on 2009-11-07:

#18

First, please have a look at bug 463347. The udev update there fixes a lot of those cases.

In Ubuntu 9.10 (Karmic), hal has nothing to do with hanlding storage devices any more, so poking it won't help.

If it still happens with the new udev, please do "ubuntu-bug", select "storage problem", and file a new bug with this (this will collect the necessary debug information). Please let me know the number here, so that I can link them.

Thanks!

Changed in devicekit-disks (Ubuntu):
status:	Confirmed → Incomplete

Revision history for this message

Giulio Malventi (giulio-people) wrote on 2009-11-09:

#19

Did not work for me. Opened bug #479206 as requested.

Revision history for this message

Scott James Remnant (Canonical) (canonical-scott) wrote on 2009-11-09:

#20

There's no udev bug here that I can see, sdc1 is present in the udev db and populated with the correct info (including blkid detecting it as fat16)

Revision history for this message

Martin Pitt (pitti) wrote on 2009-11-09:

#21

Giulio, you have a completely different problem. I followed up in bug 479206.

LarryGrower, as the original reporter you confirmed that it's working for you now, so I close this one.

Revision history for this message

Martin Pitt (pitti) wrote on 2009-11-09:

#22

Everyone else who has storage problems, please report a new bug using "ubuntu-bug storage". Thanks!

Changed in devicekit-disks (Ubuntu):
status:	Incomplete → Fix Released

Revision history for this message

brownknight (ramilclarin) wrote on 2010-01-24:

#23

I am having the same issue as oshunluvr on VirtualBox:
VitrualBox Error Message:
Could not access USB on the host system, because neither the USB file system (usbfs) nor the DBus and hal services are currently available. If you wish to use host USB devices inside guest systems, you must correct this and restart VirtualBox.
The USB Proxy Service could not be started, because neither the USB file system (usbfs) nor the hardware information service (hal) is avaiable.

andromedar (andromedar) on 2010-03-30

Changed in devicekit-disks (Ubuntu):
status:	Fix Released → Fix Committed
status:	Fix Committed → Fix Released

Ubuntu
devicekit-disks package

USB flash drive does not mount automatically

Bug Description

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntudevicekit-disks package

USB flash drive does not mount automatically

Bug Description

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
devicekit-disks package