Hi thanks for the bug report.

If you add your user to the sound group, does it work ?

I'm add user to all group, log out, log in and it's the same problem.


Maybe this is a problem with the kernel 3.2.{0,1}?
I have:
$ cat /etc/issue
Mageia release 1 (Official) for x86_64
Kernel 3.1.4-desktop-1.mga1 on a Dual-processor x86_64 / \l
$
and alsamixer works. Kernel 3.1.4-desktop-1.mga1 is from kernel-3.1.4-1.mga2.src.rpm.
But build kernel 3.2.0 (kernel-3.2.0-1.mga2.src.rpm) on Mga1, I had the same problem with alsamixer.

What user are you running alsamixer with?

Keep in mind that running a raw alsamixer (without any -c argument) will be connecting to pulseaudio. Normally PA will try and autospawn but there are some circumstances when this will not happen.

So please do try to the following:

1. whoami
2. id
3. systemd-loginctl
4. ck-list-sessions
5. ps aux | grep pulse
6. pactl stat
7. ls -l /etc/pulse/
8. ls -l ~/.pulse/
9. cat /proc/asound/cards
10. xprop -root | grep PULSE | grep -v COOKIE

(all of the above should really be done by a regular user, nothing needs to be done as root).

Status: NEW => ASSIGNED

Long shot, but this may be somewhat related to #4134 (I doesn't really have the same symptoms but worth mentioning just in case).

I had an update today (list rpms of update: http://fpaste.org/cEOH/ ) and alsamixer works.
Thank you!

Can you confirm that your user is no longer in the "audio" group? If your user is in this group, please remove him, and reboot. Does everything still work? If so, then please let us know and close this bug. Thanks

uid=1101(marcin) gid=81(audio) "grupy=81(audio),0(root),1(bin),2(daemon),3(sys),4(adm),5(tty),6(disk),7(lp),8(mem),9(kmem),10(wheel),12(mail),13(news),14(uucp),15(man),19(floppy),20(games),21(tape),22(cdrom),24(utmp),25(shadow),26(chkpwd),27(auth),43(usb),80(cdwriter),82(video),83(dialout),96(hsqldb),100(users),418(ntp),419(smmsp),420(mailnull),421(machines),483(toruser),484(lpadmin),485(usbmux),486(mysql),487(rtkit),488(gdm),489(mlocate),490(ctools),491(ntools),492(xgrp),493(haldaemon),494(polkituser),495(vcsa),496(avahi-autoipd),497(avahi),498(messagebus),499(rpm),501(vboxusers),65534(nogroup)"
Alsamixer works."

"uid=1101(marcin) gid=4(adm) grupy=4(adm),0(root),1(bin),2(daemon),3(sys),5(tty),6(disk),7(lp),8(mem),9(kmem),10(wheel),12(mail),13(news),14(uucp),15(man),19(floppy),20(games),21(tape),22(cdrom),24(utmp),25(shadow),26(chkpwd),27(auth),43(usb),80(cdwriter),82(video),83(dialout),96(hsqldb),100(users),418(ntp),419(smmsp),420(mailnull),421(machines),483(toruser),484(lpadmin),485(usbmux),486(mysql),487(rtkit),488(gdm),489(mlocate),490(ctools),491(ntools),492(xgrp),493(haldaemon),494(polkituser),495(vcsa),496(avahi-autoipd),497(avahi),498(messagebus),499(rpm),501(vboxusers),65534(nogroup)"
Alsamixer works.

Please do not close temporarily this bug.
I would like to check whether the installation Mga2 beta3 (environment: LXDE) on Virutalbox and update rpms will be the same problem.

Wow, your user is in a *lot* of groups! Why do you add your user to such groups? ACL systems in place should ensure that you don't need the vast majority of those groups... some are even a security issue. A standard login should work with your user in no groups at all (other than the private group created automatically specifically for that user (i.e you should have a marcin group)).

If you do not have specific need to add your user to all those groups, you should definitely remove them.

Thanks for the explanation. This user is only for test.
I made a mistake in comment 7: Mga2 beta3 -> Mga2 alpha3
On Virtualbox is ok ( http://www.fotosik.pl/pokaz_obrazek/pelny/b507dfb563d57f88.html ), so you can close this bug.

Status: ASSIGNED => RESOLVED
Resolution: (none) => FIXED