Comment 48 for bug 774071

Since I upgraded to 12.04 recently I've started to notice this problem. Namely, indicator-datetime-service was still running at 100% CPU, and was quickly restarted (with just highter PID) after killing its process.

However, I was puzzled why at the same time some geoclue- related service also worked? I've found that indicator-datetime package indeed has a dependency upon: geoclue-yahoo | geoclue-provider. Then I have started to suspect that the real problem somehow comes from issue with geoclue - and I was right (in my case).

MY SOLUTION:
I have used aptitude and marked geoclue-yahoo to be uninstalled, then I solved the now missing dependency by marking geoclue-ubuntu-geoip to be installed. After installation geoclue provider was essentially switched. Now I have no more 100% CPU problem, but a usable system instead.

Probably I could have used any other package that is listed in geoclue-provider virtual package, and there are many.
Go figure:
* geoclue-ubuntu-geoip 0.0.2-0ubuntu6
* geoclue-gypsy 0.12.0-1ubuntu4
* geoclue-gsmloc 0.12.0-1ubuntu4
* geoclue-gpsd 0.12.0-1ubuntu4
* geoclue-yahoo 0.12.0-1ubuntu12
* geoclue-skyhook 0.12.0-1ubuntu12
* geoclue-plazes 0.12.0-1ubuntu12
* geoclue-manual 0.12.0-1ubuntu12
* geoclue-localnet 0.12.0-1ubuntu12
* geoclue-hostip 0.12.0-1ubuntu12
* geoclue-geonames 0.12.0-1ubuntu12

Hope this helps.