serpentine crashed with SIGSEGV

Bug #150045 reported by Andreas Johansson
4
Affects Status Importance Assigned to Milestone
serpentine (Ubuntu)
Invalid
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: serpentine

When I try to quit Serpentine it won't close the program window. I finally force quit it and then I get a crash report from Serpentine.

I'm using Ubuntu 7.10
Kernel Linux 2.6.22-13-generic
SMP x86_64 on a Macbook Pro Santa Rosa

ProblemType: Crash
Architecture: amd64
Date: Sun Oct 7 01:59:46 2007
Disassembly: 0x2ab31bce4875:
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/serpentine
InterpreterPath: /usr/bin/python2.5
NonfreeKernelModules: nvidia
Package: serpentine 0.9-0ubuntu2
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/serpentine -o
ProcCwd: /home/andreas
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: serpentine
Stacktrace: #0 0x00002ab31bce4875 in ?? ()
StacktraceTop: ?? ()
ThreadStacktrace:

Title: serpentine crashed with SIGSEGV
Uname: Linux mac 2.6.22-13-generic #1 SMP Thu Oct 4 17:52:26 GMT 2007 x86_64 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

Revision history for this message
Andreas Johansson (bolanski) wrote :
Changed in serpentine:
importance: Undecided → Medium
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:?? ()

Revision history for this message
Apport retracing service (apport) wrote : Stack trace with source code
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem.

Changed in serpentine:
assignee: nobody → desktop-bugs
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 serpentine:
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.