Bug#544734: [gstreamer0.10-plugins-bad] bad $HOME/.gstreamer-0.10/registry.i486.bin file
slomo at circular-chaos.org
Fri Sep 4 11:06:26 UTC 2009
Am Freitag, den 04.09.2009, 11:47 +0200 schrieb Bégault Luc:
> Sebastian Dröge wrote:
> > Am Mittwoch, den 02.09.2009, 19:19 +0200 schrieb Bégault Luc:
> >> Package: gstreamer0.10-plugins-bad
> >> Version: 0.10.14-1
> >> Severity: grave
> >> --- Please enter the report below this line. ---
> >> Hi,
> >> using amsn I was unable to connect after gstreamer0.10-plugins-bad
> >> update. It was crashing with an error like "unable to initialize
> >> GStreamer" (sorry I forgot to note the exact message). I made an strace
> >> and discovered that the crash occured after amsn tried to access
> >> $HOME/.gstreamer-0.10/registry.i486.bin
> >> I manage to downgrade gstreamer0.10-plugins-bad and -good and it fixed
> >> the problem.
> >> Thanks.
> > Hi,
> > could you upgrade to the new versions again and run
> > GST_REGISTRY_FORK=no gdb gst-inspect-0.10
> > run
> > [wait until it crashes]
> > bt full
> > and attach the output here?
> Here is the output of gdb.
> The exact message of amsn is: "Could not initialize GStreamer: Error
> re-scanning registry , child terminated by signal"
> Program received signal SIGILL, Illegal instruction.
> 0xb69c99ed in ?? () from /usr/lib/libgavl.so.1
So the problem is in libgavl... it probably uses SSE2 but your CPU
doesn't support it or something similar :)
Do you have one of these files:
If so, does the problem go away if you remove the frei0r-plugins
-------------- 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