On Fri, 22 Jun 2007 19:49:41 +0200
Joost Yervante Damad <[EMAIL PROTECTED]> wrote:
> does it now work fine always or does it still require fiddling by you?
What exactly do you want me to test here? I'll try to answer anyway,
by guesswork:
"Always", as in every way, no. My prior messages described how
after upgrading 'timidity', it failed, and thereafter can be made to
fail depending on some lines in '/etc/alsa.conf'.
"Always" works -- yes, if 'alsa.conf' is empty, which it wasn't before
upgrading.
Perhaps 'alsa' has changed in the last ten days, and 'timidity' might
work with the old configuration again? Let's try it:
# prior to this I reverted '/etc/asound.conf' to how it was
# on June 11
% /etc/init.d/alsa force-reload
Terminating processes: 3539 4076 4109 4423.
Unloading ALSA sound driver modules: snd-seq-oss snd-seq-dummy
snd-pcm-oss snd-ens1371 snd-seq-virmidi snd-seq-midi snd-rawmidi
snd-seq-midi-event snd-rtctimer snd-intel8x0 snd-ac97-codec snd-mixer-oss
snd-pcm snd-seq snd-timer snd-seq-device snd-page-alloc.
Loading ALSA sound driver modules: snd-seq-oss snd-seq-dummy
snd-pcm-oss snd-ens1371 snd-seq-virmidi snd-seq-midi snd-rawmidi
snd-seq-midi-event snd-rtctimer snd-intel8x0 snd-ac97-codec snd-mixer-oss
snd-pcm snd-seq snd-timer snd-seq-device snd-page-alloc.
% /etc/init.d/pulseaudio start
% /etc/init.d/timidity start
Starting: timidity*** PULSEAUDIO: Unable to connect: Connection refused
failed!
One difference this time is that after commenting out the troublesome
lines in 'alsa.conf', restarting 'alsa' with 'force-reload' didn't
restore sound or allow 'timidity' to restart. A reboot worked though.
HTH...
PS: Did the 'strace' output show anything interesting?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
