Optical drives not unmounting when media removed
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Expired
|
Low
|
Unassigned |
Bug Description
ITEM the FIRST: Lucid seems to have some issue with unmounting optical drives after a disc has been ejected via the physical button on the drive, as well as not automatically mounting (that is, autorunning/
WORKAROUND:
ITEM the SECOND: So far I've had success by opening 'Computer' with Nautilus, right-clicking the media in question and selecting 'unmount' or 'eject'. Trouble arises when ejecting disks from the drive rather than the software, as Lucid won't automatically unmount.
ITEM the THIRD: Initial attempt was to edit fstab so that Lucid would have explicit instructions on what to do with its optical drives. Spent some time looking up fstab examples and documentation to figure out what options would make it work. Attempts so far didn't work out, but I have a feeling this will be the best fix until Canonical releases a patch. Regarding the floppy issue, removing its line from fstab keeps the floppy from appearing in Nautilus, but it still seems to be mounted under '/media/floppy'. Haven't figured out why.
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: linux-image-
Regression: Yes
Reproducible: Yes
ProcVersionSign
Uname: Linux 2.6.32-24-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: i386
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'V8237'/'VIA 8237 with ALC655 at 0xe000, irq 22'
Mixer name : 'Realtek ALC655 rev 0'
Components : 'AC97a:414c4760'
Controls : 48
Simple ctrls : 29
Date: Fri Aug 27 11:27:12 2010
GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit.
HibernationDevice: RESUME=
HotplugNewDevices:
HotplugNewMounts:
IwConfig:
lo no wireless extensions.
eth2 no wireless extensions.
MachineType: Gateway T3104
ProcCmdLine: BOOT_IMAGE=
ProcEnviron:
LANG=en_US.utf8
SHELL=/bin/bash
RelatedPackageV
RfKill:
SourcePackage: linux
Symptom: storage
UdevMonitorLog:
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
UdisksMonitorLog: Monitoring activity from the disks daemon. Press Ctrl+C to cancel.
dmi.bios.date: 07/26/2005
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 6.00 PG
dmi.board.name: K8M-800M
dmi.board.vendor: First International Computer, Inc.
dmi.board.version: PCB 2.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gateway
dmi.modalias: dmi:bvnPhoenixT
dmi.product.name: T3104
dmi.product.
dmi.sys.vendor: Gateway
tags: | added: acpi-method-return |
Changed in linux (Ubuntu): | |
status: | New → Confirmed |
Sean Ellefson, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http:// cdimage. ubuntu. com/releases/ .
If it remains an issue, could you run the following command in the development release from a Terminal (Applications- >Accessories- >Terminal) . It will automatically gather and attach updated debug information to this report.
apport-collect -p linux <replace- with-bug- number>
Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https:/ /wiki.ubuntu. com/KernelMainl ineBuilds . Please do not test the kernel in the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please remove the 'needs- upstream- testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs- upstream- testing' text. As well, please comment on which kernel version specifically you tested.
If this bug is fixed in the mainline kernel, please add the following tag 'kernel- fixed-upstream' .
If the mainline kernel does not fix this bug, please add the tag: 'kernel- bug-exists- upstream' .
If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel- unable- to-test- upstream' , and comment as to why specifically you were unable to test it.
Please let us know your results. Thanks in advance.