Camera (usb mass storage) no longer automounted in Gutsy

Bug #155610 reported by Menno
6
Affects Status Importance Assigned to Milestone
hal (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: hal

The memory of my camera (Nikon Coolpix 2000) used to get automounted in Feisty, but doesn't in Gutsy anymore; nothing happens.

When I put the Flashcard of my camera in my cardreader, it is mounted and recognised as a picture carrier (bringing up the camera dialogue).
USB sticks are automounted too, even a strange one that has no partitions (actually, an mp3 player - even, the mp3 player pops up).
To be sure, that the fault isn't in the camera, I booted Feisty from the Live CD (7.04 from April 2007) and connected the camera: this was still working fine.

The relevant part of dmesg output (Gutsy) is here:

[15082.688000] usb 1-6: new full speed USB device using ohci_hcd and address 3
[15082.956000] usb 1-6: configuration #1 chosen from 1 choice
[15082.960000] scsi7 : SCSI emulation for USB Mass Storage devices
[15082.960000] usb-storage: device found at 3
[15082.960000] usb-storage: waiting for device to settle before scanning
[15087.960000] usb-storage: device scan complete
[15087.968000] scsi 7:0:0:0: Direct-Access NIKON DSC E2000 1.00 PQ: 0 ANSI: 2
[15087.988000] sd 7:0:0:0: [sdf] 1018081 512-byte hardware sectors (521 MB)
[15087.996000] sd 7:0:0:0: [sdf] Write Protect is off
[15087.996000] sd 7:0:0:0: [sdf] Mode Sense: 04 00 00 00
[15087.996000] sd 7:0:0:0: [sdf] Assuming drive cache: write through
[15088.012000] sd 7:0:0:0: [sdf] 1018081 512-byte hardware sectors (521 MB)
[15088.016000] sd 7:0:0:0: [sdf] Write Protect is off
[15088.016000] sd 7:0:0:0: [sdf] Mode Sense: 04 00 00 00
[15088.016000] sd 7:0:0:0: [sdf] Assuming drive cache: write through
[15088.016000] sdf: sdf1
[15088.032000] sd 7:0:0:0: [sdf] Attached SCSI removable disk
[15088.032000] sd 7:0:0:0: Attached scsi generic sg5 type 0

Attempts to mount the device manually fail also:
- sdf1 is reported not present
- sg5 is 'not a block device'

To compare, I've also included the corresponding dmesg output from Feisty:

[ 258.268000] usb 2-6: new full speed USB device using ohci_hcd and address 2
[ 258.516000] usb 2-6: configuration #1 chosen from 1 choice
[ 258.520000] scsi3 : SCSI emulation for USB Mass Storage devices
[ 258.520000] usb-storage: device found at 2
[ 258.520000] usb-storage: waiting for device to settle before scanning
[ 263.520000] usb-storage: device scan complete
[ 263.528000] scsi 3:0:0:0: Direct-Access NIKON DSC E2000 1.00 PQ: 0 ANSI: 2
[ 263.548000] SCSI device sdf: 1018081 512-byte hdwr sectors (521 MB)
[ 263.556000] sdf: Write Protect is off
[ 263.556000] sdf: Mode Sense: 04 00 00 00
[ 263.556000] sdf: assuming drive cache: write through
[ 263.572000] SCSI device sdf: 1018081 512-byte hdwr sectors (521 MB)
[ 263.580000] sdf: Write Protect is off
[ 263.580000] sdf: Mode Sense: 04 00 00 00
[ 263.580000] sdf: assuming drive cache: write through
[ 263.580000] sdf: sdf1
[ 263.592000] sd 3:0:0:0: Attached scsi removable disk sdf
[ 263.592000] sd 3:0:0:0: Attached scsi generic sg5 type 0
<...>
[ 389.076000] usb 2-6: USB disconnect, address 2

The last line is a result of unmounting the device.

The mount command of Fiesty shows the following:

<...>
/dev/sdf1 on /media/SANVOL type vfat (rw,nosuid,nodev,shortname=mixed,uid=999,utf8,umask=077)
<...>

Revision history for this message
Samuel Magruder (bertmag101) wrote :

I have the same problem. My camera is a Nikon D40x. Had no problems in Feisty, but will not mount as a device in Gutsy. Other USB devices (printer, card reader) seem to mount without problem as does my external hard drive. However (and I include this only because it may have some bearing I cannot see) the system generates TWO icons on the desktop for ONE of my external hard drive partitions although it only shows up once in the "media" directory.

Revision history for this message
Brian Murray (brian-murray) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description didn't include enough information.
Please follow the 'How to file' procedure described at https://wiki.ubuntu.com/DebuggingHal and attach the requested files here.

Changed in hal:
status: New → Incomplete
Revision history for this message
Brian Murray (brian-murray) wrote :

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and feel free to submit bug reports in the future.

Changed in hal:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.