Hi,
For the record, I had the exact same problem on a computer running
buster that I don't use very often. For sure, it was working fine even
with timidity installed a few months ago. Many thanks to Andrei for the
'lsof | grep /dev/snd' command that pointed us in the right direction!
Debugging
riveravaldez wrote:
> On 4/12/20, riveravaldez wrote:
>> On 4/12/20, Andrei POPESCU wrote:
>>> On Sb, 11 apr 20, 21:02:39, riveravaldez wrote:
Strangely, 'speaker-test -c2' doesn't produce a sound. But 'sudo
speaker-test -c2' works flawlessly. (The idea to check that came from
On 4/12/20, riveravaldez wrote:
> On 4/12/20, Andrei POPESCU wrote:
>> On Sb, 11 apr 20, 21:02:39, riveravaldez wrote:
>>>
>>> Strangely, 'speaker-test -c2' doesn't produce a sound. But 'sudo
>>> speaker-test -c2' works flawlessly. (The idea to check that came from
>>> [1].)
>>
>> Some program
On Du, 12 apr 20, 11:39:52, riveravaldez wrote:
>
> $ groups
> thinkpad cdrom floppy sudo audio dip video plugdev netdev
Ok.
> $ speaker-test -c2 [Still not sound.]
And no error...
> $ sudo speaker-test -c2 [Sounds OK.]
That would indicate that sound is handled differently for the regular
On 4/12/20, deloptes wrote:
> riveravaldez wrote:
>
>> But this not, even as sudo (and the error is similar to JACK one):
>> $ aplay -vv -D front:CARD=PCH,DEV=0 /usr/share/sounds/alsa/Noise.wav
>> aplay: main:830: audio open error: Device or resource bussy
>
> aplay -vv -D plughw:CARD=PCH,DEV=0
On 4/12/20, Andrei POPESCU wrote:
> On Sb, 11 apr 20, 21:02:39, riveravaldez wrote:
>>
>> Strangely, 'speaker-test -c2' doesn't produce a sound. But 'sudo
>> speaker-test -c2' works flawlessly. (The idea to check that came from
>> [1].)
>
> Any error message? Is your user a member of group
riveravaldez wrote:
> But this not, even as sudo (and the error is similar to JACK one):
> $ aplay -vv -D front:CARD=PCH,DEV=0 /usr/share/sounds/alsa/Noise.wav
> aplay: main:830: audio open error: Device or resource bussy
aplay -vv -D plughw:CARD=PCH,DEV=0 /usr/share/sounds/alsa/Noise.wav
read
On Sb, 11 apr 20, 21:02:39, riveravaldez wrote:
>
> Strangely, 'speaker-test -c2' doesn't produce a sound. But 'sudo
> speaker-test -c2' works flawlessly. (The idea to check that came from
> [1].)
Any error message? Is your user a member of group 'audio'?
Some program might be blocking the
On 4/11/20, riveravaldez wrote:
> On 4/11/20, riveravaldez wrote:
>> Hi,
>>
>> I would like to know what's the proper way to solve this. I'm on an
>> updated debian-testing installation (with pulseaudio installed and
>> working, but the problem seems to be previous, i.e., in ALSA, because
>>
On 4/11/20, riveravaldez wrote:
> Hi,
>
> I would like to know what's the proper way to solve this. I'm on an
> updated debian-testing installation (with pulseaudio installed and
> working, but the problem seems to be previous, i.e., in ALSA, because
> pavucontrol doesn't show the soundcard in
Hi,
I would like to know what's the proper way to solve this. I'm on an
updated debian-testing installation (with pulseaudio installed and
working, but the problem seems to be previous, i.e., in ALSA, because
pavucontrol doesn't show the soundcard in its correspondent tab).
I can get audio from
11 matches
Mail list logo
