Bug 15362 - a11y: impossible to enter password with onscreen keyboard
Summary: a11y: impossible to enter password with onscreen keyboard
Alias: None
Product: PolicyKit
Classification: Unclassified
Component: libpolkit (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Linux (All)
: medium major
Assignee: David Zeuthen (not reading bugmail)
QA Contact: David Zeuthen (not reading bugmail)
Depends on:
Reported: 2008-04-05 05:41 UTC by Francesco Fumanti
Modified: 2008-08-29 12:12 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Description Francesco Fumanti 2008-04-05 05:41:01 UTC

PolicyKit has arrived through GNOME to Ubuntu 8.04. 

As I am a pointer-only user, I do all my typing with an onscreen keyboard; on Ubuntu it is mostly the onscreen keyboard named onboard. 

Unfortunately, the onscreen keyboard is not able to enter anything into the Authentification dialog. This is a major problem as the people that do their input only with the pointer (disabled people, tabletpc users,...) are not able to perform any administrative task that involves authentification through policykit. (Or is it policykit-gnome?) 

You can find the corresponding bug that I filed against policykit in Ubuntu at the following address: 

And here is a thread that I started on the gnome-accessibility-list about the problem:

Hoping that somebody will be able to provide a solution. 

Comment 1 Federico Mena-Quintero 2008-05-05 12:03:07 UTC
This bug should be filed in the GNOME bug tracker, under the PolicyKit-gnome product.
Comment 2 Francesco Fumanti 2008-05-05 12:45:57 UTC
Thanks for pointing me to the right product; here is the url to the bug that I just filed in GNOME against policykit-gnome:
Comment 3 Federico Mena-Quintero 2008-08-29 12:12:36 UTC
This is fixed in policykit-gnome now.  There is a GConf key to set whether the dialog should grab the keyboard.  Marking as fixed.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.