Bug 70167 - window can't be moved/resized/maximize/... and miss button on decoration
Summary: window can't be moved/resized/maximize/... and miss button on decoration
Alias: None
Product: cairo
Classification: Unclassified
Component: general (show other bugs)
Version: 1.12.14
Hardware: x86 (IA32) Linux (All)
: medium normal
Assignee: Chris Wilson
QA Contact: cairo-bugs mailing list
Depends on:
Reported: 2013-10-05 14:20 UTC by ihitabug
Modified: 2013-10-06 00:25 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

miss button(maximize/minximize/close) on decoration (38.57 KB, text/plain)
2013-10-05 14:20 UTC, ihitabug

Description ihitabug 2013-10-05 14:20:45 UTC
Created attachment 87161 [details]
miss button(maximize/minximize/close) on decoration

My env is : emerald + compiz + xfce4 

cairo:1.10.2-r3 works very well without any problems.

but after I installed cairo-1.12.14, bugs comes.

Just After I login xfce4, all work well too, but a few minutes later,   
all windows can't be moved/resized/maximize/... and miss button on decoration. So, I can't hit the maximize/minximize/close button, and Alt+Space has no effect too.  Alt+F4 works well. :D

Now, I uninstall cairo-1.12.14 and reinstall cairo:1.10.2 : bugs gone.
Comment 1 Uli Schlachter 2013-10-05 14:37:20 UTC
Cairo has nothing to do with input handling, so I don't see how it could break moving window, mouse clicks or keyboard combinations.

Also, according to "git grep", there is not a single call to cairo_surface_flush() in emerald and I found at least one place where this would be needed (src/main.c, draw_switcher_foreground(), right before a call to gdk_draw_drawable()). In other words, emerald was just lucky that it worked before.

So I would suggest you report this bug to compiz/emerald (and perhaps add a comment from here to your bug report for further reference).
Comment 2 ihitabug 2013-10-06 00:25:17 UTC

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.