synaptic crashed with SIGSEGV in vfprintf()

Bug #1027425 reported by Svein Tore
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
synaptic (Ubuntu)
New
Undecided
Unassigned

Bug Description

Selected two packages, one for removal, one for purging.

Clicked Apply.

Program crashed.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: synaptic 0.75.12build1
ProcVersionSignature: Ubuntu 3.5.0-4.4-generic 3.5.0-rc6
Uname: Linux 3.5.0-4-generic x86_64
ApportVersion: 2.4-0ubuntu3
Architecture: amd64
Date: Sat Jul 21 17:06:40 2012
ExecutablePath: /usr/sbin/synaptic
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
ProcCmdline: synaptic
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=nb_NO.UTF-8
 LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f630af1cdba <vfprintf+10042>: repnz scas %es:(%rdi),%al
 PC (0x7f630af1cdba) ok
 source "%es:(%rdi)" (0x00000001) not located in a known VMA region (needed readable region)!
 destination "%al" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: synaptic
StacktraceTop:
 vfprintf () from /lib/x86_64-linux-gnu/libc.so.6
 __vasprintf_chk () from /lib/x86_64-linux-gnu/libc.so.6
 g_vasprintf () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_strdup_vprintf () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_strdup_printf () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: synaptic crashed with SIGSEGV in vfprintf()
UpgradeStatus: Upgraded to quantal on 2012-07-18 (2 days ago)
UserGroups:

Revision history for this message
Svein Tore (sveint) 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 #940621, 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
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.