[ubuntu-uk] ubuntu-uk Digest, Vol 16, Issue 4

[Sean Miller]

Lee Tambiah wrote:
>> ----- Original Message -----
>> From: ubuntu-uk-request at lists.ubuntu.com
>> To: ubuntu-uk at lists.ubuntu.com
>> Subject: ubuntu-uk Digest, Vol 16, Issue 4
>> Date: Wed, 16 Aug 2006 12:00:17 +0100
>>
>>
>> Send ubuntu-uk mailing list submissions to
>> 	ubuntu-uk at lists.ubuntu.com
>>
>> To subscribe or unsubscribe via the World Wide Web, visit
>> 	https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk
>> or, via email, send a message with subject or body 'help' to
>> 	ubuntu-uk-request at lists.ubuntu.com
>>
>> You can reach the person managing the list at
>> 	ubuntu-uk-owner at lists.ubuntu.com
>>
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of ubuntu-uk digest..."
>>
>>
>> Today's Topics:
>>
>>     1. Re:  Sound woes - Dapper (Sean Miller)
>>
>>
>> ----------------------------------------------------------------------
>>
>> Message: 1
>> Date: Wed, 16 Aug 2006 11:44:02 +0100
>> From: Sean Miller <sean at seanmiller.net>
>> Subject: Re: [ubuntu-uk] Sound woes - Dapper
>> To: British Ubuntu Talk <ubuntu-uk at lists.ubuntu.com>
>> Message-ID: <44E2F6F2.3080602 at seanmiller.net>
>> Content-Type: text/plain; charset=us-ascii; format=flowed
>>
>> Paul Sladen wrote:
>>     
>>> What one normally does in this case is to file a bug report:  ;-)
>>>
>>>   https://launchpad.net/distros/ubuntu/+source/gnome-media/+filebug
>>>
>>> so that the appropriate people can debug it with you.  It's best to do this
>>> as soon-as-possible after you notice a change in behaviour so that the
>>> maintainer can match it up to anything they might have changed at the same
>>> point.
>>>
>>>       
>> Seeing as I filed the bug report well over 24 hours ago and it hasn't
>> even been "triaged" yet, so clearly the development team are at
>> Linuxworld California or similar, I will repeat my request on this
>> supposedly community list for ideas on how I can diagnose the issue with
>> sound.
>>
>> As I said, I did nothing to make it stop working, or not at least
>> consciously.
>>
>> Any ideas on commands I could run to find out what's wrong?
>>
>> Ta!
>>
>> Sean
>>
>>     
>
> Upgrades or patchs can change the alsa volume states, there is two things you can try. In terminal type "alsamixer" and ensure all your channels are up and unmuted. Or even better there is a command to reset the alsa settings back to its original default, but I can not remember the command :-(, though I can tell you later when I get Home from work.
>   
More, fundamental than that... it seems to have lost communication with 
the sound device...

seanmiller at seanmiller-laptop:/windows$ alsamixer

alsamixer: function snd_ctl_open failed for default: No such device
seanmiller at seanmiller-laptop:/windows$

LiveCD works fine... so it's something that's happened to the hard drive 
install... as I said there was no event that I could put it down to.

Sean