https://bugs.freedesktop.org/show_bug.cgi?id=46711 --- Comment #9 from Alex Deucher <agd5f@xxxxxxxxx> 2012-04-16 09:07:59 PDT --- (In reply to comment #8) > > Brief look doesn't show me any locks there, I'll dig in. The locking (or lack there of) would be on the kernel side. > > If relevant, we have the same symptoms with and without a "desktop > environment". Meaning same thing happens with pure X, and also with our > software running which does explicit output probing when nothing is connected. > > Problem is (seems to me) xrandr reports monitor connected when in that state. > > Also if relevant we do get two RandR events (RRScreenChangeNotify and > RRNotify_OutputChange) when re-plugging the monitor. > > Unless there is no intersection between RandR and DPMS... ? We don't change the dpms state in the hotplug handler we just use the dpms code paths to properly tear down and bring up the display when an enabled monitor is connected or disconnected. Unfortunately it's been a while since I looked at this so I don't remember how events are handled once X gets them. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
