Enable commands API for platform apps.

chrome/browser/ui/gtk/browser_window_gtk.cc

Index: chrome/browser/ui/gtk/browser_window_gtk.cc
diff --git a/chrome/browser/ui/gtk/browser_window_gtk.cc b/chrome/browser/ui/gtk/browser_window_gtk.cc
index 8757517576c37e10ce3bb541ee811734a40dbc91..92a073c7063eb0b2818f02ea740617db257d2eec 100644
--- a/chrome/browser/ui/gtk/browser_window_gtk.cc
+++ b/chrome/browser/ui/gtk/browser_window_gtk.cc
@@ -1822,7 +1822,8 @@ void BrowserWindowGtk::InitWidgets() {
 
   // Add the keybinding registry, now that the window has been realized.

[Evan Stade, 2012/09/06 18:20:22]

well this makes more sense given the above. I don't know why
ExtensionKeybindingRegistryGtk would require the widget's GDK resources to be
realized, perhaps you should ask the original author.

   extension_keybinding_registry_.reset(
-      new ExtensionKeybindingRegistryGtk(browser_->profile(), window_));
+      new ExtensionKeybindingRegistryGtk(browser_->profile(), window_,
+          extensions::ExtensionKeybindingRegistry::ALL_EXTENSIONS));
 
   // We have to call this after the first window is created, but after that only
   // when the theme changes. This sets the icon that will be used for windows