Bug 477026 – Disc does not eject when finished

Bug 477026 - Disc does not eject when finished

Summary:	Disc does not eject when finished

Status:	CLOSED NOTABUG

Aliases:	None

Product:	Fedora
Classification:	Fedora
Component:	asunder (Show other bugs)
Sub Component:
Version:	10
Hardware:	i686 Linux

Priority	low Severity low
Target Milestone:	---
Target Release:	---
Assigned To:	Marcin Zajaczkowski
QA Contact:	Fedora Extras Quality Assurance
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2008-12-18 13:34 EST by Matt Castelein
Modified:	2008-12-21 13:21 EST (History)
CC List:	1 user (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2008-12-21 13:21:18 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Matt Castelein 2008-12-18 13:34:57 EST

Description of problem:
Preferences set to "Eject disc when finished," but disc does not eject.

Version-Release number of selected component (if applicable):
asunder-1.6-1.fc10.1386

Comment 1 Matt Castelein 2008-12-18 13:51:05 EST

So far this has happened for 3 of 4 cds, and the 4th ejected.

Comment 2 Marcin Zajaczkowski 2008-12-21 09:20:49 EST

Thank you for reporting the problem.

Usually I don't use that option, so I didn't notice that behavior earlier. I have checked that after your report (in FC8), but it seems to work fine for me.
Is it possible that you had an another application (like CD player or terminal/bash placed in CD directory) which could prevent OS from unmounting that CD?
Maybe there were some error messages in the console (if you started asunder from a terminal)?

Comment 3 Matt Castelein 2008-12-21 13:21:18 EST

I did not see any messages when running from console, however it has been working for me recently so I must guess there was some process interfering in the background..

Note You need to log in before you can comment on or make changes to this bug.