Regression: Default on-screen keyboard Onboard not properly above dash

[Francesco Fumanti]

[ Impact ]

Users of the on-screen keyboard cannot properly use the Dash and the on-screen keyboard at the same time.

[ Test Case ]

1. Install and start the on-screen keyboard Onboard.
2. Open the Dash.
3. Ensure you can interact with Onboard as you would expect.

[ Regression Potential ]

None observed.

Debdiff of the SRU is found here: https://bugs.launchpad.net/unity/+bug/886478/+attachment/4401967/+files/unity.7.2.5.debdiff

---------------------------------------------------------------------

Original Description:

Hi,

Some recent update of broke the default on-screen Onboard to work properly on dash.

In fact, Onboard is shown in dash, as if it was located under dash. It is particularly visible, when the dash is maximized and covers the whole screen. However, if I drag Onboard to position it under an icon in dash and I click on the icon, the corresponding application is not started; the click goes down to Onboard, which types the letter of the Onboard key placed at the position of the click.

So, in a few words: dash draws Onboard as if it was covered by dash, but Onboard behaves as if it is located over dash.

Having a vivid backup from about one month ago, we were able to determine that the regression seem to have happened because of the update of libunity-core and the related packages somewhere between one month ago and today. In fact, the problem appeared in the test after updating the following packages and versions to the version shipping currently in the repositories.

libunity-core-6.0-9 7.3.1+15.04.20141128-0ubuntu1
libcairo-gobject2 1.13.0~20140204-0ubuntu1
libcairo-script-interpreter2 1.13.0~20140204-0ubuntu1
libcairo2 1.13.0~20140204-0ubuntu1
libcairo2-dev 1.13.0~20140204-0ubuntu1
unity 7.3.1+15.04.20141128-0ubuntu1
unity-schemas 7.3.1+15.04.20141128-0ubuntu1
unity-services 7.3.1+15.04.20141128-0ubuntu1

Cheers

[Andrea Azzarone (azzar1)]

Can you post the ouput of:
sudo apt-cache policy unity

[Francesco Fumanti (frafu)]

Here is the output of the command on a vivid installation, that has not been updated since the middle of December 2014 and where the regression was not present yet:

$ sudo apt-cache policy unity
unity:
  Installed: 7.3.1+15.04.20141128-0ubuntu1
  Candidate: 7.3.1+15.04.20150115-0ubuntu1
  Version table:
     7.3.1+15.04.20150115-0ubuntu1 0
        500 http://ubuntu.mirror.root.lu/ubuntu/ vivid/main amd64 Packages
 *** 7.3.1+15.04.20141128-0ubuntu1 0
        100 /var/lib/dpkg/status

And here the output of the command on my uptodate vivid installation having the regression:

$ sudo apt-cache policy unity
unity:
  Installed: 7.3.1+15.04.20150115-0ubuntu1
  Candidate: 7.3.1+15.04.20150115-0ubuntu1
  Version table:
 *** 7.3.1+15.04.20150115-0ubuntu1 0
        500 http://ubuntu.mirror.root.lu/ubuntu/ vivid/main amd64 Packages
        100 /var/lib/dpkg/status

As far as I understand, the regression happened somewhere between the two versions.

[Andrea Azzarone (azzar1)]

I've already proposed a fix. Should land in 15.04 in few days.

[Launchpad Janitor (janitor)]

This bug was fixed in the package unity - 7.3.1+15.04.20150227-0ubuntu1

---------------
unity (7.3.1+15.04.20150227-0ubuntu1) vivid; urgency=medium

  [ Andrea Azzarone ]
  * Draw osk above unity shell. (LP: #1413165)
  * Remove FontSettings.*. Add the possibility to specify the font size
    and the font weight without chaning the default font name. Fix lp
    886478. (LP: #886478)
  * Remove unitydialog plugin.

  [ Luke Yelavich ]
  * Explore children when a view or layout is added (LP: #1066157)
  * Move the unity a11y present environment call
  * Set focus to FALSE on window deactivation (LP: #1066157)
 -- CI Train Bot <email address hidden> Fri, 27 Feb 2015 15:38:19 +0000

[Daniel Holz (daniel-holz91)]

I'm getting this bug now in trusty. Any chance to backport the fix?

Here is the output of

sudo apt-chache policy unity

unity:
  Installiert: 7.2.4+14.04.20150316-0ubuntu1
  Installationskandidat: 7.2.4+14.04.20150316-0ubuntu1
  Versionstabelle:
 *** 7.2.4+14.04.20150316-0ubuntu1 0
        500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages
        100 /var/lib/dpkg/status
     7.2.2+14.04.20140714-0ubuntu1.1 0
        500 http://archive.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages
     7.2.0+14.04.20140416-0ubuntu1 0
        500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Package

I'm using Ubuntu on a tablet computer, so I pretty much depend on a working onscreen keyboard.

[Daniel Holz (daniel-holz91)]

Well I guess I "fixed" this bug by myself now. I've done the most stupid thing possible and installed unity-7.3.2 from the vivid repository on a trusty installation. Its a miracle that the system is not broken, but now Onboard works with the Dashboard again. :D

[Brian Murray (brian-murray)]

Hello Francesco, or anyone else affected,

Accepted unity into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/unity/7.2.5+14.04.20150521.1-0ubuntu1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

[Francesco Fumanti (frafu)]

Hi,

Unfortunately, I cannot be of much help anymore: My trusty installation that I keep for testing purposes has not been showing the bug anymore for some time. It may be due to it running a unity version from 20141212 and/or a newer version of Onboard from the Onboard PPA.

So I disabled the security, recommended, proposed, backports and Onboard PPA sources in order to replicate the bug; but I was only able to replicate it partially: in fact, Onboard looked after the downgrade as if it was covered by Dash, but a click on it restored its look by making it look as if it is above Dash. (If I remember correctly, in the original bug description, Onboard behaved as if it was above Dash, but looked all the time as if it was below Dash.)

Afterwards, I enabled the sources again, apart the Onboard PPA, and installed all the updates. The problem disappeared again, but it probably cannot count, as I was not able to replicate the exact original bug.

Cheers

[Christopher Townsend (townsend)]

With Onboard displayed on the screen and then opening the Dash, Onboard is above the Dash and takes input and the Dash accepts this input. Based on this, this bug is fixed and marking as verification-done.

[Launchpad Janitor (janitor)]

This bug was fixed in the package unity - 7.2.5+14.04.20150521.1-0ubuntu1

---------------
unity (7.2.5+14.04.20150521.1-0ubuntu1) trusty; urgency=medium

  [ Chris Townsend ]
  * Releasing 7.2.5.
  * Bump version to 7.2.5.
  * Use a 2 second delay before showing the first run shortcut hints to
    workaround a race condition on input handling. (LP: #1313597)

  [ Andrea Azzarone ]
  * Add the possibility to specify the font size and the font weight
    without chaning the default font name. (LP: #886478)
  * Do not restore focus if a quicklist is opened during launcher key
    navigation. (LP: #932486)
  * Draw osk above unity shell. (LP: #1413165)
  * Forward first key event that happens on top of the blank window to
    the lockscreen. (LP: #1308265)
  * Make sure scope_views_[filter.id] exists before using operator[] on
    it. (LP: #926979)
  * Release pointer barrier if launcher is in lock_hide state. (LP:
    #1029114)

  [ Brandon Schaefer ]
  * When we quit the quicklist it would check if the mouse was over the
    launcher, if it wasn't it would fold the launcher. We don't need to
    check this if we are in keynav as we want all the icons to be
    unfolded. (LP: #1246891)

  [ CI Train Bot ]
  * New rebuild forced.

  [ Stephen M. Webb ]
  * AP tests: accounted for arbitrarily-raised exceptions in checking
    scaled windows (LP: #1436095)

 -- CI Train Bot <email address hidden> Thu, 21 May 2015 15:07:15 +0000

[Chris J Arges (arges)]

The verification of the Stable Release Update for unity has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.