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.
Search found 337 matches
- 18 Jun 2024, 12:40
- Forum: Error reports
- Topic: Dropbox
- Replies: 4
- Views: 3695
- 18 Jun 2024, 12:38
- Forum: Error reports
- Topic: Hamlib startup failing
- Replies: 4
- Views: 4263
Re: Hamlib startup failing
This seems to be fixed in 2.32.1.5 but is not mentioned in the change log.
- 28 May 2024, 13:45
- Forum: Error reports
- Topic: New log entry colored orange instead of cyan
- Replies: 1
- Views: 2429
Re: New log entry colored orange instead of cyan
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 ...
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 ...
- 28 May 2024, 13:21
- Forum: Error reports
- Topic: New log entry colored orange instead of cyan
- Replies: 1
- Views: 2429
New log entry colored orange instead of cyan
#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.
#2 Observe the Stats showing the new entry is colored orange.
#3 Restart Log4OM and it colors it cyan.
Minor odd behavior.
- 28 May 2024, 13:18
- Forum: Error reports
- Topic: Hamlib startup failing
- Replies: 4
- Views: 4263
Re: Hamlib startup failing
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
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
- 30 Apr 2024, 11:12
- Forum: Error reports
- Topic: Hamlib startup failing
- Replies: 4
- Views: 4263
Re: Hamlib startup failing
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.
There needs to a be a longer retry.
- 24 Apr 2024, 11:26
- Forum: Error reports
- Topic: Cluster alert band not confirmed is broken
- Replies: 24
- Views: 18467
Re: Cluster alert band not confirmed is broken
Is anybody home here? I've not heard if you have been able to duplicate this problem.
- 12 Apr 2024, 16:11
- Forum: Error reports
- Topic: Hamlib startup failing
- Replies: 4
- Views: 4263
Hamlib startup failing
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 ...
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 ...
- 11 Apr 2024, 13:59
- Forum: Error reports
- Topic: Cluster alert band not confirmed is broken
- Replies: 24
- Views: 18467
Re: Cluster alert band not confirmed is broken
Have you been able to duplicate this?
We are missing DXCC alerts (new on band) due to this problem.
We are missing DXCC alerts (new on band) due to this problem.
- 19 Mar 2024, 21:48
- Forum: Feature suggestions
- Topic: User custom config cluster filters
- Replies: 0
- Views: 2612
User custom config cluster filters
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.
Right now they common to all configs.
I use a system where the other user wants CW spots and I do not.