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 changed:
- 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"]
--
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/1670721
Title:
gnome-terminal fails to launch with native GTK ["Failed to connect to
Mir: Failed to connect: not accepted by server"]
Status in Canonical System Image:
Confirmed
Status in ubuntu-app-launch package in Ubuntu:
Confirmed
Status in unity8 package in Ubuntu:
Invalid
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1670721/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
