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?
> ** 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
>
On Tue, Feb 7, 2023 at 1:35 AM Gunnar Hjalmarsson /bugs.launchpad .net/bugs/ 1887252
<email address hidden> wrote:
>
> *** This bug is a duplicate of bug 1887252 ***
> https:/
>
> 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 /stackoverflow. com/questions/ 5068951/ what-do- lt-and- gt-stand- for
[2] https:/
> ** This bug has been marked a duplicate of bug 1887252 error-dialog. sh should pass --no-markup
> config-
Best,
Zhao
> -- /bugs.launchpad .net/bugs/ 2005135 config_ error_dialog. patch which should use the --no-markup /git.launchpad. net/ubuntu/ +source/ gdm3/tree/ debian/ patches/ ubuntu/ config_ error_dialog. patch), /discourse. gnome.org/ t/are-you- sure-you- want-to- message- on-login/ 13758/10? u=hongyi- zhao) for more detailed /bugs.launchpad .net/ubuntu/ +source/ gdm3/+bug/ 2005135/ +subscriptions
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> The incorrect calling to zenity via
> /etc/gdm3/
> 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:/
> 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:/
> proceed-
> discussion on this bug.
>
> To manage notifications about this bug go to:
> https:/
>