Fix wrong constants are used for unstabbing D-Bus clients

Fix wrong constants are used for unstabbing D-Bus clients

BUG=401192
TEST=existing tests

Committed: https://crrev.com/d56f127a061c04a1820be448d61b9d985420d98e
Cr-Commit-Position: refs/heads/master@{#291879}

[satorux1, 2014-08-26 07:51:27]

satorux@chromium.org changed reviewers:
+ hashimoto@chromium.org, zelidrag@chromium.org

[satorux1, 2014-08-26 07:51:27]

Found this minor bug while looking into crbug.com/405976

[hashimoto, 2014-08-26 07:54:05]

lgtm

[satorux1, 2014-08-26 07:55:48]

I was told that this issue is fixed in
https://codereview.chromium.org/477663004/ too, but let me submit this in favor
of a small patch that fixes one thing.

[satorux1, 2014-08-26 07:56:01]

The CQ bit was checked by satorux@chromium.org

[commit-bot: I haz the power, 2014-08-26 07:58:02]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/satorux@chromium.org/497453003/1

[commit-bot: I haz the power, 2014-08-26 08:48:48]

FYI, CQ is re-trying this CL (attempt #1).
The failing builders are:
  linux_gpu_triggered_tests on tryserver.chromium.gpu
(http://build.chromium.org/p/tryserver.chromium.gpu/builders/linux_gpu_trigger...)
  linux_chromium_gn_rel on tryserver.chromium.linux
(http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)

[commit-bot: I haz the power, 2014-08-26 10:23:00]

Committed patchset #1 (1) as e1c9dccd196afe4bc6e82a372f78c781ddd256f8

[commit-bot: I haz the power, 2014-09-10 02:41:53]

Patchset 1 (id:??) landed as
https://crrev.com/d56f127a061c04a1820be448d61b9d985420d98e
Cr-Commit-Position: refs/heads/master@{#291879}