indicator-datetime-session has 100% cpu use with geoclue-geonames

Bug #1044353 reported by Michael Vogt
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
indicator-datetime (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

I had geoclue-geonames installed and not geoclue-ubuntu-geoip. I don't know why, probably happend at a random point during the quantal dist-upgrades. This caused indicator datetime to spinn 100% cpu.

Revision history for this message
Jason Conti (jconti) wrote :

Same kind of issue as bug 919364 (and upstream https://bugs.freedesktop.org/show_bug.cgi?id=40882 ), a bunch of the geoclue backends error out, either because the service was discontinued (in yahoo's case), or they just haven't updated the backend for changes to the service. Unfortunately the upstream bugs are marked 'won't fix'.

Though it would be nice if indicator-datetime gave up after a number of errors instead of spinning on it.

Revision history for this message
Charles Kerr (charlesk) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue that you reported is one that should be reproducible with the live environment of the Desktop ISO of the development release - Trusty Tahr. It would help us greatly if you could test with it so we can work on getting it fixed in the next release of Ubuntu. You can find out more about the development release at http://www.ubuntu.com/testing/ . Thanks again and we appreciate your help.

Changed in indicator-datetime (Ubuntu):
status: New → Incomplete
Revision history for this message
Sebastien Bacher (seb128) wrote :

that are no recent report of that issue, likely resolved

Changed in indicator-datetime (Ubuntu):
importance: Undecided → Low
status: Incomplete → Invalid
status: Invalid → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.