Comment 2 for bug 2054325

Revision history for this message
Heinrich Schuchardt (xypron) wrote :

The error occurred with a monitor that was in a low power state.

Rebooting with the monitor powered on showed no issues.