<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - No mouse cursor (invisible) with dual monitors and DVI/VGA "Y" cable, no display on DVI" href="https://bugs.freedesktop.org/show_bug.cgi?id=94259#c28">Comment # 28</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - No mouse cursor (invisible) with dual monitors and DVI/VGA "Y" cable, no display on DVI" href="https://bugs.freedesktop.org/show_bug.cgi?id=94259">bug 94259</a> from <a class="email" href="mailto:kevinbrace@gmx.com" title="Kevin Brace <kevinbrace@gmx.com>"> Kevin Brace</a> <pre>Hi Eric, Before the release of OpenChrome Version 0.4.0, I figured out the cause of the functional regression you have reported. I believe this was related to the detection of a LVDS FP (Flat Panel) primarily meant for laptops, and I found ways to automatically detect FPs without interfering with the detection of other display devices like VGA. What I believe happened was that when I moved to all automatic detection of display devices, all devices were running through the code that will detect a FP, and for your particular system, this was causing problems since the previous developers were doing some odd things to "guess" the native screen resolution of the FP. I removed that portion of the code, and found a good way to detect the native screen resolution of the FP before the new release. I will say that you should give the current master branch code a try (Version 0.4.107), and see how it performs.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>