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.
** Changed in: libxrandr (Ubuntu)
Status: Triaged => Invalid
** Changed in: gnome-desktop (Ubuntu)
Importance: Undecided => High
Assignee: (unassigned) => Alberto Milone (albertomilone)
Status: New => In Progress
** Changed in: gnome-power-manager (Ubuntu)
Importance: Undecided => High
Assignee: (unassigned) => Alberto Milone (albertomilone)
Status: New => In Progress
--
upgrade to 2:1.2.99.2-0ubuntu1 makes session utterly slow
https://bugs.launchpad.net/bugs/307306
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
