After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 674191 - CD Drive widget does not show selected drive
CD Drive widget does not show selected drive
Status: RESOLVED FIXED
Product: sound-juicer
Classification: Applications
Component: interface
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Sound Juicer Maintainers
Sound Juicer Maintainers
Depends on:
Blocks:
 
 
Reported: 2012-04-16 10:41 UTC by Michael Monreal
Modified: 2013-10-09 14:22 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Screenshots (10.32 KB, image/png)
2012-04-16 10:41 UTC, Michael Monreal 		Details

Description Michael Monreal 2012-04-16 10:41:54 UTC 
Created attachment 212130 [details]
Screenshots

In sound-juicer 3.4.0, running under GNOME 3.4 with the default theme, the "CD Drive" widget in the preferences does not show the selected drive. Clicking the widget will show a list containing my drive, selecting it produces an empty widget, as seen in the screenshot.
Comment 1 Phillip Susi 2013-02-18 22:46:32 UTC 
I see this too.
Comment 2 Phillip Susi 2013-02-19 02:58:18 UTC 
I noticed something odd.  If I load the scsi_debug module to simulate having a second CDROM, the list works properly and shows the currently selected drive, so it only seems to fail to show the current drive when it is the only drive detected.
Comment 3 Phillip Wood 2013-10-08 17:42:24 UTC 
I have this problem as well, I think this was a bug in brasero which was fixed fairly recently - https://git.gnome.org/browse/brasero/commit/?id=4cdec3b2aa5e726714d34fff003480403ae6ae77

Running under jhbuild with a recent version of brasero which includes that commit fixes the problem for me. The fix is in brasero 3.10
Comment 4 Phillip Susi 2013-10-08 19:16:38 UTC 
There is no 3.10; the last release is 3.8.

The commit log sounds promising though, I will have to try it tonight and hopefully it fixes it.
Comment 5 Phillip Susi 2013-10-09 02:15:37 UTC 
Yep, that did the trick.
Comment 6 Phillip Wood 2013-10-09 14:22:13 UTC 
(In reply to comment #4)
> There is no 3.10; the last release is 3.8.

Sorry I should have checked I just presumed there was a 3.10 release

(In reply to comment #5)
>Yep, that did the trick.

That's great, thanks for testing it