Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 2053530

Summary: Regression in update from zenity-3.22 to zenity-3.28
Product: Red Hat Enterprise Linux 8 Reporter: Paulo Andrade <pandrade>
Component: zenityAssignee: David King <dking>
Status: CLOSED ERRATA QA Contact: Michal Odehnal <modehnal>
Severity: medium Docs Contact:
Priority: medium    
Version: 8.7CC: loskutov, sbarcomb, tpelka, tpopela
Target Milestone: rcKeywords: Triaged
Target Release: ---Flags: pm-rhel: mirror+
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: zenity-3.28.1-2.el8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 2078712 (view as bug list) Environment:
Last Closed: 2022-11-08 09:37:21 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 2078712    
Deadline: 2022-05-30   

Description Paulo Andrade 2022-02-11 13:29:09 UTC
This bug was initially created as a copy of Bug #2053529

I am copying this bug because: 



Customer relies on behaviour of zenity 3.22. Or better saying,
requests revert of 
  https://gitlab.gnome.org/GNOME/zenity/-/commit/3b64d05e8a1aae1581d2bec7288d80ac4699e1b1
[Fix message dialog width and height on recent Gtk]

  Customer is aware that "most" of the old behaviour can be get back
with the --no-wrap option, but they have a very large product, and
do not expect to need to review every usage of zenity.

  Please see https://en.wikipedia.org/wiki/Zenity and the Posix example.

  One extreme example is:

zenity --question  --text="`perl -e 'print \"abc \" x 512'`"

previously would not be great, as it would just create a full screen
window, but would correctly wrap the text. Now, in 3.28, it creates a
really tall window. The --no-wrap option does not help, as it will just
not wrap and create a very large window.

Comment 2 Andrey Loskutov 2022-02-14 10:48:30 UTC
Our original example wasn't that extreme at all, just look at it:

zenity --title "" --error --text='Cannot launch another application instance since there is already a running one!'

With new zenity it wraps every word to a new line, old one showed the sentence in one line, not wrapped at all

Comment 3 David King 2022-04-25 12:55:02 UTC
I just submitted a merge request upstream to set the maximum width to 60 characters. That fixes the case in comment #2 and improves the case in comment #0 but does not fix it.

Comment 4 Tomas Popela 2022-04-26 05:24:47 UTC
I will clone this for RHEL 9 so we fix it there as well.

Comment 9 errata-xmlrpc 2022-11-08 09:37:21 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (zenity bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2022:7545