Bug 2106872

Summary: Text not rendered fully as expected in package change log
Product: [Fedora] Fedora Reporter: Peter Stone <fedora-topics-562353>
Component: gnome-softwareAssignee: Milan Crha <mcrha>
Status: CLOSED UPSTREAM QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 36CC: gnome-sig, mcrha, rhughes
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-07-14 05:58: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:
Attachments:
Description Flags
wrong text render none

Description Peter Stone 2022-07-13 18:08:26 UTC
Created attachment 1896843 [details]
wrong text render

Description of problem: Characters (that need extra escaping in HTML code?) are not shown as intended in package change logs.


Version-Release number of selected component (if applicable): gnome-software 42.3, Fedora 36 Workstation


How reproducible: By manually inspecting a package update change log in GNOME Software.


Steps to Reproduce:
1. have the system in such a state that it requires gnome-control-center-filesystem to need to be updated to 42.3-1.fc36
2. go to Software, Updates, click on the gnome-control-center-filesystem entry
3. the change log line starting with "Fix Wi-Fi..." isn't shown properly, some characters appear as "&quot;"

Actual results: text to be rendered 100% as intended by the person writing the change log.


Expected results: text has some "&quot;" parts in it


Additional info: screenshot attached, second to last line has the weird text.

Comment 1 Milan Crha 2022-07-14 05:58:21 UTC
Thanks for a bug report. I filled a change upstream, with possible fix for this. It'll get to Fedora, if approved, in some future update.

Comment 2 Peter Stone 2022-07-24 18:27:39 UTC
Thank you very much! Looks like the fix is reaching GNOME 42.4, via MR#1430.