Comment 87 for bug 969359

I've encountered this bug, but only on one computer. I'm running an almost identical setup on two laptops, but I've never seen this happen on the first one (after using it for months). I've seen it happen twice on the second laptop in about a week.

What I've noticed:
- Num Lock LED is blinking rapidly, numpad acts accordingly (i.e. it's unusable)
- after some time nautilus reverts to the default icon set and GTK theme (can be fixed by restarting nautilus after the system has 'calmed down')
- I get this error message every time Num Lock is pressed:
(gnome-settings-daemon:14095): libappindicator-CRITICAL **: app_indicator_set_label: assertion `IS_APP_INDICATOR (self)' failed
(this error message is repeated thousands of times in .xsession-errors)
- apparently I can 'calm the system down' by unplugging the external keyboard and plugging it back in (I had to do this twice though before it actually worked)
- both times it happened after I woke the computer (the screen was blanked). This could be completely unrelated though, because most of the time awaking it works just fine.

I'm using Linux Mint 13 (based on Ubuntu 12.04) 64-bit, and GNOME Fallback without effects.

First laptop (bug does not occur on this one):
- Dell Studio 1749, Intel i5 540M, ATI Radeon HD 5650 (using open source driver)
- does not have a Num Lock LED, I'm using indicator-keylock instead (which is also behaving a bit weird actually)
- no external keyboard

Second laptop:
- Dell Inspiron 1720, Intel Core2 Duo T9300, nVidia GeForce 8600 (using proprietary driver)
- uses an external keyboard

I will try renaming keyboard.gnome-settings-plugin.