Bug 127698

Summary:	G-streamer-error in ALSA util
Product:	[Fedora] Fedora	Reporter:	Roland Warting <roland.warting>
Component:	gstreamer	Assignee:	John (J5) Palmieri <johnp>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4	CC:	jkeck
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2008-02-13 18:54:41 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 Roland Warting 2004-07-12 18:35:03 UTC

Description of problem:

Uname:
Linux localhost.localdomain 2.6.5-1.358 #1 Sat May 8 09:04:50 EDT 2004
i686 athlon i386 GNU/Linux


How reproducible:


Steps to Reproduce:
1. Clicka a .wav-file on desktop
2. sound utility (standard Gnome) 2.6.0
3. Clicking play
  
Actual results:
popup with message 1
Could'nt get information from resource (klicking close)
popup message 2
internal G-streamer-error, send report (what i am doing now)

Expected results:
Playing the sound-file

Additional info:

Comment 1 Colin Walters 2004-09-22 06:31:49 UTC

Which sound utility came up?  Was it "Music Player" (rhythmbox)?

Comment 2 Pavel Šefránek 2005-06-19 09:00:37 UTC

(In reply to comment #1)
> Which sound utility came up?  Was it "Music Player" (rhythmbox)?
If I choose ALSA sound system in gstreamer-properties, it says: Failed to
construct test pipeline for 'ALSA - Advanced Linux Sound Architecture'. If is
ALSA choosed in gstreamer-properties, Rhytmbox says these error messages:
popup with message 1
Could'nt get information from resource (klicking close)
popup message 2
internal G-streamer-error, send report (what i am doing now)
I'm using Fedora Core 4.

Comment 3 petrosyan 2008-02-13 18:54:41 UTC

Fedora Core 4 is not maintained anymore.

Setting status to "INSUFFICIENT_DATA". If you can reproduce this bug in the
current Fedora release, please reopen this bug and assign it to the
corresponding Fedora version.