[Touch-packages] [Bug 1670721] Re: gnome-terminal fails to launch under deb-based unity8 ["Failed to connect to Mir: Failed to connect: not accepted by server"]
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 : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1670721] 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 -- 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 ["Failed to connect to Mir: Failed to connect: not accepted by server"] Status in Canonical System Image: Fix Released Status in ubuntu-app-launch package in Ubuntu: Fix Released 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 : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1670721] Re: gnome-terminal fails to launch under deb-based unity8 ["Failed to connect to Mir: Failed to connect: not accepted by server"]
** 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 in: unity8 (Ubuntu) Importance: Undecided => High ** Also affects: ubuntu-app-launch (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu-app-launch (Ubuntu) Importance: Undecided => High ** Changed in: ubuntu-app-launch (Ubuntu) Status: New => Confirmed ** Changed in: canonical-devices-system-image 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. https://bugs.launchpad.net/bugs/1670721 Title: gnome-terminal fails to launch under deb-based unity8 ["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: 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
[Touch-packages] [Bug 1670721] Re: gnome-terminal fails to launch under deb-based unity8
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
[Touch-packages] [Bug 1670721] Re: gnome-terminal fails to launch under deb-based unity8
** 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 when sending a message to the Mir server. That first error message is from GDK's Mir backend. I'm not sure what the root cause is yet. + + Or sometimes I see an error about creating the terminal backend session + daemon... ** Description changed: "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. I'm not sure what the root cause is yet. Or sometimes I see an error about creating the terminal backend session - daemon... + daemon via dbus activation. ** Description changed: "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. I'm not sure what - the root cause is yet. - - Or sometimes I see an error about creating the terminal backend session - daemon via dbus activation. + 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. -- 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
[Touch-packages] [Bug 1670721] Re: gnome-terminal fails to launch under deb-based unity8
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. 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: It tries to launch a backend user daemon terminal server. Which can't seem to connect to Mir. 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
