GA,
after upgrade Mysql under Mint 20.2 y have this this error:
2021-12-11T11:44:01.834659Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.27-0ubuntu0.20.04.1) starting as process 8354
2021-12-11T11:44:01.896763Z 0 [Warning] [MY-013242] [Server] --character-set-server: 'utf8' is currently an alias for the character set UTF8MB3, but will be an alias for UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.

Hi!
After installation CQRLOG on Ubuntu 20.04 ARM64 on cqrlog start i got error

(cqrlog:2933): GLib-GObject-CRITICAL **: 19:36:01.080: g_object_unref: assertion 'G_IS_OBJECT (object)' failed

(cqrlog:2933): GLib-CRITICAL **: 19:36:01.080: g_log_remove_handler: assertion 'handler_id > 0' failed
[FORMS.PP] ExceptionOccurred
Sender=EInvalidOp
Exception=Invalid floating point operation
Stack trace:
$0000000000000030
[FORMS.PP] ExceptionOccurred

Any ideas why this error appear?

Today when I went to start CQRLOG on my Archive machine, I got an error about starting MYSQL. Looking into databases/mysql.err, I found that the error was probably caused by a failure to shutdown correctly the previous session.

I had this problem before, and the only common factor was what I was doing at the end of the last session: deleting several old log databases. I think I dropped 4 or 5 old test cases, then canceled the selection window and exited.

Hello CQRLOG,

I'd like to announce an interesting issue using DXCluster and Callsign alert.

I'am monitoring some callsigns, e.g. DL1AB.
Today suddenly I got a spot from DL1ABC!

It seems the last letter(s) of the callsign is not checked?

73 de Martin, DL1MTG

Linux Mint 20.3 here. Been Linux Mint user (after Ubuntu) for 10 yrs+. Never used MySQL that I am aware? though it's updated automatically and is current. (Can dual boot into Win7-10 in five machines I tend to, but NEVER DO MS ANYMORE.)

However, the first, most basic simple thing that yall take for granted has me stumped. namely what to do at the MySQL server "Database Connection" screen when I open CQRLog for the first time. The default server name of 127.0.0.1, and port 64000 are pre-assigned. Is this OK to get going? Suggestions or recommendations?

Hi,

if you move a longer bandmap with the scrollbar to the beginning of the band or an upper Band segment, the bandmap stays in this position.

If a call is now selected, the bandmap jumps back to the end of the band.

From my point of view it would be better if the bandmap would remain in the once selected position (band start or band section), because otherwise you have to move the bandmap up again and again, if you want to select after an QSO several calls from the selected area one after the other.

73, Wolfgang
DL2KI

When i work QO-100 and make a spot, i check "Use RX frequency for DX spots"
I set the RX freq to 10489.500 MHz. but the spot that is uploaded appears as "489000KHz"

I found a bug in CQRLOG. It's probably not common but here it goes:
In 1995 I lived in El Salvador and I was YS1ZV. My US Call is WC4H and my CQRLOG db is only for WC4H.

Forward to today:
I downloaded the LoTW confirmations (for WC4H) and received the message that 2 QSOs were not in my log but were in LoTW.

The two QSOs were in 1995 so I was very suspicious.

I went to LoTW and saw that the 2 QSOs were for YS1ZV and were indeed confirmed on the date the error message said.

Using the following configuration:

CQRLog Version: CQRLog 2.5.2(001) 2021-09-19
Hamlib Version: rigctl Hamlib 4.4~git Thu Nov 11 23:10:57 2021 +0000 SHA=8b5685
Rig: Yaesu FTDX-101D

Using the following command string to start rigctld:
/usr/local/bin/rigctld -m 1040 -r /dev/$ftdx -s 38400 --set-conf=dtr_state=OFF &

Hello,

If eQSL qso has a Time_on = 0000,
t_eQSL_min = t_eQSL_max = 01:00:00

so the eQsl is not imported.

Debug trace :
Call: G4xxx
Band: 40M
Mode: CW
Submode:
QSO_date: 20050826
Time_on: 0000
QSLR:
------------------------------------------------
select id_cqrlog_main,eqsl_qsl_rcvd,time_on from cqrlog_main where (qsodate ='2005-08-26') and ((mode = 'CW') or (mode = '')) and (band = '40M') and (callsign = 'G4xxx')

Hello,

Is there a solution to avoid importing field like locator from LoTW ?
For example, I would like to keep locator empty field (or with existing data), but not replaced by value coming from LoTW.

I don't see (in source files) the rule of which fields are replaced or not from import.

Thanks a lot,

73's

Herve F8EHJ

Is it just me or has anyone else noticed that after the last update, see Wish List-Skipping Data Fields, the cursor does not return to the call input field after a contact is logged?