The current default behavior is to always embed Onboard into the screen- saver, but it will only actually show if either the keyboard is enabled in system settings (org.gnome.desktop.a11y.applications.screen-keyboard- enabled == true), or Onboard is currently running in the user session. If you don't already use Onboard, it shouldn't actually show up in the screen-saver either.
Barring bugs, the only unsupported case would be, if you did start Onboard from a launcher, kept using it, but still didn't want to see it in the screen-saver. The only recurse to that is to turn off screen- saver embedding in Onboard's preferences (org.onboard.xembed-onboard = false). Having control center turn off org.gnome.desktop.screensaver.embedded- keyboard-enabled wouldn't help all that much, because Onboard on startup keeps restoring those keys to something that allows it to show, until it is told not to do so. The dialog you saw is Onboard trying to restore them, but realizing the screen-saver keys have been changed by a third party and leaving the decision to the user. So my question is, is there a common use case, where you do want to use Onboard, but not have it show up in the lock screen? ** Changed in: onboard (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/993253 Title: Turning off on-screen keyboard leaves it on the locked screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/onboard/+bug/993253/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs