Bug 313224

Please elaborate, even in German if needed. Are you missing an option to activate GPS which used to be there? Does GPS work, but stop at some point? Or something else?

Hello Dennis

I have a Laptop HP 625 and the operating system is fedora 17
with a USB mouse Navilock NL -402U
 When I'm using marbel somtimes the the signal from the GPS disapear, than there are some numbers wich are not possible.
and in the chart is the signal for the position disapear too.
I dont now what cause this problem
May bee im not clever enough but marbel is the only chart program wich is running on my system,
becouse that I woud like to make t runs better


                 Regards from lower saxoni

                            hajo



________________________________
 Von: Dennis Nienhüser  <earthwings@gentoo.org>
An: hajoelbers@yahoo.de 
Gesendet: 13:54 Mittwoch, 16.Januar 2013
Betreff: [marble] [Bug 313224] the gps disapeart
 
https://bugs.kde.org/show_bug.cgi?id=313224

Dennis Nienhüser <earthwings@gentoo.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEEDSINFO
                 CC|                            |earthwings@gentoo.org
         Resolution|---                         |WAITINGFORINFO

--- Comment #1 from Dennis Nienhüser <earthwings@gentoo.org> ---
Please elaborate, even in German if needed. Are you missing an option to
activate GPS which used to be there? Does GPS work, but stop at some point? Or
something else?

Might be related to bug 312212.

I have a Navilock NL-302U here now to test with.

Git commit 17b732a713a53df8f9a7d45b4815ac3185084e78 by Dennis Nienhüser.
Committed on 23/01/2013 at 19:09.
Pushed by nienhueser into branch 'master'.

status is unreliable, check for nan explicitly.

Losing the GPS fix often results in gpsd reporting status as ok, but
reporting nan as position. These invalid coordinates result in broken
position data (nan as position, random painting on the map) and likely
also crashes.
Related: bug 312212

M  +1    -1    src/plugins/positionprovider/gpsd/GpsdPositionProviderPlugin.cpp

http://commits.kde.org/marble/17b732a713a53df8f9a7d45b4815ac3185084e78

Git commit 8ec4b0569d75f8b636e969156da6ea682b68c7a0 by Dennis Nienhüser.
Committed on 23/01/2013 at 19:09.
Pushed by nienhueser into branch 'KDE/4.10'.

status is unreliable, check for nan explicitly.

Losing the GPS fix often results in gpsd reporting status as ok, but
reporting nan as position. These invalid coordinates result in broken
position data (nan as position, random painting on the map) and likely
also crashes.
Related: bug 312212
FIXED-IN: KDE/4.10.0;Marble/1.5.0
(cherry picked from commit 17b732a713a53df8f9a7d45b4815ac3185084e78)

M  +1    -1    src/plugins/positionprovider/gpsd/GpsdPositionProviderPlugin.cpp

http://commits.kde.org/marble/8ec4b0569d75f8b636e969156da6ea682b68c7a0

Is the commit supposed to resolve this bug?

My understanding of the issue is the following:
(1) The GPS device loses the fix (not enough satellites in view)
(2) Marble does not notice it correctly and displays wrong information

I don't have control over (1). To fix (2), the commit addresses one situation I could verify where Marble operated on invalid data from gpsd. Chances are good that this fixes the display of wrong coordinates. GPS information will still disappear; in case the fix is lost this is the expected behavior.

Looking at the ever-changing gpsd API and the myriad of workarounds needed to deal with its cumbersome behavior I'm not really convinced however that we are catching all oddities yet.

Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!

Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!

Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!