Hi to all,
After editing some QSOs, CQRlog was freezing.
I kill the program and restarted it; I was cheching if QSOs were there (all seemed ok) and I close CQRLog making a backup.
After starting, ask me to install new DXCC: I choose "yes".
After restarting again, CQRlog wont start, but show a windows with "Access violation" and "Click OK to ignore... etc".
Starting it from console, I have:
/opt/cqrlog-2.5.2/usr/bin/cqrlog --debug=1
(cqrlog:9387): Gtk-WARNING **: 19:29:30.347: Impossibile trovare il motore del tema in module_path: «adwaita»,
Cqrlog Ver:2.5.2 (001) Date:2021-02-12
**** DEBUG LEVEL 1 ****
OS:
Linux version 5.10.0-26-amd64 (debian-kernel@lists.debian.org) (gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP Debian 5.10.197-1 (2023-09-29)
SSL libraries:
libssl.so
libcrypto.so
Loaded 195851 LoTW users
Loaded 216932 eQSL users
[FORMS.PP] ExceptionOccurred
Sender=EAccessViolation
Exception=Access violation
Stack trace:
$00000000004202B3
$000000000045E1F5
It's possible to restore the correct working?
First of making some test, I've made a backup of dir "/home/ik7xja/.configkde/cqrlog/" with a new name... I hope all QSO will be safe...
The exact same thing happened to me just now...Right in the middle of the CQ World Wide DX Contest
Hi, did you update something in the PC or in the CQRLog? I answered "Yes" to a DXCC update.
I also have the QSOs of CQ-WW CW contest and no backup working...
Hi!
For those who are not in Telegram Cqrlog group:
This problem appears to be in dxcc/country files update. Petr has restored old files in update.
That is why I did not get any offer to update dxcc when startting Cqrlog this morning and can not see any problem because my ~/.config/cqrlog/ctyfiles/cqrlog-cty.tar.gz file has still date2023-08-28
There is a mention in group messages that removing MASTER.SCP from that directory could help:
rm ~/.config/cqrlog/MASTER.SCP
I can not confirm that because I do not have current problem here.
It is worth of try (after you have backup from ~/.config/cqrlog first.
--
Saku
OH1KH
Hi Saku,
I'll try to restore from a backup cqrlog-cty.tar.gz (I just noticed that has a 26-11-2023 date) and I give feedback on this forum as soon as I should be at home.
Dear Saku,
thank you very much for your help, that solved the problem.
73s
hello Saku,
I confirm, with the deletion of this cqrlog file started correctly!
Thanks !
73
Didier F1MXE JN05GQ
This worked for me, thanks!
73, Bill NZ0T
Solved for me to! Thanks!
Hi Saku,
I wanted to post here as well to make sure you see it. The work-around of deleting the MASTER.SCP file will not hold once a new dxcc update is published. The issue stems from the code in dData.pas - specifically the part that loads the file into a string array. I have submitted a pull request that should solve the problem permanently and verified that it can load the new (very large) MASTER.SCP file without crashing. I'll monitor the PR thread in case you want any changes, etc.
This did it (rm ~/.config/cqrlog/MASTER.SCP). Thanks for this.
73, Bruce
Hello,
it seems I have the same issue, it came up right after the DXCC update (with --debug=1):
(cqrlog:1745): Gtk-WARNING **: 08:51:50.050: Im Modulpfad »murrine« konnte keine Themen-Engine gefunden werden,
(cqrlog:1745): Gtk-WARNING **: 08:51:50.050: Im Modulpfad »murrine« konnte keine Themen-Engine gefunden werden,
(cqrlog:1745): Gtk-WARNING **: 08:51:50.050: Im Modulpfad »murrine« konnte keine Themen-Engine gefunden werden,
Cqrlog Ver:2.6.0_(119)_Gtk2 Date:2023-10-03
**** DEBUG LEVEL 1 ****
OS:
Linux version 6.6.1-1-MANJARO (builduser@fv-az447-329) (gcc (GCC) 13.2.1 20230801, GNU ld (GNU Binutils) 2.41.0) #1 SMP PREEMPT_DYNAMIC Thu Nov 9 04:27:49 UTC 2023
SSL libraries:
libssl.so
libcrypto.so
Loaded 195851 LoTW users
Loaded 216932 eQSL users
Closing dData
[FORMS.PP] ExceptionOccurred
Sender=EAccessViolation
Exception=Access violation
Stack trace:
$000000000041FB43
$00000000004658C3
I did a new compile via yay and moved my database folder, so cqrlog creates a new one. It starts just fine with a new database, so it seems to be related to the database or something in its folder? Deleting ctyfiles folder didn't help.
Thanks for any hits.
vy 73s
Hi to all!
After the yesterday problem on launching CQRLog, according to the information on the forum and on this group, I copied from a backup the Two files:
~/.configkde/cqrlog/MASTER.SCP
~/.configkde/cqrlog/ctyfiles/cqrlog-cty.tar.gz
And all returning to work!
Many thanks for prompt reply!
CQRLog team is always the bast!
Franco, IK7XJA
Hi all,
After create a new log for a new call sign and load few qso, I close the programme.
But it could be impossible to correctly lauchning cqrlog.
After the launching picture, Error and warning message about database corruption... Abort and open buttons do the same thing : shut down the programme.
So I rename in .config/cqrlog the master.scp file by master.scp_old
Then It could be possible to yet open the cqrlog for both call signs.
My two cents...
73 Laurent F6GOX
Removing
rm ~/.config/cqrlog/MASTER.SCP
worked for me also.
73,
Bruce
N7CEE
I have also had the same problem. Starting cqrlog i get the following:
Cqrlog Ver:2.4.0 (001) Date:2019-10-27
**** DEBUG LEVEL 0 ****
**** CHANGE WITH --debug=1 PARAMETER ****
OS:
Linux version 4.15.0-213-generic (buildd@lcy02-amd64-079) (gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04)) #224-Ubuntu SMP Mon Jun 19 13:30:12 UTC 2023
[FORMS.PP] ExceptionOccurred
Sender=EAccessViolation
Exception=Access violation
Stack trace:
$000000000041F7F3
$000000000045D555
TApplication.HandleException Access violation
Stack trace:
$000000000041F7F3
$000000000045D555
Closing ini file ...
I don't want to lose my log and don't know how to back it up without running the program. What command should I run in console to do this? Or should I just run in console:
rm ~/.config/cqrlog/MASTER.SCP
Do I need to do anything else?
Thanks!
KD8CQC
Hi KD8CQC,
Removing the master.SCP file will not affect your log at all.
Saku, oh1kh, has published an updated version of cqrlog that fixes this issue without having to remove the file at all. My recommendation is that you upgrade to that.
Thanks, that did work! Back in business!
All
I fired up yesterday only to get exactly the same problem ! Would you believe it . . .
Removal of said file cured it - Master.SCP file.
System here is Linux Mint 21.1 VERA running on a Mac
So big Thanks for the info and I keep my hair :)
Rgds: Peter - g4nkx (Reg Linux user No 484861) - IO90lv