rhythmbox crashed with SIGSEGV in gst_ring_buffer_commit_full()

Bug #172496 reported by dynamethod
4
Affects Status Importance Assigned to Milestone
gstreamer0.10 (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: rhythmbox

sorry i dont know what caused this

ProblemType: Crash
Architecture: i386
Date: Wed Nov 28 17:40:29 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/rhythmbox
NonfreeKernelModules: fglrx
Package: rhythmbox 0.11.2-0ubuntu4
PackageArchitecture: i386
ProcCmdline: rhythmbox
ProcCwd: /home/xen
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_NZ.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: rhythmbox
StacktraceTop:
 gst_ring_buffer_commit_full ()
 ?? () from /usr/lib/libgstaudio-0.10.so.0
 ?? ()
 ?? ()
 ?? ()
Title: rhythmbox crashed with SIGSEGV in gst_ring_buffer_commit_full()
Uname: Linux Z10N 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

Tags: apport-crash
Revision history for this message
dynamethod (joe-t) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:gst_base_audio_sink_render (bsink=0x8a860b0, buf=0x8d71810)
gst_base_sink_render_object (basesink=0x8a860b0, pad=0x8a6b900,
gst_base_sink_queue_object_unlocked (basesink=0x8a860b0,
gst_base_sink_chain_unlocked (basesink=0x8a860b0, pad=0x8a6b900,
gst_base_sink_chain (pad=0x8a6b900, buf=0x8d71810)

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Apport retracing service (apport) wrote : Stack trace with source code
Changed in rhythmbox:
importance: Undecided → Medium
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for your report, it seems to be a gstreamer issue

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:

 * Is this reproducible?
 * If so, what specific steps should we take to recreate this bug?
 * Do you still get the issue on hardy or intrepid?

 This will help us to find and resolve the problem.

Changed in gstreamer0.10:
status: New → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.

Changed in gstreamer0.10:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.