GTK+ applications unable to be clicked on in Unity 8
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gtk+3.0 (Ubuntu) |
Fix Released
|
High
|
Robert Ancell | ||
Utopic |
Fix Released
|
High
|
Robert Ancell | ||
Vivid |
Fix Released
|
High
|
Robert Ancell |
Bug Description
[Impact]
GTK+ applications running in Unity 8 do not respond to button presses. This is due to Unity 8 / Mir changing the way events are generated (from mouse events to touch events). The GTK+ backend did not interpret these touch events.
[Test Case]
1. Set up a GTK+ application to be launchable from Unity 8 (i.e. edit a .desktop file and set X-Ubuntu-
2. Log into a Unity 8 session
3. Click on a button in the application
Expected result:
The button is pressed
Observed result:
Nothing happens when clicking on the button
[Regression Potential]
Low. The fix is just to handle the case of a pointer up/down event where no buttons are specified. This was previously ignored. The GTK+ backend is not usable without making hacks so this is unlikely to affect other GTK+ users.
Changed in gtk+3.0 (Ubuntu Utopic): | |
status: | New → Triaged |
importance: | Undecided → High |
summary: |
- [gtk-mir-backend] Clicking seems to confuse GTK (or the shell) + GTK+ applications unable to be clicked on in Unity 8 |
Changed in gtk+3.0 (Ubuntu Utopic): | |
assignee: | nobody → Robert Ancell (robert-ancell) |
description: | updated |
description: | updated |
Changed in gtk+3.0 (Ubuntu Utopic): | |
status: | Triaged → Fix Committed |
Changed in gtk+3.0 (Ubuntu Vivid): | |
status: | Triaged → Fix Committed |
Status changed to 'Confirmed' because the bug affects multiple users.