GNOME Bugzilla – Bug 551273
GStreamer core error in banshee: StateChange
Last modified: 2008-09-13 19:16:22 UTC
all of a sudden I can't play music anymore. Instead banshee spits out hundreds of the following 2 error messages: GStreamer core error: StateChange GStreamer resource error: NotFound Not very informative I'd say. Maybe somebody here has got an idea what happened or can point me towards the right place to ask (if this isn't the right one :-). My problem started after I had installed sound-juicer (somebody suggested to use sound-juicer to rip the CDs, since I just can't get banshee to fetch metadata). I installed sound-juicer and ripped 2 CDs (without any problems) and also played a CD. But next time I called banshee I got those odd GStreamer errors and now I also get them when I try to play music with sound-juicer. But then again that might be pure coincidence. Nevertheless I de-installed sound-juicer, but the errors didn't disappear for banshee. I'm at a total loss. Maybe I should try to reinstall gstreamer, but there are so many packages, that I have no idea what I should select. e.g. I see many gstreamer-0_10... packages as well as gstreamer010... ones with yast2. OS: openSuse 10.3
Could you start banshee from a terminal window / command line, like this: $ GST_DEBUG=*:5 banshee 2>dbg.log and then reproduce the error and exit, and then do bzip dbg.log and attach the dbg.log.bz2 file?
Created attachment 118463 [details] log file created with GST_DEBUG=*:5 banshee 2>dbg.log zipped with bzip2
Thanks. This is a known issue of old versions of gst-plugins-good (fixed in -good 0.10.7). The main issue is that you get a bad error message though. Ultimately this is a configuration issue (no alsa 'default' device exists and there's no sound server), so you need to run gnome-sound-properties and select the right outputs there. 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 ***