On 11/17/2013 04:37 AM, Matthieu Baerts wrote:
> @Doug: thank you for this test!
> Is it maybe possible to answer to this question from Carlos Garnacho on Gnome's bugzilla[1]?
>
>> I hence closing this bug, I also pushed
>> https://git.gnome.org/browse/gtk+/commit/?id=962415aeb7e9e47f61c006a5d817a15d181c5055
>> , so if anyone steps on this bug again (or thinks so), the output of an
>> affected application with GDK_DEBUG=events will be really handy
> [1] https://bugzilla.gnome.org/show_bug.cgi?id=699574#c27
>
Honestly I have no clue as how to produce something from that debug code
with compiz
(did include it in the gtk build..
On 11/17/2013 04:37 AM, Matthieu Baerts wrote: /git.gnome. org/browse/ gtk+/commit/ ?id=962415aeb7e 9e47f61c006a5d8 17a15d181c5055 /bugzilla. gnome.org/ show_bug. cgi?id= 699574# c27
> @Doug: thank you for this test!
> Is it maybe possible to answer to this question from Carlos Garnacho on Gnome's bugzilla[1]?
>
>> I hence closing this bug, I also pushed
>> https:/
>> , so if anyone steps on this bug again (or thinks so), the output of an
>> affected application with GDK_DEBUG=events will be really handy
> [1] https:/
>
Honestly I have no clue as how to produce something from that debug code
with compiz
(did include it in the gtk build..