CQRLOG - bugs

CW Type window

Submitted by k8wdx on

Not sure if the log is suppose to do this, but when I have the CW type window open, I can't put anything in the main log window, so the only way to log a qso with the CW type window open is to close it first, the CW keys works great. 73 Tom K8WDX

Forums: 

RBN Monitor .. change settings lets crash CQRLOG

Submitted by DK5TX on

Hi Petr,

the RBN monitor is a great feature! Just found a bug or two while using it ...

When I try to change entries in the filter criteria window of the RBN monitor, CQRLOG crashes. When it shows me the 'Access Violation' window and I can keep on using CQRLOG without any problems, but sometimes it crashes completely without any notification. It seems to be a problem whether the RBN monitor is connected to the RBN (no crash) or if its not connected (crashes).

Forums: 

cqrlog-apparmor-fix

Submitted by DL2KI on

Hi Petr,

after the update to version 1.9.1, the apparmor problem occurs to me.

Therefore I started cqrlog-apparmor-fix, but this was not successful.

So I added a "@{HOME}/.config/cqrlog/database/** rwk," directly in /etc/apparmor.d/usr.sbin.mysql.

This then works.

"cqrlog-apparmor-fix" works with the file "local / usr.sbin.mysqld", but in "/etc/apparmor.d/usr.sbin.mysqld" the include command apparently does not work ???

Forums: 

communication rigctl/cqrlog

Submitted by F4EEI on

Hello,
I have a problem. RIGCTL listen TRX of information but they do not send the data to CQRLOG.

RigCtldPath:/usr/bin/rigctl
RigCtldArgs:-m 237 -r /dev/ttyUSB0 -t 4532 -s 115200
RunRigCtld: FALSE
RigDevice: /dev/ttyUSB0
RigCtldPort:4532
RigCtldHost:localhost
RigPoll: 300
RigSendCWR: FALSE
RigId: 237

rigctld started!
Connected to localhost:4532
1
2
3
4
5
6

73 Julien

Forums: 

cqrlog 1.9.0-5 error

Submitted by CX1FK on

debian testing/stretch amd64
cqrlog 1.9.0-5 not start

http://imgur.com/qOn1SfJ

cqrlog (1.9.0-5) unstable; urgency=medium

* Bump debian/compat to 9
* Apply apparmor fix to /etc/apparmor.d/local/usr.sbin.mysqld
*not* to /etc/apparmor.d/usr.sbin.mysqld which is a conf file
(Closes: #801755)

-- Colin Tuckley Thu, 12 Nov 2015 10:12:00 +0000

cqrlog (1.9.0-4) unstable; urgency=high

Forums: 

Bug or Other Problem

Submitted by K5VJZ on

I've been off of CQRLOG since Ubuntu dropped support for RS-232 ports, and recently returned.

I have the rig control working normally, in that it reads the radio info correctly.

here's the problem...

For instance, the radio is set and operating on 14.02500 and I click
on a DX spot, the progream now shows the frequency as 114.02500.
If I am on a lower band, for instance 7.02500.. and I click a spot the
program now shows 107.12500

Forums: 

Country confusion, Fernando de Noronha

Submitted by ac8to on

I'm pretty new to this, so I'm not sure if this is a bug or a misunderstanding of how to properly use CQRLOG, but a station I recently worked, PY0F/AA4NC, in Fernando de Noronha, seems to be accounted as if it were in the USA. I tried manually editing the country, grid, ITU. WAZ, all to no avail. Any tips on why I can't seem to get this right?
Thanks,
Don - AC8TO

Forums: 

cqrlog crash when connected to dx cluster

Submitted by AA6KJ on

Hi,
 
If I leave cqrlog (1.9.0 on 32bit Fedora/Intel) connected to dx cluster (VE7CC), the program crashes usually within two hours. I left it running with debugging enabled and this is what I see at the end of the output:
 
DX de UA4M-#:     3507.0  R5WW         CW 29 dB 23 WPM CQ             2011Z
Enter critical section On Receive
Leave critical section On Receive
DX de AC0C-#:    14052.0  N1DN         CW 05 dB 15 WPM CQ             2011Z
Enter critical section On Receive
Leave critical section On Receive

Forums: 

Logging at 00:00 UTC

Submitted by k8wdx on

Hi Petr, when logging a QSO at 00:00 UTC there is a slight problem, If the QSO starts at 11:58 UTC then gets logged at 00:02 UTC, CQRlog uses the start time and the end date, so lets say the QSO starts at 11:58 8/6/2015 and ends at 00:02 8/7/2015 the log then set the end qso at 11:58 on 8/7/2015 which is incorrect. CQRlog should use the end time and date for the official logging time. very rare that this happens, because you have to log just at the right time, but the bug is there.. Thanks!

Forums: 

Pages

Subscribe to RSS - CQRLOG - bugs