After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 731612 - gtk+3_0-3.13.2 breaks tray icon left click in gnote and onboard in Mageia
gtk+3_0-3.13.2 breaks tray icon left click in gnote and onboard in Mageia
Status: RESOLVED FIXED
Product: gtk+
Classification: Platform
Component: .General
3.13.x
Other Linux
: Normal major
: ---
Assigned To: gtk-bugs
gtk-bugs
: 731610 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2014-06-13 10:46 UTC by Barry Jackson
Modified: 2014-10-08 13:10 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Barry Jackson 2014-06-13 10:46:51 UTC 
Since update to 3.13.2 the left click tray icon action in gnote and onboard is lost.

Reverting to 3.12.x fixes this.

Related Mageia bug report is:
https://bugs.mageia.org/show_bug.cgi?id=13516

This has also been reported to gnote bug tracker:
https://bugzilla.gnome.org/show_bug.cgi?id=731610
Comment 1 Matthias Clasen 2014-06-14 00:21:09 UTC 
this has been fixed in master
Comment 2 Barry Jackson 2014-06-14 12:01:34 UTC 
(In reply to comment #1)
> this has been fixed in master

Please advise which commit fixes thus - thanks.
Comment 3 Carlos Garnacho 2014-06-14 12:15:01 UTC 
The commit was:

commit 3c0ebf65cf89140825a3f8c4c4e65170f8df4e8a
Author: Carlos Garnacho <carlosg@gnome.org>
Date:   Mon Jun 2 18:04:36 2014 +0200

    window: Only check for the event widget if clicked on the "content" region
    
    Every button press/release event reaching the the multipress gesture in GtkWindow
    and happening in the "title" region must be handled, regardless of the event widget.
    Children there wanting the event(s) for themselves are (and were always) expected
    to stop event propagation.
    
    So the only place to check for the event widget's "window-dragging" style property
    is the "content" region, which matches the pre-gestures behavior.
    
    This fixes some issues with sequences being mistakenly claimed (and events not
    propagated further) on situations it shouldn't.
Comment 4 Carlos Garnacho 2014-06-14 12:15:25 UTC 
*** Bug 731610 has been marked as a duplicate of this bug. ***