Description of problem: Hello! I have installed a minimal system, later task-x11, task-gnome and then xboard. It reports errors: ALSA lib conf.c:3407:(config_file_open) cannot access file /usr/share/alsa/alsa.conf.d//99-default.conf ALSA lib conf.c:3327:(snd_config_hooks_call) function snd_config_hook_load returned error: No such file or directory ALSA lib conf.c:3769:(snd_config_update_r) hooks failed, removing configuration aplay: main:660: audio open error: No such file or directory After some research: lrwxrwxrwx 1 root root 56 lis 26 14:22 /usr/share/alsa/alsa.conf.d//99-default.conf -> ../../../../etc/sound/profiles/current/alsa-default.con $ env LC_ALL=C ls -lh /etc/sound/profiles/current/alsa-default.conf ls: cannot access /etc/sound/profiles/current/alsa-default.conf: No such file or directory $ env LC_ALL=C ls -lh /etc/sound/profiles/current/ canberra.conf profile.conf snd-oss.conf Version-Release number of selected component (if applicable): $rpm -qa|grep alsa alsa-utils-1.0.24.2-5.mga2 lib64alsa2-1.0.24.1-6.mga2 lib64alsa-oss0-1.0.17-6.mga1 libalsa-data-1.0.24.1-6.mga2 lib64alsa-plugins-1.0.24-4.mga2 Steps to Reproduce: 1. Install Mageia 2 Alpha 1 minimal system 2. Install task-x11, task-gnome (with suggested packages) 3. Install xboard (with suggested packages) 4. run xboard and read errors
@ Colin Sorry, I can't think of any smart questions to ask, nor could anyone who looked at this bugreport since it was filed. Can you help?
CC: (none) => mageia, marja11Summary: Alsa cannot access file 99-default.conf => Alsa cannot access file 99-default.conf in Mageia 2 Alpha 1 minimal systemSource RPM: libalsa-data-1.0.24.1-6.mga2.src.rpm => libalsa2-1.0.24.1-6.mga2.src.rpm
This is actually more or less fixed now, but I still need to submit the packages... I was waiting for the apprentice who did the changes to get back to me with a comment about the SVN log entries. The problem is simply that the package: alsa-plugins-pulseaudio is not installed. Not sure why it's not installed tho'. It certainly should be pulled in by a typical install... not sure why it's not, but that is another issue (and possibly one that will be fixed by the fix that should be committed). *** This bug has been marked as a duplicate of bug 2966 ***
Status: NEW => RESOLVEDResolution: (none) => DUPLICATE