aptd crashed with SIGSEGV in _IO_vfprintf_internal()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
aptdaemon (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Happened while updating
ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: aptdaemon 1.1.1+bzr981-
ProcVersionSign
Uname: Linux 3.19.0-10-generic x86_64
NonfreeKernelMo
ApportVersion: 2.16.2-0ubuntu5
Architecture: amd64
Date: Tue Mar 31 15:25:12 2015
ExecutablePath: /usr/sbin/aptd
InstallationDate: Installed on 2014-04-19 (346 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
InterpreterPath: /usr/bin/python3.4
PackageArchitec
ProcCmdline: /usr/bin/python3 /usr/sbin/aptd
ProcEnviron: LANG=C.UTF-8
SegvAnalysis:
Segfault happened at: 0x7fc8c1c514b2 <_IO_vfprintf_
PC (0x7fc8c1c514b2) 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_
___fprintf_chk (fp=0x22b5d80, flag=1, format=<optimised out>) at fprintf_chk.c:35
pkgDPkgPM:
pkgDPkgPM:
pkgDPkgPM:
Title: aptd crashed with SIGSEGV in _IO_vfprintf_
UpgradeStatus: Upgraded to vivid on 2015-03-02 (28 days ago)
UserGroups:
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.