Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
     ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***

Just wanted to note that the issue persists with Debian Trixie as well.

Hi,

I'm tagging this moreinfo because I'm not able reproduce this on any
recent Debian release.  If you have provide any additional about your
configuration, that could be helpful.

Thanks,
tony

I'm not aware of anything special I did.

It's just Debian with a MATE desktop (and i3wm, but I did that would
break audio for a single programme) and then wsjtx installed. Nothing
remotely audio related was changed and every other programme works.

Is there anything specific I could check?

I configure everything via Ansible as well, so if I really have to I
could see whether any task changes something that breaks it, but it's
more stuff like DNS that I configure, nothing audio-related.

Re: erebion

Can you fire up pavucontrol to check if there's 1) any audio 2) on the
correct sound card while transmitting?

Is the TX gain slider at something between -20dB and 0dB and not at
the very bottom?

Christoph DF7CB

According to Pavucontrol there is no audio, as wsjtx does not show up.
That is while transmitting, haven't tried to receive last time as I did
not have the required cable with me.

I think input was broken as well, but to be sure I'd need to have
another look.

Re: erebion

You don't need the radio connected, you can also let wsjtx record
audio from the local mic and check if the ambient noise shows up on
the waterfall. (Same for TX and local speaker of course.)

If wsjtx doesn't show up, I don't really know where to look further.
(Frustratingly, I have the same issue atm with wfview. I currently
blame pipewire, but I think it did work before.)

Christoph

I'm not claiming that this thread from the wsjt-devel [1] list is
related, but perhaps it's a helpful hint?  (I still can't reproduce
the issue.)

[1] https://sourceforge.net/p/wsjt/mailman/message/51780237/

Hello,

I just have had another look and I had noticed that selecting "default"
for audio input leads to a segfault:

And this is what I got when I selected an ALSA input:

ALSA lib pcm_oss.c:397:(_snd_pcm_oss_open) Cannot open device /dev/dsp
ALSA lib pcm_dsnoop.c:567:(snd_pcm_dsnoop_open) unable to open slave
ALSA lib pcm_dsnoop.c:567:(snd_pcm_dsnoop_open) unable to open slave
ALSA lib pcm_direct.c:1337:(snd1_pcm_direct_initialize_slave) unable to
install hw params
ALSA lib pcm_dsnoop.c:578:(snd_pcm_dsnoop_open) unable to initialize slave
ALSA lib pcm_direct.c:1337:(snd1_pcm_direct_initialize_slave) unable to
install hw params
ALSA lib pcm_dsnoop.c:578:(snd_pcm_dsnoop_open) unable to initialize slave
ALSA lib pcm_oss.c:397:(_snd_pcm_oss_open) Cannot open device /dev/dsp
ALSA lib pcm_route.c:878:(find_matching_chmap) Found no matching channel map
ALSA lib pcm_route.c:878:(find_matching_chmap) Found no matching channel map
ALSA lib pcm_route.c:878:(find_matching_chmap) Found no matching channel map
ALSA lib pcm_dmix.c:1000:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dmix.c:1000:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dmix.c:1000:(snd_pcm_dmix_open) unable to open slave
[1]    106253 segmentation fault  wsjtx

This is what I got when I selected "pulse" for the input:

ALSA lib pcm_oss.c:397:(_snd_pcm_oss_open) Cannot open device /dev/dsp
ALSA lib pcm_dsnoop.c:567:(snd_pcm_dsnoop_open) unable to open slave
ALSA lib pcm_dsnoop.c:567:(snd_pcm_dsnoop_open) unable to open slave
ALSA lib pcm_direct.c:1337:(snd1_pcm_direct_initialize_slave) unable to
install hw params
ALSA lib pcm_dsnoop.c:578:(snd_pcm_dsnoop_open) unable to initialize slave
ALSA lib pcm_direct.c:1337:(snd1_pcm_direct_initialize_slave) unable to
install hw params
ALSA lib pcm_dsnoop.c:578:(snd_pcm_dsnoop_open) unable to initialize slave
[1]    106631 segmentation fault  wsjtx

I know it says ALSA, but I really did select pulse!

I've also noticed that the input meter in wsjtx briefly shoots up to max
before it crashes. At least that might be an indication that it gets
audio before crashing, idk.

I then loaded two kernel modules to try out whether they were missing:

sudo modprobe snd-pcm-oss
sudo modprobe snd-mixer-oss

And then /dev/dsp appeared, but wsjtx still crashed with a segfault
without any error messages. I am in the audio group and can access the
device file just fine with other software.

I even got the same error when I selected "pipewire" for the input:

ALSA lib pcm_oss.c:397:(_snd_pcm_oss_open) Cannot open device /dev/dsp
ALSA lib pcm_dsnoop.c:567:(snd_pcm_dsnoop_open) unable to open slave
ALSA lib pcm_dsnoop.c:567:(snd_pcm_dsnoop_open) unable to open slave
ALSA lib pcm_direct.c:1337:(snd1_pcm_direct_initialize_slave) unable to
install hw params
ALSA lib pcm_dsnoop.c:578:(snd_pcm_dsnoop_open) unable to initialize slave
ALSA lib pcm_direct.c:1337:(snd1_pcm_direct_initialize_slave) unable to
install hw params
ALSA lib pcm_dsnoop.c:578:(snd_pcm_dsnoop_open) unable to initialize slave
ALSA lib pcm_oss.c:397:(_snd_pcm_oss_open) Cannot open device /dev/dsp
ALSA lib pcm_dsnoop.c:567:(snd_pcm_dsnoop_open) unable to open slave
ALSA lib pcm_dsnoop.c:567:(snd_pcm_dsnoop_open) unable to open slave
ALSA lib pcm_direct.c:1337:(snd1_pcm_direct_initialize_slave) unable to
install hw params
ALSA lib pcm_dsnoop.c:578:(snd_pcm_dsnoop_open) unable to initialize slave
ALSA lib pcm_direct.c:1337:(snd1_pcm_direct_initialize_slave) unable to
install hw params
ALSA lib pcm_dsnoop.c:578:(snd_pcm_dsnoop_open) unable to initialize slave
[1]    108774 segmentation fault  wsjtx
wsjtx  5,03s user 1,21s system 10% cpu 1:02,24 total

This makes me believe that wsjtx always tries to access ALSA stuff when
it should be using something else OR that the error message is simply wrong.

Please not that it does not matter what I select for output, it will not
crash. I will just not get output on some settings, even though I should.

However, I got the following when I had selected "pipewire" as output
and manually removed the input from the config (as it crashes otherwise
and GUI does not allow not having an input), there's nothing set to
ALSA, but it still has ALSA errors:

ALSA lib pcm.c:8740:(snd_pcm_recover) underrun occurred
ALSA lib pcm_route.c:878:(find_matching_chmap) Found no matching channel map
ALSA lib pcm_route.c:878:(find_matching_chmap) Found no matching channel map
ALSA lib pcm_route.c:878:(find_matching_chmap) Found no matching channel map
ALSA lib pcm_dmix.c:1000:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_direct.c:1337:(snd1_pcm_direct_initialize_slave) unable to
install hw params
ALSA lib pcm_dmix.c:1012:(snd_pcm_dmix_open) unable to initialize slave
ALSA lib pcm_direct.c:1337:(snd1_pcm_direct_initialize_slave) unable to
install hw params
ALSA lib pcm_dmix.c:1012:(snd_pcm_dmix_open) unable to initialize slave

So... There seems to be audio output now with "pipewire" or "default"
selected (or maybe I just selected a different option compared to around
a year ago?), but it still seems to be broken.

Oh, and looking at logs, kernel says:

kernel: traps: wsjtx[110457] general protection fault ip:7fa7cc1071ee
sp:7ffe8c52a530 error:0 in libQt5Gui.so.5.15.10[7fa7cc0e2000+4ef000]

erebion

Went doing other things, came back, opened wsjtx again and noticed audio
input works. No crashes so far. (what the?!)

Not sure what the hell is going on, but maybe I have magic hands. :p

Or maybe the config was broken and opening again wrote a new config?

For now I cannot get the issue back, but others with the same issue:
Maybe try removing the config and starting with a new config, maybe
something changed..?

erebion