Oh no! Something has gone wrong
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-shell (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I got the "Oh no!" screen.
The likely trigger was when I was playing a game and took a screenshot - where the environment is likely hard to reproduce because the game I'm playing that triggered the scenario isn't out yet. It can be built tho.
1) git clone https:/
2) git checkout core18
3) snapcraft --use-lxd
(wait a while, it's a monster snap)
4) snap install boa*.snap --dangerous
5) snap run boa
(wait for game to load to title screen)
6) press ALT+PrintScreen to get a screenshot
GNOME crashed at this point, giving me the "Oh no!" screen.
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: gnome-shell 3.38.1-1ubuntu1.1
ProcVersionSign
Uname: Linux 5.8.0-26-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.11-0ubuntu50.2
Architecture: amd64
CasperMD5CheckR
CurrentDesktop: ubuntu:GNOME
Date: Tue Dec 8 10:54:10 2020
DisplayManager: gdm3
InstallationDate: Installed on 2020-08-15 (114 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
RelatedPackageV
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to groovy on 2020-09-20 (78 days ago)
I'm not sure what the conditions are for that screen showing or failing to show (usually the latter in my experience), but your journal.txt says:
Dec 08 09:46:19 robot gnome-shell[ 1637760] : Error in freeze/thaw accounting 1637760] : GNOME Shell crashed with signal 5 1637760] : == Stack trace for context 0x55d585a44220 == 1637760] : #0 55d585f7f1d8 i resource: ///org/ gnome/shell/ ui/windowManage r.js:1384 (3fe24e7d03d0 @ 589)
Dec 08 09:46:19 robot gnome-shell[
Dec 08 09:46:19 robot gnome-shell[
Dec 08 09:46:19 robot gnome-shell[
so that's bug 1897765.