Bug 588242 - DVDROM drive tray immediately closes after using eject /dev/sr0 to eject a DVDROM disc when haldaemon service is started - when it is stopped, it doesn't do this and tray stays open
Summary: DVDROM drive tray immediately closes after using eject /dev/sr0 to eject a DV...
Alias: None
Product: Fedora
Classification: Fedora
Component: hal   
(Show other bugs)
Version: 12
Hardware: i686
OS: Linux
Target Milestone: ---
Assignee: Richard Hughes
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2010-05-03 08:43 UTC by Jasper O'neal Hartline
Modified: 2010-12-03 15:09 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-12-03 15:09:17 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Jasper O'neal Hartline 2010-05-03 08:43:51 UTC
Description of problem:
DVDROM drive tray immediately closes after using eject /dev/sr0 to eject a DVDROM disc when haldaemon service is started - when it is stopped, it doesn't do this and tray stays open

This machine has been fully updated from the updates-testing repository for i686 and running on the i686 kernel

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

How reproducible:

Steps to Reproduce:
1. Turn off all services, reboot, eject /dev/sr0 - tray stays open
2. Turn on haldaemon - chkconfig --level 35 haldaemon on - reboot
3. eject /dev/sr0 opens and immediately closes the drive tray
Actual results:
Tray closes all the time can't have 2 seconds to get a DVD data disc out.

Expected results:
Tray should stay open, as it does when haldaemon isn't running.

Additional info:
The DVDROM drive in question is the master on an IDE cable where the CDROM drive is a slave. The CDROM drive does not exhibit this same behaviour.

The kernel params I am using are these:

title Fedora (
	root (hd0,1)
	kernel /vmlinuz- ro root=UUID=eb5fa84b-7a5f-445d-8741-c8f04b038d0b  LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us selinux=0 rdblacklist=nouveau 5 libata.dma=3 elevator=deadline clocksource=hpet nomodeset
	initrd /initramfs-

Comment 1 Bug Zapper 2010-11-03 15:46:15 UTC
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '12'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 12 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 

Comment 2 Bug Zapper 2010-12-03 15:09:17 UTC
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

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