© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Okay I have just merged a fix for this behaviour this morning. This should hopefully be released Thursday. Basically the problem arises that on a amd64 machine the indicator starts before pulse audio does. The merge this morning makes the service at the backend ultimately robust against an unstable pulse audio scenario.