I'm not sure that my earlier "simplest fix" position will work: if someone is physically located outside of their custom timezone list, there's no longer an easy way to click-to-set the current timezone from the geo timezone. This regression would certainly be reported & force us to revisit this issue anyway.
After hacking & rehacking this code for the last day, I think I've found a code approach that follows some of the ideas in Javier's second patch wrt removing the special case code, but preserves the older beahvior wrt geo/current location. It improves detection & removal of duplicate entries, and also picks up a fix for Bug #833325 :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/833337 Title: Current timezone duplicates with saved locations To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/833337/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
