http://bugs.freedesktop.org/show_bug.cgi?id=19854
Jaime Velasco Juan <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #7 from Jaime Velasco Juan <[email protected]> 2009-02-12 09:59:21 PST --- (In reply to comment #6) > So, I've pushed the crash fix, but not the state resetting thing. After > testing it, it seems xrandr gets very upset (even just running xrandr > --verbose) with CRTCs disappearing (although this is probably valid behaviour) > and dies with a fatal error of "cannot find crtc 0x..", so I'll stick with the > crap lingering CRTC behaviour, rather than break xrandr whenever someone > disconnects an output. > > As for bailing out at modeset time, yes, this might be possible, but it relies > on the xserver failing gracefully, and the user app coping with a failure for > which it can determine no good reason, which I think is a higher standard to > expect than getting the application to query what display is connected before > it sets out on its modesetting journey. > > Happy for this bug to be resolved as fixed? > Yes, thank you. If it turns out this is not really correct it can be reopened again. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ Nouveau mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/nouveau
