Red Hat Bugzilla – Bug 135184
xcdroast unable to identify data disk
Last modified: 2008-05-06 11:27:30 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3)
Description of problem:
When reading a disk, xcdroast identifies all disks as audio disk when
clearly they are data disks. This makes xcdroast unable to make copies
of data disks.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Insert data CD-ROM, CD-R, CD-RW, DVD-ROM, DVD(+-)R, DVD(+-)RW
2. Run xcdroast
3. Click on Duplicate CD/DVD button
Actual Results: Disks are identified as audio disk and data tracks
identified as audio tracks
Expected Results: Disk should be identified as data disk and tracks
as data tracks
Previous rpms for xcdroast works as expected.
which kernel do you have?
Kernel version is kernel-2.6.8-1.521
then this maybe a duplicate of bug #130576
Bug #13056 relates to writing. My problem relates to reading. They may
or may not be the manifestation of the same bug. Not being familiar
with kernel code I cannot say.
I have kernel 2.6.9-1.6_FC2 and the problem is still there on three
different platform (Dell Precision 530 (smp), Dell Latitude D800,
Dell Latitude X300). It is a very nasty bug, it makes xcdroast pretty
unusable (apart from plain audio CD's). The bug related to writing
was specific to 2.6.8-1.521, it is no longer there with 2.6.9-1.6_FC2
Fedora Core 2 is now maintained by the Fedora Legacy project for
security updates only. If this problem is a security issue, please
reopen and reassign to the Fedora Legacy product. If it is not a
security issue and hasn't been resolved in the current FC3 updates or
in the FC4 test release, reopen and change the version to match.
Confirmed on Fedroa 3. The bugs is still there (checked on a Dell Precision 670),
whichever data CD is recognized as an audio CD and no copy can be successfully
I could'nt reopen or change the version to fc3 beacuse:
"You tried to change the Version field from fc2 to fc3, but only the owner or
submitter of the bug, or a sufficiently empowered user, may change that field."
-> fc3 as per comment #7
Fedora Core 3 is now maintained by the Fedora Legacy project for security
updates only. If this problem is a security issue, please reopen and
reassign to the Fedora Legacy product. If it is not a security issue and
hasn't been resolved in the current FC5 updates or in the FC6 test
release, reopen and change the version to match.
Same issues in FC5
(marking as info provided.)
Fedora Core 5 is no longer maintained. Is this bug still present in Fedora 8?
Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.
If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.
If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
Thanks for your help, and we apologize again that we haven't handled
these issues to this point.
The process we are following is outlined here:
We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.
And if you'd like to join the bug triage team to help make things
better, check out http://fedoraproject.org/wiki/BugZappers
This bug is open for a Fedora version that is no longer maintained and
will not be fixed by Fedora. Therefore we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen thus bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.