Red Hat Bugzilla – Bug 249985
Sound Card not Detected (but have sound)
Last modified: 2008-08-02 19:40:35 EDT
Description of problem:
Version-Release number of selected component (if applicable):
How reproducible: Every time
Steps to Reproduce:
1. Run system-config-soundcard
No sound, popup dialog says to create included log files
To hear sound and configure sound card
I have sound on Root and my logins however the girlfriend doesnt on hers (she
has no access to uninstall or install items since only I know the root password)
Gnuitar and Xine based media players report that soundcard is busy or another
program is using that device.
Sound Card is a SoundBlaster Audiology SE and usually uses the CA106 drivers
(which is what ALSA is currently using)
scsrun.log file contents
------- System Config Soundcard Log --------
Sat Jul 28 18:21:12 EDT 2007
aplay: main:545: audio open error: Device or resource busy
Running from command-line...
gtk.timeout_add is deprecated, use gobject.timeout_add instead
self.timer = gtk.timeout_add (100, self.checkStatus, self)
/usr/share/system-config-soundcard/soundcard.py:519: DeprecationWarning: use
self.sub_device_menu = gtk.OptionMenu()
/usr/share/system-config-soundcard/soundcard.py:571: DeprecationWarning: use
self.card_combo_menu = gtk.OptionMenu()
Created attachment 160178 [details]
Created attachment 160179 [details]
can you please attach output of "ll /dev/snd"? What username do you use and what
Usernames were blackspyder and blackbunny13. (ID #'s 500 and 501 I believe). I
have since had to downgrade to FC6 due to issues with Video card Drivers (namely
FGLXR didnt support both my card and the x server version at the same time). So
the install is long gone. However if the info from the FC6 install will help
i'll gladly send it along.
Is the problem in FC6? If so, please attach that info.
The information we've requested above is required in order
to review this problem report further and diagnose/fix the
issue if it is still present. Since there have not been any
updates to the report since thirty (30) days or more since we
requested additional information, we're assuming the problem
is either no longer present in the current Fedora release, or
that there is no longer any interest in tracking the problem.
Setting status to "CLOSED INSUFFICIENT_DATA". If you still
experience this problem after updating to our latest Fedora
release and can provide the information previously requested,
please feel free to reopen the bug report.
Thank you in advance.
Note that maintenance for Fedora 7 will end 30 days after the GA of Fedora 9.