> The latter is my best suspicion so far. It might be the mixer applet,
> however, that does not actually talk to hal. It might pick it up by
> something in between. Does arecord start working again if you keep hal
> running, have a running GNOME session, but "killall mixer_applet2"?
No, killing the mixer applet did not fixed it (ie, hald running, arecord
error).
> The latter is my best suspicion so far. It might be the mixer applet,
> however, that does not actually talk to hal. It might pick it up by
> something in between. Does arecord start working again if you keep hal
> running, have a running GNOME session, but "killall mixer_applet2"?
No, killing the mixer applet did not fixed it (ie, hald running, arecord
error).
Getting out of GNOME to test now.