synaptic crashed with SIGSEGV in _IO_vfprintf_internal()

Bug #1048561 reported by Marius B. Kotsbak
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
synaptic (Ubuntu)
New
Undecided
Unassigned

Bug Description

Crash at startup. Might be a duplicate.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: synaptic 0.75.12build1
Uname: Linux 3.6.0-030600rc4-generic i686
ApportVersion: 2.5.1-0ubuntu7
Architecture: i386
CrashCounter: 1
Date: Mon Sep 10 10:27:42 2012
ExecutablePath: /usr/sbin/synaptic
ExecutableTimestamp: 1339520460
ProcCmdline: synaptic
ProcCwd: /home/marius/projects/NetCom_LTE/networkmanager/modemmanager
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: 0xb6843b6e <_IO_vfprintf_internal+21406>: repnz scas %es:(%edi),%al
 PC (0xb6843b6e) ok
 source "%es:(%edi)" (0xae54256c) not located in a known VMA region (needed readable region)!
 destination "%al" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: synaptic
StacktraceTop:
 _IO_vfprintf_internal (s=0xbfc90840, format=<optimized out>, ap=0xbfc909a0 "\300\344\252\b") at vfprintf.c:1624
 __GI___vasprintf_chk (result_ptr=0xbfc9094c, flags=1, format=0xb76ed05f <Address 0xb76ed05f out of bounds>, args=0xbfc90984 "") at vasprintf_chk.c:68
 g_vasprintf () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_strdup_vprintf () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_strdup_printf () from /lib/i386-linux-gnu/libglib-2.0.so.0
Title: synaptic crashed with SIGSEGV in _IO_vfprintf_internal()
UpgradeStatus: Upgraded to quantal on 2012-08-31 (9 days ago)
UserGroups:

Revision history for this message
Marius B. Kotsbak (mariusko) 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-i386-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.