Ubuntu
slune package

[apport] slune crashed with SIGSEGV

Bug #115857 reported by mexlinux on 2007-05-20

This bug report is a duplicate of: Bug #115607: [apport] slune crashed with SIGSEGV. Edit Remove

Affects		Status	Importance	Assigned to	Milestone
	slune (Ubuntu)	New	Undecided	Unassigned

Bug Description

Binary package hint: slune

crashed

ProblemType: Crash
Architecture: i386
Date: Sun May 20 14:39:55 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/games/slune
InterpreterPath: /usr/bin/python2.5
Package: slune 1.0.12-1ubuntu1
PackageArchitecture: all
ProcCmdline: /usr/bin/python -O /usr/games/slune
ProcCwd: /home/mcanedo
ProcEnviron:
PATH=/home/mcanedo/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
LANG=es_MX.UTF-8
SHELL=/bin/bash
Signal: 11
SourcePackage: slune
Stacktrace:
#0 0xb7afe56c in ?? () from /var/lib/python-support/python2.5/soya/_soya.so
#1 0x00000000 in ?? ()
StacktraceTop:
?? () from /var/lib/python-support/python2.5/soya/_soya.so
?? ()
Uname: Linux mcanedo-laptop 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 netdev plugdev powerdev scanner video

Revision history for this message

mexlinux (mcanedo) wrote on 2007-05-20:

Dependencies.txt Edit (1.9 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (847 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (11.5 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (666 bytes, text/plain; charset="utf-8")
Registers.txt Edit (518 bytes, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (334 bytes, text/plain; charset="utf-8")

Revision history for this message

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

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

StacktraceTop:?? () from /lib/ld-linux.so.2
?? ()

Revision history for this message

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

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

Revision history for this message

Jérôme Guelfucci (jerome-guelfucci-deactivatedaccount) wrote on 2007-05-21:

Thanks for the bug report. This particular bug has already been reported (bug #115607), but the previous report is missing information that you might be able to provide. Please look at the other bug report and answer the questions if you can.