I still experience this issue with v3.4.6 built from MacPorts. Evidently, they rolled back the patch due to undesirable side effects: https://trac.macports.org/ticket/62769#comment:12