(In reply to comment #5) > Using intel driver with uxa is enough to reproduce the bug.
Do you mean this happens immediately after X started, not requiring any other operations?
(In reply to comment #5)
> Using intel driver with uxa is enough to reproduce the bug.
Do you mean this happens immediately after X started, not requiring any other operations?