I found it just after sending the patch for 3.8.1 to the port maintainer... what a timing. Release Notes say there are several bug fixes, so let's try again. It looks OK for 3.8.2, so I made a patch (from 3.8.0 to 3.8.2) and sent it again.…