Comment 51 for bug 127008

I did a little digging. xresprobe calls ddcprobe.sh. If that doesn't give it a valid resolution, it calls xprobe.sh, too. Indeed, on my system, ddcprobe (not ddcprobe.sh) says "edidfail", so ddcprobe.sh just returns with no output, and hence xresprobe calls xprobe.sh and smashes my screen.

At the sprint in July we discovered that the new xrandr magic had hugely better effect if I was using the -intel driver. I'd be sad to see it go, but I'd also like to get this bug fixed :)