lp:~cimi/unity8/fix-lazyImage-test-flakyness

Created by Andrea Cimitan and last modified
Get this branch:
bzr branch lp:~cimi/unity8/fix-lazyImage-test-flakyness
Only Andrea Cimitan can upload to this branch. If you are Andrea Cimitan please log in for upload directions.

Branch merges

Related bugs

Related blueprints

Branch information

Owner:
Andrea Cimitan
Project:
Unity 8
Status:
Merged

Recent revisions

2040. By Andrea Cimitan

Fix flakyness

2039. By Launchpad Translations on behalf of unity-team

Launchpad automatic translations update.

2038. By Launchpad Translations on behalf of unity-team

Launchpad automatic translations update.

2037. By Launchpad Translations on behalf of unity-team

Launchpad automatic translations update.

2036. By CI Train Bot Account

Releasing 8.11+16.04.20151104-0ubuntu1

2035. By Michael Terry

Avoid showing the shutdown dialog when turning on the screen if your device is under heavy load.

Specifically, we actually watch the timestamp of input events as they come in to determine how long it's been. This means that if for whatever reason, processing of events get delayed, we don't misinterpret user input.

To test this, try running the following command and then turning the screen on and off again:
sudo cpulimit -l 1 -c 1 -p `ps ax | grep dbus-daemon | head -n 1 | awk '{print $1;}'`

Without this branch, you'll notice that at some point, you see the shutdown dialog in error. Because unity8 couldn't keep up with events and thought 2s passed between power-pressed and power-released events.

But if we watch the timestamps, we can avoid that particular fate. Fixes: #1508563
Approved by: Albert Astals Cid, Michael Zanetti

2034. By Albert Astals Cid

CroppedImageMinimumSourceSize: Fix 'Binding loop detected for property "imageAspectRatio"'

Approved by: Gerry Boland, Michał Sawicz

2033. By Christopher Lee

Quick spelling fix in process control output.
Approved by: Albert Astals Cid

2032. By Michał Sawicz

Support server->client visibility change to stop rendering (lp:#1475678) Fixes: #1475678
Approved by: Daniel d'Andrada

2031. By Michael Terry

Handle lifecycle policy exceptions ourselves, instead of letting qtmir do it for us and allow non-Touch apps to opt-out of the Touch lifecycle.

This requires using the new isTouchApp unity-api property to ApplicationInfoInterface.

Now that qtmir won't decide policy for suspending exemptions anymore, we take over the interpretation of the lifecycleException GSettings key. Since the GSettings key for that was registered under the qtmir namespace (and there's no technical reason to migrate settings), I left the schema in qtmir itself. We merely consume it.

Branch metadata

Branch format:
Branch format 7
Repository format:
Bazaar repository format 2a (needs bzr 1.16 or later)
Stacked on:
lp:unity8
This branch contains Public information 
Everyone can see this information.

Subscribers