Seems to be basically the same problem as 1.0.18-r1 solved by unmasking 1.0.19-r2 as per Bugzilla Bug 231848. I am only reporting this now because my package.unmask broke temporarily and I accidentally downgraded to this revision.
Mistaken. Sorry. Was another error.