It seems this issue has been fixed upstream, v3.14.3 from their own Debian repo isn't affected.

Reply via email to