Red Hat Bugzilla – Bug 450945
Impossible to get any data from CD-Extra
Last modified: 2009-07-14 13:58:16 EDT
1. Insert a CD-Extra disc
CD-Extra means that it contains music and data.
2. GNOME creates an icon called "Audio CD"
Previous version asked about what to do, now it doesn't
3. There is no way to access data from CD, only manual method works fine
mount -t iso9660 /dev/cdrom /mnt/cdrom
4. Result: User can't get any data from CD without performing non-standard
(In reply to comment #0)
> 1. Insert a CD-Extra disc
> CD-Extra means that it contains music and data.
You have to be a lot more specific here. Do you mean a "mixed CD"?
> 2. GNOME creates an icon called "Audio CD"
> Previous version asked about what to do, now it doesn't
I believe we do. See the "Media" tab in the System->Preferences->Personal->File
Management preference item. In particular, select "Ask what to do" for CD Audio.
> 3. There is no way to access data from CD, only manual method works fine
> mount -t iso9660 /dev/cdrom /mnt/cdrom
> 4. Result: User can't get any data from CD without performing non-standard
Please attach the output of 'lshal' and 'gvfs-mount -li'.
More concretely, the way things work is that we mount both the audio part and
the data part. That is a change from Fedora 9 and GNOME 2.22.
Reassigning to gvfs since that's where the bug might be.
(In reply to comment #2)
> That is a change from Fedora 9 and GNOME 2.22.
Created attachment 309001 [details]
In "Media" tab in the System->Preferences->Personal->File Management preference
item everything is set to "Ask me first".
Forgive me lack of precision - yes, I meant mixed CDs
Comment on attachment 309001 [details]
(In the future, please avoid uploading zip files. Upload plain text files and
select the proper MIME type. Thanks.)
volume.disc.has_audio = true (bool)
volume.disc.has_data = true (bool)
volume.disc.is_appendable = false (bool)
volume.disc.is_blank = false (bool)
volume.disc.is_rewritable = false (bool)
volume.disc.type = 'cd_rom' (string)
volume.fstype = '' (string)
volume.fsusage = '' (string)
volume.fsversion = '' (string)
Apparently we don't discover a file system so we only show the data parts. Is
the data on the first track? If you don't know try mounting the audio bits and
paste (no attachment please) the output of 'gvfs-ls cdda://sr0/'
Can you paste (no attachment please) the output of
The data is on the last track - traditionally.
[root@IBM-Fedora ~]# /lib/udev/vol_id /dev/sr0
/dev/sr0: unknown volume type
And... that's all.
Right, we need vol_id to be smart about that. I talked to the upstream
maintainer about that the other day. Moving to udev for now; I expect we can
close this pretty soon.
does it work for F10?
This message is a reminder that Fedora 9 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 9. 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 '9'.
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 9'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 9 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:
Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 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.