Karl, maybe it's this:
(gnome-settings-daemon:2057):
libappindicator-CRITICAL **: app_indicator_set_label: assertion
`IS_APP_INDICATOR (self)' failed

2010/10/5, Karl Lattimer <email address hidden>:
> I just had the bug appear without actively changing layout, when I
> changed windows and the layout should have remained the same.
>
> I'm really not sure as to the cause of it, but I'll keep digging...
>
> --
> Keyboard layout automatically changes + 100% CPU usage [updated]
> https://bugs.launchpad.net/bugs/625793
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Gnome Settings Daemon: Invalid
> Status in Application Indicators: In Progress
> Status in “gnome-settings-daemon” package in Ubuntu: Confirmed
>
> Bug description:
> == General description ==
>
> On some Ubuntu installs with two or more keyboard layouts (e.g. Russian and
> US English), after some time the keyboard layouts start switching in an
> endless loop and gnome-settings-daemon starts using more and more CPU until
> it reaches 100%.
>
> == Known information ==
>
> 1) Some people here confirm that this happens with non-GTK (Java or Qt)
> windows more often then with native GTK. (probably, might be a coincidence)
> 2) Possible fixes are killing and restarting gnome-settings-daemon or
> disabling the "Separate layout for each window" option in keyboard
> preferences window.
> 3) The second fix, however didn't work for most people, though it might
> really reduce the probability of the bug appearing.
> 4) The bug happens both on upgrade installs and clean installs of Ubuntu,
> confirmed with RC and Alpha 3.
> 5) The bug is specific to Ubuntu, not existing in Arch Linux and
> AgiliaLinux.
> 6) There are users who experience this problem with Russian, Slovakian,
> Macedonian, Hebrew, Georgian layots. Having such a problem in final release
> will make keyboard use very problematic for users from these countries, so
> Ubuntu can lose many users.
> 7) The bug is still not fixed in GNOME 2.32, which again proves that it's an
> Ubuntu-specific issue.
> 8) For some users, the bug disappears after 2 to 15 minutes of use.
> 9) Confirmed for almost any key set for switching layouts (Shift+Alt,
> Shift+Ctrl, CapsLock, Alt, Ctrl)
> 10) Confirmed for both Latin and non-Latin layouts.
> 11) Permanent fix is to disable g-s-d keyboard plugin in gconf, not fully
> confirmed though.
> 12) Confirmed as a g-s-d issue, both with and without indicators.
>
> == Debug ==
>
> APPORT DATA here:
> https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/633167
> and here:
> https://bugs.launchpad.net/ubuntu/+source/indicator-application/+bug/633346
> MORE LOGS:
> https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/636619
> GDB DATA:
> https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/629444
> XSESSIONERRORS:
> https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/630712
> RANDOM LOGS:
> https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/64082
>
> XEV OUTPUT: infinite loop of
> PropertyNotify event, serial 30, synthetic NO, window 0x6000001, atom 0x174
> (XKLAVIER_STATE), time 11886812, state PropertyNewValue
>
> [NEW] GSD output:
> (gnome-settings-daemon:2057):
> libappindicator-CRITICAL **: app_indicator_set_label: assertion
> `IS_APP_INDICATOR (self)' failed
>
> P.S. Do. Not. Touch. This. Please. There's more info here, which can make
> the devs remove the Incomplete status. Не трогайте это, пожалуйста. Здесь
> намного больше информации, чем во всех предыдущих описаниях, может снимут
> Incomplete.
>
> TO DEVELOPERS: Please, comment on what logs and other info you need to get
> this problem solved.
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/gnome-settings-daemon/+bug/625793/+subscribe
>