packagekitd crashed with SIGSEGV in __memmove_avx_unaligned_erms()

[El jinete sin cabeza]

I have performance problems, after updating.

ProblemType: Crash
DistroRelease: Ubuntu 19.04
Package: packagekit 1.1.12-1ubuntu1
Uname: Linux 5.0.0-050000rc6-generic x86_64
ApportVersion: 2.20.10-0ubuntu21
Architecture: amd64
CrashCounter: 1
Date: Mon Feb 18 07:41:04 2019
ExecutablePath: /usr/lib/packagekit/packagekitd
InstallationDate: Installed on 2018-12-02 (77 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
ProcCmdline: /usr/lib/packagekit/packagekitd
ProcEnviron:
 LANG=es_CL.UTF-8
 LANGUAGE=es_CL:es
 PATH=(custom, no user)
 SHELL=/bin/sh
SegvAnalysis:
 Segfault happened at: 0x7f9e22107742 <__memmove_avx_unaligned_erms+770>: vmovntdq %ymm0,(%rdi)
 PC (0x7f9e22107742) ok
 source "%ymm0" ok
 destination "(%rdi)" (0x00000340) not located in a known VMA region (needed writable region)!
 Stack memory exhausted (SP below stack segment)
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: packagekit
StacktraceTop:
 __memmove_avx_unaligned_erms () at ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:495
 std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >::_M_replace(unsigned long, unsigned long, char const*, unsigned long) () from /usr/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 /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: packagekitd crashed with SIGSEGV in __memmove_avx_unaligned_erms()
UpgradeStatus: Upgraded to disco on 2018-12-02 (77 days ago)
UserGroups:

separator:

[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 #1788816, 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.