Bug 117066

Summary:	SuSE Yast can't handle config files generated by alsaconf
Product:	[openSUSE] openSUSE 11.0	Reporter:	Alexey Eremenko <al4321>
Component:	YaST2	Assignee:	Ladislav Slezák <lslezak>
Status:	RESOLVED WONTFIX	QA Contact:	Klaus Kämpf <kkaempf>
Severity:	Major
Priority:	P4 - Low	CC:	tiwai
Version:	Beta 2
Target Milestone:	---
Hardware:	PC
OS:	All
Whiteboard:
Found By:	Third Party Developer/Partner	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	y2log of yast2-sound crash

Description Alexey Eremenko 2005-09-14 18:16:06 UTC

After using "alsaconf" to configure my Sound card, it writes a file to
"/etc/modprobe.d/sound" and this file prevents usage of SuSE's Yast.

In other words SuSE's Yast - Sound Hardware Configurator doesn't understands
configuration files generated by "alsaconf".

To reproduce:

1) ensure that you'r sound works
2) start "alsaconf" as root, and install sound card.
3) go to SuSE's Yast Sound Hardware configurator
4) try either to disable/edit/remove a sound device autodetected by "alsaconf"

I think this is an issue in Yast2.

Comment 1 Alexey Eremenko 2005-09-18 15:33:23 UTC

Hello, is anyone looking at this bug ? ?

Comment 2 Ladislav Slezák 2005-09-19 14:34:06 UTC

The problem is that yast writes some extra information into the config file. The
souncard configured by alsaconf is not bind to any detected sound card in the
yast module.

One solution woud be to write the extra information by alsaconf, but I it would
need to compute 'uniqe key'.

Or the yast module could try to assign unknown device to any detected device.
(I'm not sure how to handle multiple cards though.)

Takashi, what dou you think?

Comment 3 Alexey Eremenko 2005-09-22 19:45:52 UTC

I think, it would be smarter to leave "alsaconf" as generic as possible, but
modify Yast to understand generic config files.

Comment 4 Nicolas Dubail 2005-10-28 19:51:26 UTC

Created attachment 55957 [details]
y2log of yast2-sound crash

After upgrading from 9.3 to 10.0 sound wasn't working (my conf was heavily changed). I think about reinstalling alsa and in the package description it was proposed to run yast or alsaconf for configuration. I run alsaconf and it works. After reboot same problem, i've tried yast2-sound and it show 2 cards : one without number, model Intel 82801DB-ICH4 and one not configured model 82801[snip]AC'97. It was not possible to delete the first card and trying to modify it crash yast2-sound. For the second trying to modify it leads to an error saying that kernel module snd-intel8x0and refuse.

Comment 5 Nicolas Dubail 2005-10-28 20:02:46 UTC

oops... rest of my comment. 
[kernel module snd-intel8x0] can't be loaded. 
After I had a quick look at the alsaconf code that reads :
#remove entries by yast2 sound configurator
remove_y2_block() {....

This lead to this workaround : 
- delete /etc/modprobe.d/sound ("alias snd-card-0 snd-intel8x0\n
alias sound-slot-0 snd-intel8x0") created by alsaconf. 
- run yast2 sound to configure the autodetected card.

I'm ready to

Comment 6 Christoph Thiel 2008-04-23 12:05:53 UTC

Closing WONTFIX, since this bug has been reported for 10.0.

Comment 7 Alexey Eremenko 2008-05-05 20:32:46 UTC

Unfortunately this bug is still relevant for all openSUSE 10.x series, as well as 11.0 (as of BETA2).

One community man told me of a possible solution to manage shared config file by Yast and other tools:
-Apply checksum to config files written by YaST (Feature No: 303374)

-Technolgov

Comment 8 Ladislav Slezák 2009-09-21 13:51:38 UTC

Our ALSA maintainer says that alsaconfig is obsoleted and should not be used at all.

Therefor resolving as WONTFIX.