packagekitd crashed with SIGSEGV in strlen()

Bug #1562285 reported by Mirzet Kadic
20
This bug affects 3 people
Affects Status Importance Assigned to Milestone
packagekit (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

packagekitd crashed with SIGSEGV in strlen()

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: Sat Mar 26 12:05:03 2016
ExecutablePath: /usr/lib/packagekit/packagekitd
InstallationDate: Installed on 2016-03-25 (0 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
ProcCmdline: /usr/lib/packagekit/packagekitd
SegvAnalysis:
 Segfault happened at: 0x7f642c2abed6 <strlen+38>: movdqu (%rax),%xmm4
 PC (0x7f642c2abed6) 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=0x7f641a6fe9ef "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
Mirzet Kadic (caracal-enl) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 strlen () at ../sysdeps/x86_64/strlen.S:106
 __add_to_environ (name=0x7f641a6fe9ef "http_proxy", value=0x0, combined=0x0, replace=1) at setenv.c:131
 AptIntf::init() () from /tmp/apport_sandbox_wBmXQx/usr/lib/x86_64-linux-gnu/packagekit-backend/libpk_backend_aptcc.so
 pk_backend_resolve_thread(PkBackendJob*, _GVariant*, void*) () from /tmp/apport_sandbox_wBmXQx/usr/lib/x86_64-linux-gnu/packagekit-backend/libpk_backend_aptcc.so
 pk_backend_job_thread_setup ()

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in packagekit (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in packagekit (Ubuntu):
status: New → Confirmed
information type: Private → Public
Revision history for this message
David Hoeffer (d-hoeffer) wrote :

This happens when http_proxy is not set. To reproduce, run
root# unset http_proxy
root# pkcon get-updates
Getting updates [=========================]
Starting [ == ] The daemon crashed mid-transaction!

It's fixed upstrem: https://github.com/hughsie/PackageKit/commit/e94b80f90179db18221b2eff93b4561b5418fbfb#diff-0f4bea38f9a8f781e01b5dce9e95812c

so presumably it's only a question of pulling a newer upstream version.

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.