aptd crashed with SIGSEGV in _IO_vfprintf_internal()

Bug #1437757 reported by birman123@live.com
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
aptdaemon (Ubuntu)
New
Undecided
Unassigned

Bug Description

Installing cqrlog install didn't work.

ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: aptdaemon 1.1.1+bzr981-0ubuntu2
ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
Uname: Linux 3.19.0-10-generic x86_64
ApportVersion: 2.16.2-0ubuntu5
Architecture: amd64
Date: Sat Mar 28 19:02:24 2015
ExecutablePath: /usr/sbin/aptd
InstallationDate: Installed on 2015-03-28 (0 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326)
InterpreterPath: /usr/bin/python3.4
PackageArchitecture: all
ProcCmdline: /usr/bin/python3 /usr/sbin/aptd
ProcEnviron: LANG=C.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f8c76a9a4b2 <_IO_vfprintf_internal+18578>: repnz scas %es:(%rdi),%al
 PC (0x7f8c76a9a4b2) ok
 source "%es:(%rdi)" (0x00000006) not located in a known VMA region (needed readable region)!
 destination "%al" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: aptdaemon
StacktraceTop:
 _IO_vfprintf_internal (s=s@entry=0x217cd70, format=<optimized out>, ap=ap@entry=0x7ffd39b22ab8) at vfprintf.c:1642
 ___fprintf_chk (fp=0x217cd70, flag=1, format=<optimized out>) at fprintf_chk.c:35
 pkgDPkgPM::WriteApportReport(char const*, char const*) () from /usr/lib/x86_64-linux-gnu/libapt-pkg.so.4.12
 pkgDPkgPM::ProcessDpkgStatusLine(char*) () from /usr/lib/x86_64-linux-gnu/libapt-pkg.so.4.12
 pkgDPkgPM::DoDpkgStatusFd(int) () from /usr/lib/x86_64-linux-gnu/libapt-pkg.so.4.12
Title: aptd crashed with SIGSEGV in _IO_vfprintf_internal()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
birman123@live.com (birman123) 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 #1436626, 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.

information type: 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.