Use g_spawn_async instead of _sync.

Use g_spawn_async instead of _sync to avoid blocking UI-thread.

This change does the following as well:

* Deprecate getter APIs that are currently unused.
* Stop calling 'setxkbmap -print'. Instead, just remember the last layout and modifier mappings set.

BUG=chromium-os:13029
TEST=1) manually checked 2) ran the unittest

Change-Id: If141b273c5ed455b34ae41c75f9f0e1729163e69

Committed: http://chrome-svn/viewvc/chromeos?view=rev&revision=7688b12

[Yusuke Sato, 2011-03-14 11:08:47]

As you know, changing g_spawn_sync to _async might not be perfect due to
http://crosbug.com/12875,  but I believe _async is much better than _sync (and
probably it can fix the issue 13209.)

[Daniel Erat, 2011-03-14 16:10:12]

nit: typo in the description; 13209 should be 13029

On Mon, Mar 14, 2011 at 04:08,  <yusukes@chromium.org> wrote:
> As you know, changing g_spawn_sync to _async might not be perfect due to
> http://crosbug.com/12875,  but I believe _async is much better than _sync
> (and
> probably it can fix the issue 13209.)
>
>
>
> http://codereview.chromium.org/6691007/
>

[Yusuke Sato, 2011-03-14 16:14:06]

On 2011/03/14 16:10:12, Daniel Erat wrote:
> nit: typo in the description; 13209 should be 13029

Thanks. Fixed.

[satorux1, 2011-03-14 20:52:33]

LGTM, but the change does much more than what the description says. Please
update the description before checking this in.

http://codereview.chromium.org/6691007/diff/1004/chromeos_keyboard.cc
File chromeos_keyboard.cc (right):

http://codereview.chromium.org/6691007/diff/1004/chromeos_keyboard.cc#newcode25
chromeos_keyboard.cc:25: // TODO(yusukes): Use libxkbfile.so instead of the
command.
Please file a bug and add a link to it.

[Yusuke Sato, 2011-03-15 03:09:41]

http://codereview.chromium.org/6691007/diff/1004/chromeos_keyboard.cc
File chromeos_keyboard.cc (right):

http://codereview.chromium.org/6691007/diff/1004/chromeos_keyboard.cc#newcode25
chromeos_keyboard.cc:25: // TODO(yusukes): Use libxkbfile.so instead of the
command.
On 2011/03/14 20:52:33, satorux1 wrote:
> Please file a bug and add a link to it.

Done.