Bug 28139 - [i915] top bar is covered if compiz eanbled (on Mesa master branch)
Summary: [i915] top bar is covered if compiz eanbled (on Mesa master branch)
Status: VERIFIED FIXED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/DRI/i915 (show other bugs)
Version: unspecified
Hardware: All Linux (All)
: high major
Assignee: Eric Anholt
QA Contact:
URL:
Whiteboard:
Keywords: regression
Depends on:
Blocks:
 
Reported: 2010-05-17 00:41 UTC by fangxun
Modified: 2010-05-18 00:36 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
screenshot of window manager issue on pineview (259.91 KB, image/png)
2010-05-17 00:41 UTC, fangxun
Details

Description fangxun 2010-05-17 00:41:29 UTC
Created attachment 35702 [details]
screenshot of  window manager issue on pineview

System Environment:
--------------------------
Arch:           i386
Platform:        pineview
Libdrm:		(master)a3305b076c005e0d3bd55da0214e91413cf65b48
Mesa:		(master)df3590f570cb88eb9695b443208d7576b5867fd1
Xserver:		(master)345eb171264325d73ea2c50ba8c692cf589c2a9b
Xf86_video_intel: (master)2c69709d8afa6e9c0990efc463df0061536585e1
Cairo:		(master)7ef1bd22ded512f4fad3959796d7f40c4ddc5824
Kernel:		(for-linus)722154e4cacf015161efe60009ae9be23d492296

Bug detailed description:
-------------------------
The behaviour is window manager doesn't work after gnome-session startup under compiz(see attached screenshot). It fails on Mesa 7.8 branch and works on Mesa master branch. This issue happens on i915 platform. This is regression.

Reproduce steps:
----------------
1.xinit&
2.start gnome-session with compiz
Comment 1 Kristian Høgsberg 2010-05-17 06:22:35 UTC
This looks like the compiz decorator process isn't running, which is more likely a problem in the compiz startup scripts.  Can you see if 'gtk-window-decorator' is in the process list and if it isn't try to start it?
Comment 2 fangxun 2010-05-18 00:36:08 UTC
Works fine with latest code on Mesa master branch.


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.