gnome-shell crashed with SIGBUS in __memmove_avx_unaligned_erms() from util_copy_box() from util_resource_copy_region() from util_try_blit_via_copy_region() from lp_blit() from st_BlitFramebuffer() from blit_framebuffer()
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| gnome-shell (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
| mesa (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
| mutter (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
https:/
---
I do not know what caused this issue; Gnome Shell seems to be working just fine for me. Yet the Apport app popped up so I'm reporting the bug for the sake of completeness :)
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: gnome-shell 3.28.0-0ubuntu1
ProcVersionSign
Uname: Linux 4.15.0-13-generic x86_64
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME-Greeter:GNOME
Date: Thu Mar 29 09:22:55 2018
DisplayManager: gdm3
ExecutablePath: /usr/bin/
GsettingsChanges:
InstallationDate: Installed on 2016-09-05 (569 days ago)
InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
ProcCmdline: /usr/bin/
Signal: 7
SourcePackage: gnome-shell
StacktraceTop:
__memmove_
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
Title: gnome-shell crashed with signal 7 in __memmove_
UpgradeStatus: Upgraded to bionic on 2018-03-13 (15 days ago)
UserGroups:
| Martin Vysny (vyzivus) wrote | #1 |
| Apport retracing service (apport) wrote Stacktrace.txt | #2 |
| Apport retracing service (apport) wrote StacktraceSource.txt | #3 |
| Apport retracing service (apport) wrote StacktraceTop.txt | #4 |
| Apport retracing service (apport) wrote ThreadStacktrace.txt | #5 |
| Changed in gnome-shell (Ubuntu): | |
| importance: | Undecided → Medium |
| tags: | removed: need-amd64-retrace |
| Daniel van Vugt (vanvugt) wrote | #6 |
| summary: |
- gnome-shell crashed with signal 7 in __memmove_avx_unaligned_erms() + gnome-shell crashed with SIGBUS in __memmove_avx_unaligned_erms() from + util_copy_box() from util_resource_copy_region() from + util_try_blit_via_copy_region() from lp_blit() from st_BlitFramebuffer() + from blit_framebuffer() |
| tags: | added: wayland wayland-session |
| information type: | Private → Public |
| tags: | added: hybrid |
| tags: | added: nouveau |
| Launchpad Janitor (janitor) wrote | #7 |
| Changed in gnome-shell (Ubuntu): | |
| status: | New → Confirmed |
| Changed in mesa (Ubuntu): | |
| status: | New → Confirmed |
| Changed in mutter (Ubuntu): | |
| status: | New → Confirmed |
| Daniel van Vugt (vanvugt) wrote | #11 |
| Changed in gnome-shell (Ubuntu): | |
| status: | Confirmed → Fix Released |
| Changed in mesa (Ubuntu): | |
| status: | Confirmed → Fix Released |
| Changed in mutter (Ubuntu): | |
| status: | Confirmed → Fix Released |
The crash occurred in Mesa gallium code (so radeon or nouveau). However the caller was mutter (gnome-shell) from its hybrid GPU logic, which is only used in Wayland sessions.
I know that doesn't help users right now, but it's important information for developers.