Comment 146 for bug 320632

Thanks for narrowing it down to that change. I think just reverting that patch is probably the wrong thing to do, since that would regress the feature entirely. Instead, further analysis is needed in order to discern why with this patch it is failing in this fashion. My guess is that it is incorrectly making automatic adjustment assumptions with this hardware.

Also, I'm beginning to suspect this may have a hardware-specific aspect to it, in which case I'm unsure that blocking the release on this is warranted. But I'll leave the milestone/target alone for now; I think a fix is within sight.

Alberto, do you have further comments/plans on this that need accounted for?