The commit for this issue in Maverick came in via a stable upstream release (2.6.35.14). As such it is not subject to the standard bug verification process.
The commit for this issue in Maverick came in via a stable upstream release (2.6.35.14). As such it is not subject to the standard bug verification process.