I can confirm that this bug is not present in KPDF 0.5.10. Perhaps the solution used there can be reintroduced.
I can confirm that this bug is not present in KPDF 0.5.10. Perhaps the solution used there can be reintroduced.