gnomebaker crashed with SIGSEGV in pa_stream_write()

Bug #262226 reported by selbst
6
Affects Status Importance Assigned to Milestone
gnomebaker (Ubuntu)
New
Medium
Unassigned

Bug Description

Binary package hint: gnomebaker

after ejecting a dvd and closing gnomebaker, screen darkened and the program crashed.

using ubuntu 8.08
gnome 2.22.3
nvidia-driver 173.14.12
cpu amd athlon x2

ProblemType: Crash
Architecture: amd64
Date: Thu Aug 28 13:51:42 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/gnomebaker
NonfreeKernelModules: nvidia
Package: gnomebaker 0.6.2-3ubuntu1
PackageArchitecture: amd64
ProcCmdline: gnomebaker
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: gnomebaker
StacktraceTop:
 ?? () from /usr/lib/libpulse.so.0
 ?? () from /usr/lib/libpulse.so.0
 pa_stream_write () from /usr/lib/libpulse.so.0
 ?? () from /usr/lib/gstreamer-0.10/libgstpulse.so
 ?? () from /usr/lib/libgstaudio-0.10.so.0
Title: gnomebaker crashed with SIGSEGV in pa_stream_write()
Uname: Linux 2.6.24-19-generic x86_64
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev video

Tags: apport-crash
Revision history for this message
selbst (rumsitz) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:pa_flist_pop (l=0x18d1af0) at ./pulsecore/atomic.h:86
pa_pstream_send_memblock (p=0x18d8c90, channel=0, offset=0, seek_mode=PA_SEEK_RELATIVE,
pa_stream_write (s=0x18d4800, data=0x193518c, length=52, free_cb=<value optimized out>,
gst_pulsesink_write (asink=<value optimized out>, data=0x193518c, length=1)
audioringbuffer_thread_func (buf=<value optimized out>) at gstaudiosink.c:226

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Changed in gnomebaker:
importance: Undecided → Medium
visibility: private → public
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.