CQRLOG under Fedora 35 not storing UTF-8 characters

2 posts / 0 new
Last post
CQRLOG under Fedora 35 not storing UTF-8 characters

Since I transitioned to Fedora 35 I have a problem with the character set (probably related to MariaDB).
When I type in UTF-8 characters (as swedish å,ä and ö) the form will accept the characters but as soon as I save the post or edit an old entry, CQRLOG displays some good old 7-bit substitutes.

I have tried editing the *.adi backup file, manually correcting all substitutes, e.g: "<NAME_INTL:6>Börje<QTH_INTL:11>GÃ¥nghester" => "<NAME_INTL:6>Börje<QTH_INTL:11>Gånghester" and then importing the adi-file to a new database. When I open CQRLOG with the new database, everything looks OK but as soon as I edit an old entry (like the one above) or adds a new logbook entry CQRLOG changes the characters back to the 7-bit format.

The mysql.cnf looks correct in relevant parts:

# Use UTF-8 encoding for tables

The log file has a few errors, but nothing related to character set representation:

2022-01-12 11:33:10 0 [Note] InnoDB: Uses event mutexes
2022-01-12 11:33:10 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2022-01-12 11:33:10 0 [Note] InnoDB: Number of pools: 1
2022-01-12 11:33:10 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
2022-01-12 11:33:10 0 [Note] InnoDB: Using Linux native AIO
2022-01-12 11:33:10 0 [Note] InnoDB: Initializing buffer pool, total size = 83886080, chunk size = 83886080
2022-01-12 11:33:10 0 [Note] InnoDB: Completed initialization of buffer pool
2022-01-12 11:33:10 0 [Note] InnoDB: 128 rollback segments are active.
2022-01-12 11:33:10 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2022-01-12 11:33:10 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2022-01-12 11:33:10 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
2022-01-12 11:33:10 0 [Note] InnoDB: 10.5.13 started; log sequence number 96473840; transaction id 3161
2022-01-12 11:33:10 0 [Note] InnoDB: Loading buffer pool(s) from /home/brusan/.config/cqrlog/database/ib_buffer_pool
2022-01-12 11:33:10 0 [Note] Plugin 'FEEDBACK' is disabled.
2022-01-12 11:33:10 0 [ERROR] Can't open and lock privilege tables: Table 'mysql.servers' doesn't exist
2022-01-12 11:33:10 0 [Note] Server socket created on IP: '::'.
2022-01-12 11:33:10 0 [Warning] Can't open and lock time zone table: Table 'mysql.time_zone_leap_second' doesn't exist trying to live without them
2022-01-12 11:33:10 1 [Warning] Failed to load slave replication state from table mysql.gtid_slave_pos: 1017: Can't find file: './mysql/' (errno: 2 "No such file or directory")
2022-01-12 11:33:10 0 [Note] Reading of all Master_info entries succeeded
2022-01-12 11:33:10 0 [Note] Added new Master_info '' to hash table
2022-01-12 11:33:10 0 [Note] /usr/sbin/mysqld: ready for connections.
Version: '10.5.13-MariaDB' socket: '/home/brusan/.config/cqrlog/database/sock' port: 64000 MariaDB Server
2022-01-12 11:33:10 0 [Note] InnoDB: Buffer pool(s) load completed at 220112 11:33:10
2022-01-12 11:33:11 4 [ERROR] InnoDB: Table `mysql`.`innodb_table_stats` not found.
2022-01-12 11:34:35 0 [Note] /usr/sbin/mysqld (initiated by: unknown): Normal shutdown
2022-01-12 11:34:35 0 [Note] InnoDB: FTS optimize thread exiting.
2022-01-12 11:34:35 0 [Note] InnoDB: Starting shutdown...
2022-01-12 11:34:35 0 [Note] InnoDB: Dumping buffer pool(s) to /home/brusan/.config/cqrlog/database/ib_buffer_pool
2022-01-12 11:34:35 0 [Note] InnoDB: Buffer pool(s) dump completed at 220112 11:34:35
2022-01-12 11:34:36 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2022-01-12 11:34:36 0 [Note] InnoDB: Shutdown completed; log sequence number 96552836; transaction id 3172
2022-01-12 11:34:36 0 [Note] /usr/sbin/mysqld: Shutdown complete

I can not find anything related to character sets in the CQRLOG config file so right now I feel I'm out of options.
The version is 2.5.2 (001)

Any ideas?

CQRLOG under Fedora 35 not storing UTF-8 characters


I have Fedora 35 and cqrlog compiled from latest source and there is no problem using scandinavian ÖÄÅöäå, as well as other UTF-8 characters.
What is your cqrlog version? Have you recently updated it and still using "original" logs?

It might be that in your old log, the database itself, the UTF-8 setting is not valid and the database is not in UTF-8 format.
Try to make a new log.
Add a qso to new log with comment that has öäåÖÄÅ, save and then open to edit.
Are the öäåÖÄÅ ok now?

Please read also this file that may explain your problems. https://github.com/OH1KH/cqrlog/blob/loc_testing/compiled/UTF8_logs.md
It looks to me that you are running old cqrlog with F35 and the problem described shows up "upside down" for you now.