Re: ?? user in group audio -- but only root can play sound

[Gene Heskett]

On Friday 22 January 2016 14:52:35 Floris wrote:

> Op Fri, 22 Jan 2016 15:40:01 +0100 schreef Gene Heskett
>
> :
> >> > 2.
> >> > Move the unwanted soundcard to an empty seat:
> >> > find your card location with:
> >> > $ loginctl seat-status seat0
> >
> > That command does not exist on wheezy.  Sounds useful, what repo
> > option do I need to enable to get it?
>
> loginctl is part of systemd
>
> Floris

Ahh, that explains that. And I'm stuck on wheezy until the LinuxCNC folks 
get around to rebasing it on a newer release.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 

Re: ?? user in group audio -- but only root can play sound

[Floris]

Op Fri, 22 Jan 2016 15:40:01 +0100 schreef Gene Heskett  
:



>
> 2.
> Move the unwanted soundcard to an empty seat:
> find your card location with:
> $ loginctl seat-status seat0


That command does not exist on wheezy.  Sounds useful, what repo option
do I need to enable to get it?



loginctl is part of systemd

Floris

Re: ?? user in group audio -- but only root can play sound

[Ric Moore]

On 01/22/2016 11:10 AM, Jude DaShiell wrote:


One thing udev or the linux kernel is going to have to get over fast is
its fixation on the 3.5MM jack for speakers.  Newer hardware sooner
rather than later will not be including those jacks any longer.
Probably the first noticeable instance will be Apple and what Apple does
with its next generation of iPhones but we shall know better when those
come out.


I now use only USB for audio, a pair of USB headphones with a mike, and 
a 7.1 USB audio device to rattle the house with. Life is SO much easier 
now. :) Ric



--
My father, Victor Moore (Vic) used to say:
"There are two Great Sins in the world...
..the Sin of Ignorance, and the Sin of Stupidity.
Only the former may be overcome." R.I.P. Dad.
http://linuxcounter.net/user/44256.html

Re: ?? user in group audio -- but only root can play sound

[Jude DaShiell]

On Fri, 22 Jan 2016, to...@tuxteam.de wrote:


Date: Fri, 22 Jan 2016 09:13:17
From: to...@tuxteam.de
To: debian-user@lists.debian.org
Subject: Re: ?? user in group audio -- but only root can play sound
Resent-Date: Fri, 22 Jan 2016 14:48:14 + (UTC)
Resent-From: debian-user@lists.debian.org

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Fri, Jan 22, 2016 at 09:40:01AM -0500, Gene Heskett wrote:

On Friday 22 January 2016 07:44:49 Jude DaShiell wrote:


That has to be done inside of udev, udev is the one ring that binds
them all.


Not nesessarily. When I rebooted sometime in late December, apparently a
udev update had decided that only root could use /dev/ttyUSB0 [...]



So I got out a root copy of nano, and put the fix in /etc/r.local [...]



And heyu is now a happy camper again.

Sure, someone is going to yell at me [...]


Hey, I for one am not going to. And if anyone does, send them to me: I'm
a member of the RightsToRoot movement and will take care of that :-)

After all we bought free software in order to tinker with it.

Regards
- -- tom?s
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlaiOP0ACgkQBcgs9XrR2kbd+wCfWh9ytSbVThLpESdUIaLqqnEB
/xAAn2jfQGQTi6Xo6BQLDGHjv5L1UdDQ
=Muz6
-END PGP SIGNATURE-

One thing udev or the linux kernel is going to have to get over fast is 
its fixation on the 3.5MM jack for speakers.  Newer hardware sooner 
rather than later will not be including those jacks any longer.  Probably 
the first noticeable instance will be Apple and what Apple does with its 
next generation of iPhones but we shall know better when those come out.






--

Re: ?? user in group audio -- but only root can play sound

[tomas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Fri, Jan 22, 2016 at 09:40:01AM -0500, Gene Heskett wrote:
> On Friday 22 January 2016 07:44:49 Jude DaShiell wrote:
> 
> > That has to be done inside of udev, udev is the one ring that binds
> > them all.
> >
> Not nesessarily. When I rebooted sometime in late December, apparently a 
> udev update had decided that only root could use /dev/ttyUSB0 [...]

> So I got out a root copy of nano, and put the fix in /etc/r.local [...]

> And heyu is now a happy camper again.
>  
> Sure, someone is going to yell at me [...]

Hey, I for one am not going to. And if anyone does, send them to me: I'm
a member of the RightsToRoot movement and will take care of that :-)

After all we bought free software in order to tinker with it.

Regards
- -- tomás
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlaiOP0ACgkQBcgs9XrR2kbd+wCfWh9ytSbVThLpESdUIaLqqnEB
/xAAn2jfQGQTi6Xo6BQLDGHjv5L1UdDQ
=Muz6
-END PGP SIGNATURE-

Re: ?? user in group audio -- but only root can play sound

[Gene Heskett]

On Friday 22 January 2016 09:40:01 Gene Heskett wrote:

> On Friday 22 January 2016 07:44:49 Jude DaShiell wrote:
> > That has to be done inside of udev, udev is the one ring that binds
> > them all.
>
> Not nesessarily. When I rebooted sometime in late December, apparently
> a udev update had decided that only root could use /dev/ttyUSB0 which
> is connected to my cl11a, a programable X10 controller. I was un-aware
correction, s/cl11a/cm11a/g  Ancient fingers.
> of it until a cron script that fires at 1 minute after midnight on 1 1
> 1 whatever, couldn't upload the next years schedule for my front deck
> lights and cron sent me an email saying it had no permission.  It has
> only been working for 17 years folks.
>
> I snooped thru the udev stuff without finding a specific rule
> for /dev/ttyUSB*, and as that it the only device discovered at boot, I
> couldn't compare it to /dev/ttyUSB1.
>
> So I got out a root copy of nano, and put the fix in /etc/r.local,
> which runs last at bootup, to readjust the ownership and rights to
> that device.  Now it looks like this:
>
> crwxr-xr-x 1 gene gene 188, 0 Jan 22 08:07 /dev/ttyUSB0
>
> And heyu is now a happy camper again.
>
> Sure, someone is going to yell at me, but I built this box for ME to
> use, and if its capable of doing a job, having some paranoid person
> decide I can't use it like that, sucks dead toads thru soda straws,
> and tastes about the same.
>
> We, the users, buy or build the machine to USE and we WILL use it s/b
> the message to whomever is in charge of udev presently.
>
> My $0.02 USD, but adjust for inflation over the last 81 years...
>
> > On Fri, 22 Jan 2016, Floris wrote:
> > > Date: Fri, 22 Jan 2016 04:22:50
> > > From: Floris 
> > > To: debian-user@lists.debian.org
> > > Subject: Re: ?? user in group audio -- but only root can play
> > > sound Resent-Date: Fri, 22 Jan 2016 09:23:08 + (UTC)
> > > Resent-From: debian-user@lists.debian.org
> > >
> > > Op Fri, 22 Jan 2016 00:10:27 +0100 schreef Jude DaShiell
> > >
> > > :
> > >> udev may be having adverse impacts on abilities to play sounds
> > >> from certain cards after reboot.  Anyone interested may find
> > >> sound devices in black listed category they don't want to have
> > >> black listed.  Correcting such black listing for now is beyond my
> > >> capability since I haven't done enough with udev to be safe
> > >> working with ityet.
> > >>
> > >>>> Sorry, now I see you have multiple sound cards.
> > >>>
> > >>> My fault I should have mentioned it, sorry:  That's it!
> > >>>
> > >>>
> > >>> Since 2015-12-11 my /etc/modprobe/alsa-base.conf ist:
> > >>> # PCH
> > >>> options snd-hda-intel index=0 model=auto vid=8086 pid=9c20
> > >>> # HDMI
> > >>> options snd-hda-intel index=1 model=auto vid=8086 pid=0a0c
> > >>>
> > >>> this is (if I remember correctly) from Arch wiki and should
> > >>> provide a numbering of sound devices such that the analog device
> > >>> becomes default (first one).  Since then I could hear music,
> > >>> hear sound from movies but only till a week ago.
> > >>>
> > >>>
> > >>> If I delete this file and reboot, the numbering of devices is:
> > >>>
> > >>>  List of PLAYBACK Hardware Devices 
> > >>> card 0: HDMI [HDA Intel HDMI], device 3: HDMI 0 [HDMI 0]
> > >>> Subdevices: 1/1
> > >>> Subdevice #0: subdevice #0
> > >>> card 0: HDMI [HDA Intel HDMI], device 7: HDMI 1 [HDMI 1]
> > >>> Subdevices: 1/1
> > >>> Subdevice #0: subdevice #0
> > >>> card 0: HDMI [HDA Intel HDMI], device 8: HDMI 2 [HDMI 2]
> > >>> Subdevices: 1/1
> > >>> Subdevice #0: subdevice #0
> > >>> card 1: PCH [HDA Intel PCH], device 0: ALC3232 Analog [ALC3232
> > >>> Analog] Subdevices: 1/1
> > >>> Subdevice #0: subdevice #0
> > >>>
> > >>> Now mplayer -ao alsa:device=hw=1.0 works but aplay wav still
> > >>> does not, mplayer does not without the command line switch and
> > >>> interestingly mpd still works.
> > >>>
> > >>> How to tell linux that the analog device is the default device?
> > >>> (I'll come back to this mailing list when I actually want to
> > >>> hear sound t

Re: ?? user in group audio -- but only root can play sound

[Gene Heskett]

On Friday 22 January 2016 07:44:49 Jude DaShiell wrote:

> That has to be done inside of udev, udev is the one ring that binds
> them all.
>
Not nesessarily. When I rebooted sometime in late December, apparently a 
udev update had decided that only root could use /dev/ttyUSB0 which is 
connected to my cl11a, a programable X10 controller. I was un-aware of 
it until a cron script that fires at 1 minute after midnight on 1 1 1 
whatever, couldn't upload the next years schedule for my front deck 
lights and cron sent me an email saying it had no permission.  It has 
only been working for 17 years folks.

I snooped thru the udev stuff without finding a specific rule 
for /dev/ttyUSB*, and as that it the only device discovered at boot, I 
couldn't compare it to /dev/ttyUSB1.

So I got out a root copy of nano, and put the fix in /etc/r.local, which 
runs last at bootup, to readjust the ownership and rights to that 
device.  Now it looks like this:

crwxr-xr-x 1 gene gene 188, 0 Jan 22 08:07 /dev/ttyUSB0

And heyu is now a happy camper again.
 
Sure, someone is going to yell at me, but I built this box for ME to use, 
and if its capable of doing a job, having some paranoid person decide I 
can't use it like that, sucks dead toads thru soda straws, and tastes 
about the same.

We, the users, buy or build the machine to USE and we WILL use it s/b the 
message to whomever is in charge of udev presently.

My $0.02 USD, but adjust for inflation over the last 81 years...

> On Fri, 22 Jan 2016, Floris wrote:
> > Date: Fri, 22 Jan 2016 04:22:50
> > From: Floris 
> > To: debian-user@lists.debian.org
> > Subject: Re: ?? user in group audio -- but only root can play sound
> > Resent-Date: Fri, 22 Jan 2016 09:23:08 + (UTC)
> > Resent-From: debian-user@lists.debian.org
> >
> > Op Fri, 22 Jan 2016 00:10:27 +0100 schreef Jude DaShiell
> >
> > :
> >> udev may be having adverse impacts on abilities to play sounds from
> >> certain cards after reboot.  Anyone interested may find sound
> >> devices in black listed category they don't want to have black
> >> listed.  Correcting such black listing for now is beyond my
> >> capability since I haven't done enough with udev to be safe working
> >> with ityet.
> >>
> >>>> Sorry, now I see you have multiple sound cards.
> >>>
> >>> My fault I should have mentioned it, sorry:  That's it!
> >>>
> >>>
> >>> Since 2015-12-11 my /etc/modprobe/alsa-base.conf ist:
> >>> # PCH
> >>> options snd-hda-intel index=0 model=auto vid=8086 pid=9c20
> >>> # HDMI
> >>> options snd-hda-intel index=1 model=auto vid=8086 pid=0a0c
> >>>
> >>> this is (if I remember correctly) from Arch wiki and should
> >>> provide a numbering of sound devices such that the analog device
> >>> becomes default (first one).  Since then I could hear music, hear
> >>> sound from movies but only till a week ago.
> >>>
> >>>
> >>> If I delete this file and reboot, the numbering of devices is:
> >>>
> >>>  List of PLAYBACK Hardware Devices 
> >>> card 0: HDMI [HDA Intel HDMI], device 3: HDMI 0 [HDMI 0]
> >>> Subdevices: 1/1
> >>> Subdevice #0: subdevice #0
> >>> card 0: HDMI [HDA Intel HDMI], device 7: HDMI 1 [HDMI 1]
> >>> Subdevices: 1/1
> >>> Subdevice #0: subdevice #0
> >>> card 0: HDMI [HDA Intel HDMI], device 8: HDMI 2 [HDMI 2]
> >>> Subdevices: 1/1
> >>> Subdevice #0: subdevice #0
> >>> card 1: PCH [HDA Intel PCH], device 0: ALC3232 Analog [ALC3232
> >>> Analog] Subdevices: 1/1
> >>> Subdevice #0: subdevice #0
> >>>
> >>> Now mplayer -ao alsa:device=hw=1.0 works but aplay wav still does
> >>> not, mplayer does not without the command line switch and
> >>> interestingly mpd still works.
> >>>
> >>> How to tell linux that the analog device is the default device?
> >>> (I'll come back to this mailing list when I actually want to hear
> >>> sound through the HDMI device).
> >>>
> >>>
> >>>
> >>> Thanks a lot!  This at least gives an explanation!
> >>>
> >>> Ciao; Gregor
> >
> > 3 Options:
> >
> > 1.
> > from http://alsa.opensrc.org/MultipleCards:
> >
> > ...
> > The newer "slots=" method
> >
> > Alternatively, you can use the slot option instead of the index
> > options: options snd slots=snd-interwave,snd-ens1371
> >
&g

Re: ?? user in group audio -- but only root can play sound

[Jude DaShiell]

That has to be done inside of udev, udev is the one ring that binds them 
all.


On Fri, 22 Jan 2016, Floris wrote:


Date: Fri, 22 Jan 2016 04:22:50
From: Floris 
To: debian-user@lists.debian.org
Subject: Re: ?? user in group audio -- but only root can play sound
Resent-Date: Fri, 22 Jan 2016 09:23:08 + (UTC)
Resent-From: debian-user@lists.debian.org

Op Fri, 22 Jan 2016 00:10:27 +0100 schreef Jude DaShiell 
:


udev may be having adverse impacts on abilities to play sounds from certain 
cards after reboot.  Anyone interested may find sound devices in black 
listed category they don't want to have black listed.  Correcting such 
black listing for now is beyond my capability since I haven't done enough 
with udev to be safe working with ityet.








Sorry, now I see you have multiple sound cards.


My fault I should have mentioned it, sorry:  That's it!




Since 2015-12-11 my /etc/modprobe/alsa-base.conf ist:
# PCH
options snd-hda-intel index=0 model=auto vid=8086 pid=9c20
# HDMI
options snd-hda-intel index=1 model=auto vid=8086 pid=0a0c

this is (if I remember correctly) from Arch wiki and should
provide a numbering of sound devices such that the analog device
becomes default (first one).  Since then I could hear music, hear
sound from movies but only till a week ago.


If I delete this file and reboot, the numbering of devices is:

 List of PLAYBACK Hardware Devices 
card 0: HDMI [HDA Intel HDMI], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: HDMI [HDA Intel HDMI], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: HDMI [HDA Intel HDMI], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: PCH [HDA Intel PCH], device 0: ALC3232 Analog [ALC3232 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0

Now mplayer -ao alsa:device=hw=1.0 works but aplay wav still does
not, mplayer does not without the command line switch and
interestingly mpd still works.

How to tell linux that the analog device is the default device?
(I'll come back to this mailing list when I actually want to hear
sound through the HDMI device).



Thanks a lot!  This at least gives an explanation!

Ciao; Gregor






3 Options:

1.
from http://alsa.opensrc.org/MultipleCards:

...
The newer "slots=" method

Alternatively, you can use the slot option instead of the index options:
options snd slots=snd-interwave,snd-ens1371

Then, the first slot (#0) is reserved for snd-interwave driver, and the 
second (#1) for snd-ens1371. You can omit index option in each driver if 
slots option is used (although you can still have them at the same time as 
long as they don't conflict).

...

2.
Move the unwanted soundcard to an empty seat:
find your card location with:
$ loginctl seat-status seat0

[long list]
...
/sys/devices/pci:00/:00:1b.0/sound/card0
...
[long list]

Attach the card to an other seat:
sudo loginctl attach seat1 /sys/devices/pci:00/:00:1b.0/sound/card0

Now you can only use the card when you login on seat1, but as long as you 
don't
attach a monitor, mouse and keyboard, the seat won't work. Note root can 
still

access the card as all users in the audio group can. (That why I asked you to
remove yourself from the audio group)

3.
Blacklist the module, so nobody can access the card.



--

Re: ?? user in group audio -- but only root can play sound

[Floris]

Op Fri, 22 Jan 2016 00:10:27 +0100 schreef Jude DaShiell  
:


udev may be having adverse impacts on abilities to play sounds from  
certain cards after reboot.  Anyone interested may find sound devices in  
black listed category they don't want to have black listed.  Correcting  
such black listing for now is beyond my capability since I haven't done  
enough with udev to be safe working with ityet.








Sorry, now I see you have multiple sound cards.


My fault I should have mentioned it, sorry:  That's it!




Since 2015-12-11 my /etc/modprobe/alsa-base.conf ist:
# PCH
options snd-hda-intel index=0 model=auto vid=8086 pid=9c20
# HDMI
options snd-hda-intel index=1 model=auto vid=8086 pid=0a0c

this is (if I remember correctly) from Arch wiki and should
provide a numbering of sound devices such that the analog device
becomes default (first one).  Since then I could hear music, hear
sound from movies but only till a week ago.


If I delete this file and reboot, the numbering of devices is:

 List of PLAYBACK Hardware Devices 
card 0: HDMI [HDA Intel HDMI], device 3: HDMI 0 [HDMI 0]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
card 0: HDMI [HDA Intel HDMI], device 7: HDMI 1 [HDMI 1]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
card 0: HDMI [HDA Intel HDMI], device 8: HDMI 2 [HDMI 2]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
card 1: PCH [HDA Intel PCH], device 0: ALC3232 Analog [ALC3232 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0

Now mplayer -ao alsa:device=hw=1.0 works but aplay wav still does
not, mplayer does not without the command line switch and
interestingly mpd still works.

How to tell linux that the analog device is the default device?
(I'll come back to this mailing list when I actually want to hear
sound through the HDMI device).



Thanks a lot!  This at least gives an explanation!

Ciao; Gregor






3 Options:

1.
from http://alsa.opensrc.org/MultipleCards:

...
The newer "slots=" method

Alternatively, you can use the slot option instead of the index options:
options snd slots=snd-interwave,snd-ens1371

Then, the first slot (#0) is reserved for snd-interwave driver, and the  
second (#1) for snd-ens1371. You can omit index option in each driver if  
slots option is used (although you can still have them at the same time as  
long as they don't conflict).

...

2.
Move the unwanted soundcard to an empty seat:
find your card location with:
$ loginctl seat-status seat0

[long list]
...
/sys/devices/pci:00/:00:1b.0/sound/card0
...
[long list]

Attach the card to an other seat:
sudo loginctl attach seat1 /sys/devices/pci:00/:00:1b.0/sound/card0

Now you can only use the card when you login on seat1, but as long as you  
don't
attach a monitor, mouse and keyboard, the seat won't work. Note root can  
still
access the card as all users in the audio group can. (That why I asked you  
to

remove yourself from the audio group)

3.
Blacklist the module, so nobody can access the card.

Re: ?? user in group audio -- but only root can play sound

[Jude DaShiell]

udev may be having adverse impacts on abilities to play sounds from 
certain cards after reboot.  Anyone interested may find sound devices in 
black listed category they don't want to have black listed.  Correcting 
such black listing for now is beyond my capability since I haven't done 
enough with udev to be safe working with ityet.


On Fri, 22 Jan 2016, Gregor Zattler wrote:


Date: Thu, 21 Jan 2016 18:03:52
From: Gregor Zattler 
To: debian-user 
Subject: Re: ?? user in group audio -- but only root can play sound
Resent-Date: Thu, 21 Jan 2016 23:04:43 + (UTC)
Resent-From: debian-user@lists.debian.org

Hi Floris, debian users,
* Floris  [21. Jan. 2016]:

Op Thu, 21 Jan 2016 20:32:21 +0100 schreef Gregor Zattler
:


since a few days my normal user, which is in group sound, cannot
play sound (aplay works but no sound) while root can.


[...]

You are right, the right permissions are set.

Do you have an .asoundrc file in your home directory?

If you have one remove it.
and try aplay again

If you doesn't have one create one with:

pcm.pulse {
   type pulse
}

ctl.pulse {
   type pulse
}

and try
aplay -Dpulse foo.wav


There was no ~/.asoundrc.  I filled one with your example and
tried aplay -D pulse ...  --> no sound


success,


this would be fine :-)



Sorry, now I see you have multiple sound cards.


My fault I should have mentioned it, sorry:  That's it!


use aplay -l to show all your cards


mine is

$ aplay -l
 List of PLAYBACK Hardware Devices 
card 0: PCH [HDA Intel PCH], device 0: ALC3232 Analog [ALC3232 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
card 1: HDMI [HDA Intel HDMI], device 3: HDMI 0 [HDMI 0]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
card 1: HDMI [HDA Intel HDMI], device 7: HDMI 1 [HDMI 1]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
card 1: HDMI [HDA Intel HDMI], device 8: HDMI 2 [HDMI 2]
 Subdevices: 1/1
 Subdevice #0: subdevice #0


Then test them with:
$ mplayer -ao alsa:device=hw=0.0 some-music-file
and change 0.0 to your cards. The first 0 is the card number, the second the
device number.
So I can test 0.0, 0.2, 0.3 and 3.0 and replace some-music-file with your
own music.
 / and * controls the volume

Is there sound on any of the devices?


The analog device is the very first.

mplayer  -ao alsa:device=hw=0.0 

plays sound and I hear it.

I know there are several soundcards.  Therefore I had played with
aplay-l and aplay -D but did not manage to select the device with
aplay -D 0.0.

Since 2015-12-11 my /etc/modprobe/alsa-base.conf ist:
# PCH
options snd-hda-intel index=0 model=auto vid=8086 pid=9c20
# HDMI
options snd-hda-intel index=1 model=auto vid=8086 pid=0a0c

this is (if I remember correctly) from Arch wiki and should
provide a numbering of sound devices such that the analog device
becomes default (first one).  Since then I could hear music, hear
sound from movies but only till a week ago.


If I delete this file and reboot, the numbering of devices is:

 List of PLAYBACK Hardware Devices 
card 0: HDMI [HDA Intel HDMI], device 3: HDMI 0 [HDMI 0]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
card 0: HDMI [HDA Intel HDMI], device 7: HDMI 1 [HDMI 1]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
card 0: HDMI [HDA Intel HDMI], device 8: HDMI 2 [HDMI 2]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
card 1: PCH [HDA Intel PCH], device 0: ALC3232 Analog [ALC3232 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0

Now mplayer -ao alsa:device=hw=1.0 works but aplay wav still does
not, mplayer does not without the command line switch and
interestingly mpd still works.

How to tell linux that the analog device is the default device?
(I'll come back to this mailing list when I actually want to hear
sound through the HDMI device).



Thanks a lot!  This at least gives an explanation!

Ciao; Gregor




--

Re: ?? user in group audio -- but only root can play sound

[Gregor Zattler]

Hi Floris, debian users,
* Floris  [21. Jan. 2016]:
> Op Thu, 21 Jan 2016 20:32:21 +0100 schreef Gregor Zattler
> :
> 
>>since a few days my normal user, which is in group sound, cannot
>>play sound (aplay works but no sound) while root can.
>>
[...]
>>>You are right, the right permissions are set.
>>>
>>>Do you have an .asoundrc file in your home directory?
>>>
>>>If you have one remove it.
>>>and try aplay again
>>>
>>>If you doesn't have one create one with:
>>>
>>>pcm.pulse {
>>>type pulse
>>>}
>>>
>>>ctl.pulse {
>>>type pulse
>>>}
>>>
>>>and try
>>>aplay -Dpulse foo.wav
>>
>>There was no ~/.asoundrc.  I filled one with your example and
>>tried aplay -D pulse ...  --> no sound
>>
>>>success,
>>
>>this would be fine :-)
>>
> 
> Sorry, now I see you have multiple sound cards.

My fault I should have mentioned it, sorry:  That's it!

> use aplay -l to show all your cards

mine is

$ aplay -l
 List of PLAYBACK Hardware Devices 
card 0: PCH [HDA Intel PCH], device 0: ALC3232 Analog [ALC3232 Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: HDMI [HDA Intel HDMI], device 3: HDMI 0 [HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: HDMI [HDA Intel HDMI], device 7: HDMI 1 [HDMI 1]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: HDMI [HDA Intel HDMI], device 8: HDMI 2 [HDMI 2]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

> Then test them with:
> $ mplayer -ao alsa:device=hw=0.0 some-music-file
> and change 0.0 to your cards. The first 0 is the card number, the second the
> device number.
> So I can test 0.0, 0.2, 0.3 and 3.0 and replace some-music-file with your
> own music.
>  / and * controls the volume
> 
> Is there sound on any of the devices?

The analog device is the very first.

mplayer  -ao alsa:device=hw=0.0 

plays sound and I hear it.

I know there are several soundcards.  Therefore I had played with
aplay-l and aplay -D but did not manage to select the device with
aplay -D 0.0.

Since 2015-12-11 my /etc/modprobe/alsa-base.conf ist:  
# PCH
options snd-hda-intel index=0 model=auto vid=8086 pid=9c20  
# HDMI
options snd-hda-intel index=1 model=auto vid=8086 pid=0a0c  

this is (if I remember correctly) from Arch wiki and should
provide a numbering of sound devices such that the analog device
becomes default (first one).  Since then I could hear music, hear
sound from movies but only till a week ago.


If I delete this file and reboot, the numbering of devices is:

 List of PLAYBACK Hardware Devices 
card 0: HDMI [HDA Intel HDMI], device 3: HDMI 0 [HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: HDMI [HDA Intel HDMI], device 7: HDMI 1 [HDMI 1]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: HDMI [HDA Intel HDMI], device 8: HDMI 2 [HDMI 2]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: PCH [HDA Intel PCH], device 0: ALC3232 Analog [ALC3232 Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

Now mplayer -ao alsa:device=hw=1.0 works but aplay wav still does
not, mplayer does not without the command line switch and
interestingly mpd still works.

How to tell linux that the analog device is the default device?
(I'll come back to this mailing list when I actually want to hear
sound through the HDMI device).



Thanks a lot!  This at least gives an explanation!

Ciao; Gregor 

Re: ?? user in group audio -- but only root can play sound

[Floris]

Op Thu, 21 Jan 2016 21:43:53 +0100 schreef Floris :

Op Thu, 21 Jan 2016 20:32:21 +0100 schreef Gregor Zattler  
:



since a few days my normal user, which is in group sound, cannot
play sound (aplay works but no sound) while root can.

Any ideas how to debug this?





In Debian Testing systemd takes care for setting the right rights
That is why you have a "+" at the end of the permissions.




What is the outcome of:

getfacl /dev/snd/hwC0D0


c$ getfacl /dev/snd/hwC0D0
getfacl: Removing leading '/' from absolute path names
# file: dev/snd/hwC0D0
# owner: root
# group: audio
user::rw-
user:grfz:rw-
group::rw-
mask::rw-
other::---

Did not know this command but output looks good to me.


You are right, the right permissions are set.

Do you have an .asoundrc file in your home directory?

If you have one remove it.
and try aplay again

If you doesn't have one create one with:

pcm.pulse {
type pulse
}

ctl.pulse {
type pulse
}

and try
aplay -Dpulse foo.wav


There was no ~/.asoundrc.  I filled one with your example and
tried aplay -D pulse ...  --> no sound


success,


this would be fine :-)



Sorry, now I see you have multiple sound cards.

use aplay -l to show all your cards

for example
 List of PLAYBACK Hardware Devices 
card 0: MID [HDA Intel MID], device 0: VT1828S Analog [VT1828S Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
card 0: MID [HDA Intel MID], device 2: VT1828S Alt Analog [VT1828S Alt  
Analog]

   Subdevices: 1/1
   Subdevice #0: subdevice #0
card 0: MID [HDA Intel MID], device 3: VT1828S Digital [VT1828S Digital]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
card 3: Speaker [Logitech USB Speaker], device 0: USB Audio [USB Audio]
   Subdevices: 1/1
   Subdevice #0: subdevice #0

Then test them with:
$ mplayer -ao alsa:device=hw=0.0 some-music-file
and change 0.0 to your cards. The first 0 is the card number, the second  
the device number.
So I can test 0.0, 0.2, 0.3 and 3.0 and replace some-music-file with  
your own music.

  / and * controls the volume

Is there sound on any of the devices?


Edit.

maybe you have only
==
Opening audio decoder: [mpg123] MPEG 1.0/2.0/2.5 layers I, II, III
AUDIO: 44100 Hz, 2 ch, s16le, 320.0 kbit/22.68% (ratio: 4->176400)
Selected audio codec: [mpg123] afm: mpg123 (MPEG 1.0/2.0/2.5 layers I, II,  
III)

==
AO: [alsa] 44100Hz 2ch s16le (2 bytes per sample)
Video: no video
Starting playback...
A:   3.0 (03.0) of 231.0 (03:51.0)  0.3%

and still no sound

Then (you can use an other terminal)
$ alsamixer
Use [F6] to select the right soundcard and make sure the volume levels are  
set to 100


Floris

Re: ?? user in group audio -- but only root can play sound

[tomas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Thu, Jan 21, 2016 at 04:56:31PM +0100, Gregor Zattler wrote:

[...]

> You are right of course.  play is an alias for sox on my system.
> They give different output on the terminal, but otherwise they
> behave the same: sound as root no sound as user.

perhaps you might want to try strace, redirecting output to a file,
like

  strace -f -o  play foo

once as normal user, once as root and try to compare the outputs
(the -f option is there for strace to follow child processes on
fork).

It'll be a lot of output, but perhaps you can spot some relevant
differences.

Regards
- -- tomás
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlahO04ACgkQBcgs9XrR2kbXUgCdHYkJR8JYBECKkdjfI6uMMfMh
Y04AnR93NLpfJbR8NDpgQ7eNRU+kYMey
=Ep59
-END PGP SIGNATURE-

Re: ?? user in group audio -- but only root can play sound

[Floris]

Op Thu, 21 Jan 2016 20:32:21 +0100 schreef Gregor Zattler  
:



since a few days my normal user, which is in group sound, cannot
play sound (aplay works but no sound) while root can.

Any ideas how to debug this?





In Debian Testing systemd takes care for setting the right rights
That is why you have a "+" at the end of the permissions.




What is the outcome of:

getfacl /dev/snd/hwC0D0


c$ getfacl /dev/snd/hwC0D0
getfacl: Removing leading '/' from absolute path names
# file: dev/snd/hwC0D0
# owner: root
# group: audio
user::rw-
user:grfz:rw-
group::rw-
mask::rw-
other::---

Did not know this command but output looks good to me.


You are right, the right permissions are set.

Do you have an .asoundrc file in your home directory?

If you have one remove it.
and try aplay again

If you doesn't have one create one with:

pcm.pulse {
type pulse
}

ctl.pulse {
type pulse
}

and try
aplay -Dpulse foo.wav


There was no ~/.asoundrc.  I filled one with your example and
tried aplay -D pulse ...  --> no sound


success,


this would be fine :-)



Sorry, now I see you have multiple sound cards.

use aplay -l to show all your cards

for example
 List of PLAYBACK Hardware Devices 
card 0: MID [HDA Intel MID], device 0: VT1828S Analog [VT1828S Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: MID [HDA Intel MID], device 2: VT1828S Alt Analog [VT1828S Alt  
Analog]

  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: MID [HDA Intel MID], device 3: VT1828S Digital [VT1828S Digital]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 3: Speaker [Logitech USB Speaker], device 0: USB Audio [USB Audio]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

Then test them with:
$ mplayer -ao alsa:device=hw=0.0 some-music-file
and change 0.0 to your cards. The first 0 is the card number, the second  
the device number.
So I can test 0.0, 0.2, 0.3 and 3.0 and replace some-music-file with your  
own music.

 / and * controls the volume

Is there sound on any of the devices?

Floris

Re: ?? user in group audio -- but only root can play sound

[Gregor Zattler]

Hi Floris, debian user,
* Floris  [21. Jan. 2016]:
> Op Thu, 21 Jan 2016 16:52:44 +0100 schreef Gregor Zattler
> :
>>* Floris  [21. Jan. 2016]:
>>>Op Sat, 16 Jan 2016 20:06:22 +0100 schreef Gregor Zattler
>>>:
since a few days my normal user, which is in group sound, cannot
play sound (aplay works but no sound) while root can.

Any ideas how to debug this?

This is a debian testing system with pulseaudio and mpd running.

/dev$ find |xargs ls -ld|grep audio
crw-rw+  1 root audio  14,   4 Jan 16 16:32 ./audio
lrwxrwxrwx   1 root root 8 Jan 16 16:32 ./char/14:4 ->
../audio
crw-rw+  1 root audio  14,   3 Jan 16 16:32 ./dsp
crw-rw+  1 root audio  14,   0 Jan 16 16:32 ./mixer
crw-rw+  1 root audio  14,  16 Jan 16 16:32 ./mixer1
crw-rw+  1 root audio 116,   2 Jan 16 16:32 ./snd/controlC0
crw-rw+  1 root audio 116,   6 Jan 16 16:32 ./snd/controlC1
crw-rw+  1 root audio 116,   5 Jan 16 16:32 ./snd/hwC0D0
crw-rw+  1 root audio 116,  10 Jan 16 16:32 ./snd/hwC1D0
crw-rw+  1 root audio 116,   4 Jan 16 19:27 ./snd/pcmC0D0c
crw-rw+  1 root audio 116,   3 Jan 16 19:52 ./snd/pcmC0D0p
crw-rw+  1 root audio 116,   7 Jan 16 19:52 ./snd/pcmC1D3p
crw-rw+  1 root audio 116,   8 Jan 16 19:27 ./snd/pcmC1D7p
crw-rw+  1 root audio 116,   9 Jan 16 19:27 ./snd/pcmC1D8p
crw-rw+  1 root audio 116,   1 Jan 16 16:32 ./snd/seq
crw-rw+  1 root audio 116,  33 Jan 16 16:32 ./snd/timer
>>
>>>Maybe it sounds odd, but does you have sound when you remove yourself
>>>form the audio group?
>>>
>>>In Debian Testing systemd takes care for setting the right rights
>>>That is why you have a "+" at the end of the permissions.
>>
>>Thanks for looking into this.  Actually I'm totally unaware of
>>all things systemd.  I heard sound when in group audio say two
>>weeks ago.
>>
>>Nonetheless I did a
>>
>>sudo delgroup grfz audio
>>
>>logged in on a VT, played a .wav file with aplay: No sound.
>>
>>
>>>What is the outcome of:
>>>
>>>getfacl /dev/snd/hwC0D0
>>
>>c$ getfacl /dev/snd/hwC0D0
>>getfacl: Removing leading '/' from absolute path names
>># file: dev/snd/hwC0D0
>># owner: root
>># group: audio
>>user::rw-
>>user:grfz:rw-
>>group::rw-
>>mask::rw-
>>other::---
>>
>>Did not know this command but output looks good to me.
>>
> You are right, the right permissions are set.
> 
> Do you have an .asoundrc file in your home directory?
> 
> If you have one remove it.
> and try aplay again
> 
> If you doesn't have one create one with:
> 
> pcm.pulse {
> type pulse
> }
> 
> ctl.pulse {
> type pulse
> }
> 
> and try
> aplay -Dpulse foo.wav

There was no ~/.asoundrc.  I filled one with your example and
tried aplay -D pulse ...  --> no sound

> success,

this would be fine :-)


I also looked into the systems log files:
/var/log$ sudo cat $(ls -1tr|tail -n 12)|grep "Jan 21 "  |egrep -i 
"so?u?nd|audio|pulse" |grep " 20:"

Jan 21 20:27:25 len kernel: [   12.357828] snd_hda_intel: unknown parameter 
'vid' ignored
Jan 21 20:27:25 len kernel: [   12.357901] snd_hda_intel: unknown parameter 
'pid' ignored
Jan 21 20:27:25 len kernel: [   12.357969] snd_hda_intel: unknown parameter 
'vid' ignored
Jan 21 20:27:25 len kernel: [   12.358036] snd_hda_intel: unknown parameter 
'pid' ignored
Jan 21 20:27:25 len kernel: [   12.375636] snd_hda_codec_realtek hdaudioC0D0: 
autoconfig for ALC3232: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
Jan 21 20:27:25 len kernel: [   12.375737] snd_hda_codec_realtek hdaudioC0D0:   
 speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
Jan 21 20:27:25 len kernel: [   12.375830] snd_hda_codec_realtek hdaudioC0D0:   
 hp_outs=2 (0x16/0x15/0x0/0x0/0x0)
Jan 21 20:27:25 len kernel: [   12.375917] snd_hda_codec_realtek hdaudioC0D0:   
 mono: mono_out=0x0
Jan 21 20:27:25 len kernel: [   12.375982] snd_hda_codec_realtek hdaudioC0D0:   
 inputs:
Jan 21 20:27:25 len kernel: [   12.376047] snd_hda_codec_realtek hdaudioC0D0:   
   Dock Mic=0x19
Jan 21 20:27:25 len kernel: [   12.376112] snd_hda_codec_realtek hdaudioC0D0:   
   Mic=0x1a
Jan 21 20:27:25 len kernel: [   12.376176] snd_hda_codec_realtek hdaudioC0D0:   
   Internal Mic=0x12
Jan 21 20:27:25 len kernel: [   12.410551] input: HDA Digital PCBeep as 
/devices/pci:00/:00:1b.0/sound/card0/input8
Jan 21 20:27:25 len kernel: [   12.412497] input: HDA Intel PCH Dock Mic as 
/devices/pci:00/:00:1b.0/sound/card0/input9
Jan 21 20:27:25 len kernel: [   12.412695] input: HDA Intel PCH Mic as 
/devices/pci:00/:00:1b.0/sound/card0/input10
Jan 21 20:27:25 len kernel: [   12.412780] input: HDA Intel PCH Dock Headphone 
as /devices/pci:00/:00:1b.0/sound/card0/input11
Jan 21 20:27:25 len kernel: [   12.412855] input: HDA Intel PCH Headphone as 
/devices/pci:00/:00:1b.0/sound/card0/input12
Jan 21 20:27:25 len kernel: [   12.498071] snd_hda_intel :00:03.

Re: ?? user in group audio -- but only root can play sound

[Floris]

Op Thu, 21 Jan 2016 16:52:44 +0100 schreef Gregor Zattler  
:



Hi Floris, debian user,
* Floris  [21. Jan. 2016]:

Op Sat, 16 Jan 2016 20:06:22 +0100 schreef Gregor Zattler
:

since a few days my normal user, which is in group sound, cannot
play sound (aplay works but no sound) while root can.

Any ideas how to debug this?

This is a debian testing system with pulseaudio and mpd running.

/dev$ find |xargs ls -ld|grep audio
crw-rw+  1 root audio  14,   4 Jan 16 16:32 ./audio
lrwxrwxrwx   1 root root 8 Jan 16 16:32 ./char/14:4 ->
../audio
crw-rw+  1 root audio  14,   3 Jan 16 16:32 ./dsp
crw-rw+  1 root audio  14,   0 Jan 16 16:32 ./mixer
crw-rw+  1 root audio  14,  16 Jan 16 16:32 ./mixer1
crw-rw+  1 root audio 116,   2 Jan 16 16:32 ./snd/controlC0
crw-rw+  1 root audio 116,   6 Jan 16 16:32 ./snd/controlC1
crw-rw+  1 root audio 116,   5 Jan 16 16:32 ./snd/hwC0D0
crw-rw+  1 root audio 116,  10 Jan 16 16:32 ./snd/hwC1D0
crw-rw+  1 root audio 116,   4 Jan 16 19:27 ./snd/pcmC0D0c
crw-rw+  1 root audio 116,   3 Jan 16 19:52 ./snd/pcmC0D0p
crw-rw+  1 root audio 116,   7 Jan 16 19:52 ./snd/pcmC1D3p
crw-rw+  1 root audio 116,   8 Jan 16 19:27 ./snd/pcmC1D7p
crw-rw+  1 root audio 116,   9 Jan 16 19:27 ./snd/pcmC1D8p
crw-rw+  1 root audio 116,   1 Jan 16 16:32 ./snd/seq
crw-rw+  1 root audio 116,  33 Jan 16 16:32 ./snd/timer



Maybe it sounds odd, but does you have sound when you remove yourself
form the audio group?

In Debian Testing systemd takes care for setting the right rights
That is why you have a "+" at the end of the permissions.


Thanks for looking into this.  Actually I'm totally unaware of
all things systemd.  I heard sound when in group audio say two
weeks ago.

Nonetheless I did a

sudo delgroup grfz audio

logged in on a VT, played a .wav file with aplay: No sound.



What is the outcome of:

getfacl /dev/snd/hwC0D0


c$ getfacl /dev/snd/hwC0D0
getfacl: Removing leading '/' from absolute path names
# file: dev/snd/hwC0D0
# owner: root
# group: audio
user::rw-
user:grfz:rw-
group::rw-
mask::rw-
other::---

Did not know this command but output looks good to me.


You are right, the right permissions are set.

Do you have an .asoundrc file in your home directory?

If you have one remove it.
and try aplay again

If you doesn't have one create one with:

pcm.pulse {
type pulse
}

ctl.pulse {
type pulse
}

and try
aplay -Dpulse foo.wav

success,

floris

Re: ?? user in group audio -- but only root can play sound

[Gregor Zattler]

Hi Chris,
* Chris Bannister  [20. Jan. 2016]:
> On Tue, Jan 19, 2016 at 06:28:17PM +0100, Gregor Zattler wrote:
>> Thinking about: mpd is also not in these groups and I can her
>> music.
>> 
>> So that's still not it.
>> 
>> When I play some sound, I see aplay working, but do not hear sound:
>> 
>>  $ play  /home/grfz/Downloads/tuxok.wav
> 
> Just as an aside, that is not the aplay command. Compare man aplay, and
> man play.

You are right of course.  play is an alias for sox on my system.
They give different output on the terminal, but otherwise they
behave the same: sound as root no sound as user.


Ciao, Gregor
-- 
 -... --- .-. . -.. ..--.. ...-.-

Re: ?? user in group audio -- but only root can play sound

[Gregor Zattler]

Hi Floris, debian user,
* Floris  [21. Jan. 2016]:
> Op Sat, 16 Jan 2016 20:06:22 +0100 schreef Gregor Zattler
> :
>>since a few days my normal user, which is in group sound, cannot
>>play sound (aplay works but no sound) while root can.
>>
>>Any ideas how to debug this?
>>
>>This is a debian testing system with pulseaudio and mpd running.
>>
>>/dev$ find |xargs ls -ld|grep audio
>>crw-rw+  1 root audio  14,   4 Jan 16 16:32 ./audio
>>lrwxrwxrwx   1 root root 8 Jan 16 16:32 ./char/14:4 ->
>>../audio
>>crw-rw+  1 root audio  14,   3 Jan 16 16:32 ./dsp
>>crw-rw+  1 root audio  14,   0 Jan 16 16:32 ./mixer
>>crw-rw+  1 root audio  14,  16 Jan 16 16:32 ./mixer1
>>crw-rw+  1 root audio 116,   2 Jan 16 16:32 ./snd/controlC0
>>crw-rw+  1 root audio 116,   6 Jan 16 16:32 ./snd/controlC1
>>crw-rw+  1 root audio 116,   5 Jan 16 16:32 ./snd/hwC0D0
>>crw-rw+  1 root audio 116,  10 Jan 16 16:32 ./snd/hwC1D0
>>crw-rw+  1 root audio 116,   4 Jan 16 19:27 ./snd/pcmC0D0c
>>crw-rw+  1 root audio 116,   3 Jan 16 19:52 ./snd/pcmC0D0p
>>crw-rw+  1 root audio 116,   7 Jan 16 19:52 ./snd/pcmC1D3p
>>crw-rw+  1 root audio 116,   8 Jan 16 19:27 ./snd/pcmC1D7p
>>crw-rw+  1 root audio 116,   9 Jan 16 19:27 ./snd/pcmC1D8p
>>crw-rw+  1 root audio 116,   1 Jan 16 16:32 ./snd/seq
>>crw-rw+  1 root audio 116,  33 Jan 16 16:32 ./snd/timer

> Maybe it sounds odd, but does you have sound when you remove yourself
> form the audio group?
>
> In Debian Testing systemd takes care for setting the right rights
> That is why you have a "+" at the end of the permissions.

Thanks for looking into this.  Actually I'm totally unaware of
all things systemd.  I heard sound when in group audio say two
weeks ago.

Nonetheless I did a

sudo delgroup grfz audio

logged in on a VT, played a .wav file with aplay: No sound.


> What is the outcome of:
> 
> getfacl /dev/snd/hwC0D0

c$ getfacl /dev/snd/hwC0D0
getfacl: Removing leading '/' from absolute path names
# file: dev/snd/hwC0D0
# owner: root
# group: audio
user::rw-
user:grfz:rw-
group::rw-
mask::rw-
other::---

Did not know this command but output looks good to me.


I did this for all devices somehow linked with sound (see below).
To me all the permissions semm to be ok.

Any thoughts?


Ciao; Gregor 

sudo find /dev/|xargs sudo ls -ld|egrep 
"sound|snd|pulse|pulse-access|audio"|egrep -o "/dev/[^ ]+"|xargs realpath|xargs 
getfacl

# file: dev/audio
# owner: root
# group: audio
user::rw-
user:grfz:rw-
group::rw-
mask::rw-
other::---

# file: dev/snd/hwC1D0
# owner: root
# group: audio
user::rw-
user:grfz:rw-
group::rw-
mask::rw-
other::---

# file: dev/snd/controlC0
# owner: root
# group: audio
user::rw-
user:grfz:rw-
group::rw-
mask::rw-
other::---

# file: dev/snd/pcmC0D0p
# owner: root
# group: audio
user::rw-
user:grfz:rw-
group::rw-
mask::rw-
other::---

# file: dev/snd/timer
# owner: root
# group: audio
user::rw-
user:grfz:rw-
group::rw-
mask::rw-
other::---

# file: dev/snd/pcmC0D0c
# owner: root
# group: audio
user::rw-
user:grfz:rw-
group::rw-
mask::rw-
other::---

# file: dev/snd/hwC0D0
# owner: root
# group: audio
user::rw-
user:grfz:rw-
group::rw-
mask::rw-
other::---

# file: dev/snd/controlC1
# owner: root
# group: audio
user::rw-
user:grfz:rw-
group::rw-
mask::rw-
other::---

# file: dev/snd/pcmC1D3p
# owner: root
# group: audio
user::rw-
user:grfz:rw-
group::rw-
mask::rw-
other::---

# file: dev/snd/pcmC1D7p
# owner: root
# group: audio
user::rw-
user:grfz:rw-
group::rw-
mask::rw-
other::---

# file: dev/snd/pcmC1D8p
# owner: root
# group: audio
user::rw-
user:grfz:rw-
group::rw-
mask::rw-
other::---

# file: dev/audio
# owner: root
# group: audio
user::rw-
user:grfz:rw-
group::rw-
mask::rw-
other::---

# file: dev/dsp
# owner: root
# group: audio
user::rw-
user:grfz:rw-
group::rw-
mask::rw-
other::---

# file: dev/mixer
# owner: root
# group: audio
user::rw-
user:grfz:rw-
group::rw-
mask::rw-
other::---

# file: dev/mixer1
# owner: root
# group: audio
user::rw-
user:grfz:rw-
group::rw-
mask::rw-
other::---

# file: dev/shm/pulse-shm-690874964
# owner: grfz
# group: grfz
user::rwx
group::---
other::---

# file: dev/shm/pulse-shm-911001899
# owner: grfz
# group: grfz
user::rwx
group::---
other::---

# file: dev/snd
# owner: root
# group: root
user::rwx
group::r-x
other::r-x

# file: dev/snd/by-path
# owner: root
# group: root
user::rwx
group::r-x
other::r-x

# file: dev/snd/controlC1
# owner: root
# group: audio
user::rw-
user:grfz:rw-
group::rw-
mask::rw-
other::---

# file: dev/snd/controlC0
# owner: root
# group: audio
user::rw-
user:grfz:rw-
group::rw-
mask::rw-
other::---

# file: dev/snd/controlC0
# owner: root
# group: audio
user::rw-
user:grfz:rw-
group::rw-
mask::rw-
other::---

# file: dev/snd/controlC1
# owner: root
# group: audio
user::rw-
user:grfz:rw-
group::rw-
mask::rw-
other::---

# file: dev/snd/hwC0D0
# owner: root
# group: audio
user::rw-
u

Re: ?? user in group audio -- but only root can play sound

[Floris]

Op Thu, 21 Jan 2016 12:30:44 +0100 schreef Jude DaShiell  
:



On Thu, 21 Jan 2016, Floris wrote:


Date: Thu, 21 Jan 2016 05:22:59
From: Floris 
To: debian-user@lists.debian.org
Subject: Re: ?? user in group audio -- but only root can play sound
Resent-Date: Thu, 21 Jan 2016 10:23:21 + (UTC)
Resent-From: debian-user@lists.debian.org
 Op Sat, 16 Jan 2016 20:06:22 +0100 schreef Gregor Zattler  
:



Hi there,
 since a few days my normal user, which is in group sound, cannot
play sound (aplay works but no sound) while root can.
 Any ideas how to debug this?
 This is a debian testing system with pulseaudio and mpd running.
 /dev$ find |xargs ls -ld|grep audio
crw-rw+  1 root audio  14,   4 Jan 16 16:32 ./audio
lrwxrwxrwx   1 root root 8 Jan 16 16:32 ./char/14:4 ->  
../audio

crw-rw+  1 root audio  14,   3 Jan 16 16:32 ./dsp
crw-rw+  1 root audio  14,   0 Jan 16 16:32 ./mixer
crw-rw+  1 root audio  14,  16 Jan 16 16:32 ./mixer1
crw-rw+  1 root audio 116,   2 Jan 16 16:32 ./snd/controlC0
crw-rw+  1 root audio 116,   6 Jan 16 16:32 ./snd/controlC1
crw-rw+  1 root audio 116,   5 Jan 16 16:32 ./snd/hwC0D0
crw-rw+  1 root audio 116,  10 Jan 16 16:32 ./snd/hwC1D0
crw-rw+  1 root audio 116,   4 Jan 16 19:27 ./snd/pcmC0D0c
crw-rw+  1 root audio 116,   3 Jan 16 19:52 ./snd/pcmC0D0p
crw-rw+  1 root audio 116,   7 Jan 16 19:52 ./snd/pcmC1D3p
crw-rw+  1 root audio 116,   8 Jan 16 19:27 ./snd/pcmC1D7p
crw-rw+  1 root audio 116,   9 Jan 16 19:27 ./snd/pcmC1D8p
crw-rw+  1 root audio 116,   1 Jan 16 16:32 ./snd/seq
crw-rw+  1 root audio 116,  33 Jan 16 16:32 ./snd/timer
  Ciao, Gregor


Maybe it sounds odd, but does you have sound when you remove yourself
form the audio group?

In Debian Testing systemd takes care for setting the right rights
That is why you have a "+" at the end of the permissions.

What is the outcome of:

getfacl /dev/snd/hwC0D0

success,

floris

As the user without audio capability please type groups and hit enter.   
I suspect you will see neither audio or video in that list.  If that's  
the case root will have to do something like:
usermod -a -G audio,video  and then reboot the system.  Doing  
a groups command again as the user should show audio and video along  
with whatever else was in that list earlier.  If so, try downloading  
youtube-viewer and run it and search for a youtube video as the user and  
see what happens when you try to play that video.  I think you'll have  
video and audio if the video has audio to play.


  --

The OP already has posted:


$ groups
grfz cdrom floppy sudo audio dip video plugdev netdev lpadmin
bluetooth scanner

Re: ?? user in group audio -- but only root can play sound

[Jude DaShiell]

On Thu, 21 Jan 2016, Floris wrote:


Date: Thu, 21 Jan 2016 05:22:59
From: Floris 
To: debian-user@lists.debian.org
Subject: Re: ?? user in group audio -- but only root can play sound
Resent-Date: Thu, 21 Jan 2016 10:23:21 + (UTC)
Resent-From: debian-user@lists.debian.org

Op Sat, 16 Jan 2016 20:06:22 +0100 schreef Gregor Zattler 
:



Hi there,

since a few days my normal user, which is in group sound, cannot
play sound (aplay works but no sound) while root can.

Any ideas how to debug this?

This is a debian testing system with pulseaudio and mpd running.

/dev$ find |xargs ls -ld|grep audio
crw-rw+  1 root audio  14,   4 Jan 16 16:32 ./audio
lrwxrwxrwx   1 root root 8 Jan 16 16:32 ./char/14:4 -> ../audio
crw-rw+  1 root audio  14,   3 Jan 16 16:32 ./dsp
crw-rw+  1 root audio  14,   0 Jan 16 16:32 ./mixer
crw-rw+  1 root audio  14,  16 Jan 16 16:32 ./mixer1
crw-rw+  1 root audio 116,   2 Jan 16 16:32 ./snd/controlC0
crw-rw+  1 root audio 116,   6 Jan 16 16:32 ./snd/controlC1
crw-rw+  1 root audio 116,   5 Jan 16 16:32 ./snd/hwC0D0
crw-rw+  1 root audio 116,  10 Jan 16 16:32 ./snd/hwC1D0
crw-rw+  1 root audio 116,   4 Jan 16 19:27 ./snd/pcmC0D0c
crw-rw+  1 root audio 116,   3 Jan 16 19:52 ./snd/pcmC0D0p
crw-rw+  1 root audio 116,   7 Jan 16 19:52 ./snd/pcmC1D3p
crw-rw+  1 root audio 116,   8 Jan 16 19:27 ./snd/pcmC1D7p
crw-rw+  1 root audio 116,   9 Jan 16 19:27 ./snd/pcmC1D8p
crw-rw+  1 root audio 116,   1 Jan 16 16:32 ./snd/seq
crw-rw+  1 root audio 116,  33 Jan 16 16:32 ./snd/timer


Ciao, Gregor


Maybe it sounds odd, but does you have sound when you remove yourself
form the audio group?

In Debian Testing systemd takes care for setting the right rights
That is why you have a "+" at the end of the permissions.

What is the outcome of:

getfacl /dev/snd/hwC0D0

success,

floris

As the user without audio capability please type groups and hit enter.  I 
suspect you will see neither audio or video in that list.  If that's the 
case root will have to do something like:
usermod -a -G audio,video  and then reboot the system.  Doing a 
groups command again as the user should show audio and video along with 
whatever else was in that list earlier.  If so, try downloading 
youtube-viewer and run it and search for a youtube video as the user and 
see what happens when you try to play that video.  I think you'll have 
video and audio if the video has audio to play.


 --

Re: ?? user in group audio -- but only root can play sound

[Floris]

Op Sat, 16 Jan 2016 20:06:22 +0100 schreef Gregor Zattler  
:



Hi there,

since a few days my normal user, which is in group sound, cannot
play sound (aplay works but no sound) while root can.

Any ideas how to debug this?

This is a debian testing system with pulseaudio and mpd running.

/dev$ find |xargs ls -ld|grep audio
crw-rw+  1 root audio  14,   4 Jan 16 16:32 ./audio
lrwxrwxrwx   1 root root 8 Jan 16 16:32 ./char/14:4 ->  
../audio

crw-rw+  1 root audio  14,   3 Jan 16 16:32 ./dsp
crw-rw+  1 root audio  14,   0 Jan 16 16:32 ./mixer
crw-rw+  1 root audio  14,  16 Jan 16 16:32 ./mixer1
crw-rw+  1 root audio 116,   2 Jan 16 16:32 ./snd/controlC0
crw-rw+  1 root audio 116,   6 Jan 16 16:32 ./snd/controlC1
crw-rw+  1 root audio 116,   5 Jan 16 16:32 ./snd/hwC0D0
crw-rw+  1 root audio 116,  10 Jan 16 16:32 ./snd/hwC1D0
crw-rw+  1 root audio 116,   4 Jan 16 19:27 ./snd/pcmC0D0c
crw-rw+  1 root audio 116,   3 Jan 16 19:52 ./snd/pcmC0D0p
crw-rw+  1 root audio 116,   7 Jan 16 19:52 ./snd/pcmC1D3p
crw-rw+  1 root audio 116,   8 Jan 16 19:27 ./snd/pcmC1D7p
crw-rw+  1 root audio 116,   9 Jan 16 19:27 ./snd/pcmC1D8p
crw-rw+  1 root audio 116,   1 Jan 16 16:32 ./snd/seq
crw-rw+  1 root audio 116,  33 Jan 16 16:32 ./snd/timer


Ciao, Gregor


Maybe it sounds odd, but does you have sound when you remove yourself
form the audio group?

In Debian Testing systemd takes care for setting the right rights
That is why you have a "+" at the end of the permissions.

What is the outcome of:

getfacl /dev/snd/hwC0D0

success,

floris

Re: ?? user in group audio -- but only root can play sound

[Chris Bannister]

On Tue, Jan 19, 2016 at 06:28:17PM +0100, Gregor Zattler wrote:
> Thinking about: mpd is also not in these groups and I can her
> music.
> 
> So that's still not it.
> 
> When I play some sound, I see aplay working, but do not hear sound:
> 
>  $ play  /home/grfz/Downloads/tuxok.wav

Just as an aside, that is not the aplay command. Compare man aplay, and
man play.

As to the rest, I'm stumped. Sorry.

-- 
"If you're not careful, the newspapers will have you hating the people
who are being oppressed, and loving the people who are doing the 
oppressing." --- Malcolm X

Re: ?? user in group audio -- but only root can play sound

[Gregor Zattler]

Hi Alexis, debian-users,
* Alexis  [19. Jan. 2016]:
>>Hi Jude, debian users, * Jude DaShiell  [18. Jan. 2016]:
This is astonishing, because my main user is in

$ groups grfz cdrom floppy sudo audio dip video plugdev netdev lpadmin
bluetooth scanner

being in group audio should be enough.
> 
> If you're using PulseAudio, the main user will probably need to be in the
> 'pulse' and/or 'pulse-access' groups as well.

Ah! I tried this one but sadly no change: no sound as normal
user.

Thinking about: mpd is also not in these groups and I can her
music.

So that's still not it.

When I play some sound, I see aplay working, but do not hear sound:

 $ play  /home/grfz/Downloads/tuxok.wav
 
 /home/grfz/Downloads/tuxok.wav:
 
 File Size: 129k  Bit Rate: 1.41M
 Encoding: Signed PCM
 Channels: 2 @ 16-bit
 Samplerate: 44100Hz
 Replaygain: off
 Duration: 00:00:00.73
 
 In:100%  00:00:00.73 [00:00:00.00] Out:32.3k [  |  ] Hd:0.0 Clip:0
 Done.

When I do the same with sudo I hear sound and there is additional
output on the terminal:


 $ sudo play  /home/grfz/Downloads/tuxok.wav
[...]
 In:100%  00:00:00.73 [00:00:00.00] Out:35.2k [  |  ] Hd:0.0 Clip:53
 play WARN rate: rate clipped 30 samples; decrease volume?
 play WARN dither: dither clipped 23 samples; decrease volume?
 Done.


Does this give a clue to someone?

Ciao, Gregor
-- 
 -... --- .-. . -.. ..--.. ...-.-

Re: ?? user in group audio -- but only root can play sound

[Alexis]

Gregor Zattler  writes:

Hi Jude, debian users, * Jude DaShiell  
[18. Jan. 2016]: 

This is astonishing, because my main user is in

$ groups grfz cdrom floppy sudo audio dip video plugdev netdev 
lpadmin bluetooth scanner


being in group audio should be enough.


If you're using PulseAudio, the main user will probably need to be 
in the 'pulse' and/or 'pulse-access' groups as well.



Alexis.

Re: ?? user in group audio -- but only root can play sound

[Gregor Zattler]

Hi Jude, debian users,
* Jude DaShiell  [18. Jan. 2016]:
>>This is astonishing, because my main user is in
>>
>>$ groups
>>grfz cdrom floppy sudo audio dip video plugdev netdev lpadmin
>>bluetooth scanner
>>
>>being in group audio should be enough.
>>
>>
>>Actually I do hear music ATM with ncmpcpp/mpd and:
>>
>>$ sudo groups mpd
>>mpd : audio
>>
>>So mpd plays music with permissions from group audio but I cannot
>>play a wav file or hear the sound of a movie!?


> That could be a different problem.  Check entries in .mailcap and .mimetypes
> for the user account.  The audio entries may not match what's in root's
> files and that may be a contributor to this problem.  I couldn't play web
> files with the lynx browser until I adjusted those files and now that's
> possible.

Thanks for the suggestion, but I did my tests on the command
line:

aplay ~/Downloads/tuxok.wav

works works but only when invocated as root I hear the sound.  No
sound as user in group audio.  And ATM I hear musik from mpd
(group audio).

Ciao, Gregor
-- 
 -... --- .-. . -.. ..--.. ...-.-

Re: ?? user in group audio -- but only root can play sound

[Jude DaShiell]

On Mon, 18 Jan 2016, Gregor Zattler wrote:


Date: Mon, 18 Jan 2016 16:22:45
From: Gregor Zattler 
To: debian-user 
Subject: Re: ?? user in group audio -- but only root can play sound
Resent-Date: Mon, 18 Jan 2016 21:23:35 + (UTC)
Resent-From: debian-user@lists.debian.org

Hi Ric, debian-users,
* Ric Moore  [18. Jan. 2016]:

On 01/16/2016 02:06 PM, Gregor Zattler wrote:

since a few days my normal user, which is in group sound, cannot
play sound (aplay works but no sound) while root can.

Any ideas how to debug this?


Crank up alsamixer and un-mute whatever became muted. Pulse sits on top of
alsa. Look there first, else pulse cannot work at all. Ric


Thanks, the relevant settings are unmuted and turned on.
Actually I can hear sound with aplay -- but only as root.

This is astonishing, because my main user is in

$ groups
grfz cdrom floppy sudo audio dip video plugdev netdev lpadmin
bluetooth scanner

being in group audio should be enough.


Actually I do hear music ATM with ncmpcpp/mpd and:

$ sudo groups mpd
mpd : audio

So mpd plays music with permissions from group audio but I cannot
play a wav file or hear the sound of a movie!?


Ciao, Gregor

That could be a different problem.  Check entries in .mailcap and 
.mimetypes for the user account.  The audio entries may not match what's 
in root's files and that may be a contributor to this problem.  I couldn't 
play web files with the lynx browser until I adjusted those files and now 
that's possible.


 --

Re: ?? user in group audio -- but only root can play sound

[Gregor Zattler]

Hi Ric, debian-users,
* Ric Moore  [18. Jan. 2016]:
> On 01/16/2016 02:06 PM, Gregor Zattler wrote:
>>since a few days my normal user, which is in group sound, cannot
>>play sound (aplay works but no sound) while root can.
>>
>>Any ideas how to debug this?
> 
> Crank up alsamixer and un-mute whatever became muted. Pulse sits on top of
> alsa. Look there first, else pulse cannot work at all. Ric

Thanks, the relevant settings are unmuted and turned on.
Actually I can hear sound with aplay -- but only as root.

This is astonishing, because my main user is in

$ groups
grfz cdrom floppy sudo audio dip video plugdev netdev lpadmin
bluetooth scanner

being in group audio should be enough.


Actually I do hear music ATM with ncmpcpp/mpd and:

$ sudo groups mpd
mpd : audio

So mpd plays music with permissions from group audio but I cannot
play a wav file or hear the sound of a movie!?


Ciao, Gregor
-- 
 -... --- .-. . -.. ..--.. ...-.-

Re: ?? user in group audio -- but only root can play sound

[Ric Moore]

On 01/16/2016 02:06 PM, Gregor Zattler wrote:

Hi there,

since a few days my normal user, which is in group sound, cannot
play sound (aplay works but no sound) while root can.

Any ideas how to debug this?


Crank up alsamixer and un-mute whatever became muted. Pulse sits on top 
of alsa. Look there first, else pulse cannot work at all. Ric



--
My father, Victor Moore (Vic) used to say:
"There are two Great Sins in the world...
..the Sin of Ignorance, and the Sin of Stupidity.
Only the former may be overcome." R.I.P. Dad.
http://linuxcounter.net/user/44256.html