GNOME Bugzilla – Bug 147929
[PATCH] running gst-register in non-utf8 locale can cause invalid registry
Last modified: 2004-12-22 21:47:04 UTC
1) install a properly translated ladspa package (The Debian blop package triggers it) 2) login as root 3) run LC_ALL="de_DE@euro" gst-register 4) try running gst-launch fakesrc ! fakesink observed results: 3) creates a registry that is not valid utf-8. 4) does not work because parsing the registry fails silently (with only debugging output), because the registry is not valid utf-8. expected results: 1) plugins don't set invalid texts as their info. (Someone fix LADSPA) 2) GStreamer figures out plugins set invalid info. 3) GStreamer's registry parser can recover from parsing invalid characters in the registry instead of stopping. I've attached a patch for point 2). I'm marking this bug blocker, because it fixes the common "GStreamer-ERROR **: No default scheduler name - do you have a registry ?" errors people come up with and I'd really like to have this bad first impression removed in the release.
Created attachment 29671 [details] [review] make sure ElementDetails are valid UTF-8
Ok, packaged blop to test. I have to run with de_DE, not de_DE@euro. I've also looked into making it to print the name of the offending plugin, but the elementfactory is not set yet at the time of base_init being called. we should find some way to do that. I'll open new bugs for all other issues involved not fixed by the patch.