Ubuntu
packagekit package

packagekitd crashed with SIGSEGV in __strncasecmp_l_avx()

Bug #1818059 reported by Pavlushka on 2019-02-28

This bug affects 2 people

Affects		Status	Importance	Assigned to	Milestone
	packagekit (Ubuntu)	New	High	Unassigned

Bug Description

Kept happening since yesterday 27-02-2019 every time the system starts.

ProblemType: Crash
DistroRelease: Ubuntu 19.04
Package: packagekit 1.1.12-1ubuntu1
ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
Uname: Linux 4.19.0-13-generic x86_64
ApportVersion: 2.20.10-0ubuntu21
Architecture: amd64
CrashCounter: 1
Date: Thu Feb 28 16:48:30 2019
ExecutablePath: /usr/lib/packagekit/packagekitd
InstallationDate: Installed on 2019-02-26 (1 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190226)
ProcCmdline: /usr/lib/packagekit/packagekitd
Signal: 11
SourcePackage: packagekit
StacktraceTop:
__strncasecmp_l_avx () at ../sysdeps/x86_64/multiarch/strcmp-sse42.S:260
std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >::_M_replace(unsigned long, unsigned long, char const*, unsigned long) () from /lib/x86_64-linux-gnu/libstdc++.so.6
show_errors(PkBackendJob*, PkErrorEnum, bool) () from /usr/lib/x86_64-linux-gnu/packagekit-backend/libpk_backend_aptcc.so
?? ()
?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: packagekitd crashed with SIGSEGV in __strncasecmp_l_avx()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

separator:

Tags:

Revision history for this message

Pavlushka (pavelsayekat) wrote on 2019-02-28:

CoreDump.gz Edit (1.7 MiB, application/x-gzip)
Dependencies.txt Edit (3.2 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (1.1 KiB, text/plain; charset="utf-8")
JournalErrors.txt Edit (47.2 KiB, text/plain; charset="utf-8")
ProcCpuinfoMinimal.txt Edit (1.1 KiB, text/plain; charset="utf-8")
ProcEnviron.txt Edit (212 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (29.6 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (1.3 KiB, text/plain; charset="utf-8")
Registers.txt Edit (1.0 KiB, text/plain; charset="utf-8")
SegvAnalysis.txt Edit (295 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (778 bytes, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (7.2 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2019-02-28:

StacktraceTop:
?? () from /tmp/apport_sandbox_4adiydqt/lib/x86_64-linux-gnu/libc.so.6
?? ()
?? ()
?? ()
?? ()

Revision history for this message

Apport retracing service (apport) wrote on 2019-02-28: Stacktrace.txt

Stacktrace.txt Edit (2.5 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2019-02-28: StacktraceSource.txt

StacktraceSource.txt Edit (2.8 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2019-02-28: ThreadStacktrace.txt

ThreadStacktrace.txt Edit (8.3 KiB, text/plain)

tags:	added: apport-failed-retrace
tags:	removed: need-amd64-retrace

Revision history for this message

Pavlushka (pavelsayekat) wrote on 2019-02-28:

My bad, should have updated the previous (yesterday's) bug.

Revision history for this message

Sebastien Bacher (seb128) wrote on 2019-02-28:

Thank you for your bug report. Could you get a backtrace as explained on https://wiki.ubuntu.com/Backtrace? Do you get any debug info if you start /usr/lib/packagekit/packagekitd manually?

Changed in packagekit (Ubuntu):
importance:	Undecided → High
status:	New → Incomplete

Revision history for this message

Pavlushka (pavelsayekat) wrote on 2019-02-28:

gdb packagekitd trace Edit (5.9 KiB, text/plain)

Tried to do as per asking according to https://wiki.ubuntu.com/Backtrace.

Revision history for this message

Pavlushka (pavelsayekat) wrote on 2019-02-28:

strace of packagekitd Edit (93.6 KiB, text/plain)

and also

Changed in packagekit (Ubuntu):
status:	Incomplete → New

Revision history for this message

Sebastien Bacher (seb128) wrote on 2019-02-28:

#10

The gdb log has a sigint, not a sigsegv (which is the issue initially reported), did you ctrl-C it? If not you might want to type "c" (and validate with enter) to resume the program until you hit the segfault

Sebastien Bacher (seb128) on 2019-03-01

information type:

Private → Public

Revision history for this message

Pavlushka (pavelsayekat) wrote on 2019-03-01:

#11

like this?

Revision history for this message

Pavlushka (pavelsayekat) wrote on 2019-03-01:

#12

gdb-packagekit.txt Edit (1.5 KiB, text/plain)

like this?

Revision history for this message

Sebastien Bacher (seb128) wrote on 2019-03-01:

#13

No segfault, but we believe we found the issue and fixed it in https://bugs.launchpad.net/ubuntu/+source/packagekit/1.1.12-2ubuntu1 if you could try that upgrade

Changed in packagekit (Ubuntu):
status:	New → Incomplete

Revision history for this message

Launchpad Janitor (janitor) wrote on 2019-05-01:

#14

[Expired for packagekit (Ubuntu) because there has been no activity for 60 days.]

Changed in packagekit (Ubuntu):
status:	Incomplete → Expired

Revision history for this message

Juli Tovar (ubuntling) wrote on 2020-01-26:

#15

I just wanted to add, I'm having this bug in Ubuntu 20.04 Focal Fossa, every single time I start after suspend, that's why I selected that I'm having this bug, to avoid duplication of bugs, since this happens every time I start after suspend.

Changed in packagekit (Ubuntu):
status:	Expired → New

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

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

Ubuntupackagekit package

packagekitd crashed with SIGSEGV in __strncasecmp_l_avx()

Bug Description

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
packagekit package