Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: alsa-utils-1.0.20-2.fc11.i586's "alsactl init" fails to parse /usr/share/alsa/init/default $ alsactl init Unknown hardware: "ICH" "Realtek ALC650F" "AC97a:414c4723" "0x1509" "0x3140" Hardware is initialized using a guess method /usr/share/alsa/init/default:51: control element not found /usr/share/alsa/init/default:52: missing closing brace for format /usr/share/alsa/init/default:52: error parsing CTL attribute /usr/share/alsa/init/default:52: invalid rule This issue is new with alsa-utils-1.0.20, alsa-utils-1.0.19 did not have this problem: $ alsactl init Unknown hardware: "ICH" "Realtek ALC650F" "AC97a:414c4723" "0x1509" "0x3140" Hardware is initialized using a guess method Version-Release number of selected component (if applicable): alsa-utils-1.0.20-2.fc11.i586 How reproducible: Always, on one particular machine. Steps to Reproduce: c.f. above Actual results: c.f. above Expected results: function Additional info: # lspci -nn ... 00:02.7 Multimedia audio controller [0401]: Silicon Integrated Systems [SiS] AC'97 Sound Controller [1039:7012] (rev a0) ..
Changing version to FC10: FC10 is also affected: with alsa-utils-1.0.19: # alsactl init Unknown hardware: "ICH" "Realtek ALC650F" "AC97a:414c4723" "" "" Hardware is initialized using a guess method with alsa-utils-1.0.20 (1.0.20-1.fc10): # alsactl init Unknown hardware: "ICH" "Realtek ALC650F" "AC97a:414c4723" "0x1509" "0x3140" Hardware is initialized using a guess method /usr/share/alsa/init/default:51: control element not found /usr/share/alsa/init/default:52: missing closing brace for format /usr/share/alsa/init/default:52: error parsing CTL attribute /usr/share/alsa/init/default:52: invalid rule Same machine.
alsa-utils-1.0.20-3.fc11 has been submitted as an update for Fedora 11. http://admin.fedoraproject.org/updates/alsa-utils-1.0.20-3.fc11
alsa-utils-1.0.20-2.fc10 has been submitted as an update for Fedora 10. http://admin.fedoraproject.org/updates/alsa-utils-1.0.20-2.fc10
alsa-utils-1.0.20-3.fc11 has been pushed to the Fedora 11 stable repository. If problems still persist, please make note of it in this bug report.
alsa-utils-1.0.20-2.fc10 has been pushed to the Fedora 10 stable repository. If problems still persist, please make note of it in this bug report.
The problem still persist in a Fedora 11 new installation with the same card.
Could you check alsa-utils package version and post error messages?
This message is a reminder that Fedora 10 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 10. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '10'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 10's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 10 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.