gnome-software crashed with SIGSEGV in __memmove_avx_unaligned_erms()

Bug #1843698 reported by El jinete sin cabeza
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
GNOME Software
Fix Released
Unknown
gnome-software (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

https://gitlab.gnome.org/GNOME/gnome-software/issues/792

---

I do not know what happened.

ProblemType: Crash
DistroRelease: Ubuntu 19.10
Package: gnome-software 3.30.6-2ubuntu10
ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
Uname: Linux 5.3.0-10-generic x86_64
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Sep 12 07:57:24 2019
ExecutablePath: /usr/bin/gnome-software
InstallationDate: Installed on 2018-12-02 (283 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
InstalledPlugins:
 gnome-software-plugin-flatpak 3.30.6-2ubuntu10
 gnome-software-plugin-snap 3.30.6-2ubuntu10
ProcCmdline: /usr/bin/gnome-software --gapplication-service
ProcEnviron:
 LANG=es_CL.UTF-8
 LANGUAGE=es_CL:es
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
SegvAnalysis:
 Segfault happened at: 0x7f565aa3fcc4 <__memmove_avx_unaligned_erms+372>: vmovdqu -0x20(%rsi,%rdx,1),%ymm5
 PC (0x7f565aa3fcc4) ok
 source "-0x20(%rsi,%rdx,1)" (0x7f5e4c1bab30) not located in a known VMA region (needed readable region)!
 destination "%ymm5" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-software
StacktraceTop:
 __memmove_avx_unaligned_erms () at ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:384
 g_ptr_array_remove_range () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_ptr_array_set_size () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
 as_store_remove_all () at /usr/lib/x86_64-linux-gnu/libappstream-glib.so.8
 () at /usr/lib/x86_64-linux-gnu/gs-plugins-12/libgs_plugin_flatpak.so
Title: gnome-software crashed with SIGSEGV in __memmove_avx_unaligned_erms()
UpgradeStatus: Upgraded to eoan on 2018-12-02 (283 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
separator:

Revision history for this message
El jinete sin cabeza (ejsc) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 __memmove_avx_unaligned_erms () at ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:384
 g_ptr_array_remove_range () from /tmp/apport_sandbox_62o4eebm/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_ptr_array_set_size () from /tmp/apport_sandbox_62o4eebm/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
 as_store_remove_all (store=0x560cffcee220) at ../libappstream-glib/as-store.c:360
 gs_flatpak_rescan_appstream_store (error=0x7f5644e659d8, cancellable=0x560d026f7860, self=0x560d01a67d20) at ../plugins/flatpak/gs-flatpak.c:735

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 gnome-software (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
El jinete sin cabeza (ejsc) wrote :
information type: Private → Public
description: updated
Changed in gnome-software:
status: Unknown → New
Changed in gnome-software:
status: New → Fix Released
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?

This will help us to find and resolve the problem.

Changed in gnome-software (Ubuntu):
status: New → Incomplete
Revision history for this message
Paul White (paulw2u) wrote :

Upstream bug was closed as user referred back to Ubuntu.
Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020.
Bug did not expire due to bug watch so after almost three
years with no response to comment #7 I'm closing this.

Changed in gnome-software (Ubuntu):
status: Incomplete → Invalid
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.