Bug 164146 - Gstreamer-properties defaults to OSS
Summary: Gstreamer-properties defaults to OSS
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: gstreamer   
(Show other bugs)
Version: 4
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Adam Jackson
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-07-25 11:35 UTC by Sigge Kotliar
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2007-05-26 19:09:30 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Sigge Kotliar 2005-07-25 11:35:06 UTC 
Hi!

I just installed a brand new FC4 and didn't have any sound. After half an hour
of asking for help on IRC it turned out the reason was that gstreamer-properties
defaulted to OSS instead of ALSA or ESD.

Is there a reason for this behaviour? I though OSS was deprecated like two
Fedoras ago?
Comment 1 John (J5) Palmieri 2005-07-25 15:06:40 UTC 
It should be alsa.  Most likely a regression that was not caught.  This is the
first I have heard about it.
Comment 2 Sigge Kotliar 2005-07-25 15:56:43 UTC 
Do you want me to submit some kind of info? Let me know!
Comment 3 Christian Iseli 2007-01-22 10:44:32 UTC 
This report targets the FC3 or FC4 products, which have now been EOL'd.

Could you please check that it still applies to a current Fedora release, and
either update the target product or close it ?

Thanks.
Comment 4 Adam Jackson 2007-05-26 19:09:30 UTC 
Mass closure: This bug has been in NEEDINFO for over six weeks with no
additional information provided, and is therefore being closed.  If this bug is
still an issue for you, please supply the requested information, and reopen the bug.
Note You need to log in before you can comment on or make changes to this bug.