| 2017-01-12 11:58:41 |
Albert Astals Cid |
bug |
|
|
added bug |
| 2017-01-12 12:01:30 |
Michał Sawicz |
summary |
unity8-dash crashes with ""UbuntuClientIntegration: connection to Mir server failed." |
unity8-dash crashes with "UbuntuClientIntegration: connection to Mir server failed." |
|
| 2017-01-12 12:02:12 |
Michał Sawicz |
bug task added |
|
mir (Ubuntu) |
|
| 2017-01-12 12:02:22 |
Michał Sawicz |
bug task added |
|
qtubuntu (Ubuntu) |
|
| 2017-01-12 12:02:32 |
Michał Sawicz |
summary |
unity8-dash crashes with "UbuntuClientIntegration: connection to Mir server failed." |
clients crash with "UbuntuClientIntegration: connection to Mir server failed." |
|
| 2017-01-12 12:03:46 |
Michał Sawicz |
unity8 (Ubuntu): status |
New |
Opinion |
|
| 2017-01-12 12:08:42 |
Albert Astals Cid |
description |
According to https://errors.ubuntu.com/problem/bcb050f97778eb836056c1c48139bcde30ed0bcb it seems to be common-ish.
This happens when unity8-dash can't find unity8 (mir server) and it's our controlled way of exiting (not very clean, but it is how it is).
This will happen for example if you try to start unity8-dash directly (not thorugh 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. |
According to https://errors.ubuntu.com/problem/bcb050f97778eb836056c1c48139bcde30ed0bcb it seems to be common-ish.
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 QPlatformIntegrationPlugin::create() function to return, but all it does when that happens is call qFatal anyway [2]
[2] http://code.qt.io/cgit/qt/qtbase.git/tree/src/gui/kernel/qguiapplication.cpp#n1132 |
|
| 2017-01-12 12:13:24 |
Michał Sawicz |
bug task added |
|
qtbase-opensource-src (Ubuntu) |
|
| 2017-01-12 12:15:50 |
Alan Griffiths |
mir (Ubuntu): status |
New |
Incomplete |
|
| 2017-01-12 12:35:46 |
Alan Griffiths |
bug task deleted |
mir (Ubuntu) |
|
|
| 2017-01-12 13:27:05 |
Gerry Boland |
branch linked |
|
lp:~gerboland/qtubuntu/quit-gracefully-on-no-mirconnection |
|
| 2017-01-12 13:27:09 |
Gerry Boland |
qtubuntu (Ubuntu): status |
New |
In Progress |
|
| 2017-01-12 13:27:11 |
Gerry Boland |
qtubuntu (Ubuntu): importance |
Undecided |
Medium |
|
| 2017-01-12 13:27:13 |
Gerry Boland |
qtubuntu (Ubuntu): assignee |
|
Gerry Boland (gerboland) |
|
| 2017-01-12 13:27:17 |
Gerry Boland |
qtbase-opensource-src (Ubuntu): status |
New |
Invalid |
|
| 2017-01-25 10:10:50 |
Michał Sawicz |
unity8 (Ubuntu): status |
Opinion |
Invalid |
|
| 2017-01-25 17:29:13 |
Launchpad Janitor |
qtubuntu (Ubuntu): status |
In Progress |
Fix Released |
|
