Bug #17174
On screen keyboard doesn't press space in Korean (Hangul)
0%
Description
In Korean language the screen keyboard doesnt press space, haven’t tested this in other languages which could also have this issue
Also, there is no ctrl or alt buttons or navigation or shift so it is much less useful
Subtasks
Related issues
Related to Tails - |
Resolved | ||
Blocked by Tails - |
Resolved |
History
#1 Updated by intrigeri 2019-10-22 09:35:07
- Target version deleted (
Tails_4.0)
#2 Updated by intrigeri 2019-10-22 11:22:58
- related to
Bug #17021: On-screen keyboard does not allow to input any accentuated char if one keeps the mouse button pressed added
#3 Updated by sajolida 2019-10-29 19:30:42
- Subject changed from on screen keyboard doesnt press space to On screen keyboard doesn't press space in Korean (Hangul)
- Status changed from New to Confirmed
I confirm this bug:
- Start Tails in any language.
- Enable the screen keyboard.
- Open gedit.
- Switch the input method to “Korean (Hangul)”
- Try to type a space in gedit using the screen keyboard: it doesn’t work. Typing a space on the keyboard in gedit still works. Typing another letter in gedit using the screen keyboard also works.
#4 Updated by intrigeri 2019-10-31 11:28:07
> I confirm this bug:
> * Start Tails in any language.
> * Enable the screen keyboard.
> * Open gedit.
> * Switch the input method to “Korean (Hangul)”
> * Try to type a space in gedit using the screen keyboard: it doesn’t work. Typing a space on the keyboard in gedit still works. Typing another letter in gedit using the screen keyboard also works.
I’ve followed this procedure to the letter and I can’t reproduce the bug :/
Same if I also enable “Hangul mode” in the input methods menu, after setting the input method to Korean.
#5 Updated by intrigeri 2019-11-11 08:51:48
- blocked by
Feature #17202: Upgrade to Buster 10.2 added
#6 Updated by intrigeri 2019-11-11 08:52:49
- Type of work changed from Code to Test
Let’s hope Feature #17202 fixes this, just like Bug #17021#note-13. Given the documented procedure did not allow me to reproduce this bug, I’ll need someone else, who can reproduce this bug, to test if that fixes it.
#7 Updated by intrigeri 2019-11-11 08:53:14
- Category set to Accessibility
- Affected tool set to On-screen keyboard
#8 Updated by intrigeri 2019-11-16 13:34:17
https://nightly.tails.boum.org/build_Tails_ISO_feature-17202-buster-10.2-force-all-tests/lastSuccessful/archive/build-artifacts/ should have test images in about 1 hour.
If you could previously reproduce this bug, please consider trying to reproduce it with one of these fresh images :)
#9 Updated by sajolida 2019-11-20 18:43:41
I don’t mind testing it again once 4.1 is out but not before.
#10 Updated by intrigeri 2019-11-28 16:11:19
- Assignee set to sajolida
- Target version set to Tails_4.2
(To reproduce the problem on 4.1, and ideally document how others can reproduce it.)
#11 Updated by sajolida 2020-01-06 14:39:43
- Target version changed from Tails_4.2 to Tails_4.3
#12 Updated by anonym 2020-02-11 15:26:14
- Target version changed from Tails_4.3 to Tails_4.4
#13 Updated by sajolida 2020-03-05 17:16:00
- Status changed from Confirmed to Resolved
Indeed! It’s working now from Tails 4.3 :)