I don't at the moment use Linux but there's quite a number of search
results on "linux time jump" that seem to indicate this might perhaps be
something to do with the way Linux uses time?
Maybe you need to write some kind of script to restart WSJT-X at regular
intervals?
Alan G0TLK
On 24/05/2025 22:26, Paul Simon via wsjt-devel wrote:
On 5/23/2025 9:16 AM, Josh Rovero via wsjt-devel wrote:
I see similar behavior about every 72 hours or so on Fedora Core 41,
64-bit.
Restarting wsjtx seems to cure it for another 72 hours ..
Josh Rovero
KK1D
------------------------------------------
I have been running wspr 24/7 using the linux version of wsjtx.
After
about two days, dt seems to increase by 6 seconds, in a single jump,
not
gradually. This does not happen on Windows.
1. The same happens on two different machines running Ubuntu and
Mageia,v 2.61 and v 2.7.0-rc8.
2. Computer clock is correct: checked vs. time.is <http://time.is>,
NIST controlled
clock, etc. Time measured manually is within one second.
3. Closing and reopening wsjtx immediately results in correct dt.
4. Running wsjtx under WINE gives same result.
5. Waterfall timing is correct and can see the six second early
start of
sequence.
6. Only happens if transmit box is ticked.
Could someone please confirm and/or suggest possible solutions?
Paul W6EXT
---------------
Well, good luck Josh. No response from anyone else. No developers
either. Some of the links on the SourceForge pages are dead. One of
the SourceForge pages states that WSPR is of historical interest.
"So Long, and Thanks for All the Fish"
Paul, w6...@arrl.net
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
