Impossible to unlock the screen when using non-English language

This bug is still valid for zesty 17.04

Sounds like bug 1566357

Please see bug 1660041. But also...

Thank you for reporting this bug to Ubuntu.
Ubuntu 16.10 (yakkety) reached end-of-life on July 20, 2017.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test.

Hi, this is reproducible on 17.04, I noted it above in comment #2

Hi, this issue is reproduced on my 17.04 system with lightdm display manager.

See also bug 1566357

A possible solution (confirmed working in 17.04 at least):

1. On 17.04 and earlier: System Settings > Language Support
2. On 17.10 and later: Settings > Region & Language > Manage Installed Languages
3. Configure your preferred language
4. Click "Apply System-Wide (Use the same language choices for startup and the login screen".

The workaround in comment #9 doesn't help me on 17.10

Here is what I did to solve a similar problem (german layout): I reset the whole gnome config (dconf reset -f /org/gnome/), changed the layout to "de" and then back to "ch-de". Now it works as expected.

Same issue on 18.04.

This is possibly related to bug #1769224.

Thank you for reporting this bug to Ubuntu.
Ubuntu 16.10 (yakkety) reached end-of-life on July 20, 2017.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed.

This is not 16.10 bug, it's reproducible on all latest Ubuntu versions including 18.10

Please reopen the bug

Hello Guys, this bug sucks!
Please fix it soon.

This bug has only been reported against Ubuntu 18.10 most recently, which reaches end of life this month. Please let us know if you are experiencing this bug on any other release so that this bug won't get automatically closed.

Thank you for reporting this bug to Ubuntu.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed.

I still can reproduce it on latest version of Ubuntu - 19.04

Please reopen the bug and change status to Confirmed

Done. You should have permission to make those changes yourself, but I have noticed many people are not familiar with how to do it, even after being told to do so...

Thank you for reporting this bug to Ubuntu.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed.

This bug is reproducible on 19.10

@daniel, please reopen, I still have no permission to do that

Thank you for reporting this bug to Ubuntu.
Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in.