Activity log for bug #1388875

Date Who What changed Old value New value Message
2014-11-03 15:26:59 Sebastien Bacher bug added bug
2014-11-03 15:26:59 Sebastien Bacher attachment added small program example https://bugs.launchpad.net/bugs/1388875/+attachment/4252073/+files/button.c
2014-11-03 15:27:14 Sebastien Bacher tags gtk-mir
2014-11-03 15:38:15 Lars Karlitski bug added subscriber Lars Uebernickel
2014-11-04 16:50:12 Launchpad Janitor gtk+3.0 (Ubuntu): status New Confirmed
2014-11-04 17:02:24 William Hua bug added subscriber William Hua
2014-11-05 03:13:52 Robert Ancell gtk+3.0 (Ubuntu): assignee Robert Ancell (robert-ancell)
2014-11-05 03:13:56 Robert Ancell gtk+3.0 (Ubuntu): status Confirmed Triaged
2014-11-05 04:05:59 Robert Ancell nominated for series Ubuntu Utopic
2014-11-05 04:05:59 Robert Ancell bug task added gtk+3.0 (Ubuntu Utopic)
2014-11-05 04:05:59 Robert Ancell nominated for series Ubuntu Vivid
2014-11-05 04:05:59 Robert Ancell bug task added gtk+3.0 (Ubuntu Vivid)
2014-11-05 22:02:03 Robert Ancell gtk+3.0 (Ubuntu Utopic): status New Triaged
2014-11-05 22:02:06 Robert Ancell gtk+3.0 (Ubuntu Utopic): importance Undecided High
2014-11-05 22:02:25 Robert Ancell summary [gtk-mir-backend] Clicking seems to confuse GTK (or the shell) GTK+ applications unable to be clicked on in Unity 8
2014-11-05 22:02:30 Robert Ancell gtk+3.0 (Ubuntu Utopic): assignee Robert Ancell (robert-ancell)
2014-11-05 22:08:52 Robert Ancell description Using utopic or current vivid, clicking on buttons/menubar in gtk application under unity8-mir leads to not working softwares. Not sure if that's the GTK backend or Mir to blame Small example attached, the program has a button and a label, click on the button should display "clicked!". Under unity8 the button seems to stop reacting after the first click and sometime the program closes (compile with "gcc button.c -o button`pkgconfig --cflags --libs gtk+-3.0`", to run it you need to have a .desktop running the binary and including the X-Ubuntu-Touch=true key) [Impact] GTK+ applications running in Unity 8 do not respond to button presses. This is due to Unity 8 / Mir generating the events in a different method that the GTK+ Mir backend did not understand. [Test Case] 1. Set up a GTK+ application to be launchable from Unity 8 (i.e. edit a .desktop file and set X-Ubuntu-Touch=true) 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.
2014-11-05 22:10:33 Robert Ancell description [Impact] GTK+ applications running in Unity 8 do not respond to button presses. This is due to Unity 8 / Mir generating the events in a different method that the GTK+ Mir backend did not understand. [Test Case] 1. Set up a GTK+ application to be launchable from Unity 8 (i.e. edit a .desktop file and set X-Ubuntu-Touch=true) 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. [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-Touch=true) 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.
2014-11-05 23:21:00 Robert Ancell gtk+3.0 (Ubuntu Utopic): status Triaged Fix Committed
2014-11-05 23:21:02 Robert Ancell gtk+3.0 (Ubuntu Vivid): status Triaged Fix Committed
2014-12-04 22:46:19 Brian Murray bug added subscriber Ubuntu Stable Release Updates Team
2014-12-04 22:46:24 Brian Murray bug added subscriber SRU Verification
2014-12-04 22:46:27 Brian Murray tags gtk-mir gtk-mir verification-needed
2014-12-19 08:29:01 Launchpad Janitor gtk+3.0 (Ubuntu Vivid): status Fix Committed Fix Released
2015-01-07 10:35:00 Sebastien Bacher tags gtk-mir verification-needed gtk-mir verification-done
2015-01-07 14:19:09 Chris J Arges removed subscriber Ubuntu Stable Release Updates Team
2015-01-07 14:24:13 Launchpad Janitor gtk+3.0 (Ubuntu Utopic): status Fix Committed Fix Released