toggling down object GInotifyFileMonitor that's already queued to toggle up ... GNOME Shell crashed with signal 5
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gjs |
Fix Released
|
Unknown
|
|||
gjs (Ubuntu) |
Fix Released
|
Medium
|
Marco Trevisan (Treviño) | ||
Hirsute |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
[ Impact ]
Gnome shell crashes when unexpected references happens on other threads
[ Test case ]
Createa file called modify.py:
#!/usr/bin/env python3
import time
import random
while True:
time.
with open('/
Create a file called crash-me.js:
#!/usr/bin/gjs
const {GLib, Gio} = imports.gi;
const watchFile = Gio.file_
const fileMonitor = watchFile.
fileMonitor.
GLib.MainLoop.
Open two terminals and run (in each):
$ python3 modify.py
$ gjs crash-me.js
gjs should run for some minutes without crashing.
[ Regression potential ]
gjs may use memory or not free correctly created objects
---
https:/
---
A couple of times a day, I'm noticing all of the window dressing suddenly disappear from all of my open applications, then a second or two later returning. Opening up /var/log/syslog I see:
Jun 6 20:45:53 eva gnome-shell[
Jun 6 20:46:40 eva gnome-shell[
Jun 6 20:47:40 eva gnome-shell[
Jun 6 20:47:40 eva gnome-shell[
Jun 6 20:47:40 eva gnome-shell[
Jun 6 20:47:40 eva systemd[25554]: gnome-shell-
Jun 6 20:47:40 eva systemd[25554]: gnome-shell-
Jun 6 20:47:40 eva systemd[25554]: gnome-shell-
Jun 6 20:47:40 eva systemd[25554]: Stopped target GNOME X11 Session (session: ubuntu).
Jun 6 20:47:40 eva systemd[25554]: Stopping GNOME X11 Session (session: ubuntu).
Jun 6 20:47:40 eva systemd[25554]: Stopped target GNOME X11 Session.
Jun 6 20:47:40 eva systemd[25554]: Stopping GNOME X11 Session.
Jun 6 20:47:40 eva systemd[25554]: Stopped target GNOME Shell on X11.
Jun 6 20:47:40 eva systemd[25554]: Stopping GNOME Shell on X11.
Jun 6 20:47:40 eva systemd[25554]: Stopped GNOME Shell on X11.
Jun 6 20:47:40 eva systemd[25554]: Starting GNOME Shell on X11...
Jun 6 20:47:40 eva /usr/lib/
Jun 6 20:47:40 eva /usr/lib/
Jun 6 20:47:40 eva /usr/lib/
Jun 6 20:47:40 eva /usr/lib/
Jun 6 20:47:40 eva /usr/lib/
Jun 6 20:47:40 eva /usr/lib/
Jun 6 20:47:40 eva /usr/lib/
Jun 6 20:47:40 eva /usr/lib/
Jun 6 20:47:40 eva /usr/lib/
Jun 6 20:47:40 eva /usr/lib/
Jun 6 20:47:40 eva /usr/lib/
Jun 6 20:47:40 eva /usr/lib/
Jun 6 20:47:40 eva /usr/lib/
Jun 6 20:47:40 eva /usr/lib/
Jun 6 20:47:40 eva /usr/lib/
Jun 6 20:47:40 eva /usr/lib/
Jun 6 20:47:40 eva /usr/lib/
Jun 6 20:47:40 eva /usr/lib/
Jun 6 20:47:40 eva /usr/lib/
Jun 6 20:47:40 eva gsd-media-
Jun 6 20:47:41 eva gnome-shell[
Jun 6 20:47:41 eva gnome-shell[
Jun 6 20:47:41 eva gnome-shell[
Jun 6 20:47:41 eva gsd-media-
Jun 6 20:47:41 eva dbus-daemon[1068]: [system] Activating via systemd: service name='org.
Jun 6 20:47:41 eva systemd[1]: Starting Location Lookup Service...
Jun 6 20:47:41 eva gnome-shell[
Jun 6 20:47:41 eva dbus-daemon[1068]: [system] Successfully activated service 'org.freedeskto
Jun 6 20:47:41 eva systemd[1]: Started Location Lookup Service.
Jun 6 20:47:41 eva dbus-daemon[1068]: [system] Activating via systemd: service name='org.
Jun 6 20:47:41 eva systemd[1]: Starting PackageKit Daemon...
Jun 6 20:47:41 eva PackageKit: daemon start
Jun 6 20:47:41 eva dbus-daemon[1068]: [system] Successfully activated service 'org.freedeskto
Jun 6 20:47:41 eva systemd[1]: Started PackageKit Daemon.
Jun 6 20:47:42 eva dbus-daemon[25576]: [session uid=1001 pid=25576] Activating service name='org.
Jun 6 20:47:42 eva dbus-daemon[25576]: [session uid=1001 pid=25576] Activating service name='org.
Jun 6 20:47:42 eva dbus-daemon[25576]: [session uid=1001 pid=25576] Successfully activated service 'org.gnome.
Jun 6 20:47:42 eva dbus-daemon[25576]: [session uid=1001 pid=25576] Successfully activated service 'org.freedeskto
Jun 6 20:47:42 eva systemd[25554]: Started GNOME Shell on X11.
Jun 6 20:47:42 eva systemd[25554]: Reached target GNOME Shell on X11.
Jun 6 20:47:42 eva systemd[25554]: Reached target GNOME X11 Session.
Jun 6 20:47:42 eva systemd[25554]: Reached target GNOME X11 Session (session: ubuntu).
Jun 6 20:47:42 eva NetworkManager[
Jun 6 20:47:42 eva gnome-shell[
Jun 6 20:47:42 eva gsd-media-
Jun 6 20:47:42 eva gsd-media-
Jun 6 20:47:42 eva gsd-media-
Jun 6 20:47:42 eva gsd-media-
Jun 6 20:47:43 eva gnome-shell[
Jun 6 20:47:43 eva gnome-shell[
Jun 6 20:47:43 eva gnome-shell[
Jun 6 20:47:43 eva gnome-shell[
Jun 6 20:47:43 eva gnome-shell[
Jun 6 20:47:43 eva gnome-shell[
Jun 6 20:47:43 eva gnome-shell[
Jun 6 20:47:43 eva gnome-shell[
Jun 6 20:47:43 eva gnome-shell[
Jun 6 20:47:44 eva gnome-shell[
Jun 6 20:47:44 eva gnome-shell[
Seems to recover fine afterwards, but it happens again further down the line.
Seems like something mnemosyne is doing during the transition after I hit a number is triggering this...but only one out of every couple hundred(thousand?) cards.
mnemosyne:
Installed: 2.7.1+ds-1
Candidate: 2.7.1+ds-1
Version table:
*** 2.7.1+ds-1 500
500 http://
500 http://
100 /var/lib/
themusicgod1@
gnome-shell:
Installed: 3.36.1-5ubuntu1
Candidate: 3.36.1-5ubuntu1
Version table:
*** 3.36.1-5ubuntu1 500
500 http://
100 /var/lib/
themusicgod1@
DISTRIB_ID=Ubuntu
DISTRIB_
DISTRIB_
DISTRIB_
ProblemType: BugDistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.1-5ubuntu1
ProcVersionSign
Uname: Linux 5.4.0-26-lowlatency x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckR
CurrentDesktop: ubuntu:GNOME
Date: Sat Jun 6 20:52:49 2020
DisplayManager: gdm3
InstallationDate: Installed on 2017-04-18 (1145 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
RelatedPackageV
UpgradeStatus: Upgraded to focal on 2020-04-25 (42 days ago)
tags: | added: groovy |
Changed in gjs (Ubuntu): | |
status: | Confirmed → Fix Committed |
assignee: | nobody → Marco Trevisan (Treviño) (3v1n0) |
importance: | Undecided → Medium |
no longer affects: | gnome-shell (Ubuntu) |
tags: | added: fixed-in-1.68.1 fixed-upstream |
description: | updated |
Changed in gjs: | |
status: | Unknown → Fix Released |
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.