Keyboard events being sent to null
Bug #1590060 reported by
Gerry Boland
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
qtmir (Ubuntu) |
Fix Released
|
Medium
|
Marco Trevisan (Treviño) |
Bug Description
In QtMir, we decide what window a key event goes to with the following:
virtual QWindow* QtWindowSystem:
{
return QGuiApplication
}
Trevinho is launching unity8 inside mir_demo_server on a VT (from Unity7) and finding that key events are not working - debugging we saw that focusedWindow() is null. Need to figure out what went wrong. Steps to repro are coming below
Related branches
lp:~3v1n0/qtmir/ensure-activate-window
- Gerry Boland (community): Approve
- Unity8 CI Bot (community): Approve (continuous-integration)
-
Diff: 11 lines (+1/-0)1 file modifiedsrc/platforms/mirserver/screenwindow.cpp (+1/-0)
Changed in qtmir: | |
assignee: | nobody → Daniel d'Andrada (dandrader) |
Changed in qtmir: | |
status: | New → In Progress |
importance: | Undecided → Medium |
assignee: | Daniel d'Andrada (dandrader) → Marco Trevisan (Treviño) (3v1n0) |
Changed in qtmir: | |
status: | In Progress → Fix Released |
affects: | qtmir → qtmir (Ubuntu) |
To post a comment you must log in.
This is a laptop with touch-screen. Same seems to happen when mir_demo_server (or unity8 itself) is launched in X (using mir on X), to get this I:
sudo mir_demo_server --arw-file --file /tmp/mir_socket --vt 8 /tmp/mir_ socket PLATFORM= mirserver
initctl set-env -g MIR_SOCKET=
initctl set-env -g QT_QPA_
start unity8
If I do the same by launching the same unity8 version inside a LXC container, I'm instead getting something else:
- Touchscreen events work
- Keyboard works
- Mouse pointer events are recorded (according to logs) but NOT delivered.