Activity log for bug #1413165

Date Who What changed Old value New value Message
2015-01-21 11:21:29 Francesco Fumanti bug added bug
2015-01-21 11:22:07 Francesco Fumanti bug added subscriber marmuta
2015-01-21 11:22:43 Francesco Fumanti bug added subscriber Gerd Kohlberger
2015-01-21 11:55:53 Andrea Azzarone unity: assignee Andrea Azzarone (andyrock)
2015-01-21 11:55:57 Andrea Azzarone unity: status New In Progress
2015-01-21 12:06:05 Andrea Azzarone bug task added unity (Ubuntu)
2015-01-21 12:28:55 Andrea Azzarone unity (Ubuntu): status New In Progress
2015-01-21 12:28:57 Andrea Azzarone unity (Ubuntu): assignee Andrea Azzarone (andyrock)
2015-01-21 12:28:59 Andrea Azzarone unity: importance Undecided High
2015-01-21 14:22:26 Launchpad Janitor branch linked lp:~andyrock/unity/fix-1413165
2015-01-21 15:14:49 Andrea Azzarone unity: milestone 7.3.1
2015-02-11 16:19:59 Stephen M. Webb unity: milestone 7.3.1 7.3.2
2015-03-05 09:12:45 Launchpad Janitor unity (Ubuntu): status In Progress Fix Released
2015-03-13 14:36:55 Stephen M. Webb unity: status In Progress Fix Committed
2015-03-19 15:15:49 Stephen M. Webb unity: status Fix Committed Fix Released
2015-05-15 14:06:22 Christopher Townsend nominated for series unity/7.2
2015-05-15 14:06:22 Christopher Townsend bug task added unity/7.2
2015-05-15 14:06:30 Christopher Townsend unity/7.2: status New In Progress
2015-05-15 14:06:34 Christopher Townsend unity/7.2: importance Undecided High
2015-05-15 14:06:46 Christopher Townsend unity/7.2: assignee Andrea Azzarone (azzar1)
2015-05-15 14:06:50 Christopher Townsend unity/7.2: milestone 7.2.6
2015-05-15 14:07:41 Christopher Townsend nominated for series Ubuntu Trusty
2015-05-15 14:12:49 Launchpad Janitor branch linked lp:~townsend/unity/fix-lp1413165-trusty
2015-05-21 13:40:06 Christopher Townsend unity (Ubuntu Trusty): status New In Progress
2015-05-21 13:40:11 Christopher Townsend unity (Ubuntu Trusty): importance Undecided High
2015-05-21 13:40:15 Christopher Townsend unity (Ubuntu): importance Undecided High
2015-05-21 13:40:23 Christopher Townsend unity (Ubuntu Trusty): assignee Andrea Azzarone (azzar1)
2015-05-21 13:43:11 Christopher Townsend 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 [ 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. --------------------------------------------------------------------- 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
2015-05-21 20:15:27 Christopher Townsend 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. --------------------------------------------------------------------- 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 [ 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
2015-05-21 23:46:54 Brian Murray unity (Ubuntu Trusty): status In Progress Fix Committed
2015-05-21 23:46:56 Brian Murray bug added subscriber Ubuntu Stable Release Updates Team
2015-05-21 23:46:58 Brian Murray bug added subscriber SRU Verification
2015-05-21 23:47:02 Brian Murray tags verification-needed
2015-05-22 19:17:36 Christopher Townsend tags verification-needed verification-done
2015-05-27 19:32:01 Launchpad Janitor unity (Ubuntu Trusty): status Fix Committed Fix Released
2015-05-27 19:32:52 Chris J Arges removed subscriber Ubuntu Stable Release Updates Team
2015-05-28 15:25:35 Christopher Townsend unity/7.2: status In Progress Fix Committed
2017-10-13 08:50:50 Andrea Azzarone bug task deleted unity/7.2