| 2012-07-02 22:27:30 |
Daniel d'Andrada |
bug |
|
|
added bug |
| 2012-07-02 22:29:10 |
Daniel d'Andrada |
bug task added |
|
utouch-grail (Ubuntu) |
|
| 2012-07-02 22:29:19 |
Daniel d'Andrada |
utouch-grail: assignee |
|
Daniel d'Andrada (dandrader) |
|
| 2012-07-02 22:29:31 |
Daniel d'Andrada |
utouch-grail: importance |
Undecided |
High |
|
| 2012-07-02 22:29:36 |
Daniel d'Andrada |
utouch-grail: status |
New |
In Progress |
|
| 2012-07-02 22:41:16 |
Daniel d'Andrada |
branch linked |
|
lp:~dandrader/utouch-grail/lp1020315 |
|
| 2012-07-05 15:21:11 |
Launchpad Janitor |
branch linked |
|
lp:utouch-grail |
|
| 2012-07-05 15:22:19 |
Daniel d'Andrada |
utouch-grail: status |
In Progress |
Fix Committed |
|
| 2012-07-25 23:17:41 |
Chase Douglas |
utouch-grail: milestone |
|
3.0.6 |
|
| 2012-07-25 23:22:12 |
Chase Douglas |
utouch-grail: status |
Fix Committed |
Fix Released |
|
| 2012-07-27 21:39:23 |
Launchpad Janitor |
branch linked |
|
lp:grail/ubuntu |
|
| 2012-07-30 17:44:25 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/grail |
|
| 2012-07-30 22:33:46 |
Chase Douglas |
affects |
utouch-grail (Ubuntu) |
grail (Ubuntu) |
|
| 2012-07-30 22:33:46 |
Chase Douglas |
grail (Ubuntu): status |
New |
Fix Released |
|
| 2012-08-09 20:58:52 |
Launchpad Janitor |
branch linked |
|
lp:~fginther/grail/grail-3.0.6-precise |
|
| 2012-08-09 21:51:59 |
Francis Ginther |
description |
Preconditions:
- Activate a subscription for single-touch gestures of class "Touch".
- There should be no other application with higher priority for getting ownership over the touches.
Steps to reproduce the problem:
1 - Perform a quick tap on a touchscreen.
- That will produce 3 utouch-frame events
a) a frame begin with owned == false
b) a frame update with owned == true
c) a frame end
Expected outcome:
The following slice events should be sent by grail:
1. Slice Begin, construction finished == false
2. Slice Update, construction finished == false
3. Slice End, construction finished == true
Actual outcome:
The following slice events are sent by grail:
1. Slice Begin, construction finished == false
2. Slice Update, construction finished == false
3. Slice Update, construction finished == false |
[Impact]
TBD
[Test Case]
Preconditions:
- Activate a subscription for single-touch gestures of class "Touch".
- There should be no other application with higher priority for getting ownership over the touches.
Steps to reproduce the problem:
1 - Perform a quick tap on a touchscreen.
- That will produce 3 utouch-frame events
a) a frame begin with owned == false
b) a frame update with owned == true
c) a frame end
Expected outcome:
The following slice events should be sent by grail:
1. Slice Begin, construction finished == false
2. Slice Update, construction finished == false
3. Slice End, construction finished == true
Actual outcome:
The following slice events are sent by grail:
1. Slice Begin, construction finished == false
2. Slice Update, construction finished == false
3. Slice Update, construction finished == false
[Regression Potential]
TBD
A new regression test case has been added for this issue. All previous functional and regression test cases continue to pass. |
|
| 2012-08-10 18:03:33 |
Chase Douglas |
nominated for series |
|
Ubuntu Precise |
|
| 2012-08-10 18:03:33 |
Chase Douglas |
bug task added |
|
grail (Ubuntu Precise) |
|
| 2012-08-10 18:12:52 |
Chase Douglas |
description |
[Impact]
TBD
[Test Case]
Preconditions:
- Activate a subscription for single-touch gestures of class "Touch".
- There should be no other application with higher priority for getting ownership over the touches.
Steps to reproduce the problem:
1 - Perform a quick tap on a touchscreen.
- That will produce 3 utouch-frame events
a) a frame begin with owned == false
b) a frame update with owned == true
c) a frame end
Expected outcome:
The following slice events should be sent by grail:
1. Slice Begin, construction finished == false
2. Slice Update, construction finished == false
3. Slice End, construction finished == true
Actual outcome:
The following slice events are sent by grail:
1. Slice Begin, construction finished == false
2. Slice Update, construction finished == false
3. Slice Update, construction finished == false
[Regression Potential]
TBD
A new regression test case has been added for this issue. All previous functional and regression test cases continue to pass. |
[Impact]
Proper usage of grail gestures requires processing gestures only after they have finished "construction". Software, such as Unity, waits for this event in order to handle gestures properly. When the event does not occur, a grail gesture may be left unaccepted and unrejected, which may cause the touch interface to "hang" and become unresponsive to future taps. This bug causes grail to not emit a construction finished event under certain circumstances.
[Test Case]
Preconditions:
- Activate a subscription for single-touch gestures of class "Touch".
- There should be no other application with higher priority for getting ownership over the touches.
Steps to reproduce the problem:
1 - Perform a quick tap on a touchscreen.
- That will produce 3 utouch-frame events
a) a frame begin with owned == false
b) a frame update with owned == true
c) a frame end
Expected outcome:
The following slice events should be sent by grail:
1. Slice Begin, construction finished == false
2. Slice Update, construction finished == false
3. Slice End, construction finished == true
Actual outcome:
The following slice events are sent by grail:
1. Slice Begin, construction finished == false
2. Slice Update, construction finished == false
3. Slice Update, construction finished == false
There is currently no code released that performs these steps. However, there is code in development for Unity that causes this behavior. One of the gesture stack developers will need to verify this bug is fixed.
[Regression Potential]
Small. The source code changes are minimal; a couple function calls are reordered so they behave properly. The rest of the changes introduce a test mock framework and a regression test for this issue. All previous functional and regression tests cases continue to pass.
Areas of concern for testing is whether gestures continue to operate properly, and whether touchscreens become unresponsive after gestural or pointer interactions. |
|
| 2012-08-10 18:13:04 |
Chase Douglas |
grail (Ubuntu Precise): importance |
Undecided |
Medium |
|
| 2012-08-10 18:13:15 |
Chase Douglas |
grail (Ubuntu Precise): assignee |
|
Francis Ginther (fginther) |
|
| 2012-08-10 18:13:21 |
Chase Douglas |
grail (Ubuntu Precise): status |
New |
In Progress |
|
| 2012-08-27 19:40:39 |
Chase Douglas |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2012-08-30 19:15:27 |
Adam Conrad |
grail (Ubuntu Precise): status |
In Progress |
Fix Committed |
|
| 2012-08-30 19:15:31 |
Adam Conrad |
bug |
|
|
added subscriber SRU Verification |
| 2012-08-30 19:15:38 |
Adam Conrad |
tags |
|
verification-needed |
|
| 2012-09-02 07:45:56 |
Launchpad Janitor |
branch linked |
|
lp:~ubuntu-branches/ubuntu/precise/grail/precise-proposed |
|
| 2012-09-06 16:54:31 |
Chase Douglas |
tags |
verification-needed |
verification-done |
|
| 2012-09-13 21:51:51 |
Adam Conrad |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2012-09-13 21:52:13 |
Launchpad Janitor |
grail (Ubuntu Precise): status |
Fix Committed |
Fix Released |
|
