touch-packages team mailing list archive

[Robert Ancell <robert.ancell@xxxxxxxxxxxxx>]

** Description changed:

- Using utopic or current vivid, clicking on buttons/menubar in gtk
- application under unity8-mir leads to not working softwares.
+ [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.
  
- Not sure if that's the GTK backend or Mir to blame
+ [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
  
- 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)
+ [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.

** Description changed:

  [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.
+ 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.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1388875

Title:
  GTK+ applications unable to be clicked on in Unity 8

Status in “gtk+3.0” package in Ubuntu:
  Triaged
Status in “gtk+3.0” source package in Utopic:
  Triaged
Status in “gtk+3.0” source package in Vivid:
  Triaged

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-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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1388875/+subscriptions