packagekitd crashed with SIGSEGV in AptIntf::providesCodec()

Bug #1753165 reported by h9000
This bug report is a duplicate of:  Edit Remove
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
packagekit (Ubuntu)
New
Undecided
Unassigned

Bug Description

no idea why and when this was happen

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: packagekit 1.1.7-1
Uname: Linux 4.15.7-041507-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CrashCounter: 1
Date: Sat Mar 3 21:10:53 2018
ExecutablePath: /usr/lib/packagekit/packagekitd
InstallationDate: Installed on 2018-02-15 (16 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180210)
ProcCmdline: /usr/lib/packagekit/packagekitd
SegvAnalysis:
 Segfault happened at: 0x7f0b0102f646 <__strlen_sse2+38>: movdqu (%rax),%xmm4
 PC (0x7f0b0102f646) ok
 source "(%rax)" (0x7f0b5593d770) not located in a known VMA region (needed readable region)!
 destination "%xmm4" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: packagekit
StacktraceTop:
 AptIntf::providesCodec(PkgList&, char**) () at /usr/lib/x86_64-linux-gnu/packagekit-backend/libpk_backend_aptcc.so
 () at /usr/lib/x86_64-linux-gnu/packagekit-backend/libpk_backend_aptcc.so
 ()
 () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
 start_thread (arg=0x7f0aec7a9700) at pthread_create.c:463
Title: packagekitd crashed with SIGSEGV in AptIntf::providesCodec()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
h9000 (h9000) 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 #1739916, 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.
  • Duplicate of a private bug Remove

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.