Well, if there are no processes running with "pulse" in their name, I ran "alsactl", and the error message mentions the contents of $HOME or "failure to initiate an X11 connection" - I'm not sure how that's "clearly" pulse to a normal person who's not familiar with every string in libpulsecommon.so. :)
All I've done is freshly install Lucid beta 1 using the alternate disk, update and dist-upgrade to get current, add the mythtv-frontend package, and turn on the PCM output using alsamixer. I've literally only spent a couple of hours on a fresh install on this particular machine. I played with it a little more, and clearing the DISPLAY variable before running the command makes the error message go away. In either case - with or without DISPLAY existing - the asound.state file is actually created. I ran an strace on alsactl, and sure enough, it's loading the pulse library and attempting to connect to the machine listed in DISPLAY right before that error message (pulse and X11 libs are loaded either way). So, I guess there's mostly a UI issue here: An error message is displayed which seems to indicate failure, even though the intended action is actually completed. I'd question why alsamixer is using pulse at all, but at this point, I'd be happy if either alsa or pulse somehow suppressed ignorable error messages. -- alsactl depends on X11 https://bugs.launchpad.net/bugs/557016 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
