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 521475 - state change failed
state change failed
Status: RESOLVED DUPLICATE of bug 471364
Product: GStreamer
Classification: Platform
Component: dont know
0.10.14
Other Linux
: Normal normal
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-03-09 23:20 UTC by Eugene
Modified: 2008-03-10 06:38 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20

Attachments
player's debug output (30.81 KB, application/x-compressed-tar)
2008-03-09 23:26 UTC, Eugene 		Details

Description Eugene 2008-03-09 23:20:36 UTC 
While ( or after ) running some java apps ( like KGS client at www.gokgs.com and others) Rhythmbox 0.11.2 can't play mp3 files ( and maybe not just mp3s ), I get this error message :

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

Whenever I run the client mentioned ( http://files.gokgs.com/javaBin/cgoban.jnlp ) Rhythmbox stops working - it just stops playback. Sometimes when I quit the java application the problem stays. Right now I got the message after quitting all java apps and restarting the player. Of course, all other players are affected.

I use proprietary Sun's java 6  x64 at Ubuntu 7.10 x64, but I remember I had this bug while using earlier versions of Ubuntu on Intel x86

Sorry, no logs. Just don't know right now where to get them.
Comment 1 Eugene 2008-03-09 23:26:22 UTC 
Created attachment 106935 [details]
player's debug output
Comment 2 René Stadler 2008-03-10 06:38:49 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 ***