Bug 2090996

Summary: VPN panel of gnome-control-center cannot dispaly name of VPN with '&'
Product: [Fedora] Fedora Reporter: Dario Lesca <d.lesca>
Component: gnome-control-centerAssignee: GNOME SIG Unassigned <gnome-sig>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 36CC: amigadave, gnome-sig, walter.pete
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: gnome-control-center-42.3-1.fc36 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-05-25 19:33:01 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
gnome-control-center image with error
none
Test after https://bodhi.fedoraproject.org/updates/FEDORA-2022-3db9a9733f none

Description Dario Lesca 2022-05-27 09:29:53 UTC
Description of problem:

After update, the VPN name is not show if contain a '&' character

Version-Release number of selected component (if applicable):

gnome-control-center-42.1-2.fc36.x86_64

How reproducible:
 
Steps to Reproduce:
1. Add a new VPN or modify one and set its name whit & (es. "Alfa & Omega"
2. Close and reopen the panel

Actual results:

the name of this VPN are blank

Expected results:

Show all named VPN correctly 

Additional info:

If I run gnome-control-center from a terminal, I get this error message:

[lesca@fedora ~]$ LANG=C gnome-control-center 

(gnome-control-center:3817): Gtk-WARNING **: 11:26:04.239: Failed to set text 'Alfa & Omega' from markup due to error parsing markup: Error on line 1: Entity did not end with a semicolon; most likely you used an ampersand character without intending to start an entity ? escape ampersand as &amp;

Comment 1 Dario Lesca 2022-05-27 09:35:22 UTC
Created attachment 1884051 [details]
gnome-control-center image with error

Comment 2 Fedora Update System 2022-07-06 09:09:05 UTC
FEDORA-2022-3db9a9733f has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-3db9a9733f

Comment 3 Fedora Update System 2022-07-07 01:36:04 UTC
FEDORA-2022-3db9a9733f has been pushed to the Fedora 36 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-3db9a9733f`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-3db9a9733f

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 5 Dario Lesca 2022-07-11 10:42:01 UTC
> You can provide feedback for this update here:
> https://bodhi.fedoraproject.org/updates/FEDORA-2022-3db9a9733f

The problem still exist. See attached image

https://bugzilla.redhat.com/attachment.cgi?id=1896024&action=edit

Comment 6 Fedora Update System 2022-07-12 02:30:21 UTC
FEDORA-2022-3db9a9733f has been pushed to the Fedora 36 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 7 Dario Lesca 2022-07-12 22:08:48 UTC
(In reply to Fedora Update System from comment #6)
> FEDORA-2022-3db9a9733f has been pushed to the Fedora 36 stable repository.
> If problem still persists, please make note of it in this bug report.


The problem still exist. See attached image

https://bugzilla.redhat.com/attachment.cgi?id=1896024&action=edit

Comment 8 David King 2022-07-14 13:32:38 UTC
Sorry about this, I had assumed that the wifi panel changes also affected the VPN panel. Hopefully this new patch will fix things, once it is reviewed.

Comment 9 Ben Cotton 2023-04-25 18:26:35 UTC
This message is a reminder that Fedora Linux 36 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16.
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 EOL if it remains open with a
'version' of '36'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 36 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 Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 10 Ludek Smid 2023-05-25 19:33:01 UTC
Fedora Linux 36 entered end-of-life (EOL) status on 2023-05-16.

Fedora Linux 36 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 Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.