[ubuntu-mono] [Bug 279800] Re: GStreamer update (7-Oct-2008, Intrepid) causes Banshee crash
Michael B. Trausch
mike at trausch.us
Wed Oct 8 16:07:26 UTC 2008
On Wed, Oct 08, 2008 at 08:16:03AM -0000, =?ISO-8859-1?Q?Sebastian_Dr=F6ge_ wrote:
> Hi,
> which version of banshee, gstreamer0.10-plugins-base and gstreamer0.10 is this?
The versions in Intrepid as of the time the bug report was created...
Ubuntu Intrepid:[0-8/2123-1]:test> COLUMNS=78 dpkg -l | egrep '(banshee|gstreamer)'
ii banshee 1.2.1-3ubuntu1 Media Management and Playback application
ii gstreamer0.10- 0.10.21-1 GStreamer plugin for ALSA
ii gstreamer0.10- 0.10.5-1 FFmpeg plugin for GStreamer
ii gstreamer0.10- 0.10.7.debian- Fluendo mp3 decoder GStreamer plugin
ii gstreamer0.10- 0.10.21-1 GStreamer plugin for GnomeVFS
ii gstreamer0.10- 0.10.8-1 GStreamer plugins from the "bad" set
ii gstreamer0.10- 0.10.21-1 GStreamer plugins from the "base" set
ii gstreamer0.10- 0.10.21-1 GStreamer helper programs from the "base" se
ii gstreamer0.10- 0.10.10-1 GStreamer plugins from the "good" set
ii gstreamer0.10- 0.10.9-1 GStreamer plugins from the "ugly" set
ii gstreamer0.10- 0.10.10-1 GStreamer plugin for PulseAudio
ii gstreamer0.10- 0.10.21-2 Tools for use with GStreamer
ii gstreamer0.10- 0.10.21-1 GStreamer plugins for X11 and Pango
ii libgstreamer-p 0.10.21-1 GStreamer libraries from the "base" set
ii libgstreamer0. 0.10.21-2 Core GStreamer libraries and elements
There is a new version of gstreamer for Intrepid (0.10.21-3) now, so I
am going to try that before I try to tear through the system.
> Could you try to get a backtrace with debugging symbols for glib,
> banshee, gst-plugins-base and gstreamer installed?
See the attached file, which contains the best I've been able to come up
with so far. I am about to install today's updates, and I *hope* that
whatever brokeded yesterday is unbrokeded today, but we'll see; I
noticed a few gstreamer updates in today's batch.
Note that there are no “debugging symbols”, per sé, for Banshee.
Banshee is a managed mode application and requires a different debugger
for dumping stack traces. Don't know if I know how to do that quite yet
or not, I know how to use the traces when Mono's runtime outputs them
automatically, but that's not happening in this case. It seems (from
the second stack trace in the attached file) that the SIGSEGV is being
caused by the Mono runtime's inability to handle SIGABRT properly in
this case. It's strange given that I'm used to the runtime outputting a
very helpful stack trace when something goes horribly wrong outside of
the managed world.
--- Mike
--
My sigfile ran away and is on hiatus.
** Attachment added: "stacktrace-gnu-gdb-at-crashes.txt"
http://launchpadlibrarian.net/18326520/stacktrace-gnu-gdb-at-crashes.txt
--
GStreamer update (7-Oct-2008, Intrepid) causes Banshee crash
https://bugs.launchpad.net/bugs/279800
You received this bug notification because you are a member of MOTU Mono
Team, which is subscribed to banshee in ubuntu.
More information about the Ubuntu-mono
mailing list