install.py crashed with SIGSEGV in __fprintf_chk()

Bug #623697 reported by Dale Allan
This bug report is a duplicate of:  Edit Remove
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: ubiquity

I don't know , This happened during Install.

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: ubiquity 2.2.25
ProcVersionSignature: Ubuntu 2.6.32-24.39-generic 2.6.32.15+drm33.5
Uname: Linux 2.6.32-24-generic i686
Architecture: i386
Date: Tue Aug 24 15:02:13 2010
ExecutablePath: /usr/share/ubiquity/install.py
InterpreterPath: /usr/bin/python2.6
LiveMediaBuild: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release i386 (20100816.1)
ProcCmdline: /usr/bin/python /usr/share/ubiquity/install.py
ProcEnviron:
 LANGUAGE=en_CA.UTF-8
 PATH=(custom, no user)
 LANG=en_CA.UTF-8
 LC_COLLATE=C
SegvAnalysis:
 Segfault happened at: 0x210d80 <__fprintf_chk+32>: cmpw $0x0,(%esi)
 PC (0x00210d80) ok
 source "$0x0" ok
 destination "(%esi)" (0x00000000) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: ubiquity
StacktraceTop:
 __fprintf_chk () from /lib/tls/i686/cmov/libc.so.6
 pkgDPkgPM::Go(int) ()
 pkgPackageManager::DoInstallPostFork(int) ()
 pkgPackageManager::DoInstall(int) ()
 ?? () from /usr/lib/python2.6/dist-packages/apt_pkg.so
Title: install.py crashed with SIGSEGV in __fprintf_chk()
UserGroups:

Revision history for this message
Dale Allan (dallan-prairieliftruck) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #627693, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

visibility: private → public
tags: removed: need-i386-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
  • Duplicate of a private bug Remove

Other bug subscribers

Remote bug watches

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