Ubuntu
libxrandr package

  1. Bug #307306
  2. Comment #23

Comment 23 for bug 307306

Revision history for this message
Alberto Milone (albertomilone) wrote :

As Peter Clifton pointed out, there's a new and less expensive call in the RandR 1.3 API (XRRGetScreenResourcesCurrent), credits to him for telling me about it. This function doesn't make RandR reprobe hardware and it's definitely the right function to use when listening for events (at least in this case).

As I found out that gnome-desktop wasn't the only one which was causing high CPU usage, I have filed separate bug reports against gnome-desktop and gnome-power-manager and provided upstream with patches which fix the problem. Now, if RandR 1.3 is availble, XRRGetScreenResourcesCurrent is used instead of XRRGetScreenResources and the problem is gone.

I think we can unsubscribe the both the Xserver and libxrandr since they seem to do the right thing.