Your message dated Tue, 07 Apr 2009 10:32:03 +
with message-id
and subject line Bug#521898: fixed in liblrdf 0.4.0-1.2
has caused the Debian Bug report #521898,
regarding gstreamer0.10-plugins-bad: gstreamer fails to initialize due to
segfault while loding ladspa plugin
to be marked as done
Hi,
the attached patch fixes this bug for me. I'll upload a NMU to delayed-3
for this.
diff -u liblrdf-0.4.0/debian/changelog liblrdf-0.4.0/debian/changelog
--- liblrdf-0.4.0/debian/changelog
+++ liblrdf-0.4.0/debian/changelog
@@ -1,3 +1,15 @@
+liblrdf (0.4.0-1.2) unstable; urgency=high
+
+ * Non-
$ totem
ERROR: Caught a segmentation fault while loading plugin file:
/usr/lib/gstreamer-0.10/libgstladspa.so
BTW, moving /usr/lib/gstreamer-0.10/libgstladspa.so out of the way
"solves" the problem.
Regards, Kai
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a
Sebastian Dröge wrote:
could you get a backtrace with
GST_REGISTRY_FORK=no gdb --args gst-inspect-0.10 ladspa
run
bt full
For this please also install the debug packages of libc, glib,
gstreamer, gst-plugins-base and gst-plugins-bad.
This is what I did:
$ rm ~/.gstreamer-0.10/registry.x86_64
> Please either:
> - remove it and restart.
> - run with --gst-disable-segtrap and debug.
> Could not initialize GStreamer: Error re-scanning registry , child terminated
> by signal
The same happens also with totem. I installed
gstreamer0.10-plugins-bad-dbg and totem-dbg, but to no avail.
reassign 521898 liblrdf0
found 521898 0.4.0-1.1
notfound 521898 0.10.10.3-1
notfound 521898 0.10.11-2
thanks
Am Donnerstag, den 02.04.2009, 09:38 +0200 schrieb Jan Hauke Rahm:
> Hi Sebastian,
>
> find attached more debugging. I hope it helps!
From a valgrind log with piding:
http://downloads.jhr
Processing commands for cont...@bugs.debian.org:
> reassign 521898 liblrdf0
Bug#521898: gstreamer0.10-plugins-bad: gstreamer fails to initialize due to
segfault while loding ladspa plugin
Bug reassigned from package `gstreamer0.10-plugins-bad' to `liblrdf0'.
> found 521898 0.4.
Package: gstreamer0.10-plugins-bad
Version: 0.10.11-2
Severity: normal
There's something wrong with the command line you asked me to enter:
G_DEBUG=fatal_warnings GST_REGISTRY_FORK=no gdb --args gst-inspect-0.10 ladspa
GNU gdb 6.8-debian
Copyright (C) 2008 Free Software Foundation, Inc.
License
Package: gstreamer0.10-plugins-bad
Version: 0.10.11-2
Severity: normal
Here is pidgin 2.5.5-1 backtrace; I've installed libxml2-dbg to get a more
detailed bt.
apel...@hermes:~$ gdb pidgin
GNU gdb 6.8-debian
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or
Hi Sebastian,
find attached more debugging. I hope it helps!
Hauke
$ G_DEBUG=fatal_warnings GST_REGISTRY_FORK=no gdb --args gst-inspect-0.10
/usr/lib/gstreamer-0.10/libgstladspa.so
GNU gdb 6.8-debian
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
Am Mittwoch, den 01.04.2009, 21:12 +0200 schrieb Apelete Seketeli:
> Package: gstreamer0.10-plugins-bad
> Version: 0.10.11-2
> Severity: normal
>
> I tried to provide the backtrace you asked for.
> As you can see there's no stack when asking for a full backtrace, so I might
> have done something
Sebastian Dröge wrote:
Hi,
could you get a backtrace with
GST_REGISTRY_FORK=no gdb --args gst-inspect-0.10 ladspa
run
bt full
For this please also install the debug packages of libc, glib,
gstreamer, gst-plugins-base and gst-plugins-bad.
Thanks
perhaps unexpectedly, I don't get a crash when r
Am Mittwoch, den 01.04.2009, 23:29 -0500 schrieb Jonathon Jongsma:
> Sebastian Dröge wrote:
> > Hi,
> > could you get a backtrace with
> > GST_REGISTRY_FORK=no gdb --args gst-inspect-0.10 ladspa
> > run
> > bt full
> >
> > For this please also install the debug packages of libc, glib,
> > gstreame
Package: gstreamer0.10-plugins-bad
Version: 0.10.11-2
Severity: normal
I tried to provide the backtrace you asked for.
As you can see there's no stack when asking for a full backtrace, so I might
have done something wrong (I installed all the debug packages you asked though).
I'm willing to help,
Processing commands for cont...@bugs.debian.org:
> merge 521898 521898
Bug#521898: gstreamer0.10-plugins-bad: gstreamer fails to initialize due to
segfault while loding ladspa plugin
Merged 521898.
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debi
Am Montag, den 30.03.2009, 14:30 -0500 schrieb Jonathon Jongsma:
> Package: gstreamer0.10-plugins-bad
> Version: 0.10.10.3-1
> Severity: grave
> Justification: renders package unusable
>
>
> After upgrading to 0.10.11-2, empathy would no longer run for me. Downgrading
> to 0.10.10.3-1 fixed the
merge 521898 521898
thanks
Am Dienstag, den 31.03.2009, 12:06 +0200 schrieb Kai Weber:
> Package: gstreamer0.10-plugins-bad
> Version: 0.10.11-2
> Severity: normal
>
>
> The error affects totem-gstreamer as well.
>
> $ totem
>
> ERROR: Caught a segmentation fault while loading plugin file:
> /
This seems to also affect pidgin, see #519112.
--
Magnus Therning(OpenPGP: 0xAB4DFBA4)
magnus＠therning．org Jabber: magnus＠therning．org
http://therning.org/magnus identi.ca|twitter: magthe
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.o
Package: gstreamer0.10-plugins-bad
Version: 0.10.11-2
Severity: normal
The error affects totem-gstreamer as well.
$ totem
ERROR: Caught a segmentation fault while loading plugin file:
/usr/lib/gstreamer-0.10/libgstladspa.so
Please either:
- remove it and restart.
- run with --gst-disable-segtr
Package: gstreamer0.10-plugins-bad
Version: 0.10.10.3-1
Severity: grave
Justification: renders package unusable
After upgrading to 0.10.11-2, empathy would no longer run for me. Downgrading
to 0.10.10.3-1 fixed the issue. The following error was printed to the
terminal:
$ empathy
ERROR: Caugh
20 matches
Mail list logo
