clients crash with "UbuntuClientIntegration: connection to Mir server failed."

Bug #1655936 reported by Albert Astals Cid
20
This bug affects 3 people
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://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

Related branches

Revision history for this message
Michał Sawicz (saviq) wrote :

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.

summary: - unity8-dash crashes with ""UbuntuClientIntegration: connection to Mir
+ unity8-dash crashes with "UbuntuClientIntegration: connection to Mir
server failed."
summary: - unity8-dash crashes with "UbuntuClientIntegration: connection to Mir
- server failed."
+ clients crash with "UbuntuClientIntegration: connection to Mir server
+ failed."
Changed in unity8 (Ubuntu):
status: New → Opinion
description: updated
Revision history for this message
Alan Griffiths (alan-griffiths) wrote :

I don't think anything can be done in Mir: The API [mir_connect_sync()] returns an error if it can't connect. There's no requirement to crash as a result - we have tests and examples that report the error and exit.

Changed in mir (Ubuntu):
status: New → Incomplete
Revision history for this message
Gerry Boland (gerboland) wrote :

So is actual desired fix to not crash, just quit gracefully?

Revision history for this message
Michał Sawicz (saviq) wrote :

qError() or something and exit() / QApplication::quit() would probably be desirable?

no longer affects: mir (Ubuntu)
Gerry Boland (gerboland)
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
Michał Sawicz (saviq)
Changed in unity8 (Ubuntu):
status: Opinion → Invalid
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package qtubuntu - 0.63+17.04.20170119.2-0ubuntu1

---------------
qtubuntu (0.63+17.04.20170119.2-0ubuntu1) zesty; urgency=medium

  [ Daniel d'Andrada ]
  * Resize menus and toolips when told to do so

  [ Gerry Boland ]
  * Quit gracefully if Mir connection failed (LP: #1655936)

 -- Michał Sawicz <email address hidden> Thu, 19 Jan 2017 22:55:05 +0000

Changed in qtubuntu (Ubuntu):
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.