Pulseaudio devs think it is a gst/gst client bug: The assertion would appear to be one to protect against invalid useage of the PA API (i.e. calling methods from an incorrect thread (e.g. unsafe thread handling).
This would seem to suggest one of two things: A GST bug A GST client (e.g. Pidgin) bug. I don't know enough personally about either GST or Pidgin to comment about where the problem actually is, but I guess it's best to ask a GST expert to comment to see whether the Pidgin use of the GST API is following their thread guidelines, or whether it's just something that GST needs to wrap up in order to offer a thread-safe API to it's clients (e.g. buffer the request in question and execute it in the appropriate thread when possible). http://pulseaudio.org/ticket/838#comment:3 -- crashes in gcompris Assertion '!in_worker(m)' failed at pulse/thread-mainloop.c:161, function pa_threaded_mainloop_stop(). https://bugs.launchpad.net/bugs/458071 You received this bug notification because you are a member of Registry Administrators, which is the registrant for Debian. _______________________________________________ Mailing list: https://launchpad.net/~registry Post to : [email protected] Unsubscribe : https://launchpad.net/~registry More help : https://help.launchpad.net/ListHelp
