install.py crashed with SIGSEGV in PyEval_EvalFrameEx()

Bug #643703 reported by joe
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Invalid
Medium
joe

Bug Description

Binary package hint: ubiquity

dont know

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: ubiquity 2.2.24 [modified: lib/partman/automatically_partition/question]
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic i686
Architecture: i386
Date: Mon Sep 20 18:16:28 2010
Disassembly: => 0x7947720: Cannot access memory at address 0x7947720
ExecutablePath: /usr/share/ubiquity/install.py
InterpreterPath: /usr/bin/python2.6
LiveMediaBuild: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
ProcCmdline: /usr/bin/python /usr/share/ubiquity/install.py
ProcEnviron:
 LANGUAGE=nl_NL.UTF-8
 PATH=(custom, no user)
 LANG=nl_NL.UTF-8
 LC_COLLATE=C
SegvAnalysis:
 Segfault happened at: 0x7947720: Cannot access memory at address 0x7947720
 PC (0x07947720) not located in a known VMA region (needed executable region)!
SegvReason: executing unknown VMA
Signal: 11
SourcePackage: ubiquity
StacktraceTop:
 ?? ()
 ?? ()
 PyEval_EvalFrameEx ()
 PyEval_EvalFrameEx ()
 PyEval_EvalFrameEx ()
Title: install.py crashed with SIGSEGV in PyEval_EvalFrameEx()
UserGroups:

Revision history for this message
joe (praise-jahweh) wrote :
Changed in ubiquity (Ubuntu):
assignee: nobody → joe (praise-jahweh)
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? ()
 PyEval_EvalFrameEx (f=0xffffffff, throwflag=0)
 PyEval_EvalFrameEx (f=0x9be5654, throwflag=0)
 PyEval_EvalFrameEx (f=0x9be761c, throwflag=0)
 PyEval_EvalFrameEx (f=0x95cfa4c, throwflag=0)

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in ubiquity (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Revision history for this message
Steve Beattie (sbeattie) wrote :

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

security vulnerability: yes → no
visibility: private → public
tags: added: ubiquity-2.2.24
Revision history for this message
dino99 (9d9) wrote :

This version has expired long ago; no more supported

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