Merge lp:~3v1n0/unity8/mirsocket-env-set into lp:unity8
| Status: | Merged |
|---|---|
| Approved by: | Albert Astals Cid on 2016-06-10 |
| Approved revision: | 2442 |
| Merged at revision: | 2502 |
| Proposed branch: | lp:~3v1n0/unity8/mirsocket-env-set |
| Merge into: | lp:unity8 |
| Diff against target: |
22 lines (+13/-0) 1 file modified
data/unity8.conf (+13/-0) |
| To merge this branch: | bzr merge lp:~3v1n0/unity8/mirsocket-env-set |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Unity8 CI Bot | continuous-integration | Approve on 2016-06-19 | |
| Albert Astals Cid (community) | 2016-06-09 | Approve on 2016-06-10 | |
|
Review via email:
|
|||
Commit Message
Unity8.conf: ensure MIR_SOCKET is set for future customers (such as the dash)
This ensures that if we run unity8 as standalone in Mir on X/KMS the MIR_SOCKET
is defined for other clients.
Description of the Change
Loading unity8 clients (such as the dash) in Mir or Mir on X can fail if no MIR_SOCKET is set, let's try to fallback to the standard paths.
Indicators client just creates dynamic components without being informative on failures...
* Are there any related MPs required for this MP to build/function as expected?
No
* Did you perform an exploratory manual test run of your code change and any related functionality?
Yes, tested both running unity8 from the builddir and the system-wide installed one.
* If you changed the packaging (debian), did you subscribe the ubuntu-unity team to this MP?
N/A
* If you changed the UI, has there been a design review?
N/A
| Unity8 CI Bot (unity8-ci-bot) wrote : | # |
FAILED: Continuous integration, rev:2442
https:/
Executed test runs:
SUCCESS: https:/
SUCCESS: https:/
UNSTABLE: https:/
UNSTABLE: https:/
SUCCESS: 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:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
Click here to trigger a rebuild:
https:/
| Marco Trevisan (Treviño) (3v1n0) wrote : | # |
To get unity8 running in mir on X properly without crashing you'd need lp:~gerboland/qtmir/fix-gl-on-x11, in case you don't get mouse events you'd also need lp:~3v1n0/qtmir/ensure-activate-window.
Then just
initctl set-env -g QT_QPA_
start unity8 #(or use the ./run.sh)
| Albert Astals Cid (aacid) wrote : | # |
I did use a branch with both the fix-gl and the ensure-
I get
ERROR: Throw location unknown (consider using BOOST_THROW_
Dynamic exception type: boost::
std::exception:
The bind error translates to "address in use"
| Marco Trevisan (Treviño) (3v1n0) wrote : | # |
Ouch, I just pasted the wrong thing here
It was:
initctl set-env -g QT_QPA_
start unity8 #(or use the ./run.sh)
| Albert Astals Cid (aacid) wrote : | # |
* Did you perform an exploratory manual test run of the code change and any related functionality?
Yes
* Did CI run pass? If not, please explain why.
Yes
| Unity8 CI Bot (unity8-ci-bot) wrote : | # |
PASSED: Continuous integration, rev:2442
https:/
Executed test runs:
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: 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:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
Click here to trigger a rebuild:
https:/

How do i test this? i.e. how do i make it fail without this branch and then work with this branch?