touch-packages team mailing list archive

[Robert Ancell <robert.ancell@xxxxxxxxxxxxx>]

Public bug reported:

When trying to run the Unity 8 session on an up to date wily laptop
(using the unity8-desktop-session-mir package) I'm only seeing a black
screen.

Digging down, it appears when running a Mir server in compositor mode
the Mir clients are unable to create surfaces.

To reproduce:
1. Switch to VT1
2. Run a Mir server in compositor mode:
$ sudo mir_demo_server --window-manager system-compositor --arw-file
3. Switch to VT2
4. Run a Mir client:
$ MIR_SOCKET=/tmp/mir_socket mir_demo_client_basic
5. Switch to VT1
6. Switch to VT2

Expected result:
The client runs successfully

Observed result:
The client hits an assertion that the surface is not valid.

Using a modified client to see the error message (see lp:~robert-
ancell/mir/basic-client-print-surface-error) it gives:

Error processing request: Failed to place surface in requested output
Internal error details: /build/mir-QIEYOz/mir-0.15.0+15.10.20150818/src/server/shell/graphics_display_layout.cpp(91): Throw in function virtual void mir::shell::GraphicsDisplayLayout::place_in_output(mir::graphics::DisplayConfigurationOutputId, mir::geometry::Rectangle&)
Dynamic exception type: boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<std::runtime_error> >
std::exception::what: Failed to place surface in requested output

The above steps work file if the  --window-manager system-compositor
flag is removed.

This used to work before and appears to work on some up to date wily
systems.

** Affects: mir (Ubuntu)
     Importance: Critical
         Status: Confirmed

** Changed in: mir (Ubuntu)
   Importance: Undecided => Critical

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1488431

Title:
  Clients fail to create surfaces when using Mir server in compositor
  mode

Status in mir package in Ubuntu:
  Confirmed

Bug description:
  When trying to run the Unity 8 session on an up to date wily laptop
  (using the unity8-desktop-session-mir package) I'm only seeing a black
  screen.

  Digging down, it appears when running a Mir server in compositor mode
  the Mir clients are unable to create surfaces.

  To reproduce:
  1. Switch to VT1
  2. Run a Mir server in compositor mode:
  $ sudo mir_demo_server --window-manager system-compositor --arw-file
  3. Switch to VT2
  4. Run a Mir client:
  $ MIR_SOCKET=/tmp/mir_socket mir_demo_client_basic
  5. Switch to VT1
  6. Switch to VT2

  Expected result:
  The client runs successfully

  Observed result:
  The client hits an assertion that the surface is not valid.

  Using a modified client to see the error message (see lp:~robert-
  ancell/mir/basic-client-print-surface-error) it gives:

  Error processing request: Failed to place surface in requested output
  Internal error details: /build/mir-QIEYOz/mir-0.15.0+15.10.20150818/src/server/shell/graphics_display_layout.cpp(91): Throw in function virtual void mir::shell::GraphicsDisplayLayout::place_in_output(mir::graphics::DisplayConfigurationOutputId, mir::geometry::Rectangle&)
  Dynamic exception type: boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<std::runtime_error> >
  std::exception::what: Failed to place surface in requested output

  The above steps work file if the  --window-manager system-compositor
  flag is removed.

  This used to work before and appears to work on some up to date wily
  systems.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1488431/+subscriptions