packagekitd crashed with SIGSEGV in strlen()

Bug #1565291 reported by Vasile Rotaru
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
packagekit (Ubuntu)
New
Undecided
Unassigned

Bug Description

Just going about my business when a dialog window appears with Bang!

Figuratively speaking

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: packagekit 0.8.17-4ubuntu6~gcc5.4ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
Uname: Linux 4.4.0-16-generic x86_64
ApportVersion: 2.20.1-0ubuntu1
Architecture: amd64
Date: Sat Apr 2 18:24:27 2016
ExecutablePath: /usr/lib/packagekit/packagekitd
InstallationDate: Installed on 2016-03-26 (6 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
ProcCmdline: /usr/lib/packagekit/packagekitd
SegvAnalysis:
 Segfault happened at: 0x7fd2e2f32ed6 <strlen+38>: movdqu (%rax),%xmm4
 PC (0x7fd2e2f32ed6) 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=0x7fd2ddabb9ef "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: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
Vasile Rotaru (vrotaru-md) 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 #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.

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.