On Tue, Feb 7, 2023 at 10:45 AM Daniel van Vugt <[email protected]> wrote: > > ** Tags added: jammy lunar > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (2005135). > https://bugs.launchpad.net/bugs/1887252 > > Title: > config-error-dialog.sh should pass --no-markup > > Status in gdm3 package in Ubuntu: > Incomplete > Status in lightdm package in Ubuntu: > Incomplete > > 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.
So, what should be the appropriate bug fix method in this scenario? > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1887252/+subscriptions Best, Zhao -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1887252 Title: config-error-dialog.sh should pass --no-markup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1887252/+subscriptions -- desktop-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
