No sound in rhythmbox or any other application except through headphone jack

[Samuel Kerstein]

Binary package hint: rhythmbox

2.6.24-19-generic #1 SMP Wed Jun 18 14:43:41 UTC 2008 i686 GNU/Linux

Ubuntu 8.04

alsa-base 1.0.16-0ubuntu4

Lenovo Thinkcentre M57P

Sound chip: Intel HDA AD198x

I expected to hear sound when a CD was playing in rhythmbox.

ProblemType: Bug
Architecture: i386
Date: Wed Jul 2 20:15:11 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/rhythmbox
NonfreeKernelModules: fglrx
Package: rhythmbox 0.11.5-0ubuntu8
PackageArchitecture: i386
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: rhythmbox
Uname: Linux 2.6.24-19-generic i686

[Sebastien Bacher (seb128)]

thank you for your bug report, that's not a rhythmbox bug though, rather an alsa one or an user configuration issue

[Daniel T Chen (crimsun)]

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

[Samuel Kerstein (kerstein)]

Here is the URL: http://www.alsa-project.org/db/?f=c4d86bc21148d123500c172478a5a2012351f4ce
Thank you

[Dimitrios Symeonidis (azimout)]

setting back to new

[kernel-janitor (kernel-janitor)]

Hi Samuel,

This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you 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 linux-image-`uname -r` 245062

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.]

[Roland Meier (rm369)]

Hi,
I have the same problem, after upgrading to karmic (or after one of its normal updates - sorry) I had no sound output from the speakers from any application on my HP 550 laptop.
Sound output via headphone works, and speakers were no problem before in jaunty either.
I installed linux-backports-modules-alsa-karmic-generic with no effect.
After installing the updates from https://launchpad.net/~ubuntu-audio-dev the headphones also stopped working with the default configuration (no model= parameter for the snd-hda-intel module). They now work again with "options snd-hda-intel model=basic" or "model=hp" in /etc/modprobe.d/alsa-base.conf .
Most information should be in http://www.alsa-project.org/db/?f=1fad068e798f0fdc7563ba137172b7e4e9db9503
There are lots of similar bug messages here, none of which helped, so I picked the most similar one and added my current information. Please tell me how to help any further.

[Roland Meier (rm369)]

pulseaudio or alsa, not linux generic

[Daniel T Chen (crimsun)]

Please don't touch this bug. Symptom-based triaging must be done upon recommendation from a member of the actual audio development team. Roland, you should file a new bug.

[Roland Meier (rm369)]

OK, sorry. https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/492303 issued.

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

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