[regression] Some apps fail to start with [QPA] UbuntuClientIntegration: connection to Mir server failed.

Bug #1662145 reported by Jean-Baptiste Lallement on 2017-02-06
62
This bug affects 10 people
Affects Status Importance Assigned to Milestone
Canonical System Image
Critical
kevin gunn
Unity8 Session Snap
Critical
Unassigned
platform-api
Critical
Unassigned
platform-api (Ubuntu)
Critical
Unassigned
qtubuntu (Ubuntu)
Critical
Unassigned
ubuntu-app-launch (Ubuntu)
Critical
Unassigned

Bug Description

Zesty
unity8-session 16.04 396 canonical devmode

Test Case
1. Open the app drawer
2. Launch an app (eg calculator)

Expected result
It starts successfully and the app works as expected

Actual Result
It launches, the loading screen then a black screen is shown for a sort moment, then the window closes.

They all report:

>>>>>>>>>>>
Loading module: 'libubuntu_application_api_desktop_mirclient.so.3.0.0'
[QPA] UbuntuClientIntegration: connection to Mir server failed.

Mir returned: "Failed to connect to server socket: Permission denied"
<<<<<<<<<<<

Related branches

Jean-Baptiste Lallement (jibel) wrote :
Jean-Baptiste Lallement (jibel) wrote :
Jean-Baptiste Lallement (jibel) wrote :
Jean-Baptiste Lallement (jibel) wrote :

same journalctl without apparmor ALLOWED spam

Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in ubuntu-app-launch (Ubuntu):
status: New → Confirmed
Jean-Baptiste Lallement (jibel) wrote :

These messages are shown in the journal:

févr. 07 09:56:04 ubuntu-Inspiron-3138 snappy-xmir[18402]: Loading module: 'libubuntu_application_api_desktop_mirclient.so.3.0.0'
févr. 07 09:56:04 ubuntu-Inspiron-3138 snappy-xmir[18402]: [QPA] UbuntuClientIntegration: connection to Mir server failed.
févr. 07 09:56:04 ubuntu-Inspiron-3138 snappy-xmir[18402]: Mir returned: "Failed to connect to server socket: No such file or directory"
févr. 07 09:56:04 ubuntu-Inspiron-3138 systemd[3343]: ubuntu-app-launch-application-snap-ubuntu-clock-app_ubuntu-clock-app_29-1486457714107760.service: Main process exited, code=exited, status=1/FAILURE

Changed in canonical-devices-system-image:
importance: Undecided → High
Changed in unity8-session-snap:
importance: Undecided → Critical
Changed in canonical-devices-system-image:
importance: High → Critical
Changed in ubuntu-app-launch (Ubuntu):
importance: Undecided → Critical
Changed in canonical-devices-system-image:
status: New → Confirmed
Changed in unity8-session-snap:
status: New → Confirmed
Changed in canonical-devices-system-image:
assignee: nobody → kevin gunn (kgunn72)
milestone: none → p2
summary: - unity8 session snap - Apps launch and close immediately
+ unity8 session snap - Apps launch and close immediately ([QPA]
+ UbuntuClientIntegration: connection to Mir server failed.)
description: updated

This is not a snap or Unity8 bug. The same platform-api apps fail with the same error under Mir demo servers too.

summary: - unity8 session snap - Apps launch and close immediately ([QPA]
- UbuntuClientIntegration: connection to Mir server failed.)
+ Some apps fail to start with [QPA] UbuntuClientIntegration: connection
+ to Mir server failed.
Changed in platform-api (Ubuntu):
importance: Undecided → Critical
Changed in qtubuntu (Ubuntu):
importance: Undecided → Critical
Changed in platform-api (Ubuntu):
status: New → Confirmed
Changed in qtubuntu (Ubuntu):
status: New → Confirmed
Changed in unity8-session-snap:
status: Confirmed → Invalid
Changed in ubuntu-app-launch (Ubuntu):
status: Confirmed → Invalid
Changed in platform-api:
status: New → Confirmed
importance: Undecided → Critical
Changed in qtubuntu:
status: New → Confirmed
importance: Undecided → Critical
description: updated
Daniel van Vugt (vanvugt) wrote :

Also, the problem is not Mir, despite the error message.

The Mir server is not getting any connection request from the broken apps. However other apps like 'system-settings', 'dialer-app', and various mir-demos work fine still.

summary: - Some apps fail to start with [QPA] UbuntuClientIntegration: connection
- to Mir server failed.
+ [regression] Some apps fail to start with [QPA] UbuntuClientIntegration:
+ connection to Mir server failed.
tags: added: regression
description: updated
Michael Terry (mterry) wrote :

This is not the original issue, but yesterday I switched the unity8 snap to use a different, more standard path (/run/user/xxx/mir_socket) for the socket.

So if testing against the u8 snap, please re-create your app snaps to pull down the latest version of the desktop-launch script which will point your app at the new, correct socket location. Again, this isn't the same issue as OP, but I didn't want this new issue to confuse your testing of this bug.

Daniel van Vugt (vanvugt) wrote :

I understand. Unfortunately we're hitting new launch failure bugs every few days now. So the launch failure one logged days ago might not be the same bug experienced today.

Regardless of bug status we just need to get the code back to a semi-working state where apps will actually run, and then we can clarify the bugs.

Ted Gould (ted) wrote :

The log file makes this look like an app that is exporting the unity7 interface as well as the unity8 one. But the snapd in zesty doesn't have a unity8 interface. So we're starting it as a unity7 app. It is not realizing this and trying to connect to Mir, even after we've setup XMir for it.

Michael Terry (mterry) wrote :

Is this still happening?

Seemed to have been fixed with develop rc_proposed but then the wifi broke!

On 23 February 2017 at 15:53, Michael Terry <email address hidden>
wrote:

> Is this still happening?
>
> --
> You received this bug notification because you are subscribed to Ubuntu
> Touch Developer Preview.
> Matching subscriptions: <email address hidden>
> https://bugs.launchpad.net/bugs/1662145
>
> Title:
> [regression] Some apps fail to start with [QPA]
> UbuntuClientIntegration: connection to Mir server failed.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/canonical-devices-system-image/+bug/1662145/+
> subscriptions
>

--
*Andy Bleaden*
07946481674
Skype/Twitter/Telegram *@andybleaden*

Daniel van Vugt (vanvugt) wrote :

Further to comment #12, I've noticed in a few other bug reports people are experiencing rendering glitches in Qt apps that should only happen with Xmir. So we seem to have a problem with our own Qt apps incorrectly choosing X(mir) when native Mir is available and should be used instead.

Michael Terry (mterry) wrote :

Daniel, that may be because now we choose whether to use xmir or not based on the presence of the 'mir' interface (used to be the 'unity8' interface). Not all apps may plug into that interface.

Daniel van Vugt (vanvugt) wrote :

Sure, it's important to offer both X and Mir sockets to all apps.

Also very important that those apps (toolkits) choose native Mir over X when both are available.

Michael Terry (mterry) wrote :

Agreed. I was just trying to highlight that an app that used to work as Mir might now be run under XMir because we switched which interface we look at.

Olivier Tilloy (osomon) wrote :

Does that mean that apps that plug to the "unity8" iface should be updated to plug to "mir" now?

Michael Terry (mterry) wrote :

They should add mir, yeah. No need to replace unity8, necessarily [1].

[1] For the moment, plugging unity8 will make you uninstallable. This is to prevent widespread use of that interface before we finish it. The default set of core apps have an exception to this, though.

Changed in canonical-devices-system-image:
milestone: p2 → u8c-1
Gerry Boland (gerboland) wrote :

> Also very important that those apps (toolkits) choose native Mir over
> X when both are available.
Qt isn't designed to make the choice itself, it expects to be told if either X or Mir should be used.

kevin gunn (kgunn72) on 2017-03-09
tags: added: unity8-desktop
tags: added: unity8-session-snap
removed: unity8-desktop
Michał Sawicz (saviq) on 2017-03-13
no longer affects: qtubuntu
kevin gunn (kgunn72) on 2017-03-20
Changed in canonical-devices-system-image:
milestone: u8c-1 → p2
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers