So this fix will never make it to the Ubuntu 18.04 repositories? It was applied a long time ago upstream, yet the latest version in the 3.0.x series is 3.0.5, which contains the bug. According to Ubuntu's package update policies, 18.04 users will forever be stuck with 3.0.x. There is no version 3.0.6 which contains the upstream fix that is available on the 18.04 repositories.
So this fix will never make it to the Ubuntu 18.04 repositories? It was applied a long time ago upstream, yet the latest version in the 3.0.x series is 3.0.5, which contains the bug. According to Ubuntu's package update policies, 18.04 users will forever be stuck with 3.0.x. There is no version 3.0.6 which contains the upstream fix that is available on the 18.04 repositories.