After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 554313 - Audio fails: "GStreamer resource error"
Audio fails: "GStreamer resource error"
Status: RESOLVED FIXED
Product: GStreamer
Classification: Platform
Component: dont know
0.10.0
Other All
: Normal normal
: NONE
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-09-29 15:26 UTC by Steve O'Grady
Modified: 2008-10-16 07:49 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24



Description Steve O'Grady 2008-09-29 15:26:09 UTC
Please describe the problem:
After upgrading to Intrepid, audio playback via Banshee 1.2.1 fails silently (no audio, icon appears next to track played). When run from a terminal, the following error is issued:

"[Error 18:13:39.734] GStreamer resource error: Settings"

The error appears to be unassociated with Banshee specifically, however, because playback also fails in Rhythmbox (though without triggering the same - or any, for that matter - warning.

Audio playback is only possible from VLC, which I believe does not use GStreamer as a backend.

Installed GStreamer version looks to be 0.10.

Have tried the fix recommended below [1]; this had no effect.

Steps to reproduce:
1. Open Banshee (or Rhythmbox, etc)
2. Play track from library


Actual results:
No sound produced, icon appears next to track, terminal returns error:
[Error 18:13:39.734] GStreamer resource error: Settings


Expected results:
Sound to be played

Does this happen every time?
Yes

Other information:
aplay and paplay both work on the same hardware, as does VLC. gstreamer-properties is currently set to PulseAudio Sound Server. Previously, it was set to ALSA. Neither allows Banshee or Rhythmbox to work.
Comment 1 Steve O'Grady 2008-10-09 05:38:48 UTC
After the latest round of updates to Intrepid, this bug has been resolved and Banshee now functions appropriately.