Comment 27 for bug 1053959

(In reply to comment #22)
> ok I'm using sna now, let's see. I'll try your patch later on the weekend.
>
> I have also another issue and wonder if it is related, since kernel 3.1 xrandr
> is taken a lot longer to do its thing (change screen arrangement and
> resolution) and it blocks even the mouse from working, stops the whole X for a
> full minute.
>
> Should I report a separate issue or can this be related.

Whilst we know of a reason why xrandr is slow in general (probing of disconnected outputs causes timeouts rather than a quick "not detected"), I was not aware that the situation had got any worse with 3.2