Ubuntu
gnome-shell package

apps not responding desktop not responding

Bug #1864831 reported by pleabargain on 2020-02-26

This bug report is a duplicate of: Bug #1866044: gnome-shell crashed with signal 5 in clutter_box_layout_allocate() ("ClutterBoxLayout child Gjs_ui_shellEntry_CapsLockWarning natural height: 0.000000 < minimum 24.000000 for width ...") when enable-animations=false. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	gnome-shell (Ubuntu)	Incomplete	Undecided	Unassigned

Bug Description

I don't think this is bug
#889706

UI locks up
no response
ctrl alt F3
and then ran apport-bug
came back
ctrl alt F7 or F9(?)

desktop is responding but all apps that WERE open have closed

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1
ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
Uname: Linux 5.3.0-40-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.4
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Feb 26 12:42:26 2020
DisplayManager: gdm3
InstallationDate: Installed on 2015-08-23 (1647 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to eoan on 2019-10-23 (126 days ago)

Tags:

Revision history for this message

pleabargain (dennisgdaniels) wrote on 2020-02-26:

Dependencies.txt Edit (21.1 KiB, text/plain; charset="utf-8")
GsettingsChanges.txt Edit (7.1 KiB, text/plain; charset="utf-8")
ProcCpuinfoMinimal.txt Edit (1.0 KiB, text/plain; charset="utf-8")
ProcEnviron.txt Edit (310 bytes, text/plain; charset="utf-8")
ShellJournal.txt Edit (602.1 KiB, text/plain; charset="utf-8")
monitors.xml.txt Edit (2.8 KiB, text/plain; charset="utf-8")

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2020-02-27:

It sounds like maybe the gnome-shell process has crashed so...

Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself.

Changed in gnome-shell (Ubuntu):
status:	New → Incomplete

Revision history for this message

pleabargain (dennisgdaniels) wrote on 2020-02-28:

/var/crash$ apport-bug ubuntu-bug
dpkg-query: no packages found matching ubuntu-bug

/var/crash$ sudo apt-get install ubuntu-bug
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package ubuntu-bug

There is no app called ubuntu-bug
and
I did try to run
ubuntu-bug _usr_bin_gnome-shell.1000.crash

but nothing happened...
video
https://youtu.be/uhCMGAlQ2PM

Have I found another bug?

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2020-03-02:

If you have a file '_usr_bin_gnome-shell.1000.crash' and 'ubuntu-bug' does not work then please try this:

apport-cli _usr_bin_gnome-shell.1000.crash

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2020-03-19:

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1866044, so it 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. Feel free to continue to report any other bugs you may find.