This bug was fixed in the package gdm3 - 43.0-3ubuntu2
---------------
gdm3 (43.0-3ubuntu2) lunar; urgency=medium
* debian/patches/ubuntu/config_error_dialog.patch:
- Use --no-markup option in zenity call (LP: #1887252)
-- Gunnar Hjalmarsson <gunna...@ubuntu.com> Wed, 15 Feb 2023 18:41:29
+0100
** Changed in: gdm3 (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1887252
Title:
config-error-dialog.sh should pass --no-markup
Status in gdm3 package in Ubuntu:
Fix Released
Status in lightdm package in Ubuntu:
Fix Released
Bug description:
I modified my ~/.profile to call "logger". This resulted in in
producing some output on stderr like
```
<13>Jul 11 13:02:46 /usr/sbin/lightdm-session[1408]: profile sourced ...
```
This showed an empty zenity prompt.
Logs suggest zenity was failing because it was treating `<13>` as
pango markup.
```
from markup due to error parsing markup: Error on line 3 char 6: “13” is not
a valid
```
We should not assume the error message strings contain valid markup,
since their source is unknown.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1887252/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
