I confirm this bug still present at this time in the packaged 3.0.4 release.

The issue has been fixed upstream in the stable release 3.0.6.

Reply via email to