This bug was fixed in the package zenity - 3.42.1-0ubuntu1
---
zenity (3.42.1-0ubuntu1) jammy; urgency=medium
* New upstream release (LP: #1970658)
-- Jeremy Bicha Sun, 01 May 2022 14:39:37 -0400
** Changed in: zenity (Ubuntu Jammy)
Status: Fix Committed => Fix Released
I installed zenity 3.42.1-0ubuntu1 and verified that the test case works
correctly now (but it didn't work with the older zenity version).
** Tags removed: verification-needed verification-needed-jammy
** Tags added: verification-done verification-done-jammy
--
You received this bug
Okay, it'd be real nice if we could wrap up the GNOME MRE discourse post
and have a solid list of packages to which we can all refer.
** Changed in: zenity (Ubuntu Jammy)
Status: Incomplete => Fix Committed
** Tags added: verification-needed verification-needed-jammy
--
You received
It is in https://gitlab.gnome.org/GNOME/gnome-build-
meta/-/tree/master/elements/core-deps
That group has some things that are not provided by GNOME like
NetworkManager. Things that are not part of GNOME shouldn't be part of
the GNOME microrelease exception, but zenity is provided by GNOME and
I don't see zenity listed at https://gitlab.gnome.org/GNOME/gnome-build-
meta/-/tree/master/elements/core nor is it in the list of packages on
the discourse post regarding the GNOME MRE
(https://discourse.ubuntu.com/t/scope-of-gnome-mru/18041/29).
Could you explain how this is a part of the GNOME
** Description changed:
Impact
--
+ New stable release in the 3.42 series.
+
+ https://gitlab.gnome.org/GNOME/zenity/-/blob/3.42.1/NEWS
Test Case
-
+ zenity --info --text="1234566789 223456789 323456789 423456789 523456789
623456789 723456789 823456789 923456789"
+
+
This bug was fixed in the package zenity - 3.42.1-1
---
zenity (3.42.1-1) unstable; urgency=medium
* New upstream release (LP: #1970658)
-- Jeremy Bicha Wed, 27 Apr 2022 15:37:34 -0400
** Changed in: zenity (Ubuntu)
Status: Triaged => Fix Released
--
You received this
