gnome-shell crashed with signal 5 in clutter_actor_allocate()
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| gnome-shell (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
I'm on 20.04
When I lock the screen the login screen doesn't appear.
Instead sometimes it just flashes and doesn't lock the screen or the machine freezes and needs to be restarted.
I flagged this as security related because now as a user I can't lock my screen, so I either have to leave it unlocked or completely shut down my machine.
Thank you very much in advance!
Eduardo
ProblemType: Crash
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.35.91-1ubuntu2
ProcVersionSign
Uname: Linux 5.4.0-14-generic x86_64
ApportVersion: 2.20.11-0ubuntu19
Architecture: amd64
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Tue Mar 10 19:24:39 2020
DisplayManager: gdm3
ExecutablePath: /usr/bin/
InstallationDate: Installed on 2019-09-04 (187 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
ProcCmdline: /usr/bin/
ProcEnviron:
LANG=en_GB.UTF-8
LANGUAGE=en_GB:en
PATH=(custom, no user)
SHELL=/bin/bash
XDG_RUNTIME_
RelatedPackageV
Signal: 5
SourcePackage: gnome-shell
StacktraceTop:
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
clutter_
Title: gnome-shell crashed with signal 5 in clutter_
UpgradeStatus: Upgraded to focal on 2020-03-03 (7 days ago)
UserGroups: adm cdrom dip libvirt lpadmin microk8s plugdev sambashare sudo
separator:
| Eduardo Aguilar Pelaez (edu-ap) wrote | #1 |
| Apport retracing service (apport) wrote This bug is a duplicate | #2 |
| information type: | Private Security → Public Security |
| tags: | removed: need-amd64-retrace |
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 #1866044, 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.