rhytmbox error when double clicking on a song

[Lucas Goss]

seems to be related to bug 13095. rhytmbox now comes up with almost random errors
that say the following:

Could not open resource for writing.

and

Could not start pipeline playing.

It happened to me when one song was playing and I double clicked on a new song
and also when one song finished playing and another was about to start (and I've
reproduced it many times). The application will also freeze sometimes after
receiving this error and trying to play a new song. As I mentioned in bug 13095 I
keep my system up to date so most likely a recent update (within the past week)
has affected rhtymbox.

[Sebastien Bacher (seb128)]

same question as 6740. Do you use hoary ? do you have the issue if you use
esound or alsasink/osssink ?

[Lucas Goss (lgoss007-gmail)]

Yes, hoary with ...
Default Sink: Enlightenment Sound Daemon
Default Source: OSS

[Sebastien Bacher (seb128)]

what version of the package is installed (dpkg -l esound) ?

[Lucas Goss (lgoss007-gmail)]

Hmm:

pn esound <none> (no description available)

So then I looked at synaptic and saw that I didn't have esound installed, just
esound-common:

ii esound-common 0.2.35-2ubuntu Enlightened Sound Daemon - Common files

Do I need esound? If I do then shouldn't it be installed by default with
rhythmbox and totem (same problem in totem)? Do I need esound-clients as well?
I've never changed any of my sound settings (besides the volume) and it's always
worked before. Well if you need anything else just let me know. Thanks.

[Sebastien Bacher (seb128)]

hoary has switched from esound to polypaudio, that's why I'm asking if you have
the issue with esound too. Could you install esound instead of polypaudio and
try if you get the bug ?

[Lucas Goss (lgoss007-gmail)]

Ahh. Yes esound makes it all work correctly. And other sound things that were
broken, such as the multimedia systems selector tests, now work as well. And I'm
not positive but I think the startup sound wasn't working as well. If you need
anymore tests just let me know. Oh and my hardware is the onboard nvidia nforce2.

[Sebastien Bacher (seb128)]

I'm closing this bug as a duplicate of #6740 and reassigning to polypaudio so

This bug has been marked as a duplicate of bug 13095.

[Sebastien Bacher (seb128)]

*** Bug 13095 has been marked as a duplicate of this bug. ***

[Sebastien Bacher (seb128)]

thanks for the debug, reassigning the bug.

Jeff, that's a bug for you :)

[Matt Zimmerman (mdz)]

Do you have the ubuntu-desktop package installed? If not, please install it and
re-test.

Jeff, what's your analysis of this bug and its severity?

[Lucas Goss (lgoss007-gmail)]

Ok, I've reinstalled ubuntu-desktop (it was uninstalled when I switched to
esound temporarily), and the audio now seems to be mostly working under polypaudio.

The only thing that I noticed that was not working is the welcome sound (when
logging in to Ubuntu), which played with esound but doesn't with polypaudio (not
sure about the exit sound, didn't test). So this is no longer as severe (for me
at least). Thanks.

[Daniel Robitaille (robitaille)]

(In reply to comment #11)
> The only thing that I noticed that was not working is the welcome sound (when
> logging in to Ubuntu), which played with esound but doesn't with polypaudio (not
> sure about the exit sound, didn't test).

the lack of login/logout sounds is a problem experienced by others (see for
example comment #2 of bug 13051)

[Matt Zimmerman (mdz)]

The original issue is fixed, and the problem with the login sound is tracked as
bug #13051, so closing. Thanks for testing.