On Sat, Sep 25, 2010 at 11:50:36PM EST, Mark Shuttleworth wrote:
> On 24/09/10 00:17, Luke Yelavich wrote:
> > There was an update to alsa-utils today. Everybody please update their
> > systems, completely delete ~/.pulse/ and restart your system to check
> > that all is working again..
>
> If this fix does work, how are we going to handle updates? Can we reset
> the contents of .pulse programatically on first-login-after-upgrade?
No, and as far as I am aware, packages are not allowed to touch files in a user's home directory. I was only suggesting this as a quick way of making sure pulseaudio is set back to default volume levels. All being well, when users upgarde from lucid, this bug will not surface, and their pulseaudio preferences, however simple or complex they may be, will be kept.
On Sat, Sep 25, 2010 at 11:50:36PM EST, Mark Shuttleworth wrote: after-upgrade?
> On 24/09/10 00:17, Luke Yelavich wrote:
> > There was an update to alsa-utils today. Everybody please update their
> > systems, completely delete ~/.pulse/ and restart your system to check
> > that all is working again..
>
> If this fix does work, how are we going to handle updates? Can we reset
> the contents of .pulse programatically on first-login-
No, and as far as I am aware, packages are not allowed to touch files in a user's home directory. I was only suggesting this as a quick way of making sure pulseaudio is set back to default volume levels. All being well, when users upgarde from lucid, this bug will not surface, and their pulseaudio preferences, however simple or complex they may be, will be kept.