Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
For bugs related to Red Hat Enterprise Linux 5 product line. The current stable release is 5.10. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 642510

Summary: confusing sound device setup
Product: Red Hat Enterprise Linux 5 Reporter: Karel Volný <kvolny>
Component: firstbootAssignee: Martin Gracik <mgracik>
Status: CLOSED ERRATA QA Contact: Release Test Team <release-test-team-automation>
Severity: medium Docs Contact:
Priority: low    
Version: 5.5CC: atodorov, dmach
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: firstboot-1.4.27.9-1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-02-21 06:40:37 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:
Bug Depends On:    
Bug Blocks: 726828    

Description Karel Volný 2010-10-13 07:41:15 UTC
Description of problem:
I've tried to install RHEL-5.5 using qemu.
I haven't configured any sound devices in qemu, however, after setting up the user account there comes another screen for sound card setup. It tells me that a sound device was found and then it tells me that no soundcard was found - a bit schizophrenic ...

Version-Release number of selected component (if applicable):
RHEL5.5-Server-20100322.0-x86_64-DVD

How reproducible:
(haven't tried)

Steps to Reproduce:
1. try to install RHEL5 like
qemu-kvm -m 1024 -cdrom RHEL5.5-Server-20100322.0-x86_64-DVD.iso RHEL5
2. use the defaults, go through the installation until you get to the Sound card screen

Actual results:
it says something like (rough translation, I've run the installer using Czech language):

A sound device was found at your computer.

Click "Play the testing sound" ....

No soundcard was found.


Expected results:
If no soundcard is found, this configuration screen shouldn't appear at all. If it needs to appear, then at least it should say that something was found right before it says that nothing was found ...

Additional info:

Comment 1 Martin Gracik 2010-11-18 14:55:23 UTC
I already have a patch for this.

Comment 2 RHEL Program Management 2011-01-11 20:24:01 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated in the
current release, Red Hat is unfortunately unable to address this
request at this time. Red Hat invites you to ask your support
representative to propose this request, if appropriate and relevant,
in the next release of Red Hat Enterprise Linux.

Comment 3 RHEL Program Management 2011-01-11 22:34:41 UTC
This request was erroneously denied for the current release of
Red Hat Enterprise Linux.  The error has been fixed and this
request has been re-proposed for the current release.

Comment 5 RHEL Program Management 2011-08-05 12:29:46 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release.  Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products.  This request is not yet committed for inclusion in an Update
release.

Comment 6 Martin Gracik 2011-08-22 08:33:27 UTC
Fixed in firstboot-1.4.27.9-1

Comment 8 Alexander Todorov 2011-12-02 12:51:07 UTC
With firstboot-1.4.27.9-1 I removed the sound device from my KVM guest and firstboot didn't ask me to configure any sound devices. Moving to VERIFIED.

Comment 9 errata-xmlrpc 2012-02-21 06:40:37 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2012-0278.html