synaptic crashed with SIGSEGV

Bug #931833 reported by Ian Sandulak
24
This bug affects 2 people
Affects Status Importance Assigned to Milestone
synaptic (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Problem surfaced on update request to 12.4 -

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: synaptic 0.75.5~exp5
ProcVersionSignature: Ubuntu 3.2.0-15.24-generic 3.2.5
Uname: Linux 3.2.0-15-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Mon Feb 13 16:49:56 2012
ExecutablePath: /usr/sbin/synaptic
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
ProcCmdline: /usr/sbin/synaptic
SegvAnalysis:
 Segfault happened at: 0x44f6e4: mov 0x8(%rdx),%rax
 PC (0x0044f6e4) ok
 source "0x8(%rdx)" (0x0000001a) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: synaptic
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: synaptic crashed with SIGSEGV
UpgradeStatus: Upgraded to precise on 2012-02-14 (0 days ago)
UserGroups:

Revision history for this message
Ian Sandulak (iansandulak) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 _M_data (this=0x1096748) at /usr/include/c++/4.6/bits/basic_string.h:288
 _M_rep (this=0x1096748) at /usr/include/c++/4.6/bits/basic_string.h:296
 ~basic_string (this=0x1096748, __in_chrg=<optimized out>) at /usr/include/c++/4.6/bits/basic_string.h:534
 RPackage::~RPackage (this=0x1096720, __in_chrg=<optimized out>) at rpackage.cc:96
 ?? ()

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 synaptic (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Robert Roth (evfool) 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.
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

visibility: private → public
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in synaptic (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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