Bug 13506

Summary: cinnamon title bars are unresponsive in gtk+3.0 3.13.2
Product: Mageia Reporter: Joseph Wang <joequant>
Component: RPM PackagesAssignee: Olav Vitters <olav>
Status: RESOLVED FIXED QA Contact:
Severity: critical    
Priority: Normal CC: zen25000
Version: Cauldron   
Target Milestone: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Source RPM: gtk CVE:
Status comment:

Description Joseph Wang 2014-06-10 07:40:49 CEST
Description of problem:

cinnamon title bars are unresponsive to left button in gtk+3.0 3.12.2.  
Left button does not trigger any activity including drag-move and menu
buttons in the title bar.

Other mouse buttons work, double click also works, left mouse works for events in
main window and in borders

Version-Release number of selected component (if applicable):

This is broken in cinnamon 2.2.13 an 2.2.9.
The broken gtk+3.0 version is 3.12.2.  3.12.1 works fine

How reproducible:

consistent

Steps to Reproduce:
1. upgrade gtk+3.0 to 3.12.2
2. run cinnamon
3. try to drag-move a window by the title bard
4. window is unresponsive

marking bug as critical as DE is unusuable.

Reproducible: 

Steps to Reproduce:
Joseph Wang 2014-06-10 13:09:43 CEST

Summary: cinnamon title bars are unresponsive in gtk+3.0 3.12.2 => cinnamon title bars are unresponsive in gtk+3.0 3.13.2

Comment 1 Joseph Wang 2014-06-10 13:10:36 CEST
The failing gtk+3 version is 3.13.2
Comment 2 Joseph Wang 2014-06-10 13:31:33 CEST
cross reference to cinnamon issue #3256

https://github.com/linuxmint/Cinnamon/issues/3256
Comment 3 Joseph Wang 2014-06-10 14:40:59 CEST
upstream reports problem has been fixed in next point release of GTK
Comment 4 Barry Jackson 2014-06-10 17:40:02 CEST
gtk+3.0-3.13.2-1.mga5.x86_64 also breaks gnote and onboard.
Reverting to previous version fixes both.
The issue in both applications is the inability to use the tray icon left click to open the backgrounded applications.

CC: (none) => zen25000

Manuel Hiebel 2014-06-12 00:46:09 CEST

Assignee: bugsquad => olav
Source RPM: cinnamon => gtk

Comment 5 Samuel Verschelde 2015-05-19 19:08:54 CEST
Presumably fixed. Reopen if needed.

Status: NEW => RESOLVED
Resolution: (none) => FIXED