clients crash with "UbuntuClientIntegration: connection to Mir server failed."
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
qtbase-opensource-src (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
qtubuntu (Ubuntu) |
Fix Released
|
Medium
|
Gerry Boland | ||
unity8 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
According to https:/
This happens when unity8-dash can't find unity8 (mir server) and crashing (via QFatal) is our controlled way of exiting (not very clean, but it is how it is)[1].
This will happen for example if you try to start unity8-dash directly (not through upstart) from a ssh shell in the phone, i.e
phablet-shell
stop unity8-dash
unity8-dash
And it may happen after a unity8 crash.
In general we think that it's not a pressing issue users have since there seems to have not been any report of unity8-dash failing to start, but we're creating this bug to track it from time to time and make sure it doesn't get worse.
[1] Qt platform plugins (also know as QPA) don't have a way to say they had a problem initiating themselves, Qt code is prepared for the QPlatformIntegr
[2] http://
Related branches
- Daniel d'Andrada (community): Approve
- Unity8 CI Bot: Approve (continuous-integration)
-
Diff: 35 lines (+12/-5)1 file modifiedsrc/ubuntumirclient/integration.cpp (+12/-5)
description: | updated |
no longer affects: | mir (Ubuntu) |
Changed in qtubuntu (Ubuntu): | |
status: | New → In Progress |
importance: | Undecided → Medium |
assignee: | nobody → Gerry Boland (gerboland) |
Changed in qtbase-opensource-src (Ubuntu): | |
status: | New → Invalid |
Changed in unity8 (Ubuntu): | |
status: | Opinion → Invalid |
I don't think anything can be done in either unity8 or the dash binary... this is how mirclient/qtubuntu behave when there's a connection problem.