Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 108030 - Cannot unmount and eject cdrom
Summary: Cannot unmount and eject cdrom
Keywords:
Status: CLOSED DUPLICATE of bug 106936
Alias: None
Product: Fedora
Classification: Fedora
Component: fam
Version: rawhide
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Alexander Larsson
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-10-26 17:52 UTC by bednar
Modified: 2007-11-30 22:10 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-02-21 18:59:26 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description bednar 2003-10-26 17:52:46 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1) Gecko/20031009

Description of problem:
After reading from CD I can't unmount CD. I get message that CD is in use. I
know that it is not true, because in CLI I wrote cd / and I closed all windows
with CD content. I tested it only under Gnome 2.4. After killing fam I can
unmount and eject CD.

Version-Release number of selected component (if applicable):
fam-2.6.8-12

How reproducible:
Sometimes

Steps to Reproduce:
1. Put CD in the drive.
2. cd /mnt/cdrom (under CLI)
3. Run a binary executable from cd (if you have set exec flag for the CD drive
in /etc/fstab)
4. cd /
5. try to umount /mnt/cdrom

    

Actual Results:  device is in use

Expected Results:  normal unmounting

Additional info:

This bug makes your work the mission impossible (try to install 3 CD of matlab)
Comment 1 Bill Nottingham 2003-10-27 03:01:27 UTC 

*** This bug has been marked as a duplicate of 106936 ***
Comment 2 Red Hat Bugzilla 2006-02-21 18:59:26 UTC 
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.
Note You need to log in before you can comment on or make changes to this bug.