Merge lp:~unity-team/unity8/sessionIndicatorForDevices into lp:unity8
| Status: | Merged |
|---|---|
| Approved by: | Michael Terry on 2016-03-15 |
| Approved revision: | 2226 |
| Merged at revision: | 2304 |
| Proposed branch: | lp:~unity-team/unity8/sessionIndicatorForDevices |
| Merge into: | lp:unity8 |
| Prerequisite: | lp:~unity-team/unity8/better-windowed-logic |
| Diff against target: |
266 lines (+48/-59) 8 files modified
debian/changelog (+6/-0) debian/control (+2/-1) plugins/Unity/Indicators/indicatorsmanager.cpp (+3/-5) plugins/Unity/Session/dbusunitysessionservice.cpp (+4/-1) qml/Components/Dialogs.qml (+6/-47) qml/Greeter/Greeter.qml (+6/-0) qml/Panel/IndicatorItemRow.qml (+5/-2) qml/Panel/Indicators/MenuItemFactory.qml (+16/-3) |
| To merge this branch: | bzr merge lp:~unity-team/unity8/sessionIndicatorForDevices |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Michael Terry | 2016-03-14 | Approve on 2016-03-15 | |
| Unity8 CI Bot | continuous-integration | 2016-03-14 | Needs Fixing on 2016-03-15 |
|
Review via email:
|
|||
This proposal supersedes a proposal from 2016-03-11.
Commit Message
Session indicator convergence
Description of the Change
Session indicator convergence
Enables the session indicator also on devices, tweaking/hiding some of the items that don't make sense there.
Cf. https:/
* Are there any related MPs required for this MP to build/function as expected? Please list.
https:/
Also needs indicator-session to be installed by default on devices!
* Did you perform an exploratory manual test run of your code change and any related functionality?
Yes
* Did you make sure that your branch does not contain spurious tags?
Yes
* If you changed the packaging (debian), did you subscribe the ubuntu-unity team to this MP?
Yes
* If you changed the UI, has there been a design review?
Yes, as per https:/
| Unity8 CI Bot (unity8-ci-bot) wrote : | # |
FAILED: Continuous integration, rev:2219
https:/
Executed test runs:
SUCCESS: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
Click here to trigger a rebuild:
https:/
| Albert Astals Cid (aacid) wrote : | # |
Text conflict in qml/OrientedShe
1 conflicts encountered.
| Unity8 CI Bot (unity8-ci-bot) wrote : | # |
FAILED: Continuous integration, rev:2220
https:/
Executed test runs:
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
Click here to trigger a rebuild:
https:/
| Unity8 CI Bot (unity8-ci-bot) wrote : | # |
FAILED: Continuous integration, rev:2221
https:/
Executed test runs:
SUCCESS: https:/
SUCCESS: https:/
FAILURE: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
Click here to trigger a rebuild:
https:/
| Michael Terry (mterry) wrote : | # |
+ Connections {
+ target: DBusUnitySessio
+ onLockRequested: lightDM.
+ }
I think this would better fit in Greeter.qml. We try to consolidate all the greeter logic in there, so that it's more easily ignorable if we're running without a greeter (which some split greeter scenarios need).
+ PromptLock();
Huh... org.freedesktop
But I guess this is OK for now. We might have to confirm everything works as expected here in the split greeter branches though.
+ if ((new_indicator
Can we not just drop that check and enable the correct profile for indicator-session? Does it still not have profile support? It would be more correct to fix that in the indicator than patch its menu items in unity8...
I haven't run this yet, this was just looking at code.
| Michael Terry (mterry) wrote : | # |
Oh, and as the autopilot test failure shows, you need Replaces & Breaks for unity8-schemas:
| Lukáš Tinkl (lukas-kde) wrote : | # |
> Huh... org.freedesktop
> the vt switch? I'd have to check how we know to lock the session in such cases.
> But I guess this is OK for now. We might have to confirm everything works as expected here in the > split greeter branches though.
Yup, I guess in the long term, this signal should be emitted
> + if ((new_indicator
> Can we not just drop that check and enable the correct profile for indicator-session? Does it
> still not have profile support? It would be more correct to fix that in the indicator than
> patch its menu items in unity8...
Yeah, no proper "phone" profile and certainly no time to do it now :/
- 2222. By Michael Terry on 2016-03-14
-
Fix up packaging a bit
- 2223. By Lukáš Tinkl on 2016-03-14
-
move the lock connection to Greeter.qml
| Lukáš Tinkl (lukas-kde) wrote : | # |
Moved the Connections to Greeter.qml, as requested
| Unity8 CI Bot (unity8-ci-bot) wrote : | # |
FAILED: Continuous integration, rev:2221
https:/
Executed test runs:
UNSTABLE: https:/
SUCCESS: https:/
FAILURE: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
Click here to trigger a rebuild:
https:/
| Michael Terry (mterry) wrote : | # |
OK. Code looks fine, just need to test once silo builds.
| Unity8 CI Bot (unity8-ci-bot) wrote : | # |
FAILED: Continuous integration, rev:2223
https:/
Executed test runs:
SUCCESS: https:/
SUCCESS: https:/
FAILURE: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
Click here to trigger a rebuild:
https:/
| Michael Terry (mterry) wrote : | # |
Well it works. But I've got some beefs:
- "About This Device" should probably be just "About", following System Settings' lead.
- The dialog we show on shut down is oddly different than the normal shutdown. We should use the same button sorting (Shut down on top) and labels (Restart instead of Reboot). And the menu and dialog use "Shut down" when the normal dialog uses "Power off".
We could just use the same dialog. But we'd still have to fix the menu. Has design had a chance to comment on any of this?
- The long standing bug about duplicate separator items really stands out here and makes the menu look bad... Is that an easy fix? /me looks into it real quick
| Michael Terry (mterry) wrote : | # |
(I realize that some of these issues might be on the indicator-session side, I'm just noting what I saw with the combo.)
| Michael Terry (mterry) wrote : | # |
I see, it seems that the duplicates are just because this MP strips some items during load(). But it doens't strip their associated separators.
| Lukáš Tinkl (lukas-kde) wrote : | # |
> Well it works. But I've got some beefs:
>
> - "About This Device" should probably be just "About", following System
> Settings' lead.
Nope, the design document (linked in description) says "About this device"
> - The dialog we show on shut down is oddly different than the normal shutdown.
> We should use the same button sorting (Shut down on top) and labels (Restart
> instead of Reboot). And the menu and dialog use "Shut down" when the normal
> dialog uses "Power off".
>
> We could just use the same dialog. But we'd still have to fix the menu. Has
> design had a chance to comment on any of this?
Yes, I will unify this, no idea why we even had 2 different dialogs there
> - The long standing bug about duplicate separator items really stands out here
> and makes the menu look bad... Is that an easy fix? /me looks into it real
> quick
Hmm, this one is tough, I'm afraid it's impossible to remove them :/
- 2224. By Lukáš Tinkl on 2016-03-15
-
don§t confuse the user and show just one power/shutdown dialog
| Unity8 CI Bot (unity8-ci-bot) wrote : | # |
FAILED: Continuous integration, rev:2224
https:/
Executed test runs:
SUCCESS: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
Click here to trigger a rebuild:
https:/
- 2225. By Lukáš Tinkl on 2016-03-15
-
gross hack for hiding the indicator-session for < 50GU screens
acked by dednick
| Unity8 CI Bot (unity8-ci-bot) wrote : | # |
FAILED: Continuous integration, rev:2225
https:/
Executed test runs:
SUCCESS: https:/
UNSTABLE: https:/
UNSTABLE: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
Click here to trigger a rebuild:
https:/
| Michael Terry (mterry) wrote : | # |
Tested this, worked fine.
There are a couple hacks in here that we'll want to clean up down the road (indicator-session should get proper profile support: bug 1557716, indicator-session should emit shutdown instead of reboot: bug 1557717, and the hard check for 90gu)
And we don't need unity8-schemas anymore, since the indicator-service only uses them if they are available (doesn't hard-depend on our packages anymore).
- 2226. By Lukáš Tinkl on 2016-03-15
-
remove unity8-schemas
not needed anymore, indicator-session has a runtime check
- 2227. By Lukáš Tinkl on 2016-03-15
-
make units.gu(60) the threshold between phone and tablet for the session indicator

FAILED: Continuous integration, rev:2219 /unity8- jenkins. ubuntu. com/job/ lp-unity8- ci/661/ /unity8- jenkins. ubuntu. com/job/ test-0- autopkgtest/ label=amd64, release= vivid+overlay, testname= qmluitests. sh/376 /unity8- jenkins. ubuntu. com/job/ test-0- autopkgtest/ label=amd64, release= xenial, testname= qmluitests. sh/376 /unity8- jenkins. ubuntu. com/job/ test-0- autopkgtest/ label=phone- armhf,release= vivid+overlay, testname= autopilot. sh/376 /unity8- jenkins. ubuntu. com/job/ build-0- fetch/867 /unity8- jenkins. ubuntu. com/job/ build-1- sourcepkg/ release= vivid+overlay/ 883 /unity8- jenkins. ubuntu. com/job/ build-1- sourcepkg/ release= xenial/ 883 /unity8- jenkins. ubuntu. com/job/ build-2- binpkg/ arch=amd64, release= vivid+overlay/ 881 /unity8- jenkins. ubuntu. com/job/ build-2- binpkg/ arch=amd64, release= vivid+overlay/ 881/artifact/ output/ *zip*/output. zip /unity8- jenkins. ubuntu. com/job/ build-2- binpkg/ arch=amd64, release= xenial/ 881 /unity8- jenkins. ubuntu. com/job/ build-2- binpkg/ arch=amd64, release= xenial/ 881/artifact/ output/ *zip*/output. zip /unity8- jenkins. ubuntu. com/job/ build-2- binpkg/ arch=armhf, release= vivid+overlay/ 881 /unity8- jenkins. ubuntu. com/job/ build-2- binpkg/ arch=armhf, release= vivid+overlay/ 881/artifact/ output/ *zip*/output. zip /unity8- jenkins. ubuntu. com/job/ build-2- binpkg/ arch=armhf, release= xenial/ 881 /unity8- jenkins. ubuntu. com/job/ build-2- binpkg/ arch=armhf, release= xenial/ 881/artifact/ output/ *zip*/output. zip /unity8- jenkins. ubuntu. com/job/ build-2- binpkg/ arch=i386, release= vivid+overlay/ 881 /unity8- jenkins. ubuntu. com/job/ build-2- binpkg/ arch=i386, release= vivid+overlay/ 881/artifact/ output/ *zip*/output. zip /unity8- jenkins. ubuntu. com/job/ build-2- binpkg/ arch=i386, release= xenial/ 881 /unity8- jenkins. ubuntu. com/job/ build-2- binpkg/ arch=i386, release= xenial/ 881/artifact/ output/ *zip*/output. zip
https:/
Executed test runs:
UNSTABLE: https:/
UNSTABLE: https:/
UNSTABLE: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
Click here to trigger a rebuild: /unity8- jenkins. ubuntu. com/job/ lp-unity8- ci/661/ rebuild
https:/