It is fixed already in firmware 4.0.1 release 1

Can you describe the problem?