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.
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1413165 Title: Regression: Default on-screen keyboard Onboard not properly above dash Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Committed Bug description: [ 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 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1413165/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
