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 changed:

- unity8-dash crashes with ""UbuntuClientIntegration: connection to Mir server 
failed."
+ unity8-dash crashes with "UbuntuClientIntegration: connection to Mir server 
failed."

** Also affects: mir (Ubuntu)
   Importance: Undecided
       Status: New

** Also affects: qtubuntu (Ubuntu)
   Importance: Undecided
       Status: New

** Summary changed:

- 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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1655936

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

Status in mir package in Ubuntu:
  New
Status in qtubuntu package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Opinion

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1655936/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to