Bug#33784 has been addressed and will be available in the 4.0.6 release scheduled to come out soon. Continue reading...