Bug#523345: gstreamer0.10-plugins-bad: Confirmed Pidgin crash
slomo at circular-chaos.org
Wed May 6 07:41:37 UTC 2009
Am Dienstag, den 28.04.2009, 10:10 +0200 schrieb Ivan Vilata i Balaguer:
> Sebastian Dröge (el 2009-04-27 a les 11:00:34 +0200) va dir::
> > This seems to be more related to another issue. Do you have, by any
> > chance, gstreamer0.10-ffmpeg installed and the libavcodec52/etc packages
> > from Debian Multimedia or another third party repository?
> No, I don't have any of those installed, and I'm using the official Debian
> > Otherwise, please run pidgin from a terminal and paste the output into
> > this bug. strace/ltrace would be useless but a backtrace with gdb or a
> > valgrind log would be useful.
> Here is the output of Pidgin::
> $ LANG=C pidgin
> Pidgin 2.5.5 has segfaulted and attempted to dump a core file.
> This is a bug in the software and has happened through
> no fault of your own.
> If you can reproduce the crash, please notify the developers
> by reporting a bug at:
> Please make sure to specify what you were doing at the time
> and post the backtrace from the core file. If you do not know
> how to get the backtrace, please read the instructions at
> Avortat (core dumped)
> Here is the GDB backtrace output on the core file produced by Pidgin (with
> debugging symbols, i.e. pidgin-dbg, libxml2-dbg, libglib2.0-0-dbg)::
Thanks, this looks again like a bug somewhere between liblrdf0 /
libraptor / libxml and pidgin / libxml.
Which versions of liblrdf0, gstreamer0.10-plugins-bad and libdvdread4 do
you have installed? Also, could you get a valgrind log for this?
G_SLICE=always-malloc GST_REGISTRY_FORK=no valgrind --trace-children=yes
get it to crash and attach the complete output to this bug.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 197 bytes
Desc: Dies ist ein digital signierter Nachrichtenteil
More information about the Pkg-gstreamer-maintainers