touch-packages team mailing list archive

[Daniel van Vugt <daniel.van.vugt@xxxxxxxxxxxxx>]

Dropped importance. N10 is likely not a supported device. And nobody
seems to have a problem with this bug having been mostly ignored for
over 100 days.

** Changed in: mir
   Importance: High => Medium

** Changed in: mir
    Milestone: 0.19.0 => None

-- 
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/1478231

Title:
  nexus10: unity-system-compositor crashes while turning display on with
  power key [std::exception::what: error turning display on. rc =
  fffffff0]

Status in Mir:
  New
Status in mir package in Ubuntu:
  New

Bug description:
  unity-system-compositor-log (still on top of 0.13.3 - without 0.14.0)
  with exception that causes the crash:

  [1437824578.379250] mirplatform: Found graphics driver: android
  [1437824578.379366] mirplatform: Found graphics driver: dummy
  [1437824578.390219] Server: Starting
  [1437824578.393296] Loader: Loading modules from: /usr/lib/arm-linux-gnueabihf/mir/server-platform
  [1437824578.393433] Loader: Loading module: /usr/lib/arm-linux-gnueabihf/mir/server-platform/input-stub.so
  [1437824578.394298] Loader: Loading module: /usr/lib/arm-linux-gnueabihf/mir/server-platform/graphics-android.so.2
  [1437824578.394348] Loader: Loading module: /usr/lib/arm-linux-gnueabihf/mir/server-platform/graphics-dummy.so
  [1437824578.399155] mirplatform: Found graphics driver: android
  [1437824578.399198] mirplatform: Found graphics driver: dummy
  [1437824578.399436] Platform Loader: Selected driver: android (version 0.13.3)
  [1437824579.150982] mirserver: Using software cursor
  GL_VENDOR = ARM
  GL_RENDERER = Mali-T604
  GL_VERSION = OpenGL ES 3.0
  dm_connection_start
  [1437824579.197658] GL: vendor: ARM
  [1437824579.197683] GL: renderer: Mali-T604
  [1437824579.197691] GL: version: OpenGL ES 3.0
  [1437824579.197699] GL: SL version: OpenGL ES GLSL ES 3.00
  [1437824579.197712] GL: max texture size = 8192
  [1437824579.197735] GL: framebuffer bits: RGBA=8888, depth=0, stencil=0
  [1437824579.203708] DisplayServer: Mir version 0.13.3
  set_active_session 'session-0'
  Opening session eglspinner
  Opening session session-0
  Closing session session-0
  Opening session session-0
  Closing session eglspinner
  Current active output is 2560x1600 +0+0
  Server supports 3 of 6 surface pixel formats. Using format: 1
  Signal 15 received. Good night.
  Closing session session-0
  ERROR: /build/buildd/mir-0.13.3+15.04.20150617/src/platforms/android/server/real_hwc_wrapper.cpp(156): Throw in function virtual void mir::graphics::android::RealHwcWrapper::display_on(mir::graphics::android::DisplayName) const
  Dynamic exception type: N5boost16exception_detail10clone_implINS0_19error_info_injectorISt13runtime_errorEEEE
  std::exception::what: error turning display on. rc = fffffff0

  Can't get connection

  A manual restart of lightdm resolves the issue. usc starts up fine and
  is able to turn the display on. Sometimes afer waiting long enough
  lightdm seems to become aware of the situation and respawns unity-
  system-compositor. So we might derive another bug for lightdm - as it
  takes far too long to detect the crash.

  I havent tried yet 0.14.0 - but it should happen there too.

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