synaptic crashed with SIGSEGV

Bug #942911 reported by bplzip
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 crashes upon system boot. I had just booted precise when a problem with synaptic occurred.

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
NonfreeKernelModules: nvidia wl
ApportVersion: 1.93-0ubuntu2
Architecture: amd64
CrashCounter: 1
CurrentDmesg.txt:
 [ 19.437503] init: hybrid-gfx main process (996) terminated with status 127
 [ 32.431972] gsettings-data-[1392] trap int3 ip:7f89121d013b sp:7fff14f53af0 error:0
 [ 36.387030] gsettings-data-[1584] trap int3 ip:7f3a9d8a013b sp:7fff763aabb0 error:0
 [ 55.984031] eth1: no IPv6 routers present
Date: Fri Feb 24 06:54:12 2012
ExecutablePath: /usr/sbin/synaptic
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120201.1)
ProcCmdline: /usr/sbin/synaptic
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
 PATH=(custom, no user)
SegvAnalysis:
 Segfault happened at: 0x44f774: mov 0x8(%rdx),%rax
 PC (0x0044f774) ok
 source "0x8(%rdx)" (0x313231727e363536) 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: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
bplzip (bplzip) 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.