OEM Priority Project

When using Wayland, the onscreen keyboard does not open in text inputs for non-GTK applications such as Firefox or Chrome

Bug #1831039 reported by Petr Olexa
40
This bug affects 4 people
Affects Status Importance Assigned to Milestone
OEM Priority Project
New
High
Unassigned
chromium-browser (Ubuntu)
Confirmed
Low
Unassigned
firefox (Ubuntu)
Fix Released
Low
Unassigned
gnome-shell (Ubuntu)
Confirmed
Low
Unassigned
qtbase-opensource-src (Ubuntu)
Confirmed
Low
Unassigned

Bug Description

When using wayland - onscreen keyboard not open in text inputs in many applications such as firefox or chrome.

Ubuntu 18.04
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DisplayManager: gdm3
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2015-06-09 (1455 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
Package: gnome-shell 3.28.3+git20190124-0ubuntu18.04.2
PackageArchitecture: amd64
ProcEnviron:
 LANG=cs_CZ.UTF-8
 TERM=xterm-256color
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, no user)
ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18
Tags: third-party-packages bionic
Uname: Linux 4.15.0-50-generic x86_64
UpgradeStatus: Upgraded to bionic on 2018-05-31 (368 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True

See original description
Petr Olexa (olexap)
affects: launchpad → wayland (Ubuntu)
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:

apport-collect 1831039

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

affects: wayland (Ubuntu) → gnome-shell (Ubuntu)
Changed in gnome-shell (Ubuntu):
status: New → Incomplete
tags: added: bionic
tags: added: osk
Revision history for this message
Petr Olexa (olexap) wrote :

apport-collect sent - but no update in this issue

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Try again?

  apport-collect 1831039

from the machine experiencing the problem.

Revision history for this message
Petr Olexa (olexap) wrote :

Sent again. What else can I do?

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

If that doesn't work then please try opening a new bug via:

  ubuntu-bug gnome-shell

That will attach all the necessary information and then we can track the problem there.

Revision history for this message
Petr Olexa (olexap) wrote :

It's the same. Apport collects info - show all the info in window and after pres the "send" button it just closes and do nothing. In console no errors, just terminate.

It is possible to see that info in console instead of graphical window? Maybe somehow I can copy-paste the summary directly?

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Please try this in a terminal window then:

  apport-cli -u 1831039

Revision history for this message
Petr Olexa (olexap) wrote : Dependencies.txt

apport information

tags: added: apport-collected third-party-packages
description: updated
Revision history for this message
Petr Olexa (olexap) wrote : GsettingsChanges.txt

apport information

Revision history for this message
Petr Olexa (olexap) wrote : ProcCpuinfoMinimal.txt

apport information

Daniel van Vugt (vanvugt)
summary: - wayland onscreen keyboard not open
+ In Wayland sessions the onscreen keyboard does not open in text inputs
+ for many applications such as Firefox or Chrome
Changed in gnome-shell (Ubuntu):
status: Incomplete → New
importance: Undecided → Medium
Sebastien Bacher (seb128)
Changed in gnome-shell (Ubuntu):
importance: Medium → Low
Revision history for this message
Daniel van Vugt (vanvugt) wrote : Re: In Wayland sessions the onscreen keyboard does not open in text inputs for many applications such as Firefox or Chrome

I wonder if this was an issue fixed in later versions already?

Daniel van Vugt (vanvugt)
Changed in firefox (Ubuntu):
importance: Undecided → Low
Changed in chromium-browser (Ubuntu):
importance: Undecided → Low
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in chromium-browser (Ubuntu):
status: New → Confirmed
Changed in firefox (Ubuntu):
status: New → Confirmed
Changed in gnome-shell (Ubuntu):
status: New → Confirmed
Daniel van Vugt (vanvugt)
tags: added: eoan
summary: - In Wayland sessions the onscreen keyboard does not open in text inputs
- for many applications such as Firefox or Chrome
+ The onscreen keyboard does not open in text inputs for non-GTK
+ applications such as Firefox or Chrome
Revision history for this message
Daniel van Vugt (vanvugt) wrote : Re: The onscreen keyboard does not open in text inputs for non-GTK applications such as Firefox or Chrome

Is this still a problem?

tags: removed: eoan
Changed in gnome-shell (Ubuntu):
status: Confirmed → Incomplete
Changed in firefox (Ubuntu):
status: Confirmed → Incomplete
Changed in chromium-browser (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Efthimios Chaskaris (echaskaris) wrote :

Umm, yes, but on Wayland, it works in x11.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

I should have said:

Is this still a problem in 20.04?

Revision history for this message
Efthimios Chaskaris (echaskaris) wrote :

No, it works when using x11 in 20.04.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

I really should have said:

Is this still a problem on Wayland in 20.04?

Revision history for this message
Efthimios Chaskaris (echaskaris) wrote :

Sry man

Yes, the OSK is not brought up automatically for non-Ubuntu apps when using Wayland.

Daniel van Vugt (vanvugt)
Changed in chromium-browser (Ubuntu):
status: Incomplete → Confirmed
Changed in firefox (Ubuntu):
status: Incomplete → Confirmed
Changed in gnome-shell (Ubuntu):
status: Incomplete → Confirmed
tags: added: focal
summary: - The onscreen keyboard does not open in text inputs for non-GTK
- applications such as Firefox or Chrome
+ When using Wayland, the onscreen keyboard does not open in text inputs
+ for non-GTK applications such as Firefox or Chrome
Daniel van Vugt (vanvugt)
Changed in qtbase-opensource-src (Ubuntu):
status: New → Confirmed
importance: Undecided → Low
Revision history for this message
Amr Ibrahim (amribrahim1987) wrote :

Firefox uses GTK, but in a Wayland session it runs on XWayland, the same for Qt apps and Chrome, they run on XWayland in a Wayland session. That's a common factor.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Firefox does do some things differently to what I would refer to as an "GTK app" so I don't count Firefox as a GTK app even though it uses some GTK.

Using Xwayland may be a common factor but that's probably more of a correlation than causation. Anything that's not yet ported to native Wayland will fall into the same category and end up using Xwayland.

Revision history for this message
Yuan-Chen Cheng (ycheng-twn) wrote :

per test on jammy updated on 2022/03/28, wayland mode, OSK works fine with firefox snap (v98.0.2-1, r1154)

tags: added: 2-in-1
tags: added: oem-priority
Olivier Tilloy (osomon)
Changed in firefox (Ubuntu):
status: Confirmed → Fix Released
Rex Tsai (chihchun)
Changed in oem-priority:
importance: Undecided → High
Revision history for this message
bushido (olav-magi) wrote :

In addition to not showing up automatically, the wrong text is selected.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

I feel like that's a separate bug, but on the same critical path to getting the OSK working.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.