Ok, I think I know what’s going on: qtubuntu-sensors provides position updates with a horizontal accuracy set, but it’s set to something that’s not a number (NaN). According to QGeoPositionInfo’s documentation, if an attribute is not set, querying its value will return NaN. But in that specific case the attribute is set, so I think it’s reasonable to expect the value is a valid number. It looks like qtubuntu-sensors could be patched to ensure it’s not setting invalid values on attributes. oxide can also be patched to test the attributes and discard those that are not valid numbers.
Ok, I think I know what’s going on: qtubuntu-sensors provides position updates with a horizontal accuracy set, but it’s set to something that’s not a number (NaN). According to QGeoPositionInfo’s documentation, if an attribute is not set, querying its value will return NaN. But in that specific case the attribute is set, so I think it’s reasonable to expect the value is a valid number. It looks like qtubuntu-sensors could be patched to ensure it’s not setting invalid values on attributes. oxide can also be patched to test the attributes and discard those that are not valid numbers.