synaptic crashed with SIGSEGV

Bug #944171 reported by Georges Varouchas
This bug report is a duplicate of:  Bug #936677: synaptic crashed with SIGSEGV. Edit Remove
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
synaptic (Ubuntu)
New
Undecided
Unassigned

Bug Description

Synaptic crashed after applying an update.

A message box appeared saying "Do you wish to report this bug ?".
I clicked "Yes", and triggered another error, saying roughly "the bug data cannot be processed".

As a result, I was prompted without another message box "Do you wish to report this bug ?".
I clicked "Yes", and this time, the bug reporting process seemed to follow its normal course.

I don't know how to say from which bug the current data are taken.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: synaptic 0.75.5~exp6
ProcVersionSignature: Ubuntu 3.2.0-17.27-generic 3.2.6
Uname: Linux 3.2.0-17-generic x86_64
ApportVersion: 1.93-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Thu Mar 1 18:30:47 2012
ExecutablePath: /usr/sbin/synaptic
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
ProcCmdline: /usr/sbin/synaptic
SegvAnalysis:
 Segfault happened at: 0x44f774: mov 0x8(%rdx),%rax
 PC (0x0044f774) ok
 source "0x8(%rdx)" (0x3275746e75627d) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: synaptic
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: synaptic crashed with SIGSEGV
UpgradeStatus: Upgraded to precise on 2011-10-18 (134 days ago)
UserGroups:

Revision history for this message
Georges Varouchas (gvarouchas) 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 this software better. This particular crash has already been reported and is a duplicate of bug #936677, 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
visibility: private → public
tags: removed: need-amd64-retrace
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.