Run event executor on the ui thread to remove the need to explicitly XFlush() the XTest calls.

chrome/service/remoting/chromoting_host_manager.cc

Index: chrome/service/remoting/chromoting_host_manager.cc
diff --git a/chrome/service/remoting/chromoting_host_manager.cc b/chrome/service/remoting/chromoting_host_manager.cc
index 3b73a9f913e310272aed40128c87356fda721de0..9f8d7aeba7198305ce48fead565ba0f8b16c5c5b 100644
--- a/chrome/service/remoting/chromoting_host_manager.cc
+++ b/chrome/service/remoting/chromoting_host_manager.cc
@@ -20,7 +20,7 @@ ChromotingHostManager::ChromotingHostManager(Observer* observer)
 }
 
 void ChromotingHostManager::Initialize(
-    MessageLoop* main_message_loop,
+    MessageLoopForUI* main_message_loop,
     base::MessageLoopProxy* file_message_loop) {
   FilePath user_data_dir;
   PathService::Get(chrome::DIR_USER_DATA, &user_data_dir);
@@ -165,7 +165,8 @@ void ChromotingHostManager::Start() {
     return;
 
   // Start the chromoting context first.
-  chromoting_context_.reset(new remoting::ChromotingHostContext());
+  chromoting_context_.reset(
+      new remoting::ChromotingHostContext(main_message_loop_));
   chromoting_context_->Start();
 
   // Create a chromoting host object.