Ubuntu
indicator-keyboard package

Keyboard layout doesn't swith if user types "too fast"

Bug #1243754 reported by Lain_13
28
This bug affects 6 people
Affects Status Importance Assigned to Milestone
Indicator keyboard
New
Undecided
Unassigned
indicator-keyboard (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Right after pressing layout switch combination (e.g. Ctrl+Space... since default Sup+Space doesn't work -_-) indicator tries to show window with list of layouts and if it pops up then layout switches. However if user keeps typing right after pressing layout switch without waiting for this popup then it does not pops up (this is good) but layout remains in the same state as well and user ends up with gibberish instead of desired text (which is very bad). So, to switch layout properly user have to wait ~1 second before attempting typing again which is very annoying for those who capable to type fast without looking at the keyboard.

Expected result: after pressing layout switch combination layout must switch instantly. Popup may or may not show up depending on how fast user starts to type after switching layout.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in indicator-keyboard (Ubuntu):
status: New → Confirmed
Revision history for this message
Anton Novikov (av-novikov) wrote :

Seems this bug is a duplicate of https://bugs.launchpad.net/ubuntu/+source/indicator-keyboard/+bug/1241284

Revision history for this message
Lain_13 (lain-halfbit) wrote :

Seems like ability to set any keyboard combination to switch layout were fixed, so I've reverted changes to layout switching on my system back to use indicator-keyboard and set it to CapsLock (so, it's 1 single key and there are no way to trigger bug 1241284). Now it does switch language after pressing CapsLock all the time _but_ it does so with a little lag. During this lag CapsLock acts as usual CapsLock. So, when I press any button during this period it will be displayed in opposite case (upper one usually) and only after 1-2 characters system will actually switch the language and revert change to case but it does not fix already typed characters. For some reason it's easier to spot in the Firefox when typing in the multirow text edit field like "Add comment" here but I was able to reproduce this issue in GEdit as well.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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