touch-packages team mailing list archive

[Sebastien Bacher <seb128@xxxxxxxxxx>]

Public bug reported:

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)

** Affects: gtk+3.0 (Ubuntu)
     Importance: High
         Status: New


** Tags: gtk-mir

** Attachment added: "small program example"
   https://bugs.launchpad.net/bugs/1388875/+attachment/4252073/+files/button.c

** Tags added: gtk-mir

-- 
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-mir-backend] Clicking seems to confuse GTK (or the shell)

Status in “gtk+3.0” package in Ubuntu:
  New

Bug 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)

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