> > > > Steps to reproduce: > > user$ /usr/sbin/alsactl names > > User can not write to /etc/asound.names > > > same occurs if I run as root. > > What tells > $ ls -al /etc/asound.names > ?
user$ ls -al /etc/asound.names ls: /etc/asound.names: No such file or directory user$ ls -la /etc/as* ls: /etc/as*: No such file or directory That file isn't supposed to exist according to dpkg: user$ dpkg -L alsa-utils|grep asound /usr/share/man/man1/asoundconf.1.gz /usr/bin/asoundconf I also checked for etc/asound.names, etc/asound and asound on p.d.o. Nothing. This is extremely weird, since the manual page explicitly mentions /etc/asound.conf user$ dpkg -L alsa-utils |grep etc /etc /etc/alsa /etc/alsa/modprobe-post-install.d /etc/alsa/modprobe-post-install.d/alsa-utils /etc/udev /etc/udev/rules.d /etc/udev/alsa-utils.rules /etc/init.d /etc/init.d/alsa-utils These are the alsa-* packages I have installed: user$ dpkg -l |grep alsa ii alsa-base 1.0.13-1 ALSA driver configuration files ii alsa-utils 1.0.13-1 ALSA utilities FWIW, /var/lib/alsa/asound.state looks normal user$ ls -al /var/lib/alsa/ total 16 drwxr-xr-x 2 root root 4096 2006-09-09 11:24 . drwxr-xr-x 41 root root 4096 2006-10-16 22:39 .. -rw-r--r-- 1 root root 5273 2006-10-18 07:50 asound.state > Could you please try as user > $ alsactl -f $HOME/asond_user.names names > and check that file? > > I tried same here with same soundcard and it is _not_ reproducible > for me. I still get a hard lockup. The file ~/asound_user.names is not created. I checked around in /var/log, all I could find were boot-time messages in /var/log/messages, eg Oct 18 20:46:42 tinsley kernel: es1968: not attempting power management. Oct 18 20:46:42 tinsley kernel: es1968: clocking to 48000 Thanks for your questions Vince -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
