Bug 129225

Summary: system-config-soundcard GUI doesn't start without a default soundcard
Product: [Fedora] Fedora Reporter: Ben Stanley <ben.stanley>
Component: system-config-soundcardAssignee: Bastien Nocera <bnocera>
Status: CLOSED DUPLICATE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 2   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-02-21 19:04:57 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 Ben Stanley 2004-08-05 13:09:46 UTC
Description of problem: 
Program fails to start GUI 
The following error output is given: 
[root@dragon RPMS]# system-config-soundcard 
Traceback (most recent call last): 
  File 
"/usr/share/system-config-soundcard/system-config-soundcard.py", line 
46, in ? 
    app = soundcard.childWindow() 
  File "/usr/share/system-config-soundcard/soundcard.py", line 160, 
in __init__ 
    self.primaryDeviceMenu.set_active(self.cardList.index(self.soundcardBackend.getDefaultCard())) 
ValueError: list.index(x): x not in list 
 
Version-Release number of selected component (if applicable): 
1.2.8-1 
 
How reproducible: 
I have two soundcards, and no entries in modules.conf to do with 
soundcards, so the default module is always 'None' in 
soundcardBackend.py. This causes a problem with setting the default 
soundcard in soundcard.py 
self.primaryDeviceMenu.set_active(self.cardList.index(self.soundcardBackend.getDefaultCard())) 
I commented out the above line and the tool ran fine for me. I then 
changed it to: 
                if self.soundcardBackend.getDefaultCard() != None: 
                    self.primaryDeviceMenu.set_active(self.cardList.index(self.soundcardBackend.getDefaultCard())) 
This appears to fix my problem.

Comment 1 Bill Nottingham 2004-09-17 21:49:29 UTC

*** This bug has been marked as a duplicate of 125349 ***

Comment 2 Red Hat Bugzilla 2006-02-21 19:04:57 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.