| Summary: | Yocto 2.2 "Morty" - matchbox-keyboard doesn't "pop up" automatically with Chromium 52.0.2743.76 | ||
|---|---|---|---|
| Product: | [Yocto Project Subprojects] Sato | Reporter: | Flavio Suligoi <f.suligoi> |
| Component: | sato | Assignee: | Jussi Kukkonen <jku> |
| Status: | RESOLVED NOTABUG | QA Contact: | |
| Severity: | normal | ||
| Priority: | Undecided | CC: | jku, raphael.kubo.da.costa, ross.burton |
| Version: | svn | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | arm | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
|
Description
Flavio Suligoi
2017-05-03 10:31:06 UTC
The keyboard comes with its own Gtk input method that knows how to invoke the keyboard -- meaning any applications using e.g. GtkEntries will work out of the box and anything supporting GTK input methods will work as well. I would not expect Chromium to use GTK widgets but I kind of do expect it to support gtk input methods (but don't take my word for it: I'm not a chromium expert and could be wrong here). If they do support gtk input methods then there's one more thing to check: Your chromium version is ancient by chromium standards: it might still be using GTK+2. By default the matchbox-keyboard in morty only builds with support for GTK+3 so you would have to enable GTK+2 support by adding "gtk2-im" PACKAGECONFIG to matchbox-keyboard. TL;DR: I don't think there's a bug in matchbox-keyboard (so far at least). If chromium does support Gtk+2 IM, then the workaround above might help. If Chromium does not support GTK IM then we'll have to re-assess the situation. Hi Jussi, I recompiled the matchbox-keyboard, with: PACKAGECONFIG ??= "gtk3-im applet gtk2-im" and now it works correctly with Chromium. Thanks for your support, Flavio Hi Jussi, what do you think about adding permanently also the "old" Gtk+2 IM in the matchbox-keyboard Yocto recipe? I mean to have simultaneously the two IM both for Gtk+2 and Gtk+3. Flavio (In reply to comment #3) > what do you think about adding permanently also the "old" Gtk+2 IM in the > matchbox-keyboard Yocto recipe? > I mean to have simultaneously the two IM both for Gtk+2 and Gtk+3. The current situation is definitely not optimal -- ending up with the problem is easy and figuring out the solution to the problem you had would be impossible for most users. However we would like to keep only one Gtk version in the default builds (for size and compile time reasons) and enabling "gtk2-im" of course means building gtk2 first... Essentially we'd like to enable "gtk2-im" if (and only if) something else brings gtk2 into the image but that's not really possible. We could have a DISTRO_FEATURE "gtk2" that enabled gtk2-im in matchbox-keyboard (and then e.g. chromium could refuse to build without the DISTRO_FEATURE)... Good ideas are welcome :/ I think that having to enable the gtk2 IM for chromium to work with keyboards is something the user just has to do: we don't want to pull gtk2 into all sample images just in case chromium is being used. Also, Chromium is moving to gtk3 so this may be solvable by changing how chromium builds. Closing as NOTABUG as the IM integration works as intended, the integration is up to the user. |