[Ubuntu-x-swat] [Bug 1536815] Re: Connecting Xmir to USC fails [std::exception::what: An output ID must be specified from src/server/shell/system_compositor_window_manager.cpp(66)]

** Changed in: xorg-server (Ubuntu) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1536815 Title: Connecting Xmir to USC fails [std::exception::what:

[Ubuntu-x-swat] [Bug 1536815] Re: Connecting Xmir to USC fails [std::exception::what: An output ID must be specified from src/server/shell/system_compositor_window_manager.cpp(66)]

Syncing task from Mir. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1536815 Title: Connecting Xmir to USC fails [std::exception::what: An output ID must be specified from

[Ubuntu-x-swat] [Bug 1536815] Re: Connecting Xmir to USC fails [std::exception::what: An output ID must be specified from src/server/shell/system_compositor_window_manager.cpp(66)]

The same behaviour as on mobile is: Xmir -> Unity8 -> USC which works. This bug however is about: Xmir -> USC without any Unity8. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu.

[Ubuntu-x-swat] [Bug 1536815] Re: Connecting Xmir to USC fails [std::exception::what: An output ID must be specified from src/server/shell/system_compositor_window_manager.cpp(66)]

I'm getting this issue on the stable 16.04 Ubuntu. Does this mean Mir should not (cannot) be used in this combination on Xenial ? I merely like to have a test system with similar behaviour as the mobile one as development on PC is much easier than on tablet/phone alone. -- You received this bug

[Ubuntu-x-swat] [Bug 1536815] Re: Connecting Xmir to USC fails [std::exception::what: An output ID must be specified from src/server/shell/system_compositor_window_manager.cpp(66)]

** Changed in: xorg-server (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: xorg-server (Ubuntu) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu.

[Ubuntu-x-swat] [Bug 1536815] Re: Connecting Xmir to USC fails [std::exception::what: An output ID must be specified from src/server/shell/system_compositor_window_manager.cpp(66)]

Reverted. I changed my mind; that approach might break Unity8 and others that want a root window in a window. We need a proper solution. Either: (a) Mir understand and accept client windows can be bigger than one output; or (b) Xmir chop up the root window and display it as separate surfaces

[Ubuntu-x-swat] [Bug 1536815] Re: Connecting Xmir to USC fails [std::exception::what: An output ID must be specified from src/server/shell/system_compositor_window_manager.cpp(66)]

OK, here's a quick workaround for Xmir to get things going: https://git.launchpad.net/~xmir-team/xorg-server/+git/xmir/commit/?id=18ee4ec59c1ab47c857205d6abbcdc5881ec2f9b It's a workaround and not a fix because a proper fix will have to occur in Mir itself. Mir's "system compositor" mode needs to

[Ubuntu-x-swat] [Bug 1536815] Re: Connecting Xmir to USC fails [std::exception::what: An output ID must be specified from src/server/shell/system_compositor_window_manager.cpp(66)]

** Summary changed: - Connecting Xmir to USC crashes USC [std::exception::what: An output ID must be specified from src/server/shell/system_compositor_window_manager.cpp(66)] + Connecting Xmir to USC fails [std::exception::what: An output ID must be specified from