Description of problem: After burning an ISO image successfully to disk and verification of the image checksum, a window pops up prompting the user to eject the disk manually. "Please eject the disc from "HP DVD Writer 840b" manually. The disc could not be ejected though it needs to be removed for the current operation to continue." In a second window, the progress bar labeled "Eject medium" moves forth and back without ever ending. After pressing the "Cancel" button of the first window, brasero reports "Image successfully burned to CD", yet, the disk is not ejected. Version-Release number of selected component (if applicable): brasero-2.32.0-1.fc14.x86_64 How reproducible: Always. Steps to Reproduce: 1. Burn ISO image to CD. Actual results: After burning the image, the verification process never completes. Expected results: After successful verification of the burn process, the CD is ejected. Additional info: Running 'eject -t' ejects the CD without issues.
I have had the same issue on multiple machines with different hardware. In fact since Fedora 12 that is the case every time on all machines. Brasero will not properly eject CD or DVD after burn completes. Machines: Compaq CQ60-206US laptop Dell Optiplex GX260 Desktop tower eMachine E528 laptop All of the above have original equipment and 2 of them (the laptops) are newer and have sata DVD-RW drives while the older Dell has an older IDE CD-RW drive. As stated by the OP the 'eject' command works fine from the command line. Testing with Ubuntu and Mint I do not seem to have these issues.
Sorry for quick re-post but I forget to mention that the machines listed are only what I currently have and not an overall list of all machines that I have seen this on. As of right this minute I have just completed burning Fedora 15 Beta on a CD and I received this message on the eMachine laptop: 'Please eject the disc from "MATSHITA DVD-RAM UJ890AS" manually.'
Issue still present for current F15 including packages: - brasero-3.0.0-2.fc15 - wodim-1.1.11-8.fc15
Still present with F16. brasero-3.2.0-1.fc16
I had this same problem on F15 although if I hit the eject button the CD would eject and Brasero would end up giving me an OK and the CD had been burned OK. I recently installed F17. Brasero gets a bit further. It ejects the CD/DVD OK but doesn't recognize that it has. If I let it timeout it will display the eject error. Once you click OK on the error message it then says that the CD/DVD was burned OK. I turned on the debugger and saw that it's timing out waiting for a response from the eject command in GLib2 (g_drive_eject_with_operation()). After 5 timeouts it gives the eject error for you to manually eject the CD/DVD. You might want to run brasero in debugging mode to see if it's the same problem on F15/16. In a shell type brasero -g for brasero_burn debugging or brasero --brasero-media-debug (this is where I saw the timeout error). It appears to be a problem in GLib2. As I have a workaround I'll be less pressured to dig into GLib2. I'm currently on F17 3.6.2-4-PAE 32---bit x86 with a BENQ DW1650 DVD drive and brasero-3.4.1-1. This problem doesn't seem to be high on priority since it's been around for a few years. I seem to remember that it all worked back in F13/14 days.
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. 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 '16'. 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 16'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 16 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, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. 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: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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.