[Pkg-alsa-devel] Bug#578668: Bug#578668: alsa-utils: most of volume management keys in alsamixer are not working

[Gennady Kupava]

[added correct destination]

В Срд, 21/04/2010 в 19:53 +0200, Elimar Riesebieter пишет:
> tags 578668 unreproducible
> thanks
> 
> * Gennady Kupava [100421 19:25 +0400]
> > Package: alsa-utils
> > Version: 1.0.22-1
> > Severity: important
> > 
> > In alsamixer, keys q,w,e,z,x,c,[arrow up], [arrow down] are not
> > working for me (this continues for > 1 month), while 1,2,3,4... 0
> > are ok, amixer sset is ok also.
> > 
> > This is extermly annoying, as I my sound system is regulated in
> > range of 0.5-10% while 10% is very loud.
> 
> 
> AlsaMixer v1.0.22: Works fine here. I can't reproduce on amd64, i386
> and ppc.
> 
> BTW the keys are: QWEZXC and not qwezxc
> Press <F1> in alsaxixer for an overview.
> 
> Elimar
> 

Why this is bug not wrong setup: That should i do with alsamixer to have
1,2,3 working (sets 10%, 20% and so volume) and [arrow up] do not? 

About keys case: And keys always were in both lower and upper case (also
checked alsamixer 1.0.16 on i386), lower - faster, upper - slower tuning
in 1.0.16.

About reproduction:

I downgraded to 1.0.16-2 and everything started to work. Upgraded back
to 1.0.22-11 and hit bug again.

I setup pulseaudio tcp server on snd-dummy sound card on client machine
and got same problem.

While changing volume on dummy card all keys are working perfectly
[switching with that new F6 key in alsamixer].

HOW TO REPRODUCE:
I think to reproduce it you should setup pulseaudio over network. Mb
some other cases exist.

on server, apt-get install pulseaudio. (i am using debian/stable/i386)

in following description server is 192.168.0.1, client is 192.168.0.2

Use following config for server (only changed parts):
/etc/default/daemon.conf:
system-instance = yes
resample-method = speex-float-3
daemonize = yes

FOR 'STABLE' PULSEAUDIO: /etc/pulse/default.pa (only important parts):
load-module module-alsa-sink plughw:0,0
load-module module-native-protocol-tcp auth-ip-acl=192.168.0.1/24

OR FOR 'TESTING' PULSEAUDIO (notice file name): /etc/pulse/system.pa
(only important parts):
load-module module-alsa-sink plughw:0,0
ADD FOLLOWING: load-module module-native-protocol-tcp
auth-ip-acl=192.168.0.1/24

on server enable daemon in /etc/default/pulseaudio set:
PULSEAUDIO_SYSTEM_START=1

then start server /etc/init.d/pulseaudio restart. wait 1 min and check
if it is still around and on tcp:

work:/home/gena# netstat -atnp |grep pulse
tcp 0 0 0.0.0.0:4713 0.0.0.0:* LISTEN 7923/pulseaudio 

if not, run without daemon command-line with --daemonize=no and -v
options to see why he is died.

on client (under any user):
$ cat > ~/.asoundrc:
pcm.!default {
        type pulse
        server 192.168.0.1
}

ctl.!default {
    type pulse
    server 192.168.0.1
}

this will make remote tcp pulse server default alsa card for playing and
for volume changing.

on client apt-get install libasound2-plugins,

now run alsamixer on client under same user -> you should hit bug. 

I got this few moths ago, I just didn't report it as i thought it were
already reported.

Hope this way you'll be able to reproduce it.

While testing i also hit other bug on arm/sid, which worked some time
ago, so i unable to test this issue where...

I had to add that this related to pulse to header, but didn't understand
in time that i can simple check if problem exist on dummy card
controls...

And thanks for doing Debian!