desktop-packages team mailing list archive

[marmuta <1376764@xxxxxxxxxxxxxxxxxx>]

Can confirm, Onboard doesn't start right away when it is enabled in
system settings. However, once that setting is checked, Onboard does
seem to start up at login. Does that happen for you too, Christoph?

The problem seems to be that Onboard exits voluntarily because it thinks
it is running in GNOME Shell. The autostart desktop file has "--not-
show-in=GNOME" and that checks for the existence of the D-Bus name
"org.gnome.Shell". That worked up to Trusty, but now in Utopic that name
exists in Unity too...

** Changed in: onboard (Ubuntu)
       Status: New => Confirmed

** Also affects: onboard
   Importance: Undecided
       Status: New

** Changed in: onboard
       Status: New => Confirmed

** Changed in: onboard
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to onboard in Ubuntu.
https://bugs.launchpad.net/bugs/1376764

Title:
  on-screen keyboard not available in 14.10 Final Beta

Status in Onboard on-screen keyboard:
  Confirmed
Status in “onboard” package in Ubuntu:
  Confirmed

Bug description:
  Activating the on-screen keyboard in the settings menu has no effect.
  Trying to manually execute /usr/bin/onboard via pointing-and-clicking opens up gedit (i.e., it's not recognised as an executable).
  No other keyboard input is available for the device in question, so further tests via command line (such as confirming that `python /usr/bin/onboard' starts onboard normally) are not feasible.
  Thus, 14.10 final beta is bootable but completely unusable on some tablet devices (Surface Pro 3 here).

  (Filing against `onboard' because this might be an `onboard'
  installation issue.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/onboard/+bug/1376764/+subscriptions