I noticed this behaviour in lucid also. But it is always and in my case it has nothing to do with resume, because I do not resume the machine anyway. The workaround of putting a clock rate of 48000 in /etc/pulse/daemon.conf does not help either.
Maybe this is a new bug?
I noticed this behaviour in lucid also. But it is always and in my case it has nothing to do with resume, because I do not resume the machine anyway. The workaround of putting a clock rate of 48000 in /etc/pulse/ daemon. conf does not help either.
Maybe this is a new bug?