touch-packages team mailing list archive

[Alexandros Frantzis <alexandros.frantzis@xxxxxxxxxxxxx>]

** Changed in: mir
       Status: Fix Committed => Fix Released

** Changed in: mir (Ubuntu)
       Status: New => Fix Released

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

Title:
  [usc] Mir gives up and shuts down due to input with multimonitor qtmir
  (std::exception::what: Failure sending input event)

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Triaged

Bug description:
  I'm implementing proper multimonitor support in QtMir in this branch:
  lp:~gerboland/qtmir/multimonitor/

  Please build & install on device. You don't need to change unity8. The
  immediate goal is for unity8 to remain on the tablet screen, and have
  nothing (well a black screen) drawn on the external monitor.

  This is mostly happening, but I'm experiencing problems related to
  input.

  Steps to repro:
  1. When you plug in the external monitor, nothing will appear on it (for later), but unity8 should still be interactive on the N7 
      - unity8 will flicker when the display config changes, due to it tearing down the old gl context and creating a new one.
      - unity8 is not getting any touch input events. I checked that USC is not sending it any. [1]
      - however the vol up/down key does cause the volume notification to appear.

  2. Now unplug the external monitor. 
      - *sometimes* unity8 works fine, gets input events again just fine and works great.
      - *sometimes* unity8 crashes as soon as you tap on the screen. It crashes because USC shuts down [2]! Relevant failure message:

  ERROR: /home/gerry/dev/projects/mir/mir-0.15/src/server/input/android/input_sender.cpp(218): Throw in function void mir::input::android::InputSender::ActiveTransfer::send(mir::input::android::InputSendEntry&&)
  Dynamic exception type: N5boost16exception_detail10clone_implINS0_19error_info_injectorISt13runtime_errorEEEE
  std::exception::what: Failure sending input event : 
  9, "Bad file descriptor"

  Something gone screwy with input then.

  
  Perhaps QtMir needs to do something special to its input receiver when the multimonitor situation changes and its surface is destroyed & recreated??
  Guidance appreciated
  -G


  [1] http://pastebin.ubuntu.com/12418660/ - is USC log with input reporting enabled. Started with 1 monitor, then was 2, then 1 again. Observe while in multimonitor case, no input events are "Published" and "Received"
  [2] http://pastebin.ubuntu.com/12419006/ - USC backtrace when it shuts down

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