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. -- 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 under deb-based unity8 Status in Canonical System Image: New Status in unity8 package in Ubuntu: Confirmed 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 : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
