> $ groups
> network video audio optical storage power users
I did this and wasn't in the audio group, then added myself to the audio
group and everything works! Actually, this was one of the first things that
Daniel suggested, but I didn't follow up on it (I didn't think it mattered but
I was
On Tue, Dec 03, 2013 at 08:35:40AM -0800, James Board wrote:
> >Your problem is not pulseaudio, it's your audio system below that. And by
> >attacking pulseaudio developers >or me (I am a pulseaudio user and linux
> >system administrator, no developer) you will not change that.
>
> I didn't att
>Your problem is not pulseaudio, it's your audio system below that. And by
>attacking pulseaudio developers >or me (I am a pulseaudio user and linux
>system administrator, no developer) you will not change that.
I didn't attack pulseaudio developers. I only suggested that they create a
troubl
Hi,
2013/12/2 James Board
> Okay thank you for your honesty. What part of the output from 'pulseaudio
> -vvv' said that my system was not permitting access to the real audio
> hardware? I looked at the log. What makes you think that my system is not
> allowing access to audio hardware?
>
I p
>To be honest to you: Pulseaudio is working just fine here. It plays the wav
>file without issues. It uses the best output that your system is offering to
>pulseaudio: null-sink. Pulseaudio said openly that your system is not
>permitting access to the real audio hardware.
Okay thank you for you
2013/12/2 James Board
> Actually, the system works fine. pulseaudio is the problem. I'm not
> trying to do anything complicated: mixing multiple sounds, or editing or
> anything. I'm only trying to play a simple .wav file. Before pulseaudio,
> this would work with a simple command like 'cat f
>If you insist into fixing your broken setup and/or user account settings,
>please hire some linux expert >(may also read: "ask in your circle of
>friends") and let him check your system on-site. In depth >debugging of a
>misconfigured system is impossible over mailing lists (and out of scope, t
2013/12/2 James Board
> D: module-udev-detect.c: /dev/snd/controlC1 is accessible: no
> D: module-udev-detect.c: /dev/snd/controlC0 is accessible: no
Your user has no permission to access audio hardware. I cannot tell why.
You could create a new user with the distribution favored tools. If this
I tried of everything you suggested. I'm not in the audio group in this
machine, but then I'm not in audio on another machine and sound works fine.
When I restarted pulseaudio with -vvv, here is the output. Does this tell you
anything?
Also, thanks for the help so far:
I: main.c: setrlimit
If it was my system, I would check the groups of my user to see if he's in
the "audio" group and such able to use the audio hardware at all.
Then I would check the output of "lspci -vvv" and search for audio
hardware, if it's there. Then I woud check "lsmod" if there is the "snd"
module and all ot
>I guess you may have something already hogging up the ALSA hardware devices
>before pulseaudio starts. Perhaps you installed >and activated jackd or some
>other audio system.
>
>When pulseaudio starts, it cannot find any free hardware ports to connect to
>and falls back to load a null audio si
I guess you may have something already hogging up the ALSA hardware devices
before pulseaudio starts. Perhaps you installed and activated jackd or some
other audio system.
When pulseaudio starts, it cannot find any free hardware ports to connect
to and falls back to load a null audio sink.
That's
I ran pacmd and then 'list-sinks' and it tells me one sink is available and the
name is . Does that mean it can't find the audio device? The
output of dmesg tells me that my audio device is" Intel 82801JI (ICH10 Family)
HD Audio Controller.
Does the above info help provide clue why my sound
13 matches
Mail list logo