touch-packages team mailing list archive
-
touch-packages team
-
Mailing list archive
-
Message #111363
[Bug 1496069] Re: [usc] Mir gives up and shuts down due to input with multimonitor qtmir (std::exception::what: Failure sending input event)
This bug was fixed in the package mir - 0.17.0+15.10.20151008.2-0ubuntu1
---------------
mir (0.17.0+15.10.20151008.2-0ubuntu1) wily; urgency=medium
[ Alexandros Frantzis ]
* New upstream release 0.17.0 (https://launchpad.net/mir/+milestone/0.17.0)
- ABI summary: Only servers and graphics drivers need rebuilding;
. Mirclient ABI unchanged at 9
. Mirserver ABI bumped to 35
. Mircommon ABI unchanged at 5
. Mirplatform ABI bumped to 11
. Mirprotobuf ABI bumped to 3
. Mirplatformgraphics ABI bumped to 6
. Mirclientplatform ABI unchanged at 3
- Enhancements:
. Introduce libmircookie, a simple mechanism for a group of cooperating
processes to hand out and verify difficult-to-forge timestamps to
untrusted 3rd parties.
. More refactorings to support renderers other than GL.
. Add MirBlob to the client API - a tool for serializing and
deserializing data.
. Introduce a libinput based input platform, not yet used by default.
. Provide a mechanism for the shell to send events on surface
construction.
. Provide mir::shell::DisplayConfigurationController allowing shells
to correctly change the display configuration, notifying clients
as appropriate.
. New DSO versioning guide.
. Send events pertaining to the output a surface is currently on (dpi,
form factor, scale) to clients.
- Bug fixes:
. [enhancement] XMir specific documentation should live in its own
subsection (LP: #1200114)
. Nested servers need cursor support (LP: #1289072)
. Mir cursor is missing/invisible until the client sets it multiple
times (LP: #1308133)
. [regression] Fullscreen software surfaces (like Xmir -sw) can crash
the Mir server (LP: #1493721)
. [usc] Mir gives up and shuts down due to input with multimonitor qtmir
(std::exception::what: Failure sending input event) (LP: #1496069)
. Mouse cursor disappears upon entering the surface area of a nested
client (LP: #1496849)
. [android] input is not dispatched when attaching an external monitor
(LP: #1498045)
. [android] input coordinates are scaled incorrectly when an external
display is connected (LP: #1498540)
. [android] std::exception::what: error during hwc set() when unplugging
external monitor (LP: #1498550)
. tests do not compile without precompiled headers (LP: #1498829)
. [android] std::exception::what: Failed to monitor fd: Operation not
permitted when unplugging external display in a nested configuration
(LP: #1499042)
. Mir suddenly no longer builds since 'mesa (11.0.0-1ubuntu1) wily':
/usr/include/EGL/eglplatform.h:100:35: fatal error:
android/native_window.h: No such file or directory (LP: #1499134)
. [android] various crashes when unplugging external display on a
nested configuration (LP: #1501927)
. Cursor becomes visible by itself when an external monitor is connected
(LP: #1502200)
. mesa FTBFS due to missing Requires in mirclient (LP: #1503450)
[ CI Train Bot ]
* New rebuild forced.
-- Alexandros Frantzis <alexandros.frantzis@xxxxxxxxxxxxx> Thu, 08 Oct
2015 16:12:19 +0000
** Changed in: mir (Ubuntu)
Status: Triaged => 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:
Fix Released
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