RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1591813 - Unable to disable caribou onscreen keyboard with touchscreen
Summary: Unable to disable caribou onscreen keyboard with touchscreen
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: gnome-shell
Version: 7.5
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: rc
: ---
Assignee: Carlos Garnacho
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-06-15 15:53 UTC by Joe Wright
Modified: 2022-01-05 22:37 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-08-27 15:41:32 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
GNOME Bugzilla 742246 0 Normal RESOLVED On-screen keyboard pops up with touchscreen even when physical keyboard present 2021-02-16 22:18:50 UTC

Description Joe Wright 2018-06-15 15:53:13 UTC
Description of problem:
- Unable to disable caribou when system is equipped with a touch screen

Version-Release number of selected component (if applicable):


How reproducible:
100%

Steps to Reproduce:
1. Install and run gnome on system with touch screen
2. connect physical keyboard
3. note that caribou persists with physical keyboard available

Actual results:
- caribou is displayed on screen with physical keyboard connected and will not go away despite any attempts to disable/close it

Expected results:
- caribou is not on screen or persistent when physical keyboard is available to system unless manually invoked

Additional info:
- Upstream BZ: https://bugzilla.gnome.org/show_bug.cgi?id=742246

Comment 3 Joe Wright 2018-06-15 15:57:33 UTC
Package Versions:
gnome-shell-3.26.2-5.el7.x86_64
caribou-0.4.21-1.el7.x86_64

Comment 6 Andrew Mike 2018-07-24 16:44:25 UTC
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.

Comment 11 Matthias Clasen 2019-07-15 17:57:39 UTC
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

Comment 12 Carlos Garnacho 2019-09-16 16:05:34 UTC
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.

Comment 14 Tomas Popela 2020-08-27 14:42:23 UTC
Closing the bug as the attached customer case is closed.


Note You need to log in before you can comment on or make changes to this bug.