Stig said:
but haven't had a chance to get very far yet, I'm supposed to be at work, for one, and I only understand half of it anyway.
Don't try too hard to read the bug reports, most of the verbiage is just debugging information to try and find out where the problem is. The rest is mostly "me too!" postage
I don't use Ubuntu, but a cursory look through the bug report shows that;
It's a confirmed bug with the ubuntu kernel (that's the package that includes your audio drivers) that was passed down from the "official" Linux kernel
The fix hasn't been globally released yet (I figure the report status would be changed to "resolved" by that point)
There are packages you can install manually to solve it (hopefully, they seem to be very much YMMV at the moment)
If you're not wanting to get too involved installing packages outside of synaptic, then I'd generally say you should wait until the bug is closed and then it'll be incorporated in a standard ubuntu update and thus automagically fixed with an upgrade. Restarting ALSA after you resume is just a workaround (as it unloads and then reloads the sound drivers which usually gets them working) for the time being, as you surmised
Suspend and hibernate are the biggest bugbears with Linux at the moment, due almost entirely to ACPI (that's the hardware spec that governs all this power management gubbins) being a standard that no hardware manufacturer seems to be able to follow properly; I had a problem on my HP nx7300 where ACPI would bugger up (resulting in a 1 minute POST) if the keyboard module wasn't unloaded on shutdown. These issues sometimes get fixed with BIOS updates, but usually it's left to the device drivers to work around these bugs themselves.
OK, thread derail over
