@kruemi
> Maybe you could explain why, despite these facts, the problem should
> be "blamed" on the upstream authors of applications instead of the
> change thad caused them all to break?
If you read comment #4, you will see that I agree with you, "Another way to confirm this as a definite Lucid issue and not a Folding@Home one is to confirm similar behavior with another application." Since people have done just that, it appears that this probably isn't an upstream Folding@Home issue.
@kruemi
> Maybe you could explain why, despite these facts, the problem should
> be "blamed" on the upstream authors of applications instead of the
> change thad caused them all to break?
If you read comment #4, you will see that I agree with you, "Another way to confirm this as a definite Lucid issue and not a Folding@Home one is to confirm similar behavior with another application." Since people have done just that, it appears that this probably isn't an upstream Folding@Home issue.