Bryce, While I appreciate you adding the stored EDID data to the wishlist, and your confirmation that corrupted EDID data is a factor here, I think the essential point of the bug I was driving at may have gotten lost in the shuffle. The main problem I'm having here is the behavior of xrandr, which is reporting a disconnected display even though the display is connected and active. The new title you gave this bug no longer correctly reflects the central point.
It does not seem reasonable for the disconnected/connected status to be "connected" only in cases where a monitor is both connected *and* EDID data was captured correctly. Surely if the display is in use, it must be connected for practical purposes. Thank you for your courteous reply. I'd appreciate some clarification from you on whether this behavior in xrandr is intended at present and whether it might be changed. If the "disconnected" message is truly considered correct, I can try to take the issue up with the maintainer of xscreensaver. This is the second time we've crossed paths -- the last time was about my monitor's resolution settings not being detected properly, which was no doubt due to the KVM's interference (see bug 180601 -- actually *that* bug probably deserves this bug's new title). Thanks for your continued dedication to improving Ubuntu. ** Summary changed: - Omniport KVM corrupts monitor EDID for Sony Multiscan E200 + xrandr reports display as 'disconnected' when EDID data not captured successfully, even if display in question is active and in use -- xrandr reports display as 'disconnected' when EDID data not captured successfully, even if display in question is active and in use https://bugs.launchpad.net/bugs/313220 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
