chromeos: use the correct proxy for Chromium signals

chromeos: use the correct proxy for Chromium signals

The power manager client receives signals from the session manager, 
which uses a different path for those signals. Create a proxy for
that object as well so we receive them, they were only receiving
them before because of a bug where the first object proxy would
get all signal messages.

BUG=chromium-os:27146
TEST=desktopui_ScreenLocker failed before, passes now

Change-Id: I4a8193d94e9a114d32aac79577b35a69043cbcf0


Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=124568

[satorux1, 2012-03-01 19:32:52]

Cannot we fix the login manager instead? Sending a signal from '/' doesn't sound
right to me.

[keybuk, 2012-03-01 19:37:30]

looking into that option now - this was a "quick fix" to pass the test again
(though it isn't holding our tree red)

[satorux1, 2012-03-01 19:40:02]

I'm ok with the "quick fix" if the other option turned out to be difficult.
please let me know if that's the case.

[keybuk, 2012-03-01 20:48:43]

ok, here's a proper fix that relies on the fix in
https://gerrit.chromium.org/gerrit/17171

[flackr, 2012-03-01 21:59:16]

lgtm

[commit-bot: I haz the power, 2012-03-01 22:07:33]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/keybuk@chromium.org/9566018/6001

[satorux1, 2012-03-01 22:17:34]

LGTM. Thanks.

[commit-bot: I haz the power, 2012-03-01 22:28:31]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/keybuk@chromium.org/9566018/6001

[commit-bot: I haz the power, 2012-03-02 02:02:44]

Change committed as 124568