Another FC4 Sound Problem Fix: No alsa sound as root

[JayTee]

Alsa sound problem: Sound system works as user, but alsa sound system does not work as root (may continue to show an error msg when starting root about not being able to start sound device, etc). Root sound may work originally or after installing new alsa-libs rpms, but will stop working after a switch to user and then switching back to root.

Solution and Fix: Alsa sound system is configured correctly for root initially. However, when user boots up for the first time, the dmix.conf and dsnoop.conf files (located in /etc/alsa/pcm/) get deleted!. When switched back to root mode, root can no longer find the missing sound-related files and issues errors msgs. Root can no longer start up the alsa sound system! To prevent this from happening, in the file /etc/alsa/ainit.conf, change "overwrite = yes" to "overwrite=no". This allows dmix.conf and dsnoop.conf to remain intact and alsa sound system operates ok in both user and root modes.

[DWeiner]

That's It!! That's my problem. Thanks for the tip. Now for the $64 question. I just extracted new dmix.conf and dsnoop.conf files (from the distro disk) into the /etc/alsa/pcm/ directory. The error message no longer appears upon root login and the sound works in user logons. Additionally, the sound works in root after a cold reboot. I don't normally work in root, but it just bothered my sense neatness. Thanks again.
:) djw

[gavinw6662]

Alsa sound problem: Sound system works as user, but alsa sound system does not work as root (may continue to show an error msg when starting root about not being able to start sound device, etc). Root sound may work originally or after installing new alsa-libs rpms, but will stop working after a switch to user and then switching back to root.

Solution and Fix: Alsa sound system is configured correctly for root initially. However, when user boots up for the first time, the dmix.conf and dsnoop.conf files (located in /etc/alsa/pcm/) get deleted!. When switched back to root mode, root can no longer find the missing sound-related files and issues errors msgs. Root can no longer start up the alsa sound system! To prevent this from happening, in the file /etc/alsa/ainit.conf, change "overwrite = yes" to "overwrite=no". This allows dmix.conf and dsnoop.conf to remain intact and alsa sound system operates ok in both user and root modes.

I will have to remember this in case I run into this problem when I upgrade.

[esrisupa]

I'm newbie here. So how can I extract dmix and dsnoop?

[DWeiner]

Hi esrisupa
To extract those files:
mount disk 1 of the distribution.
In Konqueror navigate to Fedora/RPMS/\alsa-lib-1.0.qrc4-2.i386.rpm
double left click on that archive icon.
a window will open with a file list.
find dmix.conf and dsnoop.conf and highlite them (hold down ctrl to highlite the second one)
left click on extract from the tool bar.
in the window that opens, double left click on "file system" in the left pane and navigate to /etc/alsa/pcm/ in the right pane. This is the extraction destination.
finally left click on extract in the lower

djw

[esrisupa]

Thanks you very much for your help and quick reply.....DWeiner

[fozner]

I was unable to apply this fix the first time I tried, probably because I was logged in as root in KDE at the time. Anyway, some time later, after messing other things up (rpm -e glibc) and re-installing, the problem was still there. This time, I changed the above mentioned config file while logged in as an unpriviliged user, using a root terminal. Since I was not logged in as root, I did not need to copy the files from CD and root will now use my existing configuration with no problems.

I hope it never happens but, if I ever have to log into KDE as root, there will be the lovely desktop sounds I am accustomed to. :rolleyes: