The incorrect calling to zenity via /etc/gdm3/config_error_dialog.patch which should use the --no-markup option for cases when the error messages contain <.

Bug #2005135 reported by Hongyi Zhao
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gdm3 (Ubuntu)
New
Undecided
Unassigned

Bug Description

The Ubuntu-specific patch to gdm that ends up calling [zenity --warning](https://git.launchpad.net/ubuntu/+source/gdm3/tree/debian/patches/ubuntu/config_error_dialog.patch), has the following problem:

The patch is probably trying to set the text to something that contains < which means the following text will be considered pango markup. It most likely is not pango markup though. So it need to use --no-markup when calling zenity to avoid the text being considered invalid markup.

See [here](https://discourse.gnome.org/t/are-you-sure-you-want-to-proceed-message-on-login/13758/10?u=hongyi-zhao) for more detailed discussion on this bug.

Tags: jammy gdm3 lunar
tags: added: jammy lunar
Revision history for this message
Gunnar Hjalmarsson (gunnarhj) wrote :

Thanks for your report! It's a duplicate of bug #1887252, so I have marked it as such.

But with that said, it would be great if you could read the discussion at the other bug, and let me know if you think that my alternative idea would help.

Revision history for this message
Hongyi Zhao (hongyi-zhao) wrote : Re: [Bug 2005135] Re: The incorrect calling to zenity via /etc/gdm3/config_error_dialog.patch which should use the --no-markup option for cases when the error messages contain <.

On Tue, Feb 7, 2023 at 1:35 AM Gunnar Hjalmarsson
<email address hidden> wrote:
>
> *** This bug is a duplicate of bug 1887252 ***
> https://bugs.launchpad.net/bugs/1887252
>
> Thanks for your report! It's a duplicate of bug #1887252, so I have
> marked it as such.
>
> But with that said, it would be great if you could read the discussion
> at the other bug, and let me know if you think that my alternative idea
> would help.

Thank you for letting me know your alternative nice solution. But
there are so many HTML Character Entities [1-2]. How does your method
deal with all these possible situations?

[1] https://www.w3schools.com/HTML/html_entities.asp
[2] https://stackoverflow.com/questions/5068951/what-do-lt-and-gt-stand-for

> ** This bug has been marked a duplicate of bug 1887252
> config-error-dialog.sh should pass --no-markup

Best,
Zhao

> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/2005135
>
> Title:
> The incorrect calling to zenity via
> /etc/gdm3/config_error_dialog.patch which should use the --no-markup
> option for cases when the error messages contain <.
>
> Status in gdm3 package in Ubuntu:
> New
>
> Bug description:
> The Ubuntu-specific patch to gdm that ends up calling [zenity
> --warning](https://git.launchpad.net/ubuntu/+source/gdm3/tree/debian/patches/ubuntu/config_error_dialog.patch),
> has the following problem:
>
> The patch is probably trying to set the text to something that
> contains < which means the following text will be considered pango
> markup. It most likely is not pango markup though. So it need to use
> --no-markup when calling zenity to avoid the text being considered
> invalid markup.
>
> See [here](https://discourse.gnome.org/t/are-you-sure-you-want-to-
> proceed-message-on-login/13758/10?u=hongyi-zhao) for more detailed
> discussion on this bug.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2005135/+subscriptions
>

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.