[Bug 1730211] [NEW] Unable to type capital letters using onscreen keyboard
Launchpad Bug Tracker
1730211 at bugs.launchpad.net
Tue Oct 16 04:19:33 UTC 2018
You have been subscribed to a public bug by Ubuntu Foundations Team Bug Bot (crichton):
Unable to type capital letters using onscreen keyboard:
1. Launch a program where you can type text (gedit for example).
2. Activate on screen keyboard (by touching the screen, foe example).
3. Notice all the keys on the on screen keyboard display lowercase letters.
4. Begin typing. Lowercase characters are typed into the text area.
5. Tap on the Shift (up arrow at left side of on screen keyboard) key of the on screen keyboard.
6. Notice all the keys on the on screen keyboard now display capital letters.
7. Begin typing.
8. A lowercase character will be typed into the text area.
This is not expected behavior.
Instead, a capital letter should have been typed.
(All the keys on the on screen keyboard revert to lower case. This is
expected, since the on screen shift key would need to be pressed again
in order to attempt to type another capital character).
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: caribou 0.4.21-2
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
CurrentDesktop: GNOME
Date: Sun Nov 5 10:57:04 2017
InstallationDate: Installed on 2017-11-03 (1 days ago)
InstallationMedia: Ubuntu 17.10.0 2017.10.23 amd64 "Custom Artful Aardvark"
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: caribou
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: oem-priority
Importance: High
Status: Confirmed
** Affects: oem-priority/bionic
Importance: Undecided
Status: New
** Affects: mutter (Ubuntu)
Importance: Low
Status: Confirmed
** Tags: 2in1 amd64 apport-bug bionic patch somerville
--
Unable to type capital letters using onscreen keyboard
https://bugs.launchpad.net/bugs/1730211
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.
More information about the Ubuntu-sponsors
mailing list