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:
-
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
--
** Summary changed:
- 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
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
** Summary changed:
- Some GTK apps (terminal, totem) fail to launch under deb-based unity8
+ gnome-terminal fails to launch under deb-based unity8
** Description changed:
"Failed to connect to Mir: Failed to connect: not accepted by server"
And then a C++ exception about a broken pipe
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: unity8 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
6 matches
Mail list logo
