Part of this is similar to bug 1551686. In addition the fix proposed in that bug (which won't help in this case, though) we have two options: 1) completely get rid of caching in location-service 2) When the client specifies maximumAge as 0, oxide should keep discarding any position update which carries an old timestamp
I think that implementing #2 is a good thing regardless of #1, so I'd suggest that at least this part would be fixed in Oxide. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1604446 Title: getcurrentPosition in oxide does not cause a wake up of the GPS To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1604446/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
