Bug 25236

Summary:	gnome maps major position error
Product:	Mageia	Reporter:	Tony Blackwell <tablackwell>
Component:	RPM Packages	Assignee:	GNOME maintainers <gnome>
Status:	RESOLVED OLD	QA Contact:
Severity:	normal
Priority:	Normal	CC:	pterjan
Version:	7
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:	gnome maps	CVE:
Status comment:
Attachments:	screenshot gnome maps screenshot opencpn correct position

Description Tony Blackwell 2019-08-06 22:16:51 CEST

gnome maps gives erroneous position.  True position at this instant is  correct in opencpn, 27 33.170 S 152 55.972 E   Gnome maps gives current location as -27.45530 153.18290 with 20km accuracy.  Clearly gnome is "not in the ball park" as true location is well outside even its 20km circle.

I'll attach screen pics if possible.

hardware: ASUS X207N laptop, Haicom HI-206-USB GPS dongle in NMEA format data output mode.

Comment 1 Tony Blackwell 2019-08-06 22:19:16 CEST

Created attachment 11244 [details]
screenshot gnome maps

See reported position and lack of accuracy

Comment 2 Tony Blackwell 2019-08-06 22:24:59 CEST

Created attachment 11245 [details]
screenshot opencpn correct position

The ship icon is in true position, correctly annotated in dashboard upper left of pic.  While opencpn gives no land details, this location is "Jamboree Heights"  which can be seen on the gnome-map print to left of and slightly below the gnome-map confidence circle.

Gnome-map's position error is around 30km, but its quie determined in this, on repeated launching of the app.

Comment 3 Lewis Smith 2019-08-07 21:48:24 CEST

Thank you Tony for the screenshots.
I tried both packages, but could not make them show the necessary info (quickly).
BTAIM Assigning to the Gnome team. No duplicate bug found.

Assignee: bugsquad => gnome

Comment 4 Pascal Terjan 2019-08-07 21:59:23 CEST

Such accuracy sounds like geoclue is not using your GPS (or even visible wifis) but only your IP address

CC: (none) => pterjan

Comment 5 Tony Blackwell 2021-05-12 11:10:48 CEST

This has been lurking here a while.  No different, but perhaps an upstream problem.  As the OP, I'll close it.
Tony

Resolution: (none) => OLD
Status: NEW => RESOLVED