[gstreamer-bugs] [Bug 147929] New: - [PATCH] running gst-register in non-utf8 locale can cause invalid registry

[bugzilla-daemon at bugzilla.gnome.org]

http://bugzilla.gnome.org/show_bug.cgi?id=147929
GStreamer | gstreamer (core) | Ver: 0.8.4

           Summary: [PATCH] running gst-register in non-utf8 locale can
                    cause invalid registry
           Product: GStreamer
           Version: 0.8.4
          Platform: Other
        OS/Version: other
            Status: UNCONFIRMED
          Severity: blocker
          Priority: Urgent
         Component: gstreamer (core)
        AssignedTo: gstreamer-maint at bugzilla.gnome.org
        ReportedBy: in7y118 at public.uni-hamburg.de
         QAContact: gstreamer-maint at bugzilla.gnome.org


1) install a properly translated ladspa package (The Debian blop package
triggers it)
2) login as root
3) run LC_ALL="de_DE at 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.

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
You are the QA contact for the bug, or are watching the QA contact.