severity 578476 important thanks I don't consider using the public API of gstreamer in a non-broken way to mean that pidgin is doing anything wrong here. Comment from the source explaining why they were originally catching/disabling forking:
/* By default, gstreamer forks when you initialize it, and waitpids for the * child. But if libpurple reaps the child rather than leaving it to * gstreamer, gstreamer's initialization fails. So, we wait a second before * reaping child processes, to give gst a chance to reap it if it wants to. * * This is not needed in later gstreamers, which let us disable the forking. * And, it breaks the world on some Real Unices. */ On 04/20/2010 03:16 AM, Sebastian Dröge wrote: > Package: pidgin > Severity: serious > > Hi, > pidgin currently crashes when a broken GStreamer plugin is installed, > e.g. if this plugin crashes on initialization. See bug #573269 for an > example. > > This only affects pidgin because the pidgin developers decided for some > reason, that the GStreamer registry updating should happen in the pidgin > process... which then of course makes it impossible to survive crashing > plugins. > > Attached patch fixes this, you should *really* include it with the next > upload. When the registry updating is done in a forked, new process, > broken plugins will be blacklisted and deactivated instead of taking > down pidgin. > > Of course bug #573269 is still a gst-plugins-bad0.10 (or LV2/liblrdf) > bug but not really critical. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
