|Summary:||zenity --info chokes on certain inputs|
|Product:||[Fedora] Fedora||Reporter:||Daniel U. Thibault <d.u.thibault>|
|Component:||zenity||Assignee:||Matthias Clasen <mclasen>|
|Status:||CLOSED WONTFIX||QA Contact:||Fedora Extras Quality Assurance <extras-qa>|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2010-12-03 13:56:28 UTC||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
Description Daniel U. Thibault 2010-06-09 23:49:09 UTC
Description of problem: When the text passed to zenity --info contains "<=", zenity issues an error message on stderr but then displays an odd information dialog. How reproducible: Feed the output of some "rpm --requires" to "zenity --text-info". Steps to Reproduce: 1. RPMOUT=$(rpm -qp "rpmfilename" --requires) 2. zenity --info --text "$RPMOUT" Actual results: An info window stating "All updates are complete." stderr: (zenity:5416): GtkWARNING **: Failed to set text from markup due to error parsing markup. Error in line nn char xx: '=' is not a valid character following a '<' character; it may not begin an element name. Expected results: An actual zenity error window, or no window at all. Additional info: Substituting '\<' for '<' does not help. stderr indicates zenity tries to interpret the input text as xml, so apparently the "<=" needs to be escaped beforehand somehow.
Comment 1 Bug Zapper 2010-11-03 13:22:28 UTC
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Comment 2 Bug Zapper 2010-12-03 13:56:28 UTC
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.