Comment 5 for bug 2011721
Revision history for this message
| Miriam España Acebal (mirespace) wrote | #5 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
7020100
(Get the code!)
Hi Cornelius,
Thank you for the test and for sharing the upstream's thread. I read at the end of the discussion that the reporter there fixed the issue by resetting the device with
ubxtool -p RESET
Can you test it?
On the other hand, gpsd package is in sync with Debian and Debian doesn't yet have the latest version 3.25 (Jan 10 2023).
If the resetting doesn't work for you, the next actions should be to have a reproducible set of steps to go through the issue (maybe a raw log from gpspipe? ) and the code commit(s) on upstream from version 3.25 that fix the issue as you commented before. Could you please provide those? All of this is needed to start an SRU procedure [1] as Paride commented before.
Furthermore, as also commented by Paride, this test is high dependant on hardware as a handicap to qualify for an SRU process, but the impact can be measured better starting with the steps of reproduce. Maybe we can hit it in other "certains devices" as you set on the bug's title ... or sadly not.
The bug will remain as "Incomplete" while we don't have that information. When you submit it, please mark the bug as "New" to let us know we can continue with additional actions due to this new info.
Thank you in advance!
[1] https:/