RANDR V1.3 RRChangeOutputProperty() not working ?

[Graeme Gill]

Hi,
	A user is reporting to me that my code that attempts
to set a property in an output using XRANDR is failing on
their system. The code seems to work fine on other systems
running (probably different versions) of XRANDR.

I'm trying to figure out if it's:
	1) A bug in XRANDR V1.3
	2) A bug in the video card vendors driver
	3) A bug in my code that is not evident with XRANDR V1.2

The error is:

X Error of failed request:  BadValue (integer parameter out of range for operation)
   Major opcode of failed request:  157 (RANDR)
   Minor opcode of failed request:  13 ()
   Value in failed request:  0x89
   Serial number of failed request:  12
   Current serial number in output stream:  14

That results from a call to

	XRRChangeOutputProperty(mydisplay, output, icc_out_atom,
                  XA_CARDINAL, 8, PropModeReplace, atomv, psize);

This immediately follows a call to XChangeProperty to the root window
that sets the very same atom to the same value successfully.
Notable is that there appear to be no output properties listed
in the xrandr --verbose output for this system. ie. the EDID
property is missing.

The users system information is as follows:

   ATI Radeon HD4850 with their proprietary driver  (Catalyst 9.5
   - 2D driver version 8.61.2 / OpenGL version 2.1.8664).

   xrandr --version
   Server reports RandR version 1.3

   Xorg -version
   X.Org X Server 1.6.0
   Release Date: 2009-2-25
   X Protocol Version 11, Revision 0
   Build Operating System: Linux 2.6.24-15-server x86_64 Ubuntu
   Current Operating System: Linux fouriron 2.6.28-11-generic #42-Ubuntu SMP
   Fri Apr 17     01:58:03 UTC 2009 x86_64
   Build Date: 09 April 2009  02:11:54AM
   xorg-server 2:1.6.0-0ubuntu14 (buildd at crested.buildd)


   fglrxinfo
   display: :0.0  screen: 0
   OpenGL vendor string: ATI Technologies Inc.
   OpenGL renderer string: ATI Radeon HD 4800 Series
   OpenGL version string: 2.1.8664

  xrandr --verbose
   Screen 0: minimum 320 x 200, current 1280 x 1024, maximum 1280 x 1280
   DFP2 connected 1280x1024+0+0 (0x8d) normal (normal left inverted right x
   axis y axis)   376mm x 301mm
     Identifier: 0x89
     Timestamp:  891369
     Subpixel:   unknown
     Clones:
     CRTC:       0
     CRTCs:      0 1
     Panning:    0x0+0+0
     Tracking:   0x0+0+0
     Border:     0/0/0/0
     Transform:  1.000000 0.000000 0.000000
                 0.000000 1.000000 0.000000
                 0.000000 0.000000 1.000000
                filter:
   1280x1024 (0x8d)  108.0MHz +HSync +VSync *current +preferred
         h: width  1280 start 1328 end 1440 total 1688 skew    0 clock   64.0KHz
         v: height 1024 start 1025 end 1028 total 1066           clock   60.0Hz

   ... lots of modes here ...

   320x200 (0xa9)   12.6MHz +HSync +VSync DoubleScan
         h: width   320 start  336 end  384 total  400 skew    0 clock   31.5KHz
         v: height  200 start  457 end  459 total  524           clock   60.1Hz
DFP_EXTTMDS disconnected (normal left inverted right x axis y axis)
     Identifier: 0x8a
     Timestamp:  891369
     Subpixel:   unknown
     Clones:
     CRTCs:      0 1
     Transform:  1.000000 0.000000 0.000000
                 0.000000 1.000000 0.000000
                 0.000000 0.000000 1.000000
                filter:
CRT1 disconnected (normal left inverted right x axis y axis)
     Identifier: 0x8b
     Timestamp:  891369
     Subpixel:   unknown
     Clones:
     CRTCs:      0 1
     Transform:  1.000000 0.000000 0.000000
                 0.000000 1.000000 0.000000
                 0.000000 0.000000 1.000000
                filter:
CRT2 disconnected (normal left inverted right x axis y axis)
     Identifier: 0x8c
     Timestamp:  891369
     Subpixel:   unknown
     Clones:
     CRTCs:      0 1
     Transform:  1.000000 0.000000 0.000000
                 0.000000 1.000000 0.000000
                 0.000000 0.000000 1.000000
                filter:

Thanks for any hints.

	Graeme Gill.