All sound channels are muted after failed shutdown
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu |
New
|
Undecided
|
Unassigned |
Bug Description
Yesterday, sound was working fine. I did nothing out of the ordinary with my computer. When I shut down the computer, it hung at "Stopping ALSA...". It hung for a maybe 30 seconds or so, then the screen went black with a flashing cursor, and I could type stuff that would just be printed on the screen. Pressing CTRL+ALT+DEL or the power button again would just "restart the shutdown", and it would hang again. I had to kill the computer by holding the power button.
After the computer was cold booted again, all sound was gone. (As I would realize later, all sound channels had been muted.) I rebooted and shutdown the computer several time, but each time it hung at "Stopping ALSA...". Had to give up.
Then, today, after being left turned off for about a day, the computer shuts down and restarts again as fine as ever.
Finally figured out, that all the sound channels had been muted. This took a good while to figure out... Un-muting the Master channel was not enough to get sound again, I had to un-mute PCM as well.)
I'm using Ubuntu 8.10. I'm using pulseaudio (as far as I know: there's a pulseaudio process running, and everything everywhere is set to auto.
Don't know if this is one or two bugs: that the sound became muted and that the shutdowns hanged...
Interestingly, I found someone with the EXACT same problem, here:
http://
Even his output of "aplay -l" is identical, by the character...
Thanks for helping to make Ubuntu better.
There are already a few bugs, that describe this behaviour. Could it be that these bugs appeared after an update?
There are different bugs, but one bug that caused the shutdown to fail was fixed in the last days, you could check if you want, just enable the -proposed repository. (That was bug 274995)
And for the sound problem are also many open bugs, one is bug 288039.
If you think that your bug is a duplicate of one of those bugs (I assume so) then you should mark it as a duplicate.