Red Hat Bugzilla – Bug 187602
gnome-cd crashes on /dev/hdd but not on /dev/cdrom
Last modified: 2008-05-04 06:59:20 EDT
gnome-cd works correctly if the device name is exactly /dev/cdrom.
However is segfaults on any other device name, that point
to the the same device.
/dev/cdrom is linked to hdd, so is /dev/cdwriter
gnome-cd crashes on /dev/hdd and /dev/cdwriter, but not on /dev/cdrom.
When clicking on the audio cd icon that appears when an
audio cd is inserted, gnome-cd is started as:
gnome-cd --unique --play --device /dev/hdd
therefore it crashes.
I confirm this is still an issue in FC6. Hardware is a dual-core AMD 4400+,
running 64-bit, in case this makes a difference. The device name for gnome-cd
must be exactly /dev/cdrom, no other device works. Doesn't matter if /dev/cdrom
is a link or the actual device.
Can you generate a backtrace for the crash, with -debuginfo packages for
gnome-media, gtk2 and glib2 installed.
Created attachment 141961 [details]
Stack trace from gnome-cd
Seems to be a gstreamer crash, related to gst_cd_paranoia.
Could you do the same with also debuginfo packages for gstreamer and cdparanoia?
Created attachment 141993 [details]
stack trace with gstreamer and cdparanoia debuginfo packages.
In cdparanoia source in file scan_devices.c in function sgio_cdda_identify_scsi
is this test:
Function check_fd_sgio returns value < 0, on error or argement if ok. For some
unknown reason when device other as /dev/cdrom is used (/dev/hdc /dev/hdd)
cdda_fd = 0 is opened (this is valid fd, but zero) and check fails and
s2_init_sg_info is used (which is wrong). Check should be changed to:
if (check_fd_sgio(d->cdda_fd) == d->cdda_fd)
I will test this when I have time (currently this is not tested).
Created attachment 143445 [details]
patch against rpmbuild SOURCE directory
Attached is patch against rpmbuild SOURCE dirctory - for me it fixes this
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
I can no longer duplicate this with either Fedora 7 or 8; suggest it be
considered closed or change status to "CurrentRelease"?
Thank you for the bug report. Closing bug as per comment #10.