Access violation while logging FT8 QSO

2 posts / 0 new
Last post
ok1rr
ok1rr's picture
Access violation while logging FT8 QSO

Debian 9 testing (unstable), CQRlog 2.3.0, WSJT-X 1.9.1

A problem encountered while logging FT8 QSO:

Cqrlog Ver:2.3.0 (001) Date:2018-06-17
**** DEBUG LEVEL 0 ****
**** CHANGE WITH --debug=1 PARAMETER ****

2018-07-23 6:05:03 140124641086592 [Note] /usr/sbin/mysqld (mysqld 10.1.29-MariaDB-6+b1) starting as process 2317 ...
[USER] Invalid borders specified for theme pixmap:
/home/martin/.themes/Breeze-gtk/gtk-2.0/../assets/line-h.png,
borders don't fit within the image
ALSA lib pcm_dsnoop.c:638:(snd_pcm_dsnoop_open) unable to open slave
ALSA lib pcm_dmix.c:1035:(snd_pcm_dmix_open) The dmix plugin supports only playback stream
ALSA lib pcm_dmix.c:1099:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dsnoop.c:575:(snd_pcm_dsnoop_open) The dsnoop plugin supports only capture stream
ALSA lib pcm_dsnoop.c:575:(snd_pcm_dsnoop_open) The dsnoop plugin supports only capture stream
ALSA lib pcm_dsnoop.c:575:(snd_pcm_dsnoop_open) The dsnoop plugin supports only capture stream
ALSA lib pcm_dsnoop.c:575:(snd_pcm_dsnoop_open) The dsnoop plugin supports only capture stream
ALSA lib pcm_dsnoop.c:575:(snd_pcm_dsnoop_open) The dsnoop plugin supports only capture stream
ALSA lib pcm_dsnoop.c:575:(snd_pcm_dsnoop_open) The dsnoop plugin supports only capture stream
ALSA lib pcm_dsnoop.c:575:(snd_pcm_dsnoop_open) The dsnoop plugin supports only capture stream
ALSA lib pcm_dsnoop.c:638:(snd_pcm_dsnoop_open) unable to open slave
ALSA lib pcm_dsnoop.c:638:(snd_pcm_dsnoop_open) unable to open slave
ALSA lib pcm_dmix.c:1099:(snd_pcm_dmix_open) unable to open slave
TApplication.HandleException Access violation
Stack trace:
$0000000000429FCE
$000000000080E3E9
$0000000000740123
$00007F4912850B73
SyncUpdate:
SyncMsg :ClubLog: Uploading Z66X
SyncUpdate:OK
SyncMsg :ClubLog:
Item:ClubLog: Uploading Z66X ... OK
SyncUpdate:
SyncMsg :ClubLog: Done ...
Invalid file handle
Closing ini file ...

73,
Martin, OK1RR

oh1kh
Access violation while logging FT8 QSO

Hi Martin!

Very strange dump!
Seems to be some kind of sound device (ALSA) problem. I can not understand what that has to do with logging.
Do you use wsjt-alerts? That could cause sound device errors if it has misconfiguration or with just one sound device already used by wsjt-x.
But on the other hand alerts do not happen while logging. Only if same time has happened a new decode with alert when you have pressed wsjt-x logging sheet's OK button.

And did you accept access violation with OK as you have clublog section after stack trace?

Can you reproduce this error?

The only logging error that I had just yesterday in normal qso logging( but happens also with wsjt-x) was: "'2018-07-24' is not valid date"
It happens every now and then, last time was I think a month ago.

--
Saku
OH1KH