Bug 569641 - Sound Juicer could not find any CD-ROM drives to read
Summary: Sound Juicer could not find any CD-ROM drives to read
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: sound-juicer
Version: 12
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Bastien Nocera
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-03-01 22:13 UTC by Jaroslav Franek
Modified: 2010-12-03 22:10 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-12-03 22:10:09 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Jaroslav Franek 2010-03-01 22:13:07 UTC
Description of problem:

Trying to rip an audio CD. Firstly, I had to workaround bug #533643 to even be able to access the CD-ROM. Then I tried to run "Audio CD Extractor" from the KDE menu and got the nasty message saying no CD-ROM was found.


Version-Release number of selected component (if applicable):

sound-juicer-2.28.1-2.fc12.x86_64


How reproducible:

Always.


Steps to Reproduce:

1. Insert audio CD
2. make sure /dev/cdrom -> /dev/sr0  (bug #533643 workaround)
3. start "Audio CD Extractor"


Actual results:

Dialog box saying:
No CD-ROM drives found
Sound Juicer could not find any CD-ROM drives to read.


Expected results:

Well, CD-ROM is in the drive, it plays in vlc or kaffeine, it is visible in Dolphin, so expectation is Sound Juicer can read it too.


Additional info:

Ripping work fine with Dolphin, but Sound Juicer is my preferred application for ripping and I know it has worked fine back in Fedora 7,8.

Comment 1 Bug Zapper 2010-11-03 21:00:50 UTC
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  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 '12'.

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 12'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 12 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: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 2 Jaroslav Franek 2010-11-07 17:17:39 UTC
Retested with Fedora 14. Similar issue. The error text now reads:

"Sound Juicer could not read the track listing on this CD.
Reason: Cannot access CD: The specified location is
not mounted"

Probably not mounted, but at the same time Dolphin shows correctly the contents of the CD, including correct track info. And the CD plays in VLC media player. KDE does not offer any mount option for the audio CD to me.

But anyway, I have turned to other, working, SW for audio ripping, so I do not need this to be fixed.

Comment 3 Bug Zapper 2010-12-03 22:10:09 UTC
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 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.


Note You need to log in before you can comment on or make changes to this bug.