Bug 139231
| Summary: | nautilus cd burning fails regularly | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Markus Bertheau <twanger> |
| Component: | nautilus-cd-burner | Assignee: | Alexander Larsson <alexl> |
| Status: | CLOSED DUPLICATE | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3 | CC: | james, stelian, stephen.walton, tgl |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2005-12-16 11:02:24 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Markus Bertheau
2004-11-14 10:31:26 UTC
I've noticed this too: all the file entries are there, but only about 60%-70% of the actual data is written. I seem to be able to use cdrecord OK, though. This is with kernel 2.6.10-1.770_FC3smp on my HP zx5030EA notebook with an HL-DT-STCD-RW/DVD GCC-4241N combined DVD reader/CD-R(W) writer. I'm seeing this problem with FC4 and nautilus-cd-burner-2.10.0-2 There is no error message, and nautilus claims that the CD was burned successfully. cdrecord works perfectly fine. I have some input on this bug. I just installed k3b on my FC3 system (a Dell Precision 350), and it burns CD's with no difficulty. The disks passed md5sum checking with the usual "dd if=/dev/hdc | md5sum", for example (contrary to http://www.redhat.com/archives/fedora-test-list/2004-November/msg00875.html which says that one has to use ide-scsi for this on 2.6 kernels). This same computer consistently fails to produce usable burned CD's with nautilus-cd-burner. I used ps to find out what commands k3b and nautilus-cd-burner was using to do the actual burn. For k3b it was /usr/bin/cdrecord -v gracetime=2 dev=/dev/hdc speed=8 -dao driveropts=burnfree -eject -data /mnt/t/swalton/rhelws4/RHEL4-U1-i386-WS-disc4.iso while for nautilus-cd-burner it was cdrecord dev=/dev/hdc -eject -v -data -nopad /mnt/t/swalton/rhelws4/RHEL4-U1-i386-WS-disc4.iso Running the second command above at a shell prompt shows that cdrecord's defaults on my machine are: -tao, no burnfree, and 32x write speed. Just one more followup: I found that simply adding -dao to the list of options used for cdrecord by nautilus-cd-burner seems to fix the problem. As of this writing, I've burned two CD's this way and both pass md5sum checking. This is beginning to look more like a cdrecord bug than a nautilus-cd-burner bug, per se. I tried to open a new report against cdrecord, but it doesn't appear in the list of fc3 components on the bugzilla report page. See also bug #160191, which suggests that the -nopad option might be the issue. |