Project

General

Profile

Bug #16291

On-screen keyboard not displayed in the Greeter on Buster

Added by intrigeri 9 months ago. Updated 6 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Accessibility
Target version:
Start date:
01/05/2019
Due date:
% Done:

100%

Spent time:
Feature Branch:
bugfix/16291-on-screen-keyboard-passwords
Type of work:
Code
Blueprint:
Starter:
Affected tool:
On-screen keyboard

Description

… while on current Debian sid, the on-screen keyboard works just fine in GDM's password entry field. So there's maybe a problem specific to our Greeter here, or perhaps we trim down a bit too much the GNOME packages list.

Associated revisions

Revision fb386c7d (diff)
Added by intrigeri 6 months ago

Enable the bugfix-16291-on-screen-keyboard-passwords APT overlay (refs: #16291).

Revision 3e31ead7
Added by intrigeri 6 months ago

Merge remote-tracking branch 'origin/bugfix/16291-on-screen-keyboard-passwords' into feature/buster

Closes: #16291

History

#1 Updated by intrigeri 9 months ago

  • Description updated (diff)

#2 Updated by intrigeri 9 months ago

  • Affected tool set to On-screen keyboard

#3 Updated by intrigeri 9 months ago

  • Assignee deleted (intrigeri)

#4 Updated by alant 6 months ago

  • Status changed from Confirmed to In Progress

#5 Updated by alant 6 months ago

If I comment WaylandEnable=false in /etc/gdm3/daemon.conf (as it is in debian) the password fields in the greeter have a virtual keyboard.
But if I uncomment WaylandEnable=false in debian sid the password fields still have a working virtual keyboard (but the greeter in implemented inside the shell).

If I start a GNOME under Xorg session under debian sid, the virtual keyboard not always appear in GTK applications. It always appers inside the shell.
If I start a GNOME under wayland session under debian sid, the virtual keyboard is fully working in the same applications, as well as in the shell.

So I conculde there is a bug in GNOME virtual keyboard under Xorg

#6 Updated by alant 6 months ago

#7 Updated by alant 6 months ago

In the greeter if I check "show passphrase" the keyboard is shown. I can reproduce this behaviour in the wifi configuration in Settings -> WiFi -> Visible Netwotrks -> Gear -> Security.

#8 Updated by alant 6 months ago

To reproduce on debian buster one need to install ibus and ibus-gtk3 to make Screen Keyboard work under Xorg. caribou is not needed anymore and can be totally uninstalled with the screen keyboard still working.

#9 Updated by alant 6 months ago

The issue comes from a bugfix in ibus (https://github.com/ibus/ibus/commit/cca4fd8993613a6993965c3120323e43c4647ef5):

    /* don't set focus on password entry */
    if (ibusimcontext->client_window != NULL) {
        GtkWidget *widget;

        gdk_window_get_user_data (ibusimcontext->client_window,
                                  (gpointer *)&widget);

        if (GTK_IS_ENTRY (widget) &&
            !gtk_entry_get_visibility (GTK_ENTRY (widget))) {
            return;
        }
    }

#10 Updated by alant 6 months ago

  • Assignee set to intrigeri

I workaround reverting this commit should be ready on https://salsa.debian.org/alant-guest/ibus/commits/tails/buster. Please build!

#11 Updated by intrigeri 6 months ago

  • Feature Branch set to bugfix/16291-on-screen-keyboard-passwords

#12 Updated by intrigeri 6 months ago

  • Assignee changed from intrigeri to alant
  • QA Check set to Ready for QA

@alant, I've:

Back on your plate for testing :)

#13 Updated by alant 6 months ago

The patch doesn't solve the issue...

#14 Updated by alant 6 months ago

  • Assignee changed from alant to intrigeri

I didn't patch GTK3 module, which was a symlink of GTK2 in the upstream git but not in debian. This should be fixed on https://salsa.debian.org/tails-team/ibus/commits/tails/buster.

The patched package works in debian buster.

#15 Updated by intrigeri 6 months ago

  • Assignee changed from intrigeri to alant

1.5.19-4.0tails3 is on the topic branch.

#16 Updated by alant 6 months ago

  • Status changed from In Progress to Fix committed
  • Assignee deleted (alant)
  • QA Check changed from Ready for QA to Pass

#17 Updated by intrigeri 6 months ago

  • Status changed from Fix committed to Resolved
  • % Done changed from 0 to 100

Also available in: Atom PDF