Re: Sound problems on Wheezy upgrade

[Gary Roach]

On 09/23/2013 10:59 AM, Gary Roach wrote:

On 09/22/2013 10:35 AM, Gary Roach wrote:

On 09/21/2013 04:18 PM, Gregory Nowak wrote:

On Sat, Sep 21, 2013 at 04:07:49PM -0700, Gary Roach wrote:

In reply to your question:

root@mysite:/var/lib# ls -ld /var/lib/alsa
drwxr-xr-x 2 root root 4096 Dec 29  2012 /var/lib/alsa
root@mysite:/var/lib# ls -ld /root
drwx-- 15 gary gary 4096 Sep  3 18:21 /root

I do stand to be corrected, but I think that's the problem. I haven't
yet come across a system where /root was owned by some user other than
root. Try this:

chown root.root /root

and try starting alsa again.

Greg



Greg

You were correct. I'm not sure why root got marked gary:gary but that 
stopped Alsa from being restarted. I still don't have sound so I'll 
be back as soon a I can find something concrete wrong.


Thanks

Gary R


Further investigation showed that pulseaudio wasn't running either. 
Attempts to restart failed. From the Ubantu Forum (Temujin April 25, 
2011) I reset the pulseaudio configuration with:


dpkg --purge --force-depends pulseaudio
sudo apt-get install pulseaudio

I then had to manually start pulseaudio with "service pulseaudio 
start." This  worked but still no sound. I started VLC player and with 
tools > preferences > audio pointed it to pulseaudio for its output 
device. I started an arbitrary icecast and under Audio > 
Visualizations picked the VU meters. These showed that I was receiving 
a signal. I then started the PulseAudio Volume Meter and found that I 
was also getting a signal out of pulseaudio. I still don't have any 
sound.


I'll be back

Gary R.

And last but not least, I found the speaker / amplifier sound cable 
plugged into the wrong jack on my KVM switch. Everything now works.


Thanks to all

Gary R.

SOLVED was Re: Sound problems on Wheezy upgrade THANK YOU

[Lisi Reisz]

On Tuesday 24 September 2013 01:24:09 Gregory Nowak wrote:
> firmware-linux-nonfree installed, and that doesn't seem to have
> helped. So, I would try a newer kernel from debian backports as
> someone else in that thread suggests. HTH.

I already had the firmwqare.  So backport kernel installed, master 
re-set to 100% instead of 0%, to which the new kernel had reset it.

And my loudspeakers blared out!

THANK YOU ALL!

And I was seriously and sadly thinking of abandoning Debian.  Shame on 
me. :-(

Lisi


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201309241613.39380.lisi.re...@gmail.com

Re: Sound problems on Wheezy upgrade

[Curt]

On 2013-09-23, Lisi Reisz  wrote:

>> 
>
> I'm ashamed to say that I hadn't, but I had in fact found most of it 
> one way or another anyway.  There was one suggestion that seemed just 
> possibly relevant, and hey! I'm getting desperate.  I tried it, but 
> still no further forward.

So you've done the obvious things like removing (or renaming) the pulse
configuration files in your user directory (~/.pulse/*), (and maybe
reexecuting 'alsactl init' somewhere along the line)?



-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/slrnl4306k.2lb.cu...@einstein.electron.org

Re: Sound problems on Wheezy upgrade

[Gregory Nowak]

On Mon, Sep 23, 2013 at 11:50:04PM +0100, Lisi Reisz wrote:
> But I finally googled how, and looked at my boot log 
> (/var/log/messages).  I got the following that seems relevant, 
> although slighly old:

Hmmm, this makes me wonder if maybe your card requires firmware with
the new 3.x kernel under wheezy, which it didn't need under 2.6.x in
squeeze. If you don't have the firmware-linux package installed, can
you please consider installing it so that we can rule out lack of
firmware as the problem? If you don't want to use the non-free parts
of debian, then I would suggest at least installing
firmware-linux-free if you don't have that already. The kernel
messages you posted don't bring anything else to mind. Did you try a
web search/google with either "alsa-util.c: Unable to load mixer:
Invalid argument" or "hda_codec: num_steps = 0". When doing a search
on the former, at least one of the results looks promising:



Doing a search on the latter also has at least one result which looks
promising:



Actually, the OP in this second post already has
firmware-linux-nonfree installed, and that doesn't seem to have
helped. So, I would try a newer kernel from debian backports as
someone else in that thread suggests. HTH.

Greg


-- 
web site: http://www.gregn..net
gpg public key: http://www.gregn..net/pubkey.asc
skype: gregn1
(authorization required, add me to your contacts list first)

--
Free domains: http://www.eu.org/ or mail dns-mana...@eu.org


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130924002409.ga3...@gregn.net

Re: Sound problems on Wheezy upgrade

[Lisi Reisz]

On Monday 23 September 2013 21:27:46 Gregory Nowak wrote:
> On Mon, Sep 23, 2013 at 10:59:56AM -0700, Gary Roach wrote:
> > I then had to manually start pulseaudio with "service pulseaudio
> > start." This  worked but still no sound. with tools > preferences
> > > audio pointed it to pulseaudio for its output device. I started
> > an arbitrary icecast and under Audio > Visualizations picked the
> > VU meters. These showed that I was receiving a signal. I then
> > started the PulseAudio Volume Meter and found that I was also
> > getting a signal out of pulseaudio. I still don't have any sound.
>
> Check if any of your playback controls are muted. It belatedly
> occurred to me to take a look at the pulseaudio page on the debian
> wiki. It seems to describe solutions to almost every problem, if
> not every problem we're seeing in this thread so far from everyone.
> All of you have read that page, right? That probably should have
> been the first question I should have asked when this got started.
>
> 

I'm ashamed to say that I hadn't, but I had in fact found most of it 
one way or another anyway.  There was one suggestion that seemed just 
possibly relevant, and hey! I'm getting desperate.  I tried it, but 
still no further forward.

But I finally googled how, and looked at my boot log 
(/var/log/messages).  I got the following that seems relevant, 
although slighly old:

Sep 17 08:18:31 Tux-II pulseaudio[3521]: [pulseaudio] alsa-util.c: 
Unable to load mixer: Invalid argument
Sep 17 08:18:31 Tux-II kernel: [   10.604811] hda_codec: num_steps = 0 
for NID=0xc (ctl = Front Playback Volume)
Sep 17 08:18:31 Tux-II pulseaudio[3521]: [pulseaudio] alsa-util.c: 
Unable to load mixer: Invalid argument
Sep 17 08:18:31 Tux-II kernel: [   10.614723] hda_codec: num_steps = 0 
for NID=0xc (ctl = Front Playback Volume)
Sep 17 08:18:31 Tux-II pulseaudio[3521]: [pulseaudio] alsa-util.c: 
Unable to load mixer: Invalid argument
Sep 17 08:18:31 Tux-II kernel: [   10.622527] hda_codec: num_steps = 0 
for NID=0xc (ctl = Front Playback Volume)
Sep 17 08:18:31 Tux-II pulseaudio[3521]: [pulseaudio] alsa-util.c: 
Unable to load mixer: Invalid argument
Sep 17 08:18:31 Tux-II kernel: [   10.654405] hda_codec: num_steps = 0 
for NID=0xc (ctl = Front Playback Volume)
Sep 17 08:18:31 Tux-II pulseaudio[3521]: [pulseaudio] alsa-util.c: 
Unable to load mixer: Invalid argument
Sep 17 08:18:31 Tux-II kernel: [   10.702246] hda_codec: num_steps = 0 
for NID=0xc (ctl = Front Playback Volume)
Sep 17 08:18:31 Tux-II pulseaudio[3521]: [pulseaudio] alsa-util.c: 
Unable to load mixer: Invalid argument
Sep 17 08:18:31 Tux-II kernel: [   10.718566] hda_codec: num_steps = 0 
for NID=0xc (ctl = Front Playback Volume)
Sep 17 08:18:31 Tux-II pulseaudio[3521]: [pulseaudio] alsa-util.c: 
Unable to load mixer: Invalid argument
Sep 17 08:18:31 Tux-II kernel: [   10.734471] hda_codec: num_steps = 0 
for NID=0xc (ctl = Front Playback Volume)
Sep 17 08:18:31 Tux-II pulseaudio[3521]: [pulseaudio] alsa-util.c: 
Unable to load mixer: Invalid argument
Sep 17 08:18:31 Tux-II kernel: [   10.758274] hda_codec: num_steps = 0 
for NID=0xc (ctl = Front Playback Volume)
Sep 17 08:18:31 Tux-II pulseaudio[3521]: [pulseaudio] alsa-util.c: 
Unable to load mixer: Invalid argument
Sep 17 08:18:31 Tux-II kernel: [   10.782299] hda_codec: num_steps = 0 
for NID=0xc (ctl = Front Playback Volume)
Sep 17 08:18:31 Tux-II pulseaudio[3521]: [pulseaudio] alsa-util.c: 
Unable to load mixer: Invalid argument
Sep 17 08:18:31 Tux-II kernel: [   10.806053] hda_codec: num_steps = 0 
for NID=0xc (ctl = Front Playback Volume)
Sep 17 08:18:31 Tux-II pulseaudio[3521]: [pulseaudio] alsa-util.c: 
Unable to load mixer: Invalid argument
Sep 17 08:18:31 Tux-II kernel: [   10.877717] hda_codec: num_steps = 0 
for NID=0xc (ctl = Front Playback Volume)
Sep 17 08:18:31 Tux-II pulseaudio[3521]: [pulseaudio] alsa-util.c: 
Unable to load mixer: Invalid argument
Sep 17 08:18:31 Tux-II kernel: [   10.885634] hda_codec: num_steps = 0 
for NID=0xc (ctl = Front Playback Volume)
Sep 17 08:18:31 Tux-II kernel: [   11.101845] hda_codec: num_steps = 0 
for NID=0xc (ctl = Front Playback Volume)
Sep 17 08:18:31 Tux-II kernel: [   11.106061] hda_codec: num_steps = 0 
for NID=0xc (ctl = Front Playback Volume)
Sep 17 16:35:07 Tux-II kernel: [29711.421558] hda_codec: num_steps = 0 
for NID=0xc (ctl = Front Playback Volume)
Sep 17 22:47:10 Tux-II shutdown[14551]: shutting down for system halt
Sep 17 22:47:11 Tux-II kernel: [51963.300984] hda_codec: num_steps = 0 
for NID=0xc (ctl = Front Playback Volume)
Sep 18 07:33:01 Tux-II kernel: imklog 5.8.11, log source = /proc/kmsg 
started.


TIA
Lisi


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201309232350.04421.lisi.re...@gmail.com

Re: Sound problems on Wheezy upgrade

[Gregory Nowak]

On Mon, Sep 23, 2013 at 10:59:56AM -0700, Gary Roach wrote:
> I then had to manually start pulseaudio with "service pulseaudio
> start." This  worked but still no sound. with tools > preferences > audio 
> pointed it to pulseaudio for its
> output device. I started an arbitrary icecast and under Audio >
> Visualizations picked the VU meters. These showed that I was
> receiving a signal. I then started the PulseAudio Volume Meter and
> found that I was also getting a signal out of pulseaudio. I still
> don't have any sound.
> 

Check if any of your playback controls are muted. It belatedly occurred
to me to take a look at the pulseaudio page on the debian wiki. It
seems to describe solutions to almost every problem, if not every
problem we're seeing in this thread so far from everyone. All of you
have read that page, right? That probably should have been the first
question I should have asked when this got started.



Greg


-- 
web site: http://www.gregn..net
gpg public key: http://www.gregn..net/pubkey.asc
skype: gregn1
(authorization required, add me to your contacts list first)

--
Free domains: http://www.eu.org/ or mail dns-mana...@eu.org


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130923202746.ga7...@gregn.net

Re: Sound problems on Wheezy upgrade

[Gary Roach]

On 09/22/2013 10:35 AM, Gary Roach wrote:

On 09/21/2013 04:18 PM, Gregory Nowak wrote:

On Sat, Sep 21, 2013 at 04:07:49PM -0700, Gary Roach wrote:

In reply to your question:

root@mysite:/var/lib# ls -ld /var/lib/alsa
drwxr-xr-x 2 root root 4096 Dec 29  2012 /var/lib/alsa
root@mysite:/var/lib# ls -ld /root
drwx-- 15 gary gary 4096 Sep  3 18:21 /root

I do stand to be corrected, but I think that's the problem. I haven't
yet come across a system where /root was owned by some user other than
root. Try this:

chown root.root /root

and try starting alsa again.

Greg



Greg

You were correct. I'm not sure why root got marked gary:gary but that 
stopped Alsa from being restarted. I still don't have sound so I'll be 
back as soon a I can find something concrete wrong.


Thanks

Gary R


Further investigation showed that pulseaudio wasn't running either. 
Attempts to restart failed. From the Ubantu Forum (Temujin April 25, 
2011) I reset the pulseaudio configuration with:


   dpkg --purge --force-depends pulseaudio
   sudo apt-get install pulseaudio

I then had to manually start pulseaudio with "service pulseaudio start." 
This  worked but still no sound. I started VLC player and with tools > 
preferences > audio pointed it to pulseaudio for its output device. I 
started an arbitrary icecast and under Audio > Visualizations picked the 
VU meters. These showed that I was receiving a signal. I then started 
the PulseAudio Volume Meter and found that I was also getting a signal 
out of pulseaudio. I still don't have any sound.


I'll be back

Gary R.

Re: Sound problems on Wheezy upgrade (and squeeze, previously)

[Gregory Nowak]

On Sun, Sep 22, 2013 at 11:29:13AM -0500, Damon Getsman wrote:
> Haven't checked to see what the BIOS menu says yet,
> but I will as soon as I can take the machine down for a bit.

I would definitely do that, since this sounds like a hardware problem
to me.

Greg


-- 
web site: http://www.gregn.net
gpg public key: http://www.gregn.net/pubkey.asc
skype: gregn1
(authorization required, add me to your contacts list first)

--
Free domains: http://www.eu.org/ or mail dns-mana...@eu.org


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130922193629.ga28...@gregn.net

Re: Sound problems on Wheezy upgrade

[Gary Roach]

On 09/21/2013 04:18 PM, Gregory Nowak wrote:

On Sat, Sep 21, 2013 at 04:07:49PM -0700, Gary Roach wrote:

In reply to your question:

root@mysite:/var/lib# ls -ld /var/lib/alsa
drwxr-xr-x 2 root root 4096 Dec 29  2012 /var/lib/alsa
root@mysite:/var/lib# ls -ld /root
drwx-- 15 gary gary 4096 Sep  3 18:21 /root

I do stand to be corrected, but I think that's the problem. I haven't
yet come across a system where /root was owned by some user other than
root. Try this:

chown root.root /root

and try starting alsa again.

Greg



Greg

You were correct. I'm not sure why root got marked gary:gary but that 
stopped Alsa from being restarted. I still don't have sound so I'll be 
back as soon a I can find something concrete wrong.


Thanks

Gary R

Re: Sound problems on Wheezy upgrade (and squeeze, previously)

[Damon Getsman]

I've been waiting to post about this issue for quite some time, nbut when I
finally saw this thread I decided it was time to pipe up.  I had lots of
issues with my soundsystem dying in squeeze whether I used alsa or pulse.
Only a reboot would fix it.  It seemed to creep up most commonly when
nultiple sound aps were in use on one desktop login (those being run by
multiple users never caused this).  For instance, a youtube video in chrome
would, if virtualbox, rhythmbox, or another application tried to work with
sound, I'd get nothing till reboot.

Since my upgrade to wheezy, new issues have arisen.  Primarily that of
VLC's (yeah I know I'm starting a war now) sound output would be massively
infused with static until audio would, at some point, spike in a certain
equalizer freq range (I suspect), and sound would then be perfect until a
pausing of playback, or switch to different media.  This turned out to
resolve as soon as I ditched VLC for the stock media player.
Unfortunately, just a couple of days after finding that fix, the entire
system, at what appears to be a kernel level, now refuses at admit that I
have sound hardware at ALL.  Dmesg scanning confirms that it's not finding
crap and the gnome control panel only shows 'dummy sound system' as
available for [non-functional] output, compared to the 3 devices total that
I had a few days ago.  Haven't checked to see what the BIOS menu says yet,
but I will as soon as I can take the machine down for a bit.

-Damon

> From: Gary Roach 
> To: debian-user@lists.debian.org
> Subject: Re: Sound problems on Wheezy upgrade
[Snip]
> On 09/20/2013 08:40 PM, drew craig wrote:
> > I ran into an alsa issue awhile back and solved it by altering the conf
file.  May or may not be of any help.  I wrote it up here
> >
> > http://linuxbbq.org/bbs/viewtopic.php?f=9&t=409
> >
> >
> I hope I am not hyjacking this thread but, while my problem seems to be
> somewhat different, it still started with a wheezy upgrade that killed
> my sound system. I don't think that any one has identified the root
> cause of this problem and are kind of using a shot gun approach to the
> problem solving. So let me get as specific as I can. Running as root
> 'service alsa-utils restart' produced the following return:
>  root@mysystem:/etc# service alsa-utils restart
>  [ ok ] Shutting down ALSA...done.
>  [] Setting up ALSA...warning: 'alsactl restore' failed with
> error message 'Home directory /root not ours.'...Home
> directory /root not ours
> Can anyone explain this error message and suggest a fix.
>
> I hope my above statement doesn't insult anyone. I know a lot of effort
> has gone into this thread. But my observation still stands. I'm finding
> references to this problem all over google but no reasonable solutions.
> I can't believe that there are more than one or two actual problems
> here. Programs just don't usually break in multiple ways all at the same
> time.
[HTMLized version of the same crap snipped]

Re: Sound problems on Wheezy upgrade

[Gregory Nowak]

On Sat, Sep 21, 2013 at 04:07:49PM -0700, Gary Roach wrote:
> In reply to your question:
> 
>root@mysite:/var/lib# ls -ld /var/lib/alsa
>drwxr-xr-x 2 root root 4096 Dec 29  2012 /var/lib/alsa
>root@mysite:/var/lib# ls -ld /root
>drwx-- 15 gary gary 4096 Sep  3 18:21 /root

I do stand to be corrected, but I think that's the problem. I haven't
yet come across a system where /root was owned by some user other than
root. Try this:

chown root.root /root

and try starting alsa again.

Greg


-- 
web site: http://www.gregn.net
gpg public key: http://www.gregn.net/pubkey.asc
skype: gregn1
(authorization required, add me to your contacts list first)

--
Free domains: http://www.eu.org/ or mail dns-mana...@eu.org


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130921231842.gc7...@gregn.net

Re: Sound problems on Wheezy upgrade

[Gary Roach]

On 09/21/2013 02:39 PM, Gregory Nowak wrote:

On Sat, Sep 21, 2013 at 09:46:45AM -0700, Gary Roach wrote:

 root@mysystem:/etc# service alsa-utils restart
 [ ok ] Shutting down ALSA...done.
 [] Setting up ALSA...warning: 'alsactl restore' failed
with error message 'Home directory /root not
ours.'...Home directory /root not ours
Can anyone explain this error message and suggest a fix.

Hmm, that looks like some sort of permissions problem. For starters,
what does

ls -ld /var/lib/alsa
ls -ld /root

give you? Maybe someone else has a better idea on where to start
searching, or even exactly what the problem is.

Greg



In reply to your question:

   root@mysite:/var/lib# ls -ld /var/lib/alsa
   drwxr-xr-x 2 root root 4096 Dec 29  2012 /var/lib/alsa
   root@mysite:/var/lib# ls -ld /root
   drwx-- 15 gary gary 4096 Sep  3 18:21 /root

I use /root for a ebook editor and nothing  else.

Gary R

Re: Sound problems on Wheezy upgrade

[Gregory Nowak]

On Sat, Sep 21, 2013 at 09:46:45AM -0700, Gary Roach wrote:
> root@mysystem:/etc# service alsa-utils restart
> [ ok ] Shutting down ALSA...done.
> [] Setting up ALSA...warning: 'alsactl restore' failed
> with error message 'Home directory /root not
> ours.'...Home directory /root not ours
> Can anyone explain this error message and suggest a fix.

Hmm, that looks like some sort of permissions problem. For starters,
what does

ls -ld /var/lib/alsa
ls -ld /root

give you? Maybe someone else has a better idea on where to start
searching, or even exactly what the problem is.

Greg


-- 
web site: http://www.gregn.net
gpg public key: http://www.gregn.net/pubkey.asc
skype: gregn1
(authorization required, add me to your contacts list first)

--
Free domains: http://www.eu.org/ or mail dns-mana...@eu.org


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130921213938.ga7...@gregn.net

Re: Sound problems on Wheezy upgrade

[Klaus]

On 19/09/13 14:36, Lisi Reisz wrote:

I am still struggling with this.
Any suggestions, please?

Many thanks,
Lisi



From your earlier messages I gather that you have a mother board with
the Z77 chipset, and a Realtek ALC887 codec. Searching around I found a
few bug reports, from which it appears that the ALSA sound driver
together with an "older" kernel may not work correctly . Sorry to be a
bit wage, I haven't dug very deeply. See this link for example:
. 

According to this description, a kernel upgrade or installing the 
Realtek-provided driver might help?


--
Klaus


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/523e01a7.2050...@gmail.com

Re: Sound problems on Wheezy upgrade

[Gary Roach]

On 09/20/2013 08:40 PM, drew craig wrote:

On Friday, September 13, 2013 10:00:03 AM UTC-4, Lisi Reisz wrote:

The problem has arisen since I upgraded.  Sound was fine in Squeeze.



Now, when I run alsamixergui:



lisi@Tux-II:~$ alsamixergui



I get an error box saying:



alsamixer: function snd_mixer_load failed: invalid argument



No pulseaudia is installed.



I get the same problem on a fresh install of Wheezy on my husband's box.



on-board sound on my box: chipset Intel Z77 Express chipset



root@Tux-II:/home/lisi# lshw | grep snd

  configuration: driver=snd_hda_intel latency=0



I have no idea where to look.  I have googled the error message, and get a

lot of hits.  It is obviously a common error, but I could see no solutions

that seemed to fit my situation.  Probably couldn't see the wood for the

trees. :-(



Two people had succeeded by purging everything Alsa related and installing

Alsa from upstream, though one of them had to run snddevices after every

boot.  Hardly satisfactory, especially on my husband's box.



Any suggestions, please?  Ought I to purge and install from upstream?  In

general, I prefer to stick to Debian versions.



Thanks for any help,

Lisi





--

To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org

with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/201309131458.27255.lisi.re...@gmail.com


I ran into an alsa issue awhile back and solved it by altering the conf file.  
May or may not be of any help.  I wrote it up here

http://linuxbbq.org/bbs/viewtopic.php?f=9&t=409


I hope I am not hyjacking this thread but, while my problem seems to be 
somewhat different, it still started with a wheezy upgrade that killed 
my sound system. I don't think that any one has identified the root 
cause of this problem and are kind of using a shot gun approach to the 
problem solving. So let me get as specific as I can. Running as root 
'service alsa-utils restart' produced the following return:

root@mysystem:/etc# service alsa-utils restart
[ ok ] Shutting down ALSA...done.
[] Setting up ALSA...warning: 'alsactl restore' failed with 
error message 'Home directory /root not ours.'...Home 
directory /root not ours

Can anyone explain this error message and suggest a fix.

I hope my above statement doesn't insult anyone. I know a lot of effort 
has gone into this thread. But my observation still stands. I'm finding 
references to this problem all over google but no reasonable solutions. 
I can't believe that there are more than one or two actual problems 
here. Programs just don't usually break in multiple ways all at the same 
time.


Gary R

Re: Sound problems on Wheezy upgrade

[drew craig]

On Friday, September 13, 2013 10:00:03 AM UTC-4, Lisi Reisz wrote:
> The problem has arisen since I upgraded.  Sound was fine in Squeeze.
> 
> 
> 
> Now, when I run alsamixergui:
> 
> 
> 
> lisi@Tux-II:~$ alsamixergui
> 
> 
> 
> I get an error box saying:
> 
> 
> 
> alsamixer: function snd_mixer_load failed: invalid argument
> 
> 
> 
> No pulseaudia is installed. 
> 
> 
> 
> I get the same problem on a fresh install of Wheezy on my husband's box.
> 
> 
> 
> on-board sound on my box: chipset Intel Z77 Express chipset
> 
> 
> 
> root@Tux-II:/home/lisi# lshw | grep snd
> 
>  configuration: driver=snd_hda_intel latency=0
> 
> 
> 
> I have no idea where to look.  I have googled the error message, and get a 
> 
> lot of hits.  It is obviously a common error, but I could see no solutions 
> 
> that seemed to fit my situation.  Probably couldn't see the wood for the 
> 
> trees. :-(
> 
> 
> 
> Two people had succeeded by purging everything Alsa related and installing 
> 
> Alsa from upstream, though one of them had to run snddevices after every 
> 
> boot.  Hardly satisfactory, especially on my husband's box.
> 
> 
> 
> Any suggestions, please?  Ought I to purge and install from upstream?  In 
> 
> general, I prefer to stick to Debian versions.
> 
> 
> 
> Thanks for any help,
> 
> Lisi
> 
> 
> 
> 
> 
> -- 
> 
> To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
> 
> with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
> 
> Archive: http://lists.debian.org/201309131458.27255.lisi.re...@gmail.com


I ran into an alsa issue awhile back and solved it by altering the conf file.  
May or may not be of any help.  I wrote it up here

http://linuxbbq.org/bbs/viewtopic.php?f=9&t=409


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/f3d723d2-19db-41c6-917e-d807a9338...@googlegroups.com

Re: Sound problems on Wheezy upgrade

[Gregory Nowak]

On Thu, Sep 19, 2013 at 02:36:11PM +0100, Lisi Reisz wrote:
> I am still struggling with this.  I have come to the conclusion that the only 
> way that I personally am going to succeed with this is to edit a 
> configuration file, but I cannot find what to edit to.  I have found advice 
> on editing the Pulse configuration file on the net, but what I have tried has 
> not helped so I have gone back to the original vanilla file.

I assume we're still dealing with pulseaudio (I.E. you haven't
uninstalled it)? If yes, then in the default debian pulseaudio setup
the file to edit is /etc/pulse/default.pa as far as I know. If you
already edited that with no success, can you please give an overview
of what you tried changing there? 

On another note, I don't think anyone has mentioned this so far. When
you ran alsamixer you said you only saw Master and Capture. However,
running alsamixer/amixer as root should let you view all
controls. Have you tried that? Also, according to the alsamixer man
page,

alsamixer -Vall

will let you view all the card controls, not just playback or just
recording. You might want to try invoking alsamixer like that if you
already haven't in the hope that it will then let you deal with the
controls which are proving elusive to deal with. Finally, have a look
at /var/lib/alsa/asound.state. Hopefully one of these suggestions will
help.

Greg


-- 
web site: http://www.gregn..net
gpg public key: http://www.gregn..net/pubkey.asc
skype: gregn1
(authorization required, add me to your contacts list first)

--
Free domains: http://www.eu.org/ or mail dns-mana...@eu.org


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130919212121.ga7...@gregn.net

Re: Sound problems on Wheezy upgrade

[Lisi Reisz]

On Monday 16 September 2013 23:20:21 Lisi Reisz wrote:
> On Monday 16 September 2013 22:02:05 Gregory Nowak wrote:
> > On Mon, Sep 16, 2013 at 09:51:17AM +0100, Lisi Reisz wrote:
> > > I had thought that sound was probably muted somewhere - I just couldn't
> > > find where!  amixer shows it clearly.  All (all? ;-) ) I now have to do
> > > is use the man pages to find out how to unmute the master at the
> > > command line.  I have found how to unmute capture, but capture isn't
> > > muted!
> >
> > Try this:
> >
> > amixer set Master unmute
>
> Thank you for continuing to help, Gregory.  Still no sound. :-(
>
> Radu is right about the PulseAudio default, so that at least is wrong and
> needs correcting.  I'm not being very successful, so I'll get some sleep
> and hope to have a clearer head in the morning!  (F6 -> select correct card
> -> no change.  Ditto with S.)

I am still struggling with this.  I have come to the conclusion that the only 
way that I personally am going to succeed with this is to edit a 
configuration file, but I cannot find what to edit to.  I have found advice 
on editing the Pulse configuration file on the net, but what I have tried has 
not helped so I have gone back to the original vanilla file.

What I need to do, it seems to me, since the n-curses alsamixer will not 
accept any alterations, is to edit a configuration file in such a way as to 
change the default. But searching for this has got me nowhere.

Any suggestions, please?

Many thanks,
Lisi


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201309191436.11561.lisi.re...@gmail.com

Re: Sound problems on Wheezy upgrade

[Marko Randjelovic]

On Mon, 16 Sep 2013 23:20:21 +0100
Lisi Reisz  wrote:

> On Monday 16 September 2013 22:02:05 Gregory Nowak wrote:
> > On Mon, Sep 16, 2013 at 09:51:17AM +0100, Lisi Reisz wrote:
> > > I had thought that sound was probably muted somewhere - I just
> > > couldn't find where!  amixer shows it clearly.  All (all? ;-) ) I
> > > now have to do is use the man pages to find out how to unmute the
> > > master at the command line.  I have found how to unmute capture,
> > > but capture isn't muted!
> >
> > Try this:
> >
> > amixer set Master unmute
> 
> Thank you for continuing to help, Gregory.  Still no sound. :-(  
> 
> Radu is right about the PulseAudio default, so that at least is wrong
> and needs correcting.  I'm not being very successful, so I'll get
> some sleep and hope to have a clearer head in the morning!  (F6 ->
> select correct card -> no change.  Ditto with S.)
> 
> Lisi
> 
> 

What does this output?

amixer -c N scontents (list each control settings for card N)

I presume your card 0 is pulseaudio, your real sound card is no 1. There may be 
also other devices.

Also, you can list sound modules:

lsmod | grep snd

Also, you can see what is your sound card:

lspci | grep Audio

Regards

-- 
Marko Ranđelović, B.Sc.
Software Developer
Niš, Serbia
marko...@eunet.rs
http://mr.flossdaily.org

Note: If you see a nonsense enclosed between lines

BEGIN PGP SIGNATURE
END PGP SIGNATURE

then this message is digitally signed using OpenPGP compliant software.
You need an appropriate plugin for your email client or other OpenPGP
compliant software in order to verify the signature. However, the concept
of computer insecurity implies digital signature is not absolute proof of
identity.


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130917134628.696c1...@eunet.rs

Re: Sound problems on Wheezy upgrade

[Lisi Reisz]

On Monday 16 September 2013 22:02:05 Gregory Nowak wrote:
> On Mon, Sep 16, 2013 at 09:51:17AM +0100, Lisi Reisz wrote:
> > I had thought that sound was probably muted somewhere - I just couldn't
> > find where!  amixer shows it clearly.  All (all? ;-) ) I now have to do
> > is use the man pages to find out how to unmute the master at the command
> > line.  I have found how to unmute capture, but capture isn't muted!
>
> Try this:
>
> amixer set Master unmute

Thank you for continuing to help, Gregory.  Still no sound. :-(  

Radu is right about the PulseAudio default, so that at least is wrong and 
needs correcting.  I'm not being very successful, so I'll get some sleep and 
hope to have a clearer head in the morning!  (F6 -> select correct card -> no 
change.  Ditto with S.)

Lisi


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201309162320.21149.lisi.re...@gmail.com

Re: Sound problems on Wheezy upgrade

[Lisi Reisz]

On Monday 16 September 2013 14:10:38 rudu wrote:
> Le 16/09/2013 10:51, Lisi Reisz a écrit :
> > On Monday 16 September 2013 01:41:29 Gregory Nowak wrote:
> >> I suggest you run either amixer/alsamixer,
> >> and see if they will let you unmute sound.
> >
> > I had tried to run alsamixer.  It gave me two channels, neither of which
> > helped. (master and capture)  I tied all possible variations that I could
> > think of with no result.  I obviously wasn't thinking very well. :-(
> >
> > I had thought that sound was probably muted somewhere - I just couldn't
> > find where!  amixer shows it clearly.  All (all? ;-) ) I now have to do
> > is use the man pages to find out how to unmute the master at the command
> > line.  I have found how to unmute capture, but capture isn't muted!
>
> FWIW, when I run alsamixer, it defaults to the channels of pulseaudio
> (master and capture).
> To get the actual channels of my audiocard, I have to explicitly choose
> it via the F6 key.

Thanks, Rudu. :-)

This is certainly wrong in mine - both card and chip are set to PulseAudio.  I 
have tried both ways (F6 and S) to change to my card, which is listed, but 
when I select it nothing happens.  I'll attack it again in the morning and 
hope to have more success.

Lisi


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201309162315.50258.lisi.re...@gmail.com

Re: Sound problems on Wheezy upgrade

[Gregory Nowak]

On Mon, Sep 16, 2013 at 09:51:17AM +0100, Lisi Reisz wrote:
> I had thought that sound was probably muted somewhere - I just couldn't find 
> where!  amixer shows it clearly.  All (all? ;-) ) I now have to do is use the 
> man pages to find out how to unmute the master at the command line.  I have 
> found how to unmute capture, but capture isn't muted!

Try this:

amixer set Master unmute

Greg


-- 
web site: http://www.gregn..net
gpg public key: http://www.gregn..net/pubkey.asc
skype: gregn1
(authorization required, add me to your contacts list first)

--
Free domains: http://www.eu.org/ or mail dns-mana...@eu.org


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130916210205.ga12...@gregn.net

Re: Sound problems on Wheezy upgrade

[rudu]

Le 16/09/2013 10:51, Lisi Reisz a écrit :

On Monday 16 September 2013 01:41:29 Gregory Nowak wrote:

I suggest you run either amixer/alsamixer,
and see if they will let you unmute sound.

I had tried to run alsamixer.  It gave me two channels, neither of which
helped. (master and capture)  I tied all possible variations that I could
think of with no result.  I obviously wasn't thinking very well. :-(

I had thought that sound was probably muted somewhere - I just couldn't find
where!  amixer shows it clearly.  All (all? ;-) ) I now have to do is use the
man pages to find out how to unmute the master at the command line.  I have
found how to unmute capture, but capture isn't muted!

Thanks, both.  I'll report back for the archives when (if?) I succeed.

Lisi

Hi Lisi,
FWIW, when I run alsamixer, it defaults to the channels of pulseaudio 
(master and capture).
To get the actual channels of my audiocard, I have to explicitly choose 
it via the F6 key.


HTH
Rudu


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/5237034e.6090...@cegetel.net

Re: Sound problems on Wheezy upgrade

[Lisi Reisz]

On Monday 16 September 2013 01:41:29 Gregory Nowak wrote:
> I suggest you run either amixer/alsamixer,
> and see if they will let you unmute sound.

I had tried to run alsamixer.  It gave me two channels, neither of which 
helped. (master and capture)  I tied all possible variations that I could 
think of with no result.  I obviously wasn't thinking very well. :-(

I had thought that sound was probably muted somewhere - I just couldn't find 
where!  amixer shows it clearly.  All (all? ;-) ) I now have to do is use the 
man pages to find out how to unmute the master at the command line.  I have 
found how to unmute capture, but capture isn't muted!

Thanks, both.  I'll report back for the archives when (if?) I succeed.

Lisi


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201309160951.17960.lisi.re...@gmail.com

Re: Sound problems on Wheezy upgrade

[Gregory Nowak]

On Mon, Sep 16, 2013 at 07:58:20AM +0900, Joel Rees wrote:
> FWIW  ...
> 
> On Mon, Sep 16, 2013 at 6:53 AM, Lisi Reisz  wrote:
> > No sound :-( but loads of output.  I cut the longest one short.  See
> > http://paste.ubuntu.com/6112471/
> >
> >> Seeing the output of:
> >>
> >> pactl list cards
> >>
> >> as a normal user would be interesting, though it's a bit lengthy.
> >
> > See:  http://paste.ubuntu.com/6112471/  again.
> >
> > There is a gap between them and they are in that order.
> >
> > Thanks for all your help.
> >
> > Lisi
> 
> I think I added mixers until I got one that gave me a master mute
> button and clicked that to un-mute.
> 
> I should have tried un-muting from the command line, I think.
> 
> I think the problem is that, after the upgrade, it ends up defaulting
> to muted, and somehow the default GUI controls decide not to give you
> access to the master sound control.

Based on the output Lisi provided, I'd say that's the case. The output
from paplay shows what I would expect. It seems to be playing all the
sound files you gave it to play. Same thing for pactl. Though I'm not
a pulse expert by any means, that doesn't have anything obvious that
jumps out at me either. It looks like it is as Joel suggests, your
sound is muted, that's the only explanation I can think of. I know you
tried alsamixer before you installed pulse, but have you tried it
since then? If not, then I suggest you run either amixer/alsamixer,
and see if they will let you unmute sound.

Greg


-- 
web site: http://www.gregn.net
gpg public key: http://www.gregn.net/pubkey.asc
skype: gregn1
(authorization required, add me to your contacts list first)

--
Free domains: http://www.eu.org/ or mail dns-mana...@eu.org


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130916004128.ga31...@gregn.net

Re: Sound problems on Wheezy upgrade

[Joel Rees]

FWIW  ...

On Mon, Sep 16, 2013 at 6:53 AM, Lisi Reisz  wrote:
> On Sunday 15 September 2013 21:11:47 Gregory Nowak wrote:
>> On Sun, Sep 15, 2013 at 07:19:17PM +0100, Lisi Reisz wrote:
>> > I'm afraid that I am woefully ignorant about sound, and cannot interpret
>> > anything there.
>>
>> Well, it seems to say that aplay is recognizing your sound hardware. I
>> get something similar when I run aplay -L, but with hardware different
>> from yours of course. Can you try playing a file as a normal user
>> using paplay (E.G. paplay -v file.wav). What happens? Do you get
>> sound? What output does paplay display?
>
> No sound :-( but loads of output.  I cut the longest one short.  See
> http://paste.ubuntu.com/6112471/
>
>> Seeing the output of:
>>
>> pactl list cards
>>
>> as a normal user would be interesting, though it's a bit lengthy.
>
> See:  http://paste.ubuntu.com/6112471/  again.
>
> There is a gap between them and they are in that order.
>
> Thanks for all your help.
>
> Lisi

I think I added mixers until I got one that gave me a master mute
button and clicked that to un-mute.

I should have tried un-muting from the command line, I think.

I think the problem is that, after the upgrade, it ends up defaulting
to muted, and somehow the default GUI controls decide not to give you
access to the master sound control.

-- 
Joel Rees

Be careful where you see conspiracy.
Look first in your own heart.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAAr43iNEF=XCyF9FcQQhWtGG5r=und3ttjvmy-rxqtgflw+...@mail.gmail.com

Re: Sound problems on Wheezy upgrade

[Lisi Reisz]

On Sunday 15 September 2013 21:11:47 Gregory Nowak wrote:
> On Sun, Sep 15, 2013 at 07:19:17PM +0100, Lisi Reisz wrote:
> > I'm afraid that I am woefully ignorant about sound, and cannot interpret
> > anything there.
>
> Well, it seems to say that aplay is recognizing your sound hardware. I
> get something similar when I run aplay -L, but with hardware different
> from yours of course. Can you try playing a file as a normal user
> using paplay (E.G. paplay -v file.wav). What happens? Do you get
> sound? What output does paplay display? 

No sound :-( but loads of output.  I cut the longest one short.  See
http://paste.ubuntu.com/6112471/

> Seeing the output of: 
>
> pactl list cards
>
> as a normal user would be interesting, though it's a bit lengthy.

See:  http://paste.ubuntu.com/6112471/  again.

There is a gap between them and they are in that order.

Thanks for all your help.

Lisi


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201309152253.49725.lisi.re...@gmail.com

Re: Sound problems on Wheezy upgrade

[Gregory Nowak]

On Sun, Sep 15, 2013 at 07:19:17PM +0100, Lisi Reisz wrote:
> I'm afraid that I am woefully ignorant about sound, and cannot interpret 
> anything there.

Well, it seems to say that aplay is recognizing your sound hardware. I
get something similar when I run aplay -L, but with hardware different
from yours of course. Can you try playing a file as a normal user
using paplay (E.G. paplay -v file.wav). What happens? Do you get
sound? What output does paplay display? Seeing the output of:

pactl list cards

as a normal user would be interesting, though it's a bit lengthy.

Greg


-- 
web site: http://www.gregn.net
gpg public key: http://www.gregn.net/pubkey.asc
skype: gregn1
(authorization required, add me to your contacts list first)

--
Free domains: http://www.eu.org/ or mail dns-mana...@eu.org


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130915201147.ga24...@gregn.net

Re: Sound problems on Wheezy upgrade

[Lisi Reisz]

Hello, Dan.  Thanks for your help.

Between now and the email from Gregory I had installed pulseaudio.

I can now run alsamixergui, but there are only two channels, master and 
chapter, and nothing I do to either enables sound.

On Sunday 15 September 2013 19:02:48 Dan Ritter wrote:
> aplay -L
>
> what audio devices does it show?

lisi@Tux-II:~$ aplay -L
default
Playback/recording through the PulseAudio sound server
sysdefault:CARD=PCH
HDA Intel PCH, ALC887-VD Analog
Default Audio Device
front:CARD=PCH,DEV=0
HDA Intel PCH, ALC887-VD Analog
Front speakers
surround40:CARD=PCH,DEV=0
HDA Intel PCH, ALC887-VD Analog
4.0 Surround output to Front and Rear speakers
surround41:CARD=PCH,DEV=0
HDA Intel PCH, ALC887-VD Analog
4.1 Surround output to Front, Rear and Subwoofer speakers
surround50:CARD=PCH,DEV=0
HDA Intel PCH, ALC887-VD Analog
5.0 Surround output to Front, Center and Rear speakers
surround51:CARD=PCH,DEV=0
HDA Intel PCH, ALC887-VD Analog
5.1 Surround output to Front, Center, Rear and Subwoofer speakers
surround71:CARD=PCH,DEV=0
HDA Intel PCH, ALC887-VD Analog
7.1 Surround output to Front, Center, Side, Rear and Woofer speakers
iec958:CARD=PCH,DEV=0
HDA Intel PCH, ALC887-VD Digital
IEC958 (S/PDIF) Digital Audio Output
hdmi:CARD=PCH,DEV=0
HDA Intel PCH, HDMI 0
HDMI Audio Output
lisi@Tux-II:~$

I'm afraid that I am woefully ignorant about sound, and cannot interpret 
anything there.

Thanks for your help,
Lisi


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201309151919.17007.lisi.re...@gmail.com

Re: Sound problems on Wheezy upgrade

[Lisi Reisz]

Thanks for the reply, Gregory. :-)

On Sunday 15 September 2013 04:31:15 Gregory Nowak wrote:
> On Fri, Sep 13, 2013 at 02:58:27PM +0100, Lisi Reisz wrote:
> > The problem has arisen since I upgraded.  Sound was fine in Squeeze.
> >
> > Now, when I run alsamixergui:
> >
> > lisi@Tux-II:~$ alsamixergui
> >
> > I get an error box saying:
> >
> > alsamixer: function snd_mixer_load failed: invalid argument
>
> User lisi is in the audio group, right?

Yes.

lisi@Tux-II:~$ groups
lisi cdrom floppy audio dip video plugdev netdev scanner

> > No pulseaudia is installed.
>
> I'm wondering if that might have something to do with it, since at
> least the gnome desktop in wheezy seems to insist on pulseaudio. What
> happens if you run for example amixer as root? If that works, but
> running amixer as a regular user doesn't, then it sounds like a
> permissions issue.

See below.  I'll try installing pulseaudio and see if that helps, so long as 
it doesn't try to bring in too much extraneous stuff.

Lisi

lisi@Tux-II:~$ amixer
amixer: Mixer default load error: Invalid argument
lisi@Tux-II:~$ su
Password:
root@Tux-II:/home/lisi# amixer
amixer: Mixer default load error: Invalid argument
root@Tux-II:/home/lisi# alsamixer
cannot load mixer controls: Invalid argument
root@Tux-II:/home/lisi# alsamixergui

No protocol specified
Can't open display: :0
root@Tux-II:/home/lisi# su lisi
lisi@Tux-II:~$ alsamixer
cannot load mixer controls: Invalid argument
lisi@Tux-II:~$ alsamixergui

I get an error box saying:
alsamixer: function snd_mixer_load failed: invalid argument


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201309151725.57847.lisi.re...@gmail.com

Re: Sound problems on Wheezy upgrade

[Gregory Nowak]

On Fri, Sep 13, 2013 at 02:58:27PM +0100, Lisi Reisz wrote:
> The problem has arisen since I upgraded.  Sound was fine in Squeeze.
> 
> Now, when I run alsamixergui:
> 
> lisi@Tux-II:~$ alsamixergui
> 
> I get an error box saying:
> 
> alsamixer: function snd_mixer_load failed: invalid argument

User lisi is in the audio group, right?

> 
> No pulseaudia is installed. 
> 

I'm wondering if that might have something to do with it, since at
least the gnome desktop in wheezy seems to insist on pulseaudio. What
happens if you run for example amixer as root? If that works, but
running amixer as a regular user doesn't, then it sounds like a
permissions issue.

Greg


-- 
web site: http://www.gregn..net
gpg public key: http://www.gregn..net/pubkey.asc
skype: gregn1
(authorization required, add me to your contacts list first)

--
Free domains: http://www.eu.org/ or mail dns-mana...@eu.org


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130915033115.gb7...@gregn.net