gnome-shell crashed with SIGSEGV

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

Bug Description

Was using laptop standalone (laptop LCD display only). Put it into dock which has two monitors plugged into it. Forgot that it was still powered on, so I pushed the power button on the dock, thinking I was waking it up when in fact I was putting it to sleep. When monitors didn't come alive, I opened the lid to see if that would help. That woke it up. Then I closed the lid again to switch to just the monitors. The monitors went blank for a while then I was able to log in, and that's the point at which I got the pop-up about gnome-shell having crashed.

ProblemType: Crash
DistroRelease: Ubuntu 18.10
Package: gnome-shell 3.30.1-2ubuntu1
ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
Uname: Linux 4.18.0-10-generic x86_64
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Nov 9 08:26:51 2018
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
InstallationDate: Installed on 2018-09-27 (42 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
ProcCmdline: /usr/bin/gnome-shell
ProcEnviron:
 LC_COLLATE=C
 PATH=(custom, user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fd7d7a083e0: mov 0x128(%rdi),%rax
 PC (0x7fd7d7a083e0) ok
 source "0x128(%rdi)" (0x00000128) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
 () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-3.so
 () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-3.so
 () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-3.so
 clutter_x11_handle_event () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-3.so
 () at /usr/lib/x86_64-linux-gnu/libmutter-3.so.0
Title: gnome-shell crashed with SIGSEGV
UpgradeStatus: Upgraded to cosmic on 2018-11-08 (0 days ago)
UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo vboxusers wireshark
modified.conffile..etc.apport.crashdb.conf: [modified]
mtime.conffile..etc.apport.crashdb.conf: 2018-10-04T06:36:50.792292

Revision history for this message
Jonathan Kamens (jik) 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 #1783673, 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.