- Package:
- sound-juicer
- Source:
- sound-juicer
- Description:
- GNOME CD Ripper
- Submitter:
- Marcus Lundblad
- Date:
- 2021-05-17 17:21:19 UTC
- Severity:
- normal
- Tags:
The first time I ran SoundJuicer on this machine, which was freshly installed with Lenny in late June, it pops up a dialog saying "The current sound profile is not available in your installation". There is two options, "Cancel" and "Change profile". If I do "Change profile" I get the settings window and the format drop-down is empty. On my other machine (laptop) which I installed when Etch was in testing in late February it worked out of the box. I sucessfully ripped to Flac. Is there some Gstreamer-related stuff missing, perhaps?
Does installing gnome-media-common solve the issue for you?
And this is the same on both machines. So there must be something else conflicting or something like that...
I managed to fix this: The problem was that the following gconf-key was empty: /system/gstreamer/0.10/audio/global/profile_list So I inserted keys into this (list) for the profiles given by these keys: /system/gstreamer/0.10/audio/profiles/* The problem seems to be that this Gconf directory has been carried over from my old machine, which has been running Testing since 2004 (Sarge).
Those entries should be default be populated from the default settings from /usr/share/gconf/schemas/gnome-audio-profiles.schemas (from the gnome-media-common package). Can you make sure that this file is present on your system? If it is, check in gconf-editor if it says "Key owner: gnome-media" for that key.
Hi, Yes, the schema file is present and is owned by gnome-media-commons (according to dpkg -S).- Also the keys all have owner gnome-media. //Marcus
Hi again, I'm still not sure why the list of profiles was gone after the upgrade, but it seems to happen to a few people as it's also mentioned in this launchpad bug; https://bugs.launchpad.net/sound-juicer/+bug/67621 Sound Juicer should handle this situation, or at least give a better error message, this upstream bug tracks this; http://bugzilla.gnome.org/show_bug.cgi?id=392591 I will downgrade the severity of this bug to normal as I don't think it deserves a status of grave (the bug doesn't happen to everyone and is easy to work around).