No sound after setting login sounds for gdm

[Saurabh]

I am a new user to Ubuntu but I have become quite familiar to it now.Recently I encountered this problem.I tried to change log in sounds via Login Window Option in preferences section.There were three options namely Log in,Successfull Login and Login Fail.I assigned sounds for Successful Login and Login Fail.Whenever i do so all sounds stop working.Rhythmbox,Banshee and any movie player cannot play any sound files.As soon as the Log in sounds are disabled the Player sounds come back to original.I changed the sound formats to WAV,MP3 and WMV too.But I encountered the same problem.I found no solution to it.

[Mike Pelley (mikepelley)]

I have this problem as well, and it appears to be a race condition of sorts between GDM playing sound and ALSA attempting to initialize. When GDM is configured to play a sound for "Login Successful", the hw:0 PCM device is busy when ALSA attempts to open it. After I've logged in, I cannot get any sound from ALSA. When I open the Volume Control dialog, there is a device labelled "Playback: Null Output (PulseAudio Mixer)". When things are working correctly, this device is labelled "Playback: HDA Intel - AD198x Analog (PulseAudio Mixer)".

The following lines of my /var/log/user.log file relate to the problem:

Jul 28 18:22:19 haven pulseaudio[3372]: alsa-util.c: Error opening PCM device hw:0: Device or resource busy
Jul 28 18:22:19 haven pulseaudio[3372]: module.c: Failed to load module "module-alsa-sink" (argument: "device_id=0 sink_name=alsa_output.pci_8086_269a_sound_card_0_alsa_playback_0 tsched=0"): initialization failed.

When I uncheck the "Login successful" sound in System / Administration / Login Window / Accessibility and logout/login, everything works fine.

[Victor Vargas (kamus)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it without more information. Would you please add the information requested from the "Reporting Sound Bugs" section of https://wiki.ubuntu.com/DebuggingSoundProblems as separate attachments? Thanks in advance.

[Mike Pelley (mikepelley)]

Here is the requested information - let me know if you need anything else.

[Victor Vargas (kamus)]

Thanks for your reply sir, but please do not confirm your own reports.
Regards

[Mike Pelley (mikepelley)]

This comment is not clear to me. First, the original report is not
mine. Second, I understood that "confirmed" represented the bug, and
since the bug had already been marked confirmed previously (by someone
else) this seemed to be a reasonable state.

It had been marked incomplete briefly, so I responded and returned the
bug to it's previous state. Marking it "new" now means that the fact
that the bug had been confirmed has been lost, which seems to be less
than optimal.

Mike.

On Mon, Oct 12, 2009 at 11:01 AM, Kamus <email address hidden> wrote:
> Thanks for your reply sir, but please do not confirm your own reports.
> Regards
>
>
> ** Changed in: linux (Ubuntu)
>       Status: Confirmed => New
>
> --
> No sound after setting login sounds for gdm
> https://bugs.launchpad.net/bugs/400529
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “linux” package in Ubuntu: New
>
> Bug description:
> I am a new user to Ubuntu but I have become quite familiar to it now.Recently I encountered this problem.I tried to change log in sounds via Login Window Option in preferences section.There were three options namely Log in,Successfull Login and Login Fail.I assigned sounds for Successful Login and Login Fail.Whenever i do so all sounds stop working.Rhythmbox,Banshee and any movie player cannot play any sound files.As soon as the Log in sounds are disabled the Player sounds come back to original.I changed the sound formats to WAV,MP3 and WMV too.But I encountered the same problem.I found no solution to it.
>

[Saurabh (saurabhprimal)]

I was just playing on Ubuntu.I fixed this problem.I converted the format of the sound file to OGG using an audio converter easily available on the internet.The login sound has no problem now.You can now assign any sound of your own when you login.

Saurabh

[Victor Vargas (kamus)]

@Mike, sorry I was a litle bit confused hehe. @Saurabh according to your last comment I will close this report because apparently your issue was fixed after a configuration update ;-)

Best regards

[Mike Pelley (mikepelley)]

No problem Kamus - as you can see I'm overly sensitive to correction ;o)

I was thinking this should remain open, as the login sounds provided
as defaults after install cause this problem. I guess a fix would be
to change those sounds to ogg in the gnome-audio distribution, but it
would be better to leave it open until any reasonable sound format can
be used without triggering the obscure error.

Mike.

[Saurabh (saurabhprimal)]

@Mike-Yeah converting the sound file to OGG is the solution to this problem.I have tried it out.There is no problem now.

@Kamus- i too think this should remain open as the defaults are really a problem at the beginning.

thanks

Saurabh

[Mike Pelley (mikepelley)]

I moved this back to confirmed again, as Saurabh and I thought appropriate. Please correct me if I've got that wrong.

[penalvch (penalvch)]

Saurabh, 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 in the development release from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux <replace-with-bug-number>

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.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.

Please let us know your results. Thanks in advance.

[Launchpad Janitor (janitor)]

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