CQRLOG - bugs

Bug while overwriting

The overwrite bug previously noticed in 2.1.0 remains. If I need to overwrite something in the logging window (RST, Name, QTH etc.) there is NOT overwritten the highlighted character but the next to them - ie. RST - when the default 599 (with the middle 9 highlighted) need to change to 579, the simple overwritting of the highlighted 9 results in 597 entry. The same applies to ANY field in the logging screen. This bug shows in the Debian Stretch 9 with Gnome, tests in older Ubuntu/Unity versions were OK.

It is apparently a Lazarus issue.

Forums: 

US ZIP Code is out of place in address fetched from QRZ

When I edit a log entry (for example, when preparing to create QSL address labels), I press F11 to fetch the address from QRZ. Usually, I copy from that auto-completed field, and paste into the Comment to Callsign field, and then I use some custom SQL to generate a CSV file for label printing.

For US hams, the address from QRZ is displayed as follows:

WB1DYR
LEE H KNAPP
19307 STATE ROUTE 29
MONTROSE 18801-7195 PA

However, the more "proper" way to write an address for the US Postal System is:

Forums: 

Error during connection to database: Server connect failed.

Dear Petr,
After a sudden power outage I can't connect to my DB anymore.
Here are the last 20 lines of mysql.err
Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0x0 thread_stack 0x48400
/usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x55a2ffe8936e]
/usr/sbin/mysqld(handle_fatal_signal+0x3bd)[0x55a2ff9cea4d]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x110c0)[0x7f2e460b20c0]

Forums: 

Neither cqrlog versions 2.0.4 and 2.1.0 will run

I'm running Raspbian Jessie on a Raspberry Pi B+. CQRLOG version 1.8 will run, but when I downloaded and upgraded to version 2.0.4 or 2.1.0 the program will not run. Also, with the 1.8 version if I update the LoTW and QSL manager lists, I get an "access violation". It doesn't matter which option I choose, the program is killed. I've tried some of the fixes posted, but they don't work. Does anyone have any suggestions or fixes?

Forums: 

Problems with new 2.1.0 WSJT window

Been using 2.0.5, upgraded to 2.1.0, but it errors out most of the time when "Remote mode for wsjt" is enabled.
Only occasionally does it successfully open the new activity window. Most of the time the program crashes.

2.1.0 from tar.gz, Centos 6.9
--debug=1
...
LoadForm: frmNewQSO
Socket created!
Bind issued 127.0.0.1:2238

(cqrlog:13870): Gtk-CRITICAL **: IA__gtk_text_iter_get_buffer: assertion `iter != NULL' failed

Forums: 

Pages

Subscribe to RSS - CQRLOG - bugs