Ubuntu
ubuntu-app-launch package

gnome-terminal fails to launch with native GTK ["Failed to connect to Mir: Failed to connect: not accepted by server"]

Bug #1670721 reported by Michael Terry
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Canonical System Image
Confirmed
High
Unassigned
ubuntu-app-launch (Ubuntu)
Confirmed
High
Unassigned
unity8 (Ubuntu)
Invalid
High
Unassigned

Bug Description

"Failed to connect to Mir: Failed to connect: not accepted by server"

And then a C++ exception about a broken pipe when sending a message to the Mir server.

That first error message is from GDK's Mir backend when creating the terminal server user daemon. I'm not sure what the root cause is yet.

See original description
Michael Terry (mterry)
tags: added: unity8-desktop
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in unity8 (Ubuntu):
status: New → Confirmed
Michael Terry (mterry)
summary: - gnome-terminal fails to launch under deb-based unity8
+ Some GTK apps (terminal, totem) fail to launch under deb-based unity8
description: updated
Michael Terry (mterry)
summary: - Some GTK apps (terminal, totem) fail to launch under deb-based unity8
+ gnome-terminal fails to launch under deb-based unity8
description: updated
Michael Terry (mterry)
description: updated
description: updated
Revision history for this message
Michael Terry (mterry) wrote :

Some research... So normally, gnome-terminal seems to start a systemd unit for a server process. Which UAL doesn't associate with the launching process, so doesn't allow a connection to Mir.

We can change how gnome-terminal is started by passing --disable-factory, but that doesn't make much progress either. It starts the server process as a child, but a window still never appears for an undiagnosed reason.

Daniel van Vugt (vanvugt)
summary: - gnome-terminal fails to launch under deb-based unity8
+ gnome-terminal fails to launch under deb-based unity8 ["Failed to
+ connect to Mir: Failed to connect: not accepted by server"]
Changed in canonical-devices-system-image:
importance: Undecided → High
Changed in unity8 (Ubuntu):
importance: Undecided → High
Changed in ubuntu-app-launch (Ubuntu):
importance: Undecided → High
status: New → Confirmed
Changed in canonical-devices-system-image:
status: New → Confirmed
Revision history for this message
Michael Terry (mterry) wrote : Re: gnome-terminal fails to launch under deb-based unity8 ["Failed to connect to Mir: Failed to connect: not accepted by server"]

With the switch to XMir by default, this is fixed.

Changed in canonical-devices-system-image:
status: Confirmed → Fix Released
Changed in ubuntu-app-launch (Ubuntu):
status: Confirmed → Fix Released
Changed in unity8 (Ubuntu):
status: Confirmed → Invalid
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

That's an accidental workaround (bug 1672931), which will go away in time. Not a permanent fix.

Changed in canonical-devices-system-image:
status: Fix Released → Confirmed
Changed in ubuntu-app-launch (Ubuntu):
status: Fix Released → Confirmed
summary: - gnome-terminal fails to launch under deb-based unity8 ["Failed to
- connect to Mir: Failed to connect: not accepted by server"]
+ gnome-terminal fails to launch with native GTK ["Failed to connect to
+ Mir: Failed to connect: not accepted by server"]
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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