packagekitd crashed with SIGSEGV in strlen()

[Vladimir Scherbaev]

Description: Ubuntu Xenial Xerus (development branch)
Release: 16.04
packagekit:
  Установлен: 0.8.17-4ubuntu6~gcc5.4ubuntu1
  Кандидат: 0.8.17-4ubuntu6~gcc5.4ubuntu1
  Таблица версий:
 *** 0.8.17-4ubuntu6~gcc5.4ubuntu1 500
        500 http://ru.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: packagekit 0.8.17-4ubuntu6~gcc5.4ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
Uname: Linux 4.4.0-15-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
Date: Sun Mar 27 13:16:53 2016
ExecutablePath: /usr/lib/packagekit/packagekitd
InstallationDate: Installed on 2015-07-21 (249 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
ProcCmdline: /usr/lib/packagekit/packagekitd
ProcEnviron:
 LANG=ru_RU.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/sh
SegvAnalysis:
 Segfault happened at: 0x7f0b3300aed6 <strlen+38>: movdqu (%rax),%xmm4
 PC (0x7f0b3300aed6) ok
 source "(%rax)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%xmm4" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: packagekit
StacktraceTop:
 strlen () at ../sysdeps/x86_64/strlen.S:106
 __add_to_environ (name=0x7f0b2a9af9ef "http_proxy", value=0x0, combined=0x0, replace=1) at setenv.c:131
 AptIntf::init() () from /usr/lib/x86_64-linux-gnu/packagekit-backend/libpk_backend_aptcc.so
 ?? () from /usr/lib/x86_64-linux-gnu/packagekit-backend/libpk_backend_aptcc.so
 ?? ()
Title: packagekitd crashed with SIGSEGV in strlen()
UpgradeStatus: Upgraded to xenial on 2016-03-26 (0 days ago)
UserGroups:

[Apport retracing service (apport)]

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 #1560759, 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.