Main application window doesn't show on Fedora

[domfe]

Hi.
When I run audacity I can see the logo but then it disappears and no window is displayed, the process is still there eating 100% of cpu.
Running from the command line gives this output:

WARNING: cgroup v2 is not fully supported yet, proceeding with partial confinement
Trying to route ALSA through PulseAudio...
Attempting to connect to Audacity failed...retrying
ALSA lib control.c:1373:(snd_ctl_open_noupdate) Invalid CTL hw:0
ALSA lib control.c:1373:(snd_ctl_open_noupdate) Invalid CTL hw:1
ALSA lib control.c:1373:(snd_ctl_open_noupdate) Invalid CTL hw:3
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
ALSA lib seq.c:935:(snd_seq_open_noupdate) Unknown SEQ default
ALSA lib control.c:1373:(snd_ctl_open_noupdate) Invalid CTL hw:0
ALSA lib control.c:1373:(snd_ctl_open_noupdate) Invalid CTL hw:0
Expression 'stream->capture.pcm' failed in '/build/audacity/parts/audacity/src/lib-src/portaudio-v19/src/hostapi/alsa/pa_linux_alsa.c', line: 4611
ALSA lib control.c:1373:(snd_ctl_open_noupdate) Invalid CTL hw:0
ALSA lib control.c:1373:(snd_ctl_open_noupdate) Invalid CTL hw:0

and then 252 lines of

(audacity:12093): Pango-CRITICAL **: 10:26:01.137: pango_font_description_set_size: assertion 'size >= 0' failed

System is Fedora.

rpm -qi snapd
Name        : snapd
Version     : 2.48.2
Release     : 1.fc33
Architecture: x86_64

[frenchwr]

Hello, we recently updated the audacity snap to version 3.7.1 and are closing old issues (including this one) that are most likely no longer relevant.

If you would like to test the new version, it can be installed with:

sudo snap install audacity

Or if you already have the audacity snap installed and would like to upgrade from a prior version:

sudo snap refresh audacity

Feel free to re-open this issue if you discover this bug is still present, or open a new one if you uncover some other issue. We would welcome the feedback!