GNOME Bugzilla – Bug 409564
Sound device selection critical
Last modified: 2007-03-06 15:03:20 UTC
+++ This bug was initially created as a clone of Bug #343172 +++ +++ This bug was initially created as a clone of Bug #329112 +++ $ ./gnome-sound-properties (lt-gnome-sound-properties:4956): -properties-CRITICAL **: add_selected_device: assertion `pipeline != NULL' failed (lt-gnome-sound-properties:4956): -properties-CRITICAL **: add_selected_device: assertion `pipeline != NULL' failed I believe those warnings come from: add_selected_device ("music", AUDIO_PLAYBACK); and add_selected_device ("chat", AUDIO_PLAYBACK); calling: gconf_key = get_gconf_key_for_profile (profile, type); pipeline = gconf_client_get_string (gconf_client, gconf_key, NULL); g_free (gconf_key); There's either a missing schema, or hard-coded defaults for fallback, or a new enough version of GStreamer (which configure doesn't check for).
And Jürg said: " Sorry for not responding earlier. The missing schema is part of gst-plugins-good >= 0.10.3. Unfortunately that package doesn't provide a pkg-config file, any ideas how that could be fixed easily? "
Applications should be able to gracefully handle missing or invalid GConf keys, since there are many ways it can happen. In addition, detecting plugins at compile time isn't generally a good idea, as it means you can't install it later or have things Just Work by upgrading you plugins, and it also breaks cross-compilation. Making add_selected_device() deal with missing gconf keys would probably be a better idea.
I agree with James, applications should be able to handle this gracefully. Thomas is also against adding a .pc file for this, so closing as WONTFIX.