I tested 4.4.0-29 and can confirm it has the bug. For good measure I also tested 4.4.0-28 (I did 22 previously) and can confirm that the bug is not present in version 28.
I think we found the culprit in what ever happened between 28 and 29.
Cheers, Chris
I tested 4.4.0-29 and can confirm it has the bug. For good measure I also tested 4.4.0-28 (I did 22 previously) and can confirm that the bug is not present in version 28.
I think we found the culprit in what ever happened between 28 and 29.
Cheers, Chris