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 500610 - a trace on pidgin told me to report a bug here, and here it is.
a trace on pidgin told me to report a bug here, and here it is.
Status: RESOLVED NOTABUG
Product: GStreamer
Classification: Platform
Component: dont know
0.10.x
Other Linux
: Normal normal
: NONE
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-11-30 08:20 UTC by Ethan Anderson
Modified: 2007-12-06 09:31 UTC
See Also:
GNOME target: ---
GNOME version: 2.1/2.2



Description Ethan Anderson 2007-11-30 08:20:31 UTC
(23:12:10) jabber: Sending (ssl): <message type='chat' id='purplee49c0051' to='kumailht@gmail.com/Talk.v104FD00A2FF'><active xmlns='http://jabber.org/protocol/chatstates'/></message>
(23:12:10) gstreamer: Resource busy or not available.
(23:12:10) gstreamer: Internal GStreamer error: state change failed.  Please file a bug at http://bugzilla.gnome.org/enter_bug.cgi?product=GStreamer.
(23:12:10) GLib-GObject: invalid uninstantiatable type `(null)' in cast to `GstObject'

I thought I'd do what it says.
Ubuntu Gutsy, everything up to date.
...PulseAudio sound server.
--wait, is pidgin making assumptions?  Should they be telling me to send bugs here?  What is the relationship between GStreamer and PulseAudio?
Comment 1 Tim-Philipp Müller 2007-12-06 09:31:32 UTC
The log shows two error messages generated by GStreamer.  The first one is the 'proper' one.  The second one is the generic fallback one that the user should never really get to see, and the way it's meant is that you should only really file a bug if your application shows you this in an error dialog :)

Also, usually the application resets the pipeline to NULL state when it encounters  the first error message, which would flush/discard all following error messages (since the first is the 'most precise' one).  I don't know if pidgin fails to do this properly, or if it lists the second error message on purpose here, but it does not really look like a bug in GStreamer.

As for the problem itself: the 'Resource busy or not available' error might be due to pidgin trying to open an audio device directly instead of going via pulseaudio (which has this device already open for its own use).  You might be able to fix this by playing with the pidgin configuration settings or the GNOME settings via  System => Preferences => Sound.

If this doesn't help, you might be able to find more support in the pidgin or ubuntu fora.