kupfer.py crashed with SIGSEGV in PyErr_Restore()

Bug #1052139 reported by MFeif
26
This bug affects 4 people
Affects Status Importance Assigned to Milestone
kupfer (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

kupfer crashes after ~ 10-15s.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: kupfer 0+v208-2
ProcVersionSignature: Ubuntu 3.5.0-14.19-generic 3.5.3
Uname: Linux 3.5.0-14-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.5.2-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Mon Sep 17 14:21:05 2012
ExecutablePath: /usr/share/kupfer/kupfer.py
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120905.2)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/share/kupfer/kupfer.py
SegvAnalysis:
 Segfault happened at: 0x4ca588 <PyErr_Restore+136>: mov 0x8(%rdx),%rax
 PC (0x004ca588) ok
 source "0x8(%rdx)" (0x7990000000000008) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: kupfer
StacktraceTop:
 PyErr_Restore ()
 PyDict_GetItem ()
 _PyObject_GenericGetAttrWithDict ()
 PyEval_EvalFrameEx ()
 ?? ()
Title: kupfer.py crashed with SIGSEGV in PyErr_Restore()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
MFeif (matt-feifarek) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceTop.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in kupfer (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
information type: Private → Public
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in kupfer (Ubuntu):
status: New → Confirmed
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.