Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 183731 - Cannot switch CD-ROM device in sound-juicer using prefs
Cannot switch CD-ROM device in sound-juicer using prefs
Product: Fedora
Classification: Fedora
Component: sound-juicer (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Need Real Name
Depends On:
  Show dependency treegraph
Reported: 2006-03-03 02:05 EST by John Thacker
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-03-14 10:48:09 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
GNOME Bugzilla 333220 None None None Never

  None (edit)
Description John Thacker 2006-03-03 02:05:12 EST
Description of problem:
sound-juicer has a prefs window that is supposed to allow one to update the
CD-ROM device.  Currently, it doesn't do anything.  I have two CD-ROM devices,
and sound-juicer only wants to read from one of them regardless of what I select
in Prefs, unless I explicitly start sound-juicer with the --device= option.

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

How reproducible:

Steps to Reproduce:
1. Have two CD-ROM devices
2. Start sound-juicer
3. Try to switch drives in "Edit/Preferences"
Actual results:
sound-juicer does not switch to the selected drive.

Expected results:
sound-juicer switches to reading from the selected drive.

Additional info:
Comment 1 John Thacker 2006-03-04 10:40:46 EST
It's apparently the fault of nautilus-cd-burner.  It's been fixed in upstream
nautilus-cd-burner CVS, though it hasn't been released yet.  Should be in the
next release after 2.13.92.  See the GNOME bug 333220
Comment 2 John Thacker 2006-03-14 10:48:09 EST
Fixed upstream and now in Rawhide with GNOME 2.14

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