Bug#965308: jackd won't start
On Fri, 14 Aug 2020 at 10:51:46 +0200, Arnaldo Pirrone wrote:
> I would like to point out that the error is not showing up any more after the
> updates, now the error is different
It seems it's now failing to open the configured ALSA PCM devices (which
probably also shouldn't happen?). From the strace output, it seems the
configured ALSA devices doesn't exist in /dev/snd:
> strace -efile jackd -d alsa
...
> openat(AT_FDCWD, "/dev/snd/pcmC0D0p", O_RDWR|O_NONBLOCK|O_CLOEXEC) = -1 ENOENT (File o directory non esistente)
> stat("/usr/share/alsa/alsa.conf", {st_mode=S_IFREG|0644, st_size=9623, ...}) = 0
> openat(AT_FDCWD, "/dev/snd/controlC0", O_RDONLY|O_CLOEXEC) = 6
> openat(AT_FDCWD, "/dev/snd/controlC0", O_RDWR|O_CLOEXEC) = 6
> openat(AT_FDCWD, "/dev/snd/pcmC0D0c", O_RDWR|O_NONBLOCK|O_CLOEXEC) = -1 ENOENT (File o directory non esistente)
> ALSA: Cannot open PCM device alsa_pcm for playback. Falling back to capture-only mode
That seems like a completely different failure mode.
smcv
Reply to: