Bug 1591813
Summary: | Unable to disable caribou onscreen keyboard with touchscreen | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Joe Wright <jwright> |
Component: | gnome-shell | Assignee: | Carlos Garnacho <cgarnach> |
Status: | CLOSED WONTFIX | QA Contact: | Desktop QE <desktop-qa-list> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 7.5 | CC: | alanm, amike, cww, dbasant, kyoneyam, mboisver, mclasen, mkolbas, tpelka |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2020-08-27 15:41:32 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Joe Wright
2018-06-15 15:53:13 UTC
Package Versions: gnome-shell-3.26.2-5.el7.x86_64 caribou-0.4.21-1.el7.x86_64 To clarify: One of the issues here is the fact that the "Enable On-Screen Keyboard" switch in GNOME Settings is not honored; the on-screen keyboard will pop up regardless. Can we clarify if this bug report is about the gnome-shell osk, or about a 3rd party keyboard (caribou) ? And what is the requested change ? See https://gitlab.gnome.org/GNOME/gnome-shell/issues/872 for a related upstream discussion FTR I looked not long ago into https://gitlab.gnome.org/GNOME/gnome-shell/issues/872, but I failed to come up with a proper heuristic based on device availability alone, obstacles being: - There's a number of devices that report keys, thus are seen as keyboards by Xorg/libinput - We can weed those out to "real keyboards" by eg. looking up ID_INPUT_KEYBOARD udev properties, checking key ranges, or similar. - But some of those devices may stay even though no "real keyboard" is attached, eg. "AT Translated Set 2 keyboard" legacy devices. For 2-in-1 laptops probably handling the tablet mode switch would yield better results, but 1) those are not the only devices that may benefit from this, and 2) it becomes harder to cover the X11 session. Closing the bug as the attached customer case is closed. |