I added this to /etc/security/console.perms.d/50-default-perms
at the top:
<sound>=/dev/dsp* /dev/snd/*
at the bottom:
<console> 0666 <sound> 0600 root

I did not do this:
yum remove alsa-plugins-pulseaudio

as i wanted to get mine working via instructions from and then did an installation of
sudo yum install pavucontrol pavumeter paman padevchooser paprefs

then I rebooted and everything from here went downhill
so I then decided to
sudo yum remove pavucontrol pavumeter paman padevchooser paprefs

rebooted and and it all was working!!! Lesson learned... don't try and do too much before a reboot. Thought this might or might not help someone.

tylerwylie

19th November 2007 05:34 AM

Quote:

Originally Posted by scottro

Anyway, here is my experience. Firstly, sound has been broken for some people as non-root for awhile. The usual solution, leaving pulseaudio out of the equation, is to edit /etc/security/console.perms.d/50-whatever it's called, and add

<sound>=/dev/dsp* /dev/snd/*

Then, at the bottom add

<console> 0666 <sound> 0600 root

This fixes the non-root issue if pulseaudio isn't involved.

This worked for me after removing pulseaudio, one thing is after you do this you might want to chmod 0666 /dev/snd/* or otherwise just reboot.

pedroivo

22nd November 2007 12:35 AM

i solved the problem adding my user to the groups:
pulse, pulse-"something" and pulse-"the other one"

don't know if this is the right thing to do, i'm new to linux...

to access the group edition gui:

K>Administration>Users and Groups (easy, as walking uh?)

click edit>preferences to tell the program that you want to see all system groups and users (or not, i just did)
then you click on your user name and then click the big "properties" icon. go to the tab groups, tick all groups related to audio (pulse, pulse-access, pulse-rt (i also ticked jackuser))

now i can hear all my mp3. ops! not supposed to talk about mp3 on fedora, it's against the distro's ideology...

if it works, please listen to good music only...

zak_neutron

25th November 2007 10:46 PM

4 Attachment(s)

I have been reading this thread with interest and while useful I still have a problem with PA :mad:

Problem: No sound at all apart from (Hillbilly guitar) Sound card detection app from Gnome menu!

No other app or web works!!! (I can see sound being played on Volume Meter on vlc - but no sound out of speakers)

I have one soundcard.

I have ConsoleKit running
I have avahi-daemon running
PA Server is running according to the Pulse Manager. However it cannot find any sinks or sources. See screenshots.

OK. This has been hateful. I tried everything mentioned in this thread and nothing worked. I logged into KDE (I normally use Gnome) and it *****ed about there being no device and using the null device. Hoping against hope I started KMix and, lo!, the bugger works.

Youtube and everything.

Even in Gnome.

I'm not sure about Skype, I'll try that later.

Much thanks to the eggheads here who have calmly and patiently shared their knowledge and experience with the rest of us.

Edit: Well, Skype doesn't work. Playback in one ear, can't be heard on the other end. Le sigh.

The Crafty One

craftyminion

26th November 2007 10:24 PM

Alas, the whole thing was too odious. The Crafty One has returned to the comfort and safety of Fedora 7.

All problem was in this tmp directory. I don't know why but root was owner. I remember messing around in root console from my sisters account (makinka) for a while but this should not happen. It must have been sideefect of somthing I have been doing. Anyway chown and chmod that directory solved it out for me.

I hope it will be useful for you

shermy451

1st December 2007 02:22 AM

I Found Waldo!!!!! Or one big Answer found.

I was running into the same problem, NO SOUND.
Something didn't look right in the default.pa file. The same thing was in mine too....

And rebooted (hush). And WOW! it found everything!!! sound works!!
Your thanks is all the reward I need, but if you feel you must, feel free to buy me a beer sometime.

Erick

mbratch

1st December 2007 03:09 AM

Quote:

Originally Posted by high

im puzzled :confused: anyone else have the same issue?

I had all sorts of trouble with sound until I uninstalled all the pulse audio stuff. Then it all worked fine.

heliopaixao

3rd December 2007 12:04 AM

I noticed that file /etc/asound.conf does not pertain to any package then I have removed it. This fix my problem with vlc no having sound after upgrade from fedora7 to fedora8.

radekrat

3rd December 2007 10:40 AM

This is really annoying. The sound was working for me till Friday update. I tried everything in this thread and still PulseAudio-manager shows me "Failed to connect" and won't find any audio device. :confused:

I have myuser in all pulse* groups, I've changed /etc/security and also asound.conf ..

I have pulseaudio-0.9.7-0.17.svn20071017.fc8 and ConsoleKit-0.2.3-1.fc8

Managed to get my pulseaudio working - after much hair loss and gnashing of teeth. Found some useful info on another forum - see here

I have to say permissions continues to be the main culprit.

In the above link, pay close attention to the solution put forward by David De Graff (mainly focussed in getting PA to work with XFCE)

I found the process for me to be 2 stage:

1. Get F8 to recognize my soundcard via alsa - again permissions!!!
This brought some of the gnome sound tools into play
2. Get PA configured to point towards your now recognised sound card

I really cannot remember (or just don't want to) all the actual steps that worked for me (nearly 2 full days!!), but Davids amended "/etc/udev/rules.d/40-alsa.rules" file and numerous reboots helped get me started to find my sound card. After this The Gnome System>Preferences>Hardware>Sounds could see the pulseadio sound server as an option

The alsa/sound card problem was understood from the difference between running "aplay -lL" as root and non root.

Don't give up, it is worth it in the end - although you can't help think for F8 that PA was a headline grabbing feature probably released a bit too soon!

:)

strikeforce

3rd December 2007 10:40 PM

I'm quoting the part of the thread here.

Quote:

OK, here's what I had to do to make it possible to start pulseaudio.

1) Edit /etc/udev/rules.d/40-alsa.rules to set MODE="0666" to all
"snd" files:
# do not edit this file, it will be overwritten on update

I guess we just have to ignore the admonition not to edit this file;
there seems to be no other way to do it.

The clue that permissions were too restrictive came from running
aplay -lL
When root did it, the sound card was detected and displayed
reasonably; when non-root did it, no sound devices were found.
This contrasts with Fedora 7, where it works identically for all.

With only root able to access these file, it was impossible for an
ordinary user to start the pulseaudio daemon.

2) Edit /etc/passwd to set the home directory of user pulse to
/var/run/pulse, eg,
pulse:x:492:488:PulseAudio daemon:/var/run/pulse:/sbin/nologin

This is necessary to allow the --system option to work properly.
On startup, pulseaudio must create directories .gconf and .gconfd in
its home directory. This it cannot do when the home directory is /.

3) On my system, certain files in /var/run and directory
/tmp/gconfd-pulse/ had somehow become owned by user kismet:kismet.
I can't imagine how this happened, but it blocked use by pulseaudio,
which complained in /var/log/messages.
I removed these files and restarted pulseaudio with no more
complaints.

With the above fixes, the --system option works properly when root
starts pulseaudio, extending to all users the full use of the sound
system. The last line confirms proper behaviour.

When xfce is started all users inherit the ability to run aplay and
other X sound programs such as xmms. Any console user can use aplay.
Crontab entries of any user can use aplay.

I simply cannot comprehend why Fedora 8 starts the pulseaudio daemon as
a gnome task. With the above fixes, it is perfectly possible to start
it in /etc/rc.d/rc.local. With only a bit more effort, it should be
possible to come up with a simple startup script in /etc/init.d so that
this daemon is treated the same as any other proper Linux daemon.

zak_neutron

3rd December 2007 10:48 PM

Thanks strikeforce - still a bit new to this forum posting! :eek:

zak_neutron

3rd December 2007 10:53 PM

Quote:

2) Edit /etc/passwd to set the home directory of user pulse to
/var/run/pulse, eg,
pulse:x:492:488:PulseAudio daemon:/var/run/pulse:/sbin/nologin

- word of warning make sure your GID matches the pulse group F8 has created - on my system is wasn't 488 - but 498!!

:)

strikeforce

3rd December 2007 10:54 PM

mine is

Code:

pulse:x:496:495:PulseAudio daemon:/:/sbin/nologin

QuantumKnot

4th December 2007 12:49 PM

I had the same problem after doing a yum update. When trying to start pulseaudio volume control, I got a connection refused message (despite both ConsoleKit and Avahi running). RhythmBox would just freeze when trying to play something.

As noted in an earlier post, I noticed suddenly these few lines in my /etc/modprobe.conf

alias snd-card-7 snd-usb-audio
options snd-usb-audio index=7

So I commented them out, did a rm -rf in my /tmp directory and rebooted, and voila, pulseaudio is back alive again. :)

I'm not sure which fixed it but perhaps those strange lines in modprobe.conf is causing the problem.

BoyWonder410

5th December 2007 03:39 AM

it's not a feature if it breaks everything.... i dont know exactly what all sound problems i am having,
sound works fine in WINE, but, amarok, xine, mplayer et cetera dont have any sound
if PCM is set to 100% my speakers are increadibly staticy, which did not occur on fc7.... i'm not going to put a lot of effort into fixing this yt, no time...

jnissly

8th December 2007 06:43 PM

Quote:

Originally Posted by high

im puzzled :confused: anyone else have the same issue?

As soon as I ran the 68 updates I needed yesterday, my non-root account also lost access to sound. I was getting a "Gstreamer" error.

Now sound works, on a session-by-session basis. I need to re-run this every time I reboot.

Since my experience with Linux is moderate (6 months), I am not sure as to how to make this change permanent. Can anyone please advise me?

xaoslaad

9th December 2007 04:06 AM

Backup and replace your /etc/security/console.perms.d/50-default.perms with this one. I have made changes to it in the passed, and based on some quick reading I just did it appears some people have problems starting the server without these changes being made.

# $Id: client.conf.in 1285 2006-08-19 01:18:57Z lennart $
#
# This file is part of PulseAudio.
#
# PulseAudio is free software; you can redistribute it and/or modify
# it under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# PulseAudio is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
#
# You should have received a copy of the GNU Lesser General Public License
# along with PulseAudio; if not, write to the Free Software
# Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307
# USA.

## Configuration file for pulseaudio clients. Default values are
## commented out. Use either ; or # for commenting

## Path to the pulseaudio daemon to run when autospawning.
; daemon-binary = /usr/bin/pulseaudio

Hello all,
I just wanted to know, if anyone has had succeeded in using skype v1.4 or v2.0beta with pulseaudio, and if yes how!
Because I had lotsa troubles with skype and pulse, rest all was working fine(mplayer,xine etc) . So I have disabled pulse currently, but i wanna use desperately coz i need to switch between snd cards frequently( BT headset and Onboard soundcard) , so pulse Is what I need !!!

ahvi

23rd January 2008 05:46 PM

For anybody having problems with sound in VLC, make sure /usr/lib/pulse-0.9/modules/module-esound-sink.so is displayed in Settings>Preferences>Audio>Output Modules>EsounD>Esound server

cable_txg

23rd January 2008 05:59 PM

I do have PulseAudio working fine for me. When installing FC4 - FC8 I believe I had to set my group to also belong to sound(PulseAudio in FC8). Here's my id:
uid=500(Cable_txg) gid=500(Cable_txg) groups=100(users),495(pulse-access),497(pulse),500(Cable_txg) context=system_u:system_r:unconfined_t:s0

Also from System->Administration->Users and Groups click on properties for any user name and under "Groups" tab, click on pulse and pulse-access to include user in that group.

Hope that works.... :D

elvenhack

27th January 2008 09:06 PM

Fedora 8 pulse audio as a system-wide daemon

For anybody trying to get Fedora 8 to run as a system-wide deamon as opposed to only starting up when someone logs into an X-server (ex: I'm setting up my machine as a headless jukebox, so I want to be able to ssh into it and start a song using mpg/ogg123 on the command line) here was the last crucial step for me. I'm sure this somehow bad for security but at least it works.

Go into /etc/pulse/default.pa and comment out the line
load-module module-x11-publish.

After doing this I was able to successfully run the following command as root:

# pulseaudio --system -D

Good luck!

escapeflowne

14th February 2008 02:03 PM

i have this problem with sound->in general pulseaudio plays sound fine. but after some reboots i hear no sound and when i run alsamixer in terminal it says pulseaudio:connection refused. the only solution i found was either remove alsa-plugins-pulseaudio or rm -rf /tmp/pulse-username as root ,pulseaudio -k and pulseaudio -D. so my question is -are these solutions real solutions or am i missing a simple trick ? i have consolekit and avahi-daemon running.

strikeforce

14th February 2008 10:25 PM

Console Kit is supposed to fix that since it is supposed to be giving you permissions.

The actual error comes from /tmp/pulse-username

jnissly

24th February 2008 03:23 AM

Quote:

Originally Posted by scottro

Sigh, sound. I'll just say, remember, Fedora is considered a bleeding edge distro. Yeah, it should Just Work(TM) but when I get ticked, I tell myself, well, it's not one of those distros that aims to try to be an MS replacement. :)

Personally, I feel that even ALSA was an answer to a question no one asked, but, that's a rant for a different day. OSS worked with less effort.

Anyway, here is my experience. Firstly, sound has been broken for some people as non-root for awhile. The usual solution, leaving pulseaudio out of the equation, is to edit /etc/security/console.perms.d/50-whatever it's called, and add

<sound>=/dev/dsp* /dev/snd/*

Then, at the bottom add

<console> 0666 <sound> 0600 root

This fixes the non-root issue if pulseaudio isn't involved.

.

Thank you for posting this, it did the trick for me. I used to have to chown /dev/snd every time I booted.

bluestone

16th March 2008 04:25 PM

For my issue (no sound in Nexuiz: crime). I found some great tips from the links on this page regarding sound:

I seem to have the same problem as you guys. For me, there's no sound, root or no root.
Did anyone succeeded in using skype 1.4? I hope someone can help me. I've been looking for an answer for quite a while now but it never seemed to work.Simulation pret immobilier

Thanks all!

JohnVV

16th January 2009 07:40 AM

as far as i know skype dose not work with pulse on fedora 8 ,may have been fixed in fedora 9 or 10 .or just remove pulse and reinstall alsa -- before the servers are taken offline ( 8 hit End of Life on jan 7)

ok, so whether I set up pulseaudio or alsa I get no sound. One cannot be opened and the otherrefuses to connect.

SELinux message when attempting to watch online streaming video is

>The mplayer application attempted to load /usr/lib/codecs/drv4.so.6.0 which requires text relocation. This is a potential security problem. Most libraries do not need this permission. Libraries are sometimes coded incorrectly and request this permission.<

Seems trying to write to a file and execute it at the same time is a no-no, but this was supposedly corrected in kernels >2.6...

Anyone know about this?

Thanks for your time

JohnVV

9th April 2009 01:47 AM

glhere please start a new thread for this NEW problem.
and what dose your problem have to do with fedora 8 .

scottro

9th April 2009 02:25 AM

Folks to avoid confusion, I think I'm going to close this thread. The last new information is from January, and while that's relatively recent, I think that it might result in issues like the one in the last few posts, a newcomer posting a new issue because it's pulse related. The thread originated in 2007, so I think it served it's original purpose.

If any of you think that this is REALLY wrong, you can PM me, but I probably won't see it till tomorrow.