Bug#932776: marked as done (cqrlog: Receiving QSO data in WSJT-X remote mode generates a "Access Violation" message box)
Your message dated Wed, 01 Jan 2020 20:13:44 +0000
with message-id <E1imkNE-0003aE-8O@fasolo.debian.org>
and subject line Bug#932776: fixed in cqrlog 2.4.0-1
has caused the Debian Bug report #932776,
regarding cqrlog: Receiving QSO data in WSJT-X remote mode generates a "Access Violation" message box
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
932776: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932776
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: cqrlog: Receiving QSO data in WSJT-X remote mode generates a "Access Violation" message box
- From: Nate Bargmann <n0nb@n0nb.us>
- Date: Mon, 22 Jul 2019 18:47:36 -0500
- Message-id: <156383925686.6307.12426771880284885190.reportbug@merlin.lan>
- Reply-to: Nate Bargmann <n0nb@n0nb.us>
Package: cqrlog
Version: 2.3.0-2
Severity: normal
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Dear Maintainer,
I am reporting this in case other users of CQRlog and WSJT-X run into this bug.
This issue has been known by upstream for over a year and yet no release
incorporating the fix has been made. I first encountered this error after
upgrading to CQRlog 2.3.0 last year. The CQRlog forum has a workaround
described and a link to unofficial fixed binaries:
https://www.cqrlog.com/node/2061
It is important to know that anyone following the directions of copying the
fixed unofficial binary should be aware that a version later than
cqrtest230-216 will force a change to the database schema. I am using the
216 version here with WSJT-X without issue now. It is not ideal, and
certainly not likely recommended by the Debian maintainers, but this is out
there and I think it should be useful to document it so others can make a
choice.
73, Nate, N0NB
- -- System Information:
Debian Release: 10.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages cqrlog depends on:
ii default-mysql-server-core 1.0.5
ii libatk1.0-0 2.30.0-2
ii libc6 2.28-10
ii libcairo2 1.16.0-4
ii libgdk-pixbuf2.0-0 2.38.1+dfsg-1
ii libglib2.0-0 2.58.3-2
ii libgtk2.0-0 2.24.32-3
ii libhamlib-utils 3.3-5
ii libhamlib2 3.3-5
ii libmariadb-dev-compat 1:10.3.15-1
ii libpango-1.0-0 1.42.4-6
ii libx11-6 2:1.6.7-1
ii mariadb-client-core-10.3 [virtual-mysql-client-core] 1:10.3.15-1
ii mariadb-server-core-10.3 [virtual-mysql-server-core] 1:10.3.15-1
Versions of packages cqrlog recommends:
ii default-mysql-server 1.0.5
ii xplanet 1.3.0-5.1
cqrlog suggests no packages.
- -- no debconf information
-----BEGIN PGP SIGNATURE-----
iQHBBAEBCgArFiEEG5vcSeqIHtMzWHg79yYl4u2+1ZgFAl02SxgNHG4wbmJAbjBu
Yi51cwAKCRD3JiXi7b7VmAcXC/4zpMa+NY28LBfxt41xBFzxcmCskzREMZZA1PGa
0fZuZatUXm+bflV4zq6slXQGuTwyoa5/amApo9niXJIUoyy6+UlfOHNKcwH1uTv0
c/yy7WHK8s/vbs8JA3l5WlF7vqrH5c+Ds5G2gANtVdsBw8oUU7VIA2jW4JNFYifd
4f7Es4kp17FCSBtcnNHKtxTg98COxlYQES3bjRzPDbWGvZObdQm0CwglvAjlHaWV
siUv+H+mTghF7ME8t4WbAxxlK7JguwAoR6pTypinfEyK4NYzGN2fGM9xfAPwd5xN
6MnWoTC3ybfzTvSTHGe4XfDes/Q+m4/2tBjea69SXUEC4wr1cnd4aCPL/myt+qI5
bJaRcJu6VgWwqmQeSFbB0GHFbTN44tNDvzpLJW3pXdetmICAJ3VQsZZML5MDoBNT
zapk9S/rLo4YmWN6HW47IaAOT5E6anF8Y7s9tb0y++QO80kzycggKvsLHdH0j2R+
agKqKdE9Gtcp8KrD50WFTbj7go4=
=omfB
-----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---
Source: cqrlog
Source-Version: 2.4.0-1
We believe that the bug you reported is fixed in the latest version of
cqrlog, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 932776@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Christoph Berg <myon@debian.org> (supplier of updated cqrlog package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Mon, 30 Dec 2019 10:31:26 +0100
Source: cqrlog
Binary: cqrlog cqrlog-data
Architecture: source all amd64
Version: 2.4.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Hamradio Maintainers <debian-hams@lists.debian.org>
Changed-By: Christoph Berg <myon@debian.org>
Description:
cqrlog - Advanced logging program for hamradio operators
cqrlog-data - Advanced logging program for hamradio operators (data files)
Closes: 932776
Changes:
cqrlog (2.4.0-1) unstable; urgency=medium
.
* Team upload.
* New upstream version.
+ Fixes wsjtx integration. (Closes: #932776)
* Move arch-indep files to cqrlog-data.
* Don't remove debian/cqrlog.* on clean, it would remove cqrlog.install.
* Add debian/gitlab-ci.yml.
* DH 12.
Checksums-Sha1:
7a6388b9da71ff3ba61514e6ce52ef99a58a263e 2312 cqrlog_2.4.0-1.dsc
e53e02afcb89d985bff671de29cc54f7f4300919 12361259 cqrlog_2.4.0.orig.tar.gz
a4c809faea77214a250d7eeb489bd083528ce9fc 11940 cqrlog_2.4.0-1.debian.tar.xz
04d32450f5891c8fc4eba63306cd06c24f9accc1 8805416 cqrlog-data_2.4.0-1_all.deb
b2e048974323eaf88b3938e3b0f2562f24ced1c9 12573 cqrlog_2.4.0-1_amd64.buildinfo
fe402eaf22920e1000dca63e0dcfcdcb1505526b 4022704 cqrlog_2.4.0-1_amd64.deb
Checksums-Sha256:
2987b6895465a11572d90bee205cfcef60f49c2184abf16c9cbaee34cef3ea73 2312 cqrlog_2.4.0-1.dsc
f492839803f7fdbaed873308c169ae251e7b9e6c3eb232a20a5773fd0d9acecd 12361259 cqrlog_2.4.0.orig.tar.gz
5f832904a91eebe935341699da2447868b4ac1bc7a902e670970cc5f0048f7d7 11940 cqrlog_2.4.0-1.debian.tar.xz
fe89f9da8720b808dbcd0654343448957b52ede64324c4315d6b8e705cc46178 8805416 cqrlog-data_2.4.0-1_all.deb
8ee2df69299f51ab8bfebf9337b8a0ceba80bb2cab690afa3acb7e92ddc2572f 12573 cqrlog_2.4.0-1_amd64.buildinfo
9ece9d05db4d2a7b261cd136ff813ff0ff42cc78998e5b576b284359bbd1ddfc 4022704 cqrlog_2.4.0-1_amd64.deb
Files:
de2f4473f7a20e432f2993542b31f285 2312 hamradio optional cqrlog_2.4.0-1.dsc
3be6e7c0dfc2595e33680f68627449fe 12361259 hamradio optional cqrlog_2.4.0.orig.tar.gz
360f8eb65d5fecbf295430d8c4ce5575 11940 hamradio optional cqrlog_2.4.0-1.debian.tar.xz
c80fe81489c805876d0de538b97987a9 8805416 hamradio optional cqrlog-data_2.4.0-1_all.deb
27994e1fe07aabc4e7d403cb8e17a5c6 12573 hamradio optional cqrlog_2.4.0-1_amd64.buildinfo
54c2fd2a2ef23f29129fce7d222c46e6 4022704 hamradio optional cqrlog_2.4.0-1_amd64.deb
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEXEj+YVf0kXlZcIfGTFprqxLSp64FAl4J4aoACgkQTFprqxLS
p66M1hAAsT4tfUSqjGclpxan9S8QBJ36QDJ/2x8ZZkFWZTVO1pRyvkpRQu64XqJD
uVvQA7wsq5Y2jMh5TmABorXFredZ2ISnXo6/Al5UWWqSiwvd/k7yTjyTsE0hMBxW
WPeccpqn5RRE60EIlDOtK1rjbXgfouU0O9L7xq0Av+8TMHT+aFSFBd2jshDuN8At
EaXkoYY93AE9eJO30QgnK6PSbrI+uUVVrKBdmGUQsgDZWYH03gQwqR30fB9M9iEW
HFDUdlX4FOfZ/g6d5g4Nh3B39e1S25h7Tq+sW/R5nIc8wux5gVIvtz15UBkxpSPS
m84cslSOBmB/Tb9QF5ezg6aFjzE3l07/V215vH3h5oRnAbouyXOZXsv4O76tz0VB
O+1jSFFEei0VIjvuRQvk7SfCWW14I166UfSlcLav/l3+DmfAd8Y93GVm4NBot+DL
TbBM1bywHwL3ZSlA/YNlmDjgIvPJrXZMI7MAQey+OTOUCuna+c8QdTDnewsrJHCZ
qqqyV9+XmKTIqyAFDJOfS8lcBqSi+Hyb8UIrw63++lRUVEuIWxip+CMUZ9cEbaCO
3m91s+EfgLHMkfW1MYdyhX7N4Xk0GVp+LHzcGHp7tpqLJsh7T18N2DGkgr15l3w8
J3N+hCRb8p1DTmt3daMga2GA4MJ2iixSBrNlKZm0yAsUy79uFlo=
=OJiK
-----END PGP SIGNATURE-----
--- End Message ---
Reply to: