diff --git a/dbus/bus.cc b/dbus/bus.cc
index 3d77d0f..b35718d 100644
--- a/dbus/bus.cc
+++ b/dbus/bus.cc
@@ -845,7 +845,7 @@
   base::ThreadRestrictions::AssertIOAllowed();
 
   if (dbus_task_runner_.get()) {
-    DCHECK(dbus_task_runner_->RunsTasksOnCurrentThread());
+    DCHECK(dbus_task_runner_->RunsTasksInCurrentSequence());
   } else {
     AssertOnOriginThread();
   }
diff --git a/dbus/exported_object.cc b/dbus/exported_object.cc
index 0024df6..2047f3f 100644
--- a/dbus/exported_object.cc
+++ b/dbus/exported_object.cc
@@ -94,7 +94,7 @@
   dbus_message_ref(signal_message);
 
   const base::TimeTicks start_time = base::TimeTicks::Now();
-  if (bus_->GetDBusTaskRunner()->RunsTasksOnCurrentThread()) {
+  if (bus_->GetDBusTaskRunner()->RunsTasksInCurrentSequence()) {
     // The Chrome OS power manager doesn't use a dedicated TaskRunner for
     // sending DBus messages.  Sending signals asynchronously can cause an
     // inversion in the message order if the power manager calls