toggling down object GInotifyFileMonitor that's already queued to toggle up ... GNOME Shell crashed with signal 5

[themusicgod1]

[ 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.sleep(0.001)
    with open('/tmp/testfile', 'w') as f:
        f.write(str(random.random()))

Create a file called crash-me.js:

#!/usr/bin/gjs

const {GLib, Gio} = imports.gi;
const watchFile = Gio.file_new_for_path('/tmp/testfile');
const fileMonitor = watchFile.monitor(Gio.FileMonitorFlags.NONE, null);
fileMonitor.connect('changed', () => {});

GLib.MainLoop.new(null, false).run();

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://errors.ubuntu.com/problem/a6a50b0ae57f939286a1782a5fc9c45a296d2215

---

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[335243]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0x4a00015 specified for 0x4a00518.
Jun 6 20:46:40 eva gnome-shell[335243]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0x4a00015 specified for 0x4a0051f.
Jun 6 20:47:40 eva gnome-shell[335243]: toggling down object GInotifyFileMonitor that's already queued to toggle down
Jun 6 20:47:40 eva gnome-shell[335243]: GNOME Shell crashed with signal 5
Jun 6 20:47:40 eva gnome-shell[335243]: == Stack trace for context 0x557e3a0446a0 ==
Jun 6 20:47:40 eva systemd[25554]: gnome-shell-x11.service: Main process exited, code=dumped, status=5/TRAP
Jun 6 20:47:40 eva systemd[25554]: gnome-shell-x11.service: Failed with result 'core-dump'.
Jun 6 20:47:40 eva systemd[25554]: gnome-shell-x11.service: Scheduled restart job, restart counter is at 3.
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/gdm3/gdm-x-session[25623]: (II) modeset(0): EDID vendor "ACI", prod id 8434
Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Using hsync ranges from config file
Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Using vrefresh ranges from config file
Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Printing DDC gathered Modelines:
Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "1600x900"x0.0 108.00 1600 1624 1704 1800 900 901 904 1000 +hsync +vsync (60.0 kHz eP)
Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "800x600"x0.0 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e)
Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "640x480"x0.0 31.50 640 664 704 832 480 489 492 520 -hsync -vsync (37.9 kHz e)
Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "640x480"x0.0 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz e)
Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e)
Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "1024x768"x0.0 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz e)
Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "832x624"x0.0 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e)
Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "800x600"x0.0 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz e)
Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "1152x864"x0.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
Jun 6 20:47:40 eva gsd-media-keys[26011]: Failed to grab accelerators: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface “org.gnome.Shell” on object at path /org/gnome/Shell
Jun 6 20:47:41 eva gnome-shell[338452]: Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly.
Jun 6 20:47:41 eva gnome-shell[338452]: Will monitor session 764
Jun 6 20:47:41 eva gnome-shell[338477]: current session already has an ibus-daemon.
Jun 6 20:47:41 eva gsd-media-keys[26011]: Failed to grab accelerators: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface “org.gnome.Shell” on object at path /org/gnome/Shell
Jun 6 20:47:41 eva dbus-daemon[1068]: [system] Activating via systemd: service name='org.freedesktop.GeoClue2' unit='geoclue.service' requested by ':1.21125' (uid=1001 pid=338452 comm="/usr/bin/gnome-shell " label="unconfined")
Jun 6 20:47:41 eva systemd[1]: Starting Location Lookup Service...
Jun 6 20:47:41 eva gnome-shell[338452]: Telepathy is not available, chat integration will be disabled.
Jun 6 20:47:41 eva dbus-daemon[1068]: [system] Successfully activated service 'org.freedesktop.GeoClue2'
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.freedesktop.PackageKit' unit='packagekit.service' requested by ':1.21125' (uid=1001 pid=338452 comm="/usr/bin/gnome-shell " label="unconfined")
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.freedesktop.PackageKit'
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.freedesktop.FileManager1' requested by ':1.15623' (uid=1001 pid=338452 comm="/usr/bin/gnome-shell " label="unconfined")
Jun 6 20:47:42 eva dbus-daemon[25576]: [session uid=1001 pid=25576] Activating service name='org.gnome.Shell.Notifications' requested by ':1.15623' (uid=1001 pid=338452 comm="/usr/bin/gnome-shell " label="unconfined")
Jun 6 20:47:42 eva dbus-daemon[25576]: [session uid=1001 pid=25576] Successfully activated service 'org.gnome.Shell.Notifications'
Jun 6 20:47:42 eva dbus-daemon[25576]: [session uid=1001 pid=25576] Successfully activated service 'org.freedesktop.FileManager1'
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[1069]: <info> [1591498062.4557] agent-manager: agent[3d345b5a383c546a,:1.21125/org.gnome.Shell.NetworkAgent/1001]: agent registered
Jun 6 20:47:42 eva gnome-shell[338452]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation
Jun 6 20:47:42 eva gsd-media-keys[26011]: Failed to grab accelerator for keybinding settings:playback-repeat
Jun 6 20:47:42 eva gsd-media-keys[26011]: Failed to grab accelerator for keybinding settings:rfkill
Jun 6 20:47:42 eva gsd-media-keys[26011]: Failed to grab accelerator for keybinding settings:playback-random
Jun 6 20:47:42 eva gsd-media-keys[26011]: Failed to grab accelerator for keybinding settings:hibernate
Jun 6 20:47:43 eva gnome-shell[338452]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
Jun 6 20:47:43 eva gnome-shell[338452]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).
Jun 6 20:47:43 eva gnome-shell[338452]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
Jun 6 20:47:43 eva gnome-shell[338452]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
Jun 6 20:47:43 eva gnome-shell[338452]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
Jun 6 20:47:43 eva gnome-shell[338452]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
Jun 6 20:47:43 eva gnome-shell[338452]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
Jun 6 20:47:43 eva gnome-shell[338452]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
Jun 6 20:47:43 eva gnome-shell[338452]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
Jun 6 20:47:44 eva gnome-shell[338452]: GNOME Shell started at Sat Jun 06 2020 20:47:41 GMT-0600 (CST)
Jun 6 20:47:44 eva gnome-shell[338452]: Registering session with GDM

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://mirrors.layeronline.com/ubuntu focal/universe amd64 Packages
        500 http://mirrors.layeronline.com/ubuntu focal/universe i386 Packages
        100 /var/lib/dpkg/status
themusicgod1@eva1:~$ apt-cache policy gnome-shell
gnome-shell:
  Installed: 3.36.1-5ubuntu1
  Candidate: 3.36.1-5ubuntu1
  Version table:
 *** 3.36.1-5ubuntu1 500
        500 http://mirrors.layeronline.com/ubuntu focal/main amd64 Packages
        100 /var/lib/dpkg/status
themusicgod1@eva1:~$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=20.04
DISTRIB_CODENAME=focal
DISTRIB_DESCRIPTION="Ubuntu 20.04 LTS"

ProblemType: BugDistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.1-5ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-26.30-lowlatency 5.4.30
Uname: Linux 5.4.0-26-lowlatency x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
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)
RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3SourcePackage: gnome-shell
UpgradeStatus: Upgraded to focal on 2020-04-25 (42 days ago)

[Daniel van Vugt (vanvugt)]

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.

[themusicgod1 (themusicgod1)]

alas there are 2 files in /var/crash neither of them line up with when the crash happened

nothing in https://errors.ubuntu.com/user/ID since 2017

I've made the change to /etc/apport/crashdb.conf (that was the workaround right?)

we'll see when it happens again after I reboot next

[themusicgod1 (themusicgod1)]

reproduced and got a crash file
but...

themusicgod1@eva1:~$ ubuntu-bug /var/crash/_usr_bin_gnome-shell.1001.crash

consistently results in Sorry, Ubuntu 20.04 has experienced an internal error

If you notice further problems, try restarting the computer
stack:
/usr/bin/gnome-shell

[themusicgod1 (themusicgod1)]

actually that little error window has a bunch of data in it
stack seems to be
() at /usr/lib/libgjs.so.0
() at /usr/lib/libgjs.so.0
() at /usr/lib/libgjs.so.0

i'm going to try installing the symbols for that and reproduce again

[Daniel van Vugt (vanvugt)]

Please try using 'apport-cli' instead of 'ubuntu-bug'. Please also follow all the steps in comment #2.

[themusicgod1 (themusicgod1)]

done

[Daniel van Vugt (vanvugt)]

We still don't have any usable information here, sorry. Please follow all the steps in comment #2 again.

[themusicgod1 (themusicgod1)]

still nothing in https://errors.ubuntu.com/user/ID since 2017

[Daniel van Vugt (vanvugt)]

Try this:

  Settings > Privacy > Diagnostics > Send error reports to Canonical = Automatic

then reproduce the crash and hopefully errors.ubuntu.com will show it.

Although I would hope that even with 'Manual' set you would find the crash file in /var/crash ..?

[themusicgod1 (themusicgod1)]

the file was in /var/crash hence where bug #1884925 's contents came from

[Daniel van Vugt (vanvugt)]

Good, bug 1884925 is what I need to look at then. But I can't because it is private. Are you able to set bug 1884925 to public?

[themusicgod1 (themusicgod1)]

done. hope i didn't just give away too much info

[themusicgod1 (themusicgod1)]

(ie is it safe to power on my computer after doing so or should i be changing the password or something? )

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Daniel van Vugt (vanvugt)]

Thanks. Bug 1884925 only confirms that:

[70766.731562] eva1 gnome-shell[3790]: toggling down object GInotifyFileMonitor that's already queued to toggle up
[70766.734900] eva1 gnome-shell[3790]: GNOME Shell crashed with signal 5
[70766.734900] eva1 gnome-shell[3790]: == Stack trace for context 0x55c1921056f0 ==
(stack trace missing from the log)

which is a tiny improvement.

The fact that GInotifyFileMonitor is mentioned makes me suspect the problem is the Desktop Icons extension. Please try disabling 'Desktop Icons' in the 'Extensions' app (gnome-shell-extension-prefs).

[themusicgod1 (themusicgod1)]

done. we'll see if it reproduces

[Daniel van Vugt (vanvugt)]

Seems it was reported here too:

https://gitlab.gnome.org/GNOME/gjs/-/issues/297

[themusicgod1 (themusicgod1)]

Now...maybe this is jumping the gun a little. But after disabling desktop icons I just spent a bunch of time on mnemosyne (which was triggering this)...and it didn't trigger. Maybe I lucked out and just didn't trigger it...but it's awfully suspicious that it didn't trigger.

[Daniel van Vugt (vanvugt)]

Certainly most instances of GInotifyFileMonitor would be in the Desktop Icons extension. Still annoying we can't get a stack trace.

[Jim Persson (spambox2)]

This is happening to me a few times every day lately. I do not have any icons on the desktop.

#0 __GI_raise (sig=<optimized out>) at ../sysdeps/unix/sysv/linux/raise.c:50
#1 0x0000556612c6552a in dump_gjs_stack_on_signal_handler (signo=5) at ../src/main.c:421
#2 0x00007f17472b6210 in <signal handler called> () at /lib/x86_64-linux-gnu/libc.so.6
#3 _g_log_abort (breakpoint=1) at ../../../glib/gmessages.c:554
#4 0x00007f17480f8159 in g_log_default_handler (log_domain=<optimized out>, log_level=<optimized out>, message=<optimized out>, unused_data=<optimized out>) at ../../../glib/gmessages.c:3123
#5 0x0000556612c655ee in default_log_handler (log_domain=0x7f1747836e20 "Gjs", log_level=6, message=0x55661bb3aca0 "toggling down object GInotifyFileMonitor that's already queued to toggle up\n", data=0x0)
    at ../src/main.c:363
#6 0x00007f17480f839c in g_logv (log_domain=0x7f1747836e20 "Gjs", log_level=G_LOG_LEVEL_ERROR, format=<optimized out>, args=args@entry=0x7ffc2bb6e820) at ../../../glib/gmessages.c:1350
#7 0x00007f17480f8583 in g_log
    (log_domain=log_domain@entry=0x7f1747836e20 "Gjs", log_level=log_level@entry=G_LOG_LEVEL_ERROR, format=format@entry=0x7f174783c308 "toggling down object %s that's already queued to toggle %s\n")
    at ../../../glib/gmessages.c:1415
#8 0x00007f17477e40a7 in wrapped_gobj_toggle_notify(void*, GObject*, gboolean) (gobj=0x556615cd10b0 [GInotifyFileMonitor], is_last_ref=<optimized out>) at ../gi/object.cpp:1274
#9 0x00007f17477f7058 in ToggleQueue::handle_toggle(void (*)(_GObject*, ToggleQueue::Direction))
    (this=0x7f17478a14a0 <ToggleQueue::get_default()::the_singleton>, handler=0x7f17477e3f20 <toggle_handler(GObject*, ToggleQueue::Direction)>) at ../gi/toggle.cpp:125
#10 0x00007f17477f70df in ToggleQueue::idle_handle_toggle(void*) (data=0x7f17478a14a0 <ToggleQueue::get_default()::the_singleton>) at ../gi/toggle.cpp:69
#11 0x00007f17480f0e8e in g_main_dispatch (context=0x5566149c1350) at ../../../glib/gmain.c:3309
#12 g_main_context_dispatch (context=context@entry=0x5566149c1350) at ../../../glib/gmain.c:3974
#13 0x00007f17480f1240 in g_main_context_iterate (context=0x5566149c1350, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at ../../../glib/gmain.c:4047
#14 0x00007f17480f1533 in g_main_loop_run (loop=0x556614e05dc0) at ../../../glib/gmain.c:4241
#15 0x00007f174751aaf0 in meta_run () at /lib/x86_64-linux-gnu/libmutter-6.so.0
#16 0x0000556612c64d7d in main (argc=<optimized out>, argv=<optimized out>) at ../src/main.c:634

[Daniel van Vugt (vanvugt)]

Tracking in: https://errors.ubuntu.com/problem/a6a50b0ae57f939286a1782a5fc9c45a296d2215

[Jim Persson (spambox2)]

Is there any workaround to this issue?
This is a huge productivity killer for me.

[Daniel van Vugt (vanvugt)]

The crash appears to be relatively rare globally:

  20.04: 602 times
  20.10: 52 times

I hope I was wrong thinking that this might be caused by the desktop-icons extension. Please start by uninstalling all extensions except those three that are shipped with Ubuntu.

[Daniel van Vugt (vanvugt)]

You can also try disabling the 'Desktop Icons' extension in the 'Extensions' app.

[Jim Persson (spambox2)]

I've had the "Desktop Icons" disabled for a while now, and it doesn't solve the problem but it feels like it is less frequent.

It most often happens when I open a new terminal.

[Dario Petrillo (dariop1)]

I would like to confirm that this bug happens to me as well on Ubuntu 20.04.1.

I've been able to reproduce it consistently when downloading two or more big (1GB+) files at the same time from google drive on chrome to the Desktop folder.
Downloading the files one at a time or to a different folder doesn't seem to trigger the bug, at least for me

[Launchpad Janitor (janitor)]

This bug was fixed in the package gjs - 1.68.0-2

---------------
gjs (1.68.0-2) experimental; urgency=medium

  * debian/patches: Cherry-pick upstream memory fixes

 -- Marco Trevisan (Treviño) <email address hidden> Wed, 05 May 2021 05:53:50 +0200

[Timo Aaltonen (tjaalton)]

Hello themusicgod1, or anyone else affected,

Accepted gjs into hirsute-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gjs/1.68.1-1~ubuntu0.21.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-hirsute to verification-done-hirsute. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-hirsute. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Brian Murray (brian-murray)]

The Hirsute Hippo has reached End of Life, so this bug will not be fixed for that release.