gnome-shell crashed with SIGSEGV in wl_resource_get_version()

Bug #1867414 reported by Matthew Orr
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-shell (Ubuntu)
New
Undecided
Unassigned

Bug Description

crash when using wayland gnome session

ProblemType: Crash
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.35.91-1ubuntu2
Uname: Linux 5.4.24-xanmod13 x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu20
Architecture: amd64
CurrentDesktop: GNOME
Date: Sat Mar 14 01:13:28 2020
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
InstallationDate: Installed on 2020-03-14 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309)
ProcCmdline: /usr/bin/gnome-shell
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/usr/bin/fish
 XDG_RUNTIME_DIR=<set>
RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1
SegvAnalysis:
 Segfault happened at: 0x7fb96802c624 <wl_resource_get_version+4>: mov 0x50(%rdi),%eax
 PC (0x7fb96802c624) ok
 source "0x50(%rdi)" (0x00000050) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
 wl_resource_get_version () from /lib/x86_64-linux-gnu/libwayland-server.so.0
 ?? () from /lib/x86_64-linux-gnu/libmutter-6.so.0
 ?? () from /lib/x86_64-linux-gnu/libmutter-6.so.0
 ?? () from /lib/x86_64-linux-gnu/libmutter-6.so.0
 ?? () from /lib/x86_64-linux-gnu/libmutter-6.so.0
Title: gnome-shell crashed with SIGSEGV in wl_resource_get_version()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
separator:

Revision history for this message
Matthew Orr (pawp) 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 #1866368, 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.

Other bug subscribers

Remote bug watches

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