macbook 3.1: Internal speakers don't silence when headphone socket is used from boot.

Bug #205059 reported by Ian Ohr
20
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ALSA driver
Fix Released
Undecided
Unassigned
Mactel Support
Invalid
Undecided
Unassigned
linux (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

edited: 2008-04-21@2057GMT+1
I have a MacBook 3,1 and when I connect headphones or speakers to the headphones socket, before booting the laptop, audio comes out of both the headphones and the MacBook's internal speakers. If, the headphones are unplugged and replaced, normal operation is restored.

If I perform the same scenario in OSX leopard, nothing goes wrong. I suppose this means that the function of switching from speakers to headphones is software controlled.

Revision history for this message
ramaboo (david-ramaboo) wrote :

I have a similar problem on a macbook 3.1 with ubuntu 8.04 beta. if my headphones are plugged into when the computer is turned on then the sound comes out the speakers instead of headphones. If i unplug the headphones and plug them back in everything works as it should.

Revision history for this message
Ian Ohr (munk3h) wrote :

ramaboo, you are absolutely right. That is the actual behaviour I am getting. I did not look into this thoroughly enough. I am going to change the bug title and description. I am using Gutsy by the way.

Ian Ohr (munk3h)
description: updated
Revision history for this message
Daniel T Chen (crimsun) wrote :

Please execute the alsa-info.sh script referenced from https://wiki.ubuntu.com/DebuggingSoundProblems and attach the URL here.

Changed in alsa-driver:
status: New → Incomplete
Revision history for this message
Javier Jardón (jjardon) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in linux:
status: Incomplete → Invalid
Revision history for this message
Alex Karpenko (alexkarpenko) wrote :

I can confirm this issue also exists on my Macbook Pro 4,1 running Intrepid. Here's the requested information: http://www.alsa-project.org/db/?f=3e98928842d58d7406cd2458ada92aa525c294d1

I'm reopening the bug.

Changed in linux:
status: Invalid → New
Revision history for this message
Luke Yelavich (themuso) wrote :

Alex, this should be fixed for you in jaunty. If you are running jaunty, or are willing to try the latest jaunty alpha to make sure of this, could you please reply back stating whether things work or otherwise?

Thanks.

Javier Jardón (jjardon)
Changed in mactel-support:
status: New → Incomplete
Changed in linux:
status: New → Incomplete
Revision history for this message
Paul Maddox (paul-maddox-gmail) wrote :

I'm running the latest version of Jaunty and still have this problem.

Thanks.

Changed in mactel-support:
status: Incomplete → New
Changed in linux:
status: Incomplete → New
Revision history for this message
mike powers jr. (mjpowersjr) wrote :

I can confirm, I am also experiencing the same problem. The results of alsa-info.sh can be viewed at:

http://www.alsa-project.org/db/?f=c17110d637f32f60282b086d56f7ae5efde60629

I am able to compile / test patches if needed.

Revision history for this message
kernel-janitor (kernel-janitor) wrote :

Hi munk3h,

Please be sure to confirm this issue exists with the latest development release of Ubuntu. ISO CD images are available from http://cdimage.ubuntu.com/releases/ . Please then run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p alsa-base 205059

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

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

tags: added: kernel-sound
tags: added: needs-kernel-logs
tags: added: needs-upstream-testing
tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Przemysław Kochański (kochas315) wrote :

I experienced exact the same bug on Lenovo N200, with all versions of ubuntu, opensuse, fedora, and few others.
Only distro that doesn't have that bug is Sabayon (4.2)! I'm uploading alsa-info.sh generated on it, hope that will help. I have Sabayon currently installed so I can run more test/scripts/etc, just tell me what to do.

http://www.alsa-project.org/db/?f=a4c3daad8cd079bd255040aebae33eb47f049b94

Revision history for this message
Przemysław Kochański (kochas315) wrote :

I have just upgreaded to alpha 9.10 and the problem is gone! Thanks to developers!

Revision history for this message
Przemysław Kochański (kochas315) wrote :

It's wide bug, not mactel-specific

Changed in mactel-support:
status: New → Invalid
Revision history for this message
Przemysław Kochański (kochas315) wrote :

fixed with ALSA 1.0.20

Changed in alsa-driver:
status: New → Fix Released
Revision history for this message
Przemysław Kochański (kochas315) wrote :

not ubuntu but alsa bug

Changed in linux (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.