Hi Matt,
thanks for the prompt response!
Matt Taggart wrote:
> On 1/16/21 10:25 AM, Axel Beckert wrote:
>
> > Matt: You said, you had the issue also on the console. Could you check
> > if that "pasuspender -- env PULSE_SERVER= bb" command workarounds the
> > issue for you on the virtual console, too? Maybe there's more virtual
> > console support from pulseaudio nowadays…
>
> When I run that on a vc I get a brief error flash by about not being able to
> open an audio device and then BB runs, but no audio (even though I selected
> it). But at least it doesn't hang.
I see. Might be a separate issue then, not necessarily in bb.
Then again, in the meanwhile I was able to reproduce this issue even
on a virtual console — on a minimal Raspberry Pi running Debian
Testing/Bullseye. It was more or less a minimal installation. I
installed pulseaudio and rebooted to be sure the logins are setup with
pulseaudio.
I though also got a lot of pulseaudio warnings on the console about
audio driver issues. But these seemed hardware-specific.
But in the end, the workaround described in the README.Debian with
"pasuspend -- env PULSE_SERVER= bb" worked there, too.
So I will simplify the README.Debian and focus on that variant as it
seems to help in most if not all cases.
Oh, and I found another workaround, but I can't really recommend it:
Run it as root on the virtual console. Seems to work because
pulseaudio isn't started for root. ;-D
Regards, Axel
--
,''`. | Axel Beckert <[email protected]>, https://people.debian.org/~abe/
: :' : | Debian Developer, ftp.ch.debian.org Admin
`. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5
`- | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
