GNOME Bugzilla – Bug 333220
Cannot switch CD-ROM device in sound-juicer using prefs
Last modified: 2014-03-24 16:38:26 UTC
Please describe the problem: I have multiple CD-ROM devices. The "Edit/Prefs" menu in sound-juicer completely fails to switch between them during a running sound-juicer instance. I can only switch devices by explicitly stating the device using --device= on the command line. The pref shows all the drives I have, but changing the value does not seem to affect the device used. Steps to reproduce: 1. Start sound-juicer normally, with multiple CD-ROMs installed 2. Switch devices using the prefs menu 3. Re-read the CD Actual results: sound-juicer attempts to read from the old, already set drive. Expected results: sound-juicer should read from the new drive. Does this happen every time? Yes Other information: In my case, the GConf key in /apps/sound-juicer/device is at the default of NULL. sound-juicer always wants to read using /dev/hdc. No matter what I change it to, it doesn't affect anything in the program, doesn't change the GConf key, and resets to reading from /dev/hdc when I restart. If I run sound-juicer --device=/dev/hdd it reads from /dev/hdd the one time, and cannot be changed to /dev/hdc during that run. If I manually set the device GConf key to /dev/hdd, then it runs off of /dev/hdd (and the pref defaults to that device), and cannot be changed from that no matter what device is selected in Edit/Preferences. Even with a non-NULL GConf key, the key is never written to, regardless of selection, and only one device (in this case the one specified by the key) can be used unless --device= is used at the command line. Changing the other prefs seems to work fine, such as "Eject on extract." Those changes take place immediately, are written to the GConf prefs, and are preserved for the next time sound-juicer is run. I assume that there's something wrong in the gconf-bridge stuff.
Confirmed, the selection widget isn't firing notify::device when the drive changes.
Fixed in nautilus-cd-burner, you'll need something later than 2.13.92 (I expect 2.14.0) though.