config-error-dialog.sh should pass --no-markup
Bug #1887252 reported by
Mikel Ward
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gdm3 (Ubuntu) |
Fix Released
|
Low
|
Gunnar Hjalmarsson | ||
lightdm (Ubuntu) |
Fix Released
|
Low
|
Gunnar Hjalmarsson |
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/
```
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.
affects: | gdm (Ubuntu) → lightdm (Ubuntu) |
tags: | added: jammy lunar |
To post a comment you must log in.
Thanks for your report. Using the --no-markup option sounds reasonable to me.