synaptic crashed with SIGSEGV in pkgAcqArchive::pkgAcqArchive()

Bug #517250 reported by Mossroy on 2010-02-04
This bug affects 1 person
Affects Status Importance Assigned to Milestone
synaptic (Ubuntu)

Bug Description

Binary package hint: synaptic

I was trying to import in ubuntu 10.04 alpha 2 a list of packages coming from a ubuntu 9.10 system.
In Synaptic, I imported the attached file as a selection of packages, corrected the few broken packages, and validated the installation of this selection.

Synaptic crashed before starting the installation.

ProblemType: Crash
Architecture: amd64
Date: Thu Feb 4 21:28:37 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/sbin/synaptic
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100113)
Package: synaptic 0.63ubuntu3
ProcAttrCurrent: unconfined (enforce)
ProcCmdline: /usr/sbin/synaptic
 PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.32-12.16-generic
 Segfault happened at: 0x7f5ef887f7d8 <_ZN13pkgAcqArchiveC1EP10pkgAcquireP13pkgSourceListP10pkgRecordsRKN8pkgCache11VerIteratorERSs+568>: mov (%rax),%esi
 PC (0x7f5ef887f7d8) ok
 source "(%rax)" (0x7f610cb67000) not located in a known VMA region (needed readable region)!
 destination "%esi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: synaptic
 pkgAcqArchive::pkgAcqArchive(pkgAcquire*, pkgSourceList*, pkgRecords*, pkgCache::VerIterator const&, std::string&) ()
 pkgPackageManager::GetArchives(pkgAcquire*, pkgSourceList*, pkgRecords*) () from /usr/lib/
 ?? ()
 ?? ()
 ?? ()
Title: synaptic crashed with SIGSEGV in pkgAcqArchive::pkgAcqArchive()
Uname: Linux 2.6.32-12-generic x86_64

Mossroy (mossroy) wrote :

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 #408459, 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-amd64-retrace
Mossroy (mossroy) wrote :

It looks like I don't have the permissions to see : is this a public bug?

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers