Comment 53 for bug 1875062

Of course I have problems reproducing this, I tried multiple times and got nothing. It's hard to pinpoint this without a reproducer. I'll try to scan the code for any funny parts where it could break, but I'd at least like to know if the problem here is with setxkbmap failing, or ubiquity setting it to a different value at some weird moment.

If anyone is able to reproduce the issue right now, I'd welcome some logs/info from a running ubiquity instance there:
 * I'd love the ubiquity syslog from /var/log/syslog when ubiquity is running
 * Might be good to get some locale and layout info straight away. So if someone notices at some ubiquity page that the layout is wrong, opening a terminal with ctrl+alt+t and then running `setxkbmap -query` and `locale`, pasting their output here

From the initial logs attached to the bug here I was maybe thinking that there's some race that could cause setxkbmap maybe fail when an invalid/incompatible locale is running, but then again I couldn't actually lead to such situation myself. I'd really appreciate as much logs as possible from a running system.

@Nicolas, @Michel - could you possibly help out? Thank you!