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 1067366 - Screen keyboard accessibility does not work in non-gtk applications
Summary: Screen keyboard accessibility does not work in non-gtk applications
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: qt
Version: 7.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Lukáš Tinkl
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-02-20 10:43 UTC by Martin Simon
Modified: 2016-09-20 02:15 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-03-10 15:03:23 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
patch to qt-at-spi packaging (3.35 KB, patch)
2014-02-20 22:34 UTC, David King 		no flags Details | Diff
View All

Description Martin Simon 2014-02-20 10:43:13 UTC 
Description of problem:
Screen Keyboard accessibility only works in gnome-like applications. It means, with enabled Screen Keyboard option when I focus an input field in {gnome-terminal,xchat,gnome-shell,evince,...}, I get on-screen keyboard and everything works fine. Otherwise, when I focus an input field in non-gnome app like {firefox,thunderbird,skype,probably all KDE apps,...}, I get no on-screen keyboard. I understand that is graphical toolkit relevant and I understand it probably requires bigger changes to support Qt application such as KDE apps are, but it should be possible to use it for firefox and thunderbird as they are default, at least.

Version-Release number of selected component (if applicable):
gnome-shell-3.8.4-22.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Enable Screen Keyboard accessibility
2. Open firefox and focus any input field

Actual results:
no on-screen keybord shown

Expected results:
on-screen keyboard shown

Additional info:
Comment 2 Martin Simon 2014-02-20 11:08:48 UTC 
firefox and thunderbird works, my mistake, only needs to be restarted. Changing this bug to non-gtk apps as the KDE applications and e.g. skype does not invoke on-screen keyboard
Comment 3 Martin Simon 2014-02-20 11:41:12 UTC 
(In reply to Martin Simon from comment #2)
> firefox and thunderbird works, my mistake, only needs to be restarted.
See the bug 1068395 for this issue
Comment 4 David King 2014-02-20 22:34:26 UTC 
Created attachment 865746 [details]
patch to qt-at-spi packaging

Caribou (the GNOME on-screen keyboard) pops up when it is enabled in the accessibility options and an editable text widget is focused. To determine whether an editable widget is focused, it needs to communicate with the toolkit via AT-SPI2. Caribou provides a GTK+ 2 and a GTK+ 3 module to do that, but it does not provide a a Qt module.

In order for that to work for Qt applications (only Qt 4 applications, Qt 5 has AT-SPI2 support built-in), qt-at-spi should be installed. It is packaged in Fedora, but not in RHEL from what I can see. I tested the Fedora package on a RHEL 7 system, and was able to input text with the on-screen keyboard when focusing a text field in a Qt application. While investigating this, I realised that there is a bug in qt-at-spi which prevents Caribou from detecting that a text field is focused. The patch is simple, and attached.

In order for this to work in RHEL, qt-at-spi needs to be installed (with the attached patch, pre-built packages are at: http://koji.fedoraproject.org/koji/taskinfo?taskID=6554102), the QT_ACCESSIBILITY environment variable must be set to "1" and the on-screen keyboard must be enabled (in the Universal Access settings).
Comment 5 Matthias Clasen 2014-02-21 19:48:22 UTC 
I'm moving this over to the qt component, since I think it would make most sense for the qt package maintainer to own qt-at-spi too.
Comment 6 Matthias Clasen 2014-02-21 20:02:52 UTC 
If you find a package owner on the kde side, you can head to 

https://maitai.engineering.redhat.com/maitai/

to start the process, but it needs to happen pretty quickly, if we still want to get it in for 7.0
Comment 7 Than Ngo 2014-03-10 15:03:23 UTC 
qt-at-spi is not included in rhel7. I conside it as a feature request. I close it as DEFERRED. Please open a new feature request for qt-at-spi.
Note You need to log in before you can comment on or make changes to this bug.