Ubuntu
lxdoom package

[apport] sndserv crashed with SIGSEGV

Bug #104258 reported by Sebastian Kempinski on 2007-04-07

4

Affects		Status	Importance	Assigned to	Milestone
	lxdoom (Ubuntu)	Invalid	Medium	Unassigned

Bug Description

Binary package hint: lxdoom

The system reported the sound server crash when I launched lxdoom (game). I subsequently have no sound - even after a reboot.

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Fri Apr 6 23:47:39 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/games/sndserv
Package: lxdoom-sndserv 1.4.4main-0.1ubuntu1
PackageArchitecture: i386
ProcCmdline: /usr/games/sndserv /dev/dsp
ProcCwd: /home/sebic
ProcEnviron:
LANGUAGE=pl_PL:pl:en_GB:en
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games
LANG=pl_PL.UTF-8
SHELL=/bin/bash
Signal: 11
SourcePackage: lxdoom
StacktraceTop:
?? ()
?? ()
?? ()
?? ()
?? () from /lib/tls/i686/cmov/libc.so.6
Uname: Linux sebicubu 2.6.20-14-generic #2 SMP Mon Apr 2 20:37:49 UTC 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin mysql plugdev scanner video

Revision history for this message

Sebastian Kempinski (sebic-k) wrote on 2007-04-07:

#1

Dependencies.txt Edit (784 bytes, text/plain; charset="utf-8")
Disassembly.txt Edit (854 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (739 bytes, text/plain; charset="utf-8")
ProcStatus.txt Edit (665 bytes, text/plain; charset="utf-8")
Registers.txt Edit (455 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (177 bytes, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (205 bytes, text/plain; charset="utf-8")

Revision history for this message

Martin Pitt (pitti) wrote on 2007-05-19: Symbolic stack trace

#2

Stacktrace.txt (retraced) Edit (177 bytes, text/plain)

StacktraceTop:?? ()
?? ()
?? ()
?? ()
?? () from /lib/tls/i686/cmov/libc.so.6

Revision history for this message

Martin Pitt (pitti) wrote on 2007-05-19: Symbolic threaded stack trace

#3

ThreadStacktrace.txt (retraced) Edit (205 bytes, text/plain)

Siegfried Gevatter (rainct) on 2007-12-08

Changed in lxdoom:
importance:	Undecided → Medium

Revision history for this message

Boniek (boniek12p) wrote on 2010-03-16:

#4

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. If you could test the current Ubuntu development version, this would help us a lot. If you can test it, and it is still an issue, we would appreciate if you could upload updated logs by running apport-collect 104258 , and any other logs that are relevant for this particular issue.

Changed in lxdoom (Ubuntu):
status:	New → Incomplete

Revision history for this message

Vish (vish) wrote on 2010-08-05:

#5

Thank you for taking the time to report this bug and helping to make Ubuntu better.
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".

Changed in lxdoom (Ubuntu):
status:	Incomplete → Invalid

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

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