[argyllcms] dispcal 1.1.0 RC gets stuck starting up

dispcal gets stuck starting up.  This happens with and without a
calibration device attached.  Version 1.0.4 works fine.  This started
happening when I upgraded to F12 beta.  This even happens just running
dispcal -h or running dispwin -c.

ARGYLL_IGNORE_XRANDR1_2 works around the problem.

xtrace says (apparently in an infinite loop):

  000:<:18cc: 28: RANDR-Request(147,15): GetOutputProperty
output=0x00000041 property=0x131("EDID_DATA") type=0x13("INTEGER")
offset=0x00000000 length=0x07ffffff delete=false(0x00)
pending=false(0x00)
000:>:18cc:32: Reply to GetOutputProperty: type=None(0x0) bytes-after=0x00000000
000:<:18cd: 28: RANDR-Request(147,15): GetOutputProperty
output=0x00000041 property=0x131("EDID_DATA") type=0x13("INTEGER")
offset=0x00000000 length=0x07ffffff delete=false(0x00)
pending=false(0x00)
000:>:18cd:32: Reply to GetOutputProperty: type=None(0x0) bytes-after=0x00000000
000:<:18ce: 28: RANDR-Request(147,15): GetOutputProperty
output=0x00000041 property=0x131("EDID_DATA") type=0x13("INTEGER")
offset=0x00000000 length=0x07ffffff delete=false(0x00)
pending=false(0x00)
000:>:18ce:32: Reply to GetOutputProperty: type=None(0x0) bytes-after=0x00000000
000:<:18cf: 28: RANDR-Request(147,15): GetOutputProperty
output=0x00000041 property=0x131("EDID_DATA") type=0x13("INTEGER")
offset=0x00000000 length=0x07ffffff delete=false(0x00)
pending=false(0x00)
000:>:18cf:32: Reply to GetOutputProperty: type=None(0x0) bytes-after=0x00000000
000:<:18d0: 28: RANDR-Request(147,15): GetOutputProperty
output=0x00000041 property=0x131("EDID_DATA") type=0x13("INTEGER")
offset=0x00000000 length=0x07ffffff delete=false(0x00)
pending=false(0x00)
000:>:18d0:32: Reply to GetOutputProperty: type=None(0x0) bytes-after=0x00000000
000:<:18d1: 28: RANDR-Request(147,15): GetOutputProperty
output=0x00000041 property=0x131("EDID_DATA") type=0x13("INTEGER")
offset=0x00000000 length=0x07ffffff delete=false(0x00)
pending=false(0x00)
000:>:18d1:32: Reply to GetOutputProperty: type=None(0x0) bytes-after=0x00000000

Other related posts: