gnome-shell uses idle monitor directly (as does unity-settings-daemon) if we revert the code in gnome-desktop we are going to have two independent idle monitors running, the one used via gnome-desktop plus the directly accessed one.
Alternatively if unity-settings-daemon exposes the d-bus interface then we only have one idle monitor that is accessed by everyone. This is more or less what I did previously in my displayconfig attempts, so I have copied the relevant bits (from mutter 3.10 with lots of renaming etc) and hooked it into u-s-d.
test package is at ppa:darkxst/libusd its mostly working but maybe crashing occassionally, trying to catch it in gdb so I can investigate
gnome-shell uses idle monitor directly (as does unity-settings- daemon) if we revert the code in gnome-desktop we are going to have two independent idle monitors running, the one used via gnome-desktop plus the directly accessed one.
Alternatively if unity-settings- daemon exposes the d-bus interface then we only have one idle monitor that is accessed by everyone. This is more or less what I did previously in my displayconfig attempts, so I have copied the relevant bits (from mutter 3.10 with lots of renaming etc) and hooked it into u-s-d.
test package is at ppa:darkxst/libusd its mostly working but maybe crashing occassionally, trying to catch it in gdb so I can investigate