Bug 246053 - sound card not detected
Summary: sound card not detected
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: alsa-lib
Version: 6
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Martin Stransky
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-06-28 05:41 UTC by Donald Cohen
Modified: 2008-02-22 10:35 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-02-22 10:35:26 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
one of two files created on the system tab (46.74 KB, text/plain)
2007-06-28 05:41 UTC, Donald Cohen
no flags Details
the other file generated by the system tab (276 bytes, text/plain)
2007-06-28 05:42 UTC, Donald Cohen
no flags Details

Description Donald Cohen 2007-06-28 05:41:27 UTC
Description of problem:
sound card not recognized

Version-Release number of selected component (if applicable):
(What component is this?)

How reproducible:
System - Administration - Sound card detection
brings up a window titled Audio Configuration in the "sound test" tab.
I do the sound test, I hear nothing, I click the button saying so and
it tells me to file a bug report here.

Steps to Reproduce:
see above
  
Actual results:
 I don't hear the test sound

Expected results:
 I gather I'm supposed to hear something

Additional info:
 See attached files created on the system tab.

A few other details.
This is a Gateway MX6955
uname -a => Linux number8 2.6.20-1.2962.fc6 #1 SMP Tue Jun 19 19:27:14 EDT 2007
i686 i686 i386 GNU/Linux

Comment 1 Donald Cohen 2007-06-28 05:41:27 UTC
Created attachment 158093 [details]
one of two files created on the system tab

Comment 2 Donald Cohen 2007-06-28 05:42:46 UTC
Created attachment 158094 [details]
the other file generated by the system tab

Comment 3 Martin Stransky 2008-02-22 10:35:26 UTC
Logs look sane...shoudl be fixed in the latest fedora, if not please reopen.


Note You need to log in before you can comment on or make changes to this bug.