Bug 136000

Summary:	gnome-sound-recorder - Internal GStreamer error: pad problem.
Product:	[Fedora] Fedora	Reporter:	David Mohring <heretic>
Component:	gnome-media	Assignee:	John (J5) Palmieri <johnp>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	rawhide	CC:	jkeck, mstuff
Target Milestone:	---
Target Release:	---
Hardware:	i686
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2006-04-29 14:42:43 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description David Mohring 2004-10-16 16:37:55 UTC

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; rv:1.7.3) Gecko/20041012
Firefox/0.10.1

Description of problem:
gnome-sound-recorder : Record works fine, using ALSA or OSS , but try
to playback more than once and it replies with the error 

"Internal GStreamer error: pad problem.  File a bug."

Audio output to is set oss in gstreamer-properties due to
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=135990



Version-Release number of selected component (if applicable):
gnome-media-2.8.0-1

How reproducible:
Always

Steps to Reproduce:
1. Using gstreamer-properties set audio output to OSS, because ALSA
fails outright See
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=135990
2. launch the gnome-sound-recorder
3. record a message to wav
4. Play back once 
5. Play back again - Error message.

    

Actual Results:  "Internal GStreamer error: pad problem.  File a bug."

Additional info:

Comment 1 John Thacker 2006-04-29 14:42:43 UTC

From gnome-media RPM changelog:

* Tue May 17 2005 John (J5) Palmieri <johnp> 2.10.2-2
- remove gnome-sound-recorder because it hasn't worked for some time

So this won't be fixed since gnome-sound-recorder is removed.

Comment 2 John Thacker 2006-04-29 14:44:09 UTC

*** Bug 153972 has been marked as a duplicate of this bug. ***