[KARMIC] USB storage not auto mounting on Acer Aspire One
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| linux (Ubuntu) |
Won't Fix
|
Medium
|
Unassigned | ||
Bug Description
Inserted USB storage storage device into Acer Aspire One, did not auto-mount and read contents.
ProblemType: Bug
AplayDevices:
**** List of PLAYBACK Hardware Devices ****
card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
Architecture: i386
ArecordDevices:
**** List of CAPTURE Hardware Devices ****
card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0x58540000 irq 16'
Mixer name : 'Realtek ALC268'
Components : 'HDA:10ec0268,
Controls : 9
Simple ctrls : 6
CheckboxTest: 023_usb_access
Date: Fri Sep 18 20:34:40 2009
DistroRelease: Ubuntu 9.10
HibernationDevice: RESUME=
MachineType: Acer AOA110
Package: linux-image-
PccardctlIdent:
PccardctlStatus:
ProcCmdLine: BOOT_IMAGE=
ProcEnviron:
SHELL=/bin/bash
LANG=en_US.UTF-8
ProcVersionSign
RelatedPackageV
linux-
linux-firmware 1.18
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
Tags: checkbox-bug
Uname: Linux 2.6.31-10-generic i686
dmi.bios.date: 05/09/2008
dmi.bios.vendor: Acer
dmi.bios.version: v0.3305
dmi.board.
dmi.board.vendor: Acer
dmi.board.version: Base Board Version
dmi.chassis.type: 1
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.
dmi.modalias: dmi:bvnAcer:
dmi.product.name: AOA110
dmi.product.
dmi.sys.vendor: Acer
| Changed in linux (Ubuntu): | |
| importance: | Undecided → Medium |
| status: | New → Triaged |
| tags: | added: kj-triage |
| tags: | added: acpi-namespace-lookup |
| tags: | added: acpi-parse-exec-fail |
| tags: | added: karmic |
| Changed in linux (Ubuntu): | |
| status: | New → Confirmed |
| tags: | added: b73a1py79 |

Could you check whether it is really the automount part that fails for you or possibly "only" the nautilus window opening as a result of that? If you insert your usb key and wait a while, do you get a directory in /media which is either named disk or have the name of the volume label of the usb keys partitions? This is what I see here: the mount is done ok but opening the nautilus window seems rather unreliable.