Audio is broken on resume from Sleep in 12.04 on Asus UL50AG notebook

[Andrei]

This bug is present in Ubuntu 12.04. It was also present in 11.10 and before.

If I put the Asus UL50AG notebook to sleep and resume it, the audio is dead. Curiously, if speakers are connected to it BEFORE putting it to sleep, this bug doesn't apply. It just resumes from sleep and keeps on pumping out sound. When I say sound, I mean ANY sound. Not from a particular program.

Also, another instance of this bug was present on my desktop with Ubuntu 11.10. It had an Asus P5Q motherboard, a 7.1 Creative Soundblaster Audigy SE sound card and a 5.1 Logitech X-530 sound system. After resume from Sleep, the rear-left speaker was dead. Yes, only that one from the whole 5.1 system. So something is seriously messed up with ALSA.

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/944355/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 944355

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Andrei (andrei-doom)]

The output of that command was:

-----------------
No packages found matching linux.
ERROR: KeyError('ProblemType',)

Gdk-WARNING **: apport-gtk: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
-----------------

I don't know what this error means. Please do tell if I can be of further assistance.

[Brad Figg (brad-figg)]

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

[Andrei (andrei-doom)]

The bug is still present with kernel 3.2.0-18.28.

Just tested with mainline kernel 3.3 rc6; the sound is working as it should after resume from suspend. So this is fixed in that kernel release. Added corespondent tag. Didn't delete the other one, just to be safe. Awaiting further instructions.

[Andrei (andrei-doom)]

So I guess you didn't do anything on this front, right ? You hope it will automatically get fixed with 3.3 on Ubuntu 12.10 ?

[Andrei (andrei-doom)]

Bump

[Joseph Salisbury (jsalisbury)]

Yes this issue will be fixed in 12.10, since it will be based on a kernel newer than v3.3.

Have you tried the latest 12.04 updates to confirm this bug still exists there? If it does, we can perform a "Reverse bisect" to identify the commit that fixed this bug in v3.3.

[Andrei (andrei-doom)]

Up to date on all packages and this is still present. Well guess this is going to stay this way for 12.04 and under. Shame, but I'm ok with it; going to test 12.10 Alpha 1 from June + new ultrabook in a couple of weeks, so this issue is dead to me; I just thought it would be nice for other UL50AG users to have a fix by now...

[Joseph Salisbury (jsalisbury)]

@Andrei We could perform a reverse bisect to identify the commit that fixed this bug in upstream v3.3. Would you be able to test some test kernels to help in the bisect? If we can identify the commit that fixed this, we can submit it to upstream stable, which would allow the fix to propagate to 12.04 through the normal SRU process.

[Andrei (andrei-doom)]

I'll try to do my best.

[Andrei (andrei-doom)]

The bug is back in Quantal 3.4... This is getting nowhere, FAST.

[Joseph Salisbury (jsalisbury)]

Can you test the upstream 3.4 kernel, which Quantal is based off of:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.4-quantal/

That will tell us if the regression was introduced upstream or not.

[Andrei (andrei-doom)]

I just told you this is also present in 3.4...

[Andrei (andrei-doom)]

bump

[Joseph Salisbury (jsalisbury)]

So the bug exists in 3.2, 3.4 but not 3.3 rc6?

[Andrei (andrei-doom)]

Yes. At this rate, I'm going to change the laptop long before a fix is in place. That's IF there is going to be one.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test some of the later v3.3 release candidates, such as rc7? It would be very helpful to know when the regression was re-introduced.

[Andrei (andrei-doom)]

Would it make any difference ? Because I'm starting to question the usefulness of all these procedures, as I've seen tens of bugs from 2+ years ago, still unresolved.

So OK, let's assume you find the right version that contains the regression; how long does it take to resolve it ? 2 years ? 5 years ? 10 ? More ? Never ? Probably the last. In this case, I've lost all hope in open-source-ing... at least this type of it. And that's shame. Because at the same time, I hate all the corporate bullshit packed with Windows/OS X. And where am I standing then ? Well, between a half/quarter backed distribution and 2 OS'es that make me wanna puke every minute I use them. Disgrace to the whole software industry...

I'm retiring. This is a complete waste of time.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]