| 2017-03-07 15:11:43 |
Michael Terry |
bug |
|
|
added bug |
| 2017-03-07 15:11:57 |
Michael Terry |
bug task added |
|
canonical-devices-system-image |
|
| 2017-03-07 15:12:01 |
Michael Terry |
tags |
|
unity8-desktop |
|
| 2017-03-07 15:28:41 |
Launchpad Janitor |
unity8 (Ubuntu): status |
New |
Confirmed |
|
| 2017-03-07 18:38:28 |
Michael Terry |
summary |
gnome-terminal fails to launch under deb-based unity8 |
Some GTK apps (terminal, totem) fail to launch under deb-based unity8 |
|
| 2017-03-07 18:40:38 |
Michael Terry |
description |
It tries to launch a backend user daemon terminal server. Which can't seem to connect to Mir. |
"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. |
|
| 2017-03-07 18:57:47 |
Michael Terry |
summary |
Some GTK apps (terminal, totem) fail to launch under deb-based unity8 |
gnome-terminal fails to launch under deb-based unity8 |
|
| 2017-03-07 18:58:47 |
Michael Terry |
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. I'm not sure what the root cause is yet. |
"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... |
|
| 2017-03-07 19:03:44 |
Michael Terry |
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. I'm not sure what the root cause is yet.
Or sometimes I see an error about creating the terminal backend session daemon... |
"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. |
|
| 2017-03-07 19:05:05 |
Michael Terry |
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. 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. |
"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. |
|
| 2017-03-08 02:42:35 |
Daniel van Vugt |
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"] |
|
| 2017-03-08 02:42:39 |
Daniel van Vugt |
canonical-devices-system-image: importance |
Undecided |
High |
|
| 2017-03-08 02:42:42 |
Daniel van Vugt |
unity8 (Ubuntu): importance |
Undecided |
High |
|
| 2017-03-08 02:43:08 |
Daniel van Vugt |
bug task added |
|
ubuntu-app-launch (Ubuntu) |
|
| 2017-03-08 02:43:13 |
Daniel van Vugt |
ubuntu-app-launch (Ubuntu): importance |
Undecided |
High |
|
| 2017-03-08 02:43:17 |
Daniel van Vugt |
ubuntu-app-launch (Ubuntu): status |
New |
Confirmed |
|
| 2017-03-08 02:43:21 |
Daniel van Vugt |
canonical-devices-system-image: status |
New |
Confirmed |
|
| 2017-03-16 14:14:51 |
Michael Terry |
canonical-devices-system-image: status |
Confirmed |
Fix Released |
|
| 2017-03-16 14:14:53 |
Michael Terry |
ubuntu-app-launch (Ubuntu): status |
Confirmed |
Fix Released |
|
| 2017-03-16 14:14:56 |
Michael Terry |
unity8 (Ubuntu): status |
Confirmed |
Invalid |
|
| 2017-03-17 02:51:44 |
Daniel van Vugt |
canonical-devices-system-image: status |
Fix Released |
Confirmed |
|
| 2017-03-17 02:51:47 |
Daniel van Vugt |
ubuntu-app-launch (Ubuntu): status |
Fix Released |
Confirmed |
|
| 2017-03-17 02:52:07 |
Daniel van Vugt |
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"] |
|
