| 2014-06-05 17:58:16 |
Pat McGowan |
bug |
|
|
added bug |
| 2014-06-05 18:11:58 |
Pat McGowan |
tags |
not-reproducible rtm14 |
rtm14 |
|
| 2014-06-05 18:20:44 |
Pat McGowan |
attachment added |
|
Crash after closing clock app in app scope https://bugs.launchpad.net/unity-mir/+bug/1326906/+attachment/4125991/+files/_usr_lib_arm-linux-gnueabihf_qt5_bin_qmlscene.32011.crash |
|
| 2014-06-05 18:44:26 |
Michał Sawicz |
summary |
Apps still using cpu when not active |
Apps escape lifecycle if unfocused in "starting" state |
|
| 2014-06-05 18:45:53 |
Michał Sawicz |
description |
Mako running 67
Phone got into a state where the clock app, the settings app and sensors.qcom were all running continuously at 8-10% cpu despite the fact that they were not in the foreground, and either app scope or lock screen was shown. Other apps I had started were not using cpu.
I had set a timer in clock app at some point. I have not been able to reproduce since. |
Mako running 67
Phone got into a state where the clock app, the settings app and sensors.qcom were all running continuously at 8-10% cpu despite the fact that they were not in the foreground, and either app scope or lock screen was shown. Other apps I had started were not using cpu.
I had set a timer in clock app at some point. I have not been able to reproduce since.
Steps to repro:
* start an app and immediately press power to lock the phone
Expected results:
* app gets suspended
Current result:
* app stays active |
|
| 2014-06-05 18:45:55 |
Michał Sawicz |
unity-mir: status |
New |
Triaged |
|
| 2014-06-05 18:45:58 |
Michał Sawicz |
unity-mir: importance |
Undecided |
High |
|
| 2014-06-05 18:46:04 |
Michał Sawicz |
unity-mir: assignee |
|
Gerry Boland (gerboland) |
|
| 2014-06-05 20:44:24 |
Pat McGowan |
description |
Mako running 67
Phone got into a state where the clock app, the settings app and sensors.qcom were all running continuously at 8-10% cpu despite the fact that they were not in the foreground, and either app scope or lock screen was shown. Other apps I had started were not using cpu.
I had set a timer in clock app at some point. I have not been able to reproduce since.
Steps to repro:
* start an app and immediately press power to lock the phone
Expected results:
* app gets suspended
Current result:
* app stays active |
Mako running 67
Phone got into a state where the clock app, the settings app and sensors.qcom were all running continuously at 8-10% cpu despite the fact that they were not in the foreground, and either app scope or lock screen was shown. Other apps I had started were not using cpu.
Steps to repro:
* start an app and immediately press power to lock the phone
Alternate steps:
0 - start top from command line
1 - start an app (notes, system settings clock, ) and wait until its fully loaded, say 5-10 secs
2 - left edge swipe to reveal the app scope
3 - press power to turn off, then again to turn on
4 - right edge swipe to dismiss lock screen and show the app scope
top will start to show the app and sensors.qcom at 8-10% until the system goes to suspend.
Expected results:
* app gets suspended
Current result:
* app stays active |
|
| 2014-09-02 21:15:03 |
kevin gunn |
summary |
Apps escape lifecycle if unfocused in "starting" state |
Apps escape lifecycle if unfocused in "starting" state from hitting power button |
|
| 2014-09-02 21:24:20 |
kevin gunn |
tags |
rtm14 |
rtm14 touch-2014-10-16 |
|
| 2014-09-03 09:07:12 |
Gerry Boland |
affects |
unity-mir |
qtmir |
|
| 2014-09-12 08:59:30 |
Michael Zanetti |
branch linked |
|
lp:~unity-team/qtmir/fix-some-lifecycle-bugs |
|
| 2014-09-12 09:01:18 |
Michael Zanetti |
qtmir: status |
Triaged |
In Progress |
|
| 2014-09-12 09:01:21 |
Michael Zanetti |
qtmir: assignee |
Gerry Boland (gerboland) |
Michael Zanetti (mzanetti) |
|
| 2014-10-08 10:08:29 |
Michael Zanetti |
qtmir: status |
In Progress |
Fix Released |
|
| 2017-03-13 17:14:34 |
Michał Sawicz |
affects |
qtmir |
qtmir (Ubuntu) |
|
