Bug#619504: Probably fixed in 2.6.32-34squeeze1
On Wed, 2011-05-25 at 15:13 +0200, firstname.lastname@example.org wrote:
> The bug seems to be fixed in current stable. After fast-forward
> upgrade from 2.6.32-30 to 2.6.32-34squeeze1, the trip points have
> remained exactly the same (see previous email).
Mark, does this new version also fix the problem on your computer
Once a job is fouled up, anything done to improve it makes it worse.