Log4OM

w9mdb

That's a Dropbox message which I think you can click "Ignore" or such on.
It's part of the sqlite journaling system that causes that.

w9mdb

This seems to be fixed in 2.32.1.5 but is not mentioned in the change log.

w9mdb

2nd problem similar to this one...
I put in a test QSO for FT4GL to test this color thing....then after I deleted it the Stats page still showed the band as worked.
This could be related to the other outstanding problem of not recognizing "Confirmed on band".
That this bug https://forum.log4om.com ...

w9mdb

#1 Add a new log entry for a new DXCC/Band.
#2 Observe the Stats showing the new entry is colored orange.
#3 Restart Log4OM and it colors it cyan.

Minor odd behavior.

w9mdb

To restate this -- it seems Log4OM is only waiting 10ms for rigctld to offer the TCP port.
That is too short as things can take longer before the tcp port is available.
I'd recommend a retry for 2 seconds to cover the future.

Mike W9MDB

w9mdb

rigctld is still running -- but it is Log4OM expecting an immediate (i.e. 10ms) response that is the problem.
There needs to a be a longer retry.

w9mdb

Is anybody home here? I've not heard if you have been able to duplicate this problem.

w9mdb

Sometimes...not all the time...hamlib fails to start up.
Was able to catch this with CAT debug turning on quickly startup -- since we don't save the debug settings across restarts -- could we get these saved please?

Here's the debug showing Log4OM trying to connect to rigctl with only about a 10ms ...

w9mdb

Have you been able to duplicate this?
We are missing DXCC alerts (new on band) due to this problem.

w9mdb

Would like to request that the cluster filters be stored by configuration.
Right now they common to all configs.
I use a system where the other user wants CW spots and I do not.

Search found 337 matches

Re: Dropbox

Re: Hamlib startup failing

Re: New log entry colored orange instead of cyan

New log entry colored orange instead of cyan

Re: Hamlib startup failing

Re: Hamlib startup failing

Re: Cluster alert band not confirmed is broken

Hamlib startup failing

Re: Cluster alert band not confirmed is broken

User custom config cluster filters