We definitely added uninhibit calls at the job's finish, so either we're leaking jobs or for whatever reason the Uninhibit call isn't working.
Does valgrind complain we're leaking *Job structs? Can you add a break in nautilus-file-operations.c:finalize_common and make sure we're actually calling it at the end of jobs (and thusly nautilus_uninhibit_power_manager?) If you run nautilus in a terminal does it complain that it can't uninhibit the power manager? Does dbus-monitor --session show the outgoing "Uninhibit" call?
We definitely added uninhibit calls at the job's finish, so either we're leaking jobs or for whatever reason the Uninhibit call isn't working.
Does valgrind complain we're leaking *Job structs? Can you add a break in nautilus- file-operations .c:finalize_ common and make sure we're actually calling it at the end of jobs (and thusly nautilus_ uninhibit_ power_manager? ) If you run nautilus in a terminal does it complain that it can't uninhibit the power manager? Does dbus-monitor --session show the outgoing "Uninhibit" call?