Bug 22536 - glxgears_pixmap shows black screen and seeing error message from X
Summary: glxgears_pixmap shows black screen and seeing error message from X
Status: CLOSED FIXED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Demos (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Linux (All)
: medium normal
Assignee: mesa-dev
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-06-29 10:43 UTC by Yu Dai
Modified: 2010-03-23 08:56 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
patch for glxgears_pixmap black window issue by using consistent XID drawable in DRI2 interface (1.89 KB, text/plain)
2009-06-29 10:43 UTC, Yu Dai
Details

Description Yu Dai 2009-06-29 10:43:02 UTC
Created attachment 27224 [details]
patch for glxgears_pixmap black window issue by using consistent XID drawable in DRI2 interface

We found glxgears_pixmap does not work on DRI2, gallium-mesa-7.4 and xserver 1.6.2. We are seeing error message from X:
----------------------------------------------------------------------------
X Error of failed request:  BadDrawable (invalid Pixmap or Window parameter)
  Major opcode of failed request:  135 (DRI2)
  Minor opcode of failed request:  6 (DRI2CopyRegion)
  Resource id in failed request:  0x2a00005
  Serial number of failed request:  38
  Current serial number in output stream:  38

Program exited with code 01.
----------------------------------------------------------------------------

We noticed that there are some inconsistency about drawable id to use in DRI2 interfaces. For example, in dri2CreateDrawable, XID xDrawable is used to send request to X to create drawable. However, in dri2DestroyDrawable, GLXDrawable drawable is used to tell X to destroy it. And, we believe that the wrong id used in dri2CopySubBuffer causes error message above. Because XID xDrawable is the one used to create a X drawable, we are pretty sure anywhere else in DRI2 interfaces should use this id.

Attachment is a patch for this, which resolve this issue.
Comment 1 Kristian Høgsberg 2010-03-22 19:16:40 UTC
The patch has been applied, can we close this bug?


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.