Keyboard language layout setting doesn't persist, keeps switching from UK to a different English layout

Bug #1943339 reported by no
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu
Expired
Undecided
Unassigned

Bug Description

My keyboard language setting seems to be getting switched from `English (UK)` to `English (US)` unexpectedly.

I had no problems with this on Ubuntu 20.10, but it appeared after upgrading to 21.04 Hirsute Hippo and also seems to happen on the latest 21.10 daily build.

I have a Lenovo T14s laptop with UK keyboard layout.

I don't know whether this is an issue in Ubuntu or caused by VSCode - apologies if it's the latter.

Repro steps:

- Press `windows` key
- Open `Settings`
- Go to `Language and Region`
- Set `Language` to `English (United Kingdom)`
- Set `Input Sources` to `English (UK)` only
- Open `Manage Installed Languages`
- Set `English (United Kingdom)` to appear at the top, with `English` next
- Open a terminal
- When pressing the `#` key on the keyboard, `#` appears as expected
- Open the VSCode text editor using `code --disable-extensions`
- Create a file (file type does not appear to matter)
- Press the `#` key, `\` appears
- Open Chrome, click on the address bar and press the `#` key, `\` appears
- Navigate back to the still-open terminal and press the `#` key, `#` appears (this surprised me)
- Go to `Settings` > `Language and Region` > `Input Sources`, add `English (US)` and then remove it again
- Go to VSCode - press the `#` key, `#` appears
- Go to Chrome - press the `#` key, `#` appears
- Close VSCode and Chrome
- Open VSCode - press the `#` key, `\` appears
- Go to `Settings` > `Language and Region` > `Input Sources`, add `English (US)` and then remove it again
- Go to the still-open instance of VSCode - press the `#` key, `#` appears

Tags: bot-comment
Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1943339/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
Revision history for this message
Chris Guiver (guiverc) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better.

Bug reporting is mostly about finding & fixing problems thus preventing future users from hitting the same bug.

I suspect a Support site would be more appropriate, eg. https://answers.launchpad.net/ubuntu. You can also find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at https://askubuntu.com or https://ubuntuforums.org, or for more support options please look at https://discourse.ubuntu.com/t/community-support/709

This report currently is vague & unhelpful. No details as to your system were provided; are you talking about a desktop or server install?, how was it installed (ie. which ISO), what packages etc are included. By filing with `ubuntu-bug <package>` this detail is provided, but you've filed it with none of these details.

If you change the package to the respective package (`linux` if it's kernel related; maybe it's a desktop package but we don't yet know it's a desktop system..) VSCode is not a Ubuntu package so it maybe involved; does the issue occur outside of VSCode? how was VSCode installed? Snap? deb? You mention Chrome; likewise a 3rd party package; does it occur with Ubuntu tools (or only 3rd party)

As such I've marked this bug as incomplete. You can change package details, then run `apport-collect 1943339` and the status can be returned to "New". If you believe I'm in error, please leave a message detailing why, and the status can be returned to "New".

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

Changed in ubuntu:
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for Ubuntu because there has been no activity for 60 days.]

Changed in ubuntu:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.