Kiosk mode: SetFirstLoginPrefs() should be called for kiosk sessions.

chrome/browser/chromeos/login/users/chrome_user_manager_impl.cc

Index: chrome/browser/chromeos/login/users/chrome_user_manager_impl.cc
diff --git a/chrome/browser/chromeos/login/users/chrome_user_manager_impl.cc b/chrome/browser/chromeos/login/users/chrome_user_manager_impl.cc
index f543561a56d963ab000070d703e99249aaed96e1..1935cb62f837243655255a0d9a2572250fe82b27 100644
--- a/chrome/browser/chromeos/login/users/chrome_user_manager_impl.cc
+++ b/chrome/browser/chromeos/login/users/chrome_user_manager_impl.cc
@@ -721,6 +721,7 @@ void ChromeUserManagerImpl::KioskAppLoggedIn(const std::string& app_id) {
       user_manager::User::USER_IMAGE_INVALID,
       false);
 
+  SetIsCurrentUserNew(true);

[xiyuan, 2015/02/25 20:18:43]

KioskAppLoggedIn is called on every kiosk app launch. App is like regular user
and it's cryptohome/profile is persisted. So it is not always a "new" user.
Would lying here have side effects?

We had problems with input before. At that time, the bug is fixed
 by explicitly calling InitChromeOSPreferences() on kiosk launch code path in
AppLaunchController::OnProfileLoaded [1]. Could we do something similar and call
SetFirstLoginPrefs with proper args there?

[1]:
https://code.google.com/p/chromium/codesearch#chromium/src/chrome/browser/chr...

[Alexander Alekseev, 2015/02/25 20:48:47]

We only need to call SetFirstLoginPrefs for the first Kiosk session.
Is there way to catch first Kiosk session?

[xiyuan, 2015/02/25 21:20:50]

Think we can use Profile::IsNewProfile to check whether this is the first kiosk
run.

   WallpaperManager::Get()->SetUserWallpaperNow(app_id);
 
   // TODO(bartfab): Add KioskAppUsers to the users_ list and keep metadata like