Yes, I noticed this with 5.1.18_Debian r114002 and I checked that it still happens with 5.1.22_Debian r115126, and my workaround still works as well.
Yes, I noticed this with 5.1.18_Debian r114002 and I checked that it still happens with 5.1.22_Debian r115126, and my workaround still works as well.