# Wrong geolocation in brave on linux **URL:** \ **Category:** Desktop Support\ **Tags:** linux, feature-request\ **Created:** [October 9, 2026, 11:22am UTC](https://community.brave.app/t/wrong-geolocation-in-brave-on-linux/659441 "2026-10-09T11:22:14Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![Bhajneet](https://avatars.discourse-cdn.com/v4/letter/b/7ea924/32.png) [@Bhajneet](https://community.brave.app/u/Bhajneet)\ **Post date:** [October 9, 2026, 11:22am UTC](https://community.brave.app/t/wrong-geolocation-in-brave-on-linux/659441/1 "2026-10-09T11:22:14Z")
Hi guys, I have been getting wrong geolocation on google maps on brave browser (~50 km off from my current location). I tested it on chrome, it works fine and the location is very accurate (probably few meters accuracy). I have tried all possible ways like clearing cache, checking if I have provided correct permissions and other suggestions on the forums but nothing helped. I searched around a bit and found this issue on github:- > > > \## Description > > On Linux, we should use the GeoClue LocationProvider when it'…s available instead of relying on the Mozilla LocationService. > > > This is part of https://github.com/brave/brave-browser/issues/8451 and it’s PR:- > > > Resolves https://github.com/brave/brave-browser/issues/29715 > > > > \## Submitter… Checklist: > > \- \[\] I confirm that no security/privacy review \[is needed\](https://github.com/brave/brave-browser/wiki/Security-reviews), or that I have \[requested\](https://github.com/brave/security/issues/new/choose) one > \- \[\] There is a \[ticket\](https://github.com/brave/brave-browser/issues) for my issue > \- \[\] Used Github \[auto-closing keywords\](https://docs.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue) in the PR description above > \- \[\] Wrote a good \[PR/commit description\](https://google.github.io/eng-practices/review/developer/cl-descriptions.html) > \- \[\] Squashed any review feedback or "fixup" commits before merge, so that history is a record of what happened in the repo, not your PR > \- \[\] Added appropriate labels (\`QA/Yes\` or \`QA/No\`; \`release-notes/include\` or \`release-notes/exclude\`; \`OS/...\`) to the associated issue > \- \[\] Checked the PR locally: > \* \`npm run test -- brave\_browser\_tests\`, \`npm run test -- brave\_unit\_tests\` \[wiki\](https://github.com/brave/brave-browser/wiki/Tests) > \* \`npm run lint\`, \`npm run presubmit\` \[wiki\](https://github.com/brave/brave-browser/wiki/Presubmit-checks), \`npm run gn\_check\`, \`npm run tslint\` > \- \[\] Ran \`git rebase master\` (if needed) > > \## Reviewer Checklist: > > \- \[\] A security review \[is not needed\](https://github.com/brave/brave-browser/wiki/Security-reviews), or a link to one is included in the PR description > \- \[\] New files have MPL-2.0 license header > \- \[\] Adequate test coverage exists to prevent regressions > \- \[\] Major classes, functions and non-trivial code blocks are well-commented > \- \[\] Changes in component dependencies are properly reflected in \`gn\` > \- \[\] Code follows the \[style guide\](https://chromium.googlesource.com/chromium/src/+/HEAD/styleguide/c++/c++.md) > \- \[\] Test plan is specified in PR before merging > > \## After-merge Checklist: > > \- \[\] The associated issue milestone is set to the smallest version that the > changes has landed on > \- \[\] All relevant documentation has been updated, for instance: > - \[\] https://github.com/brave/brave-browser/wiki/Deviations-from-Chromium-(features-we-disable-or-remove) > - \[\] https://github.com/brave/brave-browser/wiki/Proxy-redirected-URLs > - \[\] https://github.com/brave/brave-browser/wiki/Fingerprinting-Protections > - \[\] https://github.com/brave/brave-browser/wiki/Brave%E2%80%99s-Use-of-Referral-Codes > - \[\] https://github.com/brave/brave-browser/wiki/Custom-Headers > - \[\] https://github.com/brave/brave-browser/wiki/Web-Compatibility-Exceptions-in-Brave > - \[\] https://github.com/brave/brave-browser/wiki/QA-Guide > - \[\] https://github.com/brave/brave-browser/wiki/P3A > > \## Test Plan: Regarding this PR and issue:- Seems like (GeoClue)[[https://github.com/droidian/geoclue\\](https://github.com/droidian/geoclue%5C%5C)] uses (MLS)[[https://wiki.mozilla.org/CloudServices/Location\\](https://wiki.mozilla.org/CloudServices/Location%5C%5C)] but the service got discontinued in 2024. Are there any updates on this? Any plans on using any other service provider like BeaconDB or any other approach for the same? Thanks OS:- Ubuntu 24.04 Brave Version:- 1.96.61 ---
**Author:** ![Bhajneet](https://avatars.discourse-cdn.com/v4/letter/b/7ea924/32.png) [@Bhajneet](https://community.brave.app/u/Bhajneet)\ **Post date:** [October 15, 2026, 12:48pm UTC](https://community.brave.app/t/wrong-geolocation-in-brave-on-linux/659441/2 "2026-10-15T12:48:13Z")
Does anyone has any thoughts on this?