Please note I think no Caribou developer is having touch screen machine to test such bugs. I afraid there will be no action happen on this bug.

I suspect it's bug 739293, where both physical keyboard and touch screen are present.

(In reply to Parag AN from comment #1)
> Please note I think no Caribou developer is having touch screen machine to
> test such bugs. I afraid there will be no action happen on this bug.
The Caribou developers... don't have touch screen machines? If this is true, it's pretty bizarre, and I encourage them to buy a cheap old tablet laptop to test things out.

(In reply to Daiki Ueno from comment #2)
> I suspect it's bug 739293, where both physical keyboard and touch screen are
> present.
The bug you linked is not the problem I'm describing. I'm describing a problem where the onscreen keyboard pops up regardless of whether I have turned it off in the Universal Access settings.

Don't you use ThinkPad Yoga[1], which has both physical keyboard and touch screen?  In GNOME, there are two places which enable OSK: one is the accessibility setting you mentioned, and the other is gnome-settings-daemon which checks if any touch screen device is present.  What I was suspecting is that the latter is interfering with the former.

1. https://en.wikipedia.org/wiki/ThinkPad_Yoga

If you still think this is not bug 739293, please reopen.

*** This bug has been marked as a duplicate of bug 739293 ***

> you still think this is not bug 739293, please reopen.
bug 739293 describes one of my complaints, but not the main bug I am describing. The bug I'm describing is that the GNOME Universal Access setting for turning the OSK on and off doesn't work. If I enable the OSK in Universal Access, it shows up. If I disable the OSK in Universal Access, the OSK still shows up. The OSK pops up when I tap on a terminal or text editor with my touch screen (though it doesn't pop up if I tap on a Firefox text field).
bug 739293 only has to do with the OSK staying up onscreen while the physical keyboard is being used, so it doesn't cover this bug.

Dupe of bug 742246?

Sam, no, this bug is not duplicate of bug 742246, because user may use tablet without attached keyboard and at the same time doesn't want Caribou be enable. For example in case when user native keyboard layout is present in another on-screen keyboard, but doesn't present in Caribou there is no point to have Caribou enabled. Especially, as I recently find out, if Caribou somehow interfere normal usage of another onscreen keyboard: https://bugs.launchpad.net/ubuntu/+source/onboard/+bug/1718298

since gnome 3.26 osk appears when I touch any window.
My laptop has a real keyboard, I dont need this annoying and useless osk.
The bug reported here is a big problem now and fix it should be a priority.

Actually, I have to add that with Ubuntu and Ubuntu Gnome 17.10 release this issue will became real nuisance for many people. For now, before proper fix will arrive, any workaround, even very hackish, will be very appreciated.

The following path makes Caribou appear only when it’s explicitly enabled in the accessibility settings:

diff --git a/js/ui/keyboard.js b/js/ui/keyboard.js
index da36c36..ae6f852 100644
--- a/js/ui/keyboard.js
+++ b/js/ui/keyboard.js
@@ -305,8 +305,8 @@ var Keyboard = new Lang.Class({
     },
 
     _syncEnabled: function () {
-        this._enableKeyboard = this._a11yApplicationsSettings.get_boolean(SHOW_KEYBOARD) ||
-                               this._lastDeviceIsTouchscreen();
+        this._enableKeyboard = this._a11yApplicationsSettings.get_boolean(SHOW_KEYBOARD);
+
         if (!this._enableKeyboard && !this._keyboard)
             return;

Given that the check of device type is done in gnome-shell, I doubt that the problem can be fixed in Caribou.

(In reply to errr from comment #11)
> The following path makes Caribou appear only when it’s explicitly enabled in
> the accessibility settings

No, that's not acceptable. The setting exists so users who cannot use a physical keyboard can force on the on-screen keyboard even on non-touch systems. It is *not* something tablet users need to track down (without help from Google!) to fix their input.

We will not turn the setting into a way to work around bugs or make it easier to replace a built-in component, sorry. Bugs should be fixed, and there are plans to make use of Android layouts to increase the range of supported layouts (and thus fixing one of the main motivations for wanting to replace the built-in keyboard with an external one).  If you need a work-around in the meantime, please resort to extensions.

*** This bug has been marked as a duplicate of bug 792870 ***

*** Bug 792870 has been marked as a duplicate of this bug. ***

(In reply to Florian Müllner from comment #13)
> (In reply to errr from comment #11)
> > The following path makes Caribou appear only when it’s explicitly enabled in
> > the accessibility settings
> 
> No, that's not acceptable. The setting exists so users who cannot use a
> physical keyboard can force on the on-screen keyboard even on non-touch
> systems. It is *not* something tablet users need to track down (without help
> from Google!) to fix their input.

Then can I request an additional setting that disables the on-screen keyboard for users who do not want to use it in their sessions without having to resort to work around this issue that would break configurations for other users.

Same problem in Gnome 3.28.
OSK appears when gnome-terminal is focused even if it's disabled in gnome settings.

(In reply to Strangiato from comment #17)
> OSK appears when gnome-terminal is focused even if it's disabled in gnome
> settings.

... which has been explained repeatedly on this bug:
The setting exists so users who cannot use a physical keyboard can *enable* the on-screen keyboard independently from the hardware. It is *not* a setting to disable a feature you don't like (or worse, the setting tablet users have to track down if the intend to input any text).

As I see it, there are two cases:
 - the OSK should be disabled if a physical keyboard is attached (bug 742246) or in use (bug 739293)
 - some users want to turn off the OSK on touch-only hardware in order to use a different 3rd party keyboard

The first case is already tracked in separate bugs. The second case is not something we add settings for (see "missing" settings for pulseaudio, NetworkManager, evolution-data-server etc.), taking out (and possibly replacing) built-in components like that is extension-territory.

So this is either a duplicate of bug 742246 (or 739293) or WONTFIX.

*** This bug has been marked as a duplicate of bug 742246 ***