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 392591 - Alert about "The currently selected audio profile" is not understandable
Alert about "The currently selected audio profile" is not understandable
Status: RESOLVED OBSOLETE
Product: sound-juicer
Classification: Applications
Component: interface
2.16.x
Other Linux
: Normal normal
: ---
Assigned To: Sound Juicer Maintainers
Sound Juicer Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-01-04 03:08 UTC by Matthew Paul Thomas (mpt)
Modified: 2021-05-17 15:57 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description Matthew Paul Thomas (mpt) 2007-01-04 03:08:44 UTC
Rhythmbox 0.9.6, Ubuntu 6.10

Upon inserting a music CD, Rhythmbox presented me with an alert which (from searching Bugzilla) seems to come from gnome-media. (Please move this bug report if I'm mistaken.) The alert reads:

    The currently selected audio profile is not available on your
    installation.

                                      ( Quit ) ( Change Profile )

I'm fairly knowledgable about computers, but I have *no idea* what this means. Explain it to me, and I'll have a go at turning it into a useful message. :-)

Also, the "?" icon for the alert is inappropriate (it's not asking a question), "Quit" doesn't quit (it just closes the alert), and "Change Profile" doesn't change any profile (it opens Rhythmbox's Preferences window instead). The appropriate fixes for each of these problems depend heavily on what the alert is supposed to be saying.
Comment 1 Ronald Bultje 2007-01-06 18:49:17 UTC
-> rhythmbox? maybe it's a sound-juicer bug, though, dunno...
Comment 2 Reinout van Schouwen 2007-01-06 19:47:30 UTC
Some more info on sound profiles in Aaron Bockover's blog: 
http://abock.org/2007/01/06/audio-profile-configuration-for-the-masses/
Comment 3 Matthew Paul Thomas (mpt) 2007-01-06 23:09:50 UTC
You're right, the problem also occurs when running -> Sound Juicer by itself. (Boo to non-integrated music management!)
Comment 4 Ronald Bultje 2007-01-07 00:29:28 UTC
As for the usefulness of the message, it probably means something like "vorbis encoder not found" (in this case). I'm thoroughly confused as for why it'd open the RB preferences instead of the s-j one.

RB should really have a CD source for itself and offer to play it. Only if the user wants to rip them, should it open s-j. The error that s-j gives would be a lot easier to understand in that context, although it still lacks details and apparently offers no proper way to fix the error. :-).
Comment 5 Matthew Paul Thomas (mpt) 2007-01-07 01:20:41 UTC
Ronald, you're right too, it's Sound Juicer's Preferences that are opened. (I thought they were Rhythmbox's because that was the program I had open.) Nevertheless, clicking the button still isn't changing any profile.
Comment 6 Sven Arvidsson 2007-09-29 19:22:35 UTC
[ From http://bugs.debian.org/436986 ]

A Debian user has reported a similar problem. In this case /system/gstreamer/0.10/audio/global/profile_list which should contain a list of encoding profiles was empty. I'm not sure why, as the schemas file was properly installed and owned by gnome-media. 

The easiest way to get this working again is to unset the key (so it picks up the default profiles). I'm guessing that s-j (or gnome-media) should either offer a way to reset this, or automatically reset it if the key is empty.
Comment 7 Matthew Paul Thomas (mpt) 2007-10-11 11:52:37 UTC
This bug report is not about whatever problems cause the error message; it is about the uselessness of the error message itself.
Comment 8 GNOME Infrastructure Team 2021-05-17 15:57:17 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/sound-juicer/-/issues/61.