Hi, Marcos Marado wrote (02 Jul 2013 10:33:19 GMT) : > I had pidgin running without problems on squeeze, but after dist-upgrading to > wheezy I've run into this problem.
Confirmed on a fresh Wheezy installation with these GStreamer bits installed: gstreamer0.10-ffmpeg gstreamer0.10-gconf gstreamer0.10-gnonlin gstreamer0.10-nice gstreamer0.10-plugins-bad gstreamer0.10-plugins-base gstreamer0.10-plugins-good gstreamer0.10-plugins-ugly gstreamer0.10-pulseaudio gstreamer0.10-x ... Pidgin crashes the first time it is run *unless* another application already initialized the GStreamer registry. Removing ~/.gstreamer-0.10/ and starting Pidgin again allows me to reproduce the crash every time: sys:1: Warning: /build/buildd-glib2.0_2.33.12+really2.32.4-5-i386-eISom6/glib2.0-2.33.12+really2.32.4/./gobject/gsignal.c:2459: signal `destroy' is invalid for instance `0xb9ec3958' sys:1: Warning: invalid (NULL) pointer instance sys:1: Warning: g_signal_emit_by_name: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed sys:1: Warning: value "-1217420652" of type `gint' is invalid or out of range for property `weight' of type `gint' Pidgin 2.10.6 has segfaulted and attempted to dump a core file. If I start Pidgin again, then it works just fine. I guess this issue is not so important for most stable users, *but* it is pretty important for Debian Live systems such as Tails [1], since we can't reasonably bet on the fact that the user will have started another GStreamer application already. [1] https://tails.boum.org/ Cheers, -- intrigeri | GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc | OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
