[apport] gxine crashed with SIGFPE

Bug #109999 reported by Thomas Wiegand
2
Affects Status Importance Assigned to Milestone
xine-lib (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: gxine

I wanted to open several radio-straems in firefox. Each time gixine started and the following error message appeared: No sound available. I closed gixine with "file -> close". When I stated the computer a couple of hours later, the message gxine crashed was on the screen. What exactly happened, I do not know.

ProblemType: Crash
Architecture: i386
Date: Wed Apr 25 16:15:25 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/bin/gxine
Package: gxine 0.5.11-1ubuntu2
PackageArchitecture: i386
ProcCmdline: /usr/bin/gxine -a http://193.164.131.210:8004/listen.pls
ProcCwd: /home/thommy
ProcEnviron:
 SHELL=/bin/bash
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games
 LANG=de_DE.UTF-8
 LANGUAGE=de_DE:de:en_GB:en
Signal: 8
SourcePackage: gxine
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Uname: Linux urmel 2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin plugdev scanner video

Revision history for this message
Thomas Wiegand (thommy) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:oscope_port_put_buffer (port_gen=0x942ee38, buf=0x8321578, stream=0x888f028) at oscope.c:288
?? ()
?? ()
?? ()
?? ()

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Darren Salt (dsalt) wrote :

That backtrace marks it as a libxine bug. I can cause it with 1.1.6 (if I run enough other programs to use up the available PCM outputs); however, I'm using goom rather than oscope.

Revision history for this message
Daniel T Chen (crimsun) wrote :

Is this symptom still reproducible in 8.10 beta?

Changed in xine-lib:
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 xine-lib:
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.