Hide Forgot
+++ This bug was initially created as a clone of Bug #697124 +++ Description of problem: I am running Fedora 14, 64 bit version. When I use the default program for copying files to a CD or DVD---which I understand is brasero, it seems to write them, except for requiring a manual ejection. But I have trouble reading the same CD (DVD) using the same system. I get an error message, and the disk doesn't appear on my desktop. Usually, if I click okay to the error message, I can go to Places, and I find the CD (DVD) which I can then open. But often the copied files are corrupted. I have this problem both with the built-in drive and an external USB drive. It doesn't seem to depend on the write speed. If I use Gnomebaker instead, I don't have problems creating the files disks or reading them. I don't have similar problems on another machine running Fedora 13. Version-Release number of selected component (if applicable): brasero-2.32.0-1.fc14.x86_64 brasero-nautilus-2.32.0-1.fc14.x86_64 How reproducible: I always have some problems but sometimes the files are copied correctly. Steps to Reproduce: 1. Put a CD (DVD) in a drive. 2. Choose files to write to the CD (DVD) and write them. I am told the writing was a success, but then after the checksum is done, I am asked to manually eject. 3. When I put the same disk back in either of my two drives, I get an error message, and no icon appears on my desktop. I can then open the disk by going to Places, but usually the files have been corrupted. Actual results: See above Expected results: The files should be written to the disk and it should be ejected. If I reinsert the disk in either of my two drives, an icon should appear on my desktop and the contents should be displayed in a window. Using cmp to compare the files with the originals should show they are identical. Additional info: Gnomebaker works as expected. I believe that when I did not have the problem right after I installed Fedora 14, but it developed recently.
Exactly the same bug exists in Fedora 15 (x86-64). Brasero (or Nautilus) always asks for manually eject after checksum checking. After ejecting 4 of 5 disk becomes unusable. I'm sure it's not a hardware problem, it's a brand new Thinkpad and I get 100% success rate with k3b.
I am getting exactly the same problem on Fedora 16, 64 bit. My hardware is a "DVD+-RW GS30N" (builtin drive in my laptop), and the problem only seems to happen with Brasero. Like the original reporter, it reports the burning as successful, but the resulting discs are garbage (can't be read on either Windows or Linux, I tried multiple machines and even a CD player). K3B works just fine though. Interestingly, this only happens with data or audio projects. Burning ISO images to disc works with Brasero.
The problem still exists on Fedora 17 (64 bit). However, I have found out what triggers this. Unchecking the option "Burn the image directly without saving it to disc" burns a valid disc. So the problem only occurs when leaving that checkbox enabled (which is the default setting and will be reset with each start of Brasero it seems)
I found this upstream, seems to be a known problem. https://bugzilla.gnome.org/show_bug.cgi?id=655601
*** Bug 892131 has been marked as a duplicate of this bug. ***
Similar bug on other distribution: https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/780117
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. 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 '17'. 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 17'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 17 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 change the 'version' to a later Fedora version prior to Fedora 17's end of life. 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.
Bug still there in Fedora 18 but I cannot update the version because I am not the owner of the bug.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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.