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 571682 - Internal GStreamer error: state change failed. When Playing MP3
Internal GStreamer error: state change failed. When Playing MP3
Status: RESOLVED DUPLICATE of bug 471364
Product: GStreamer
Classification: Platform
Component: dont know
0.10.x
Other All
: Normal major
: NONE
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-02-13 20:40 UTC by Mark E Johnson
Modified: 2009-02-14 12:48 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description Mark E Johnson 2009-02-13 20:40:07 UTC 
Please describe the problem:
I tried to play an MP3 file by double clicking it.  The MP3 file type is associated with Totem using GStreamer.

Steps to reproduce:
1. double click on any MP3 file
2. 
3. 


Actual results:
The following error occurs:
Totem could not play 'file:///home/mejohn/workplace-tmp/notes4ED8AA/~8829834.mp3'.

You do not have a decoder installed to handle this file. You might need to install the necessary plugins.

then

Internal GStreamer error: state change failed.  Please file a bug at http://bugzilla.gnome.org/enter_bug.cgi?product=GStreamer.

Expected results:
I would expect Totem, using GStreamer for MP3 decoding, to play the MP3 audio file.

Does this happen every time?
The error occurs every time, and the MP3 file is never played.

Other information:
Comment 1 Philip Withnall 2009-02-13 21:35:05 UTC 
The error message said to file a bug for GStreamer, not Totem => moving to GStreamer. Could you please attach the MP3 which causes the problem to this bug report, or if that's not possible, the first few tens of kilobytes.
Comment 2 Tim-Philipp Müller 2009-02-14 12:48:13 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


*** This bug has been marked as a duplicate of 471364 ***