[Touch-packages] [Bug 1655936] Re: clients crash with "UbuntuClientIntegration: connection to Mir server failed."

2017-01-25 Thread Launchpad Bug Tracker 
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   Thu, 19 Jan 2017
22:55:05 +

** Changed in: qtubuntu (Ubuntu)
   Status: In Progress => Fix Released

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

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

Status in qtbase-opensource-src package in Ubuntu:
  Invalid
Status in qtubuntu package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Invalid

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/qtbase-opensource-src/+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

[Touch-packages] [Bug 1655936] Re: clients crash with "UbuntuClientIntegration: connection to Mir server failed."

2017-01-25 Thread Michał Sawicz 
** Changed in: unity8 (Ubuntu)
   Status: Opinion => Invalid

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

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

Status in qtbase-opensource-src package in Ubuntu:
  Invalid
Status in qtubuntu package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  Invalid

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/qtbase-opensource-src/+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

[Touch-packages] [Bug 1655936] Re: clients crash with "UbuntuClientIntegration: connection to Mir server failed."

2017-01-12 Thread Gerry Boland 
** Branch linked: lp:~gerboland/qtubuntu/quit-gracefully-on-no-
mirconnection

** Changed in: qtubuntu (Ubuntu)
   Status: New => In Progress

** Changed in: qtubuntu (Ubuntu)
   Importance: Undecided => Medium

** Changed in: qtubuntu (Ubuntu)
 Assignee: (unassigned) => Gerry Boland (gerboland)

** Changed in: qtbase-opensource-src (Ubuntu)
   Status: New => Invalid

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

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

Status in qtbase-opensource-src package in Ubuntu:
  Invalid
Status in qtubuntu package in Ubuntu:
  In Progress
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/qtbase-opensource-src/+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

[Touch-packages] [Bug 1655936] Re: clients crash with "UbuntuClientIntegration: connection to Mir server failed."

2017-01-12 Thread Alan Griffiths 
** No longer affects: mir (Ubuntu)

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

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

Status in qtbase-opensource-src 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/qtbase-opensource-src/+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

[Touch-packages] [Bug 1655936] Re: clients crash with "UbuntuClientIntegration: connection to Mir server failed."

2017-01-12 Thread Michał Sawicz 
qError() or something and exit() / QApplication::quit() would probably
be desirable?

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

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

Status in qtbase-opensource-src 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/qtbase-opensource-src/+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

[Touch-packages] [Bug 1655936] Re: clients crash with "UbuntuClientIntegration: connection to Mir server failed."

2017-01-12 Thread Gerry Boland 
So is actual desired fix to not crash, just quit gracefully?

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

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

Status in mir package in Ubuntu:
  Incomplete
Status in qtbase-opensource-src 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

[Touch-packages] [Bug 1655936] Re: clients crash with "UbuntuClientIntegration: connection to Mir server failed."

2017-01-12 Thread Alan Griffiths 
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

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

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

Status in mir package in Ubuntu:
  Incomplete
Status in qtbase-opensource-src 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

[Touch-packages] [Bug 1655936] Re: clients crash with "UbuntuClientIntegration: connection to Mir server failed."

2017-01-12 Thread Michał Sawicz 
** Also affects: qtbase-opensource-src (Ubuntu)
   Importance: Undecided
   Status: New

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

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

Status in mir package in Ubuntu:
  Incomplete
Status in qtbase-opensource-src 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

[Touch-packages] [Bug 1655936] Re: clients crash with "UbuntuClientIntegration: connection to Mir server failed."

2017-01-12 Thread Albert Astals Cid 
** Description changed:

  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 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 
thorugh upstart) from a ssh shell in the phone, i.e
+ 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

-- 
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:
  Incomplete
Status in qtbase-opensource-src 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