gstreamer+esound problem in Feisty->Gutsy upgrade

Bug #160317 reported by Luke Robison on 2007-11-05
Affects Status Importance Assigned to Milestone
rhythmbox (Ubuntu)

Bug Description

I recently upgraded to Gutsy on my amd64, and found that neither rhythmbox nor totem could produce any sound. I initially thought the problem lay in Gstreamer, but found that gst-launch would play my files (mostly mp3s) without problems. Sound from all other sources seems to work fine as well (vlc, xine, amarok... )

In Rhythmbox, when I double click on a song in my library, the Artist and Album indicators show that the file has been read (or maybe just library info) but the song progress indicator stays at the left side, and the song has an Icon next to it that indicates 'pause'. No errors are printed. If i right click on the song in the library at this point I get the usual pop-up with an error icon and the text "Could not establish connection to sound server" at the bottom of the window. If I press the "Play" button, the following errors are printed:
(rhythmbox:17697): RhythmDB-CRITICAL **: rhythmdb_entry_ref: assertion `entry != NULL' failed

(rhythmbox:17697): RhythmDB-CRITICAL **: rhythmdb_entry_get_string: assertion `entry != NULL' failed
after this, the icon beside the song in the library turns to a Red and White "do not enter" icon. Right clicking on the song produces the regular popup, but with the same icon and the following text: "Internal GStreamer Error: state change failed"
Rhythmbox has all plugins (including visualizations) disabled.

In totem, videos play fine, but no sound is produced, and the volume button is disabled. By turning the visualization to Monoscope I can confirm that the audio is being decoded correctly, but simply not being played.
no errors are printed.

 I have removed and reinstalled the gstreamer0.10-plugins-ugly package (as well as *-good and *-bad)

**Edit: fixed typo, changed Summary

description: updated
Luke Robison (lukerobison) wrote :

Needed packages for gstreamer were not installed when upgrading from Feisty to Gutsy on an amd64. specifically "esound".

I had "esound-common" and "gstreamer0.10-esd" installed after upgrading, but not "esound" or "esound-clients". After installing these two, Rhythmbox will now play music, but only if another source is also playing a sound (Totem, or Amarok).

With no other application using the sound, the problem persists as described above

description: updated
Luke Robison (lukerobison) wrote :

immediately after installing esound, rhythmbox would not work consistently, but after a reboot the problem seems to be gone entirely. I would mark this bug as closed, but it might be a package management error that caused this in the first place.

Brian Murray (brian-murray) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at . I have classified this bug as a bug in rhythmbox as those bug triagers will be best able to help you.

Pedro Villavicencio (pedro) wrote :

Closing this bug as per reporter comments, thanks.

Changed in rhythmbox:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers