I second the issue with 4.2.4-1ubuntu10.2 as reported by @intronauta
4.2.4-1ubuntu10.2 seems to revert the previous fix.
I second the issue with 4.2.4-1ubuntu10.2 as reported by @intronauta
4.2.4-1ubuntu10.2 seems to revert the previous fix.