This bug was fixed in the package gjs - 1.72.4-0ubuntu0.22.04.1
---------------
gjs (1.72.4-0ubuntu0.22.04.1) jammy; urgency=medium
* New upstream stable release (LP: #2023572)
* debian/patches: Drop, they've been all applied upstream
gjs (1.72.3-0ubuntu0.22.04.1) jammy; urgency=medium
* New upstream release (LP: #2023572):
* debian/patches: Refresh teardown patch, replacing it with the one landed
upstream (LP: #1974293)
* debian/patches: Cherry-pick upstream fixes to address various memory leaks
(LP: #2012978)
-- Marco Trevisan (Treviño) <ma...@ubuntu.com> Thu, 15 Jun 2023
17:23:40 +0200
** Changed in: gjs (Ubuntu Jammy)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gjs in Ubuntu.
https://bugs.launchpad.net/bugs/2023572
Title:
SRU gjs 1.72.4 to jammy
Status in gjs package in Ubuntu:
Fix Released
Status in gjs source package in Jammy:
Fix Released
Bug description:
[ Impact ]
That's the GNOME 42 stable update, including some fixes:
https://gitlab.gnome.org/GNOME/gjs/-/commits/1.72.4
[ Test case ]
The update is part of GNOME stable updates
https://wiki.ubuntu.com/StableReleaseUpdates/GNOME
The test plan that will be used is documented at
https://wiki.ubuntu.com/DesktopTeam/TestPlans/gjs
[ Regression potential ]
Gjs is fundamental part of the ubuntu desktop, so any failure of it
may cause the desktop not even to boot (because it's being used by gdm
too).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2023572/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
