> This is using a very recent snapshot (5th December) and not something home
> grown. Has this problem been fixed in -current yet? If not, shall I
> send-pr it?

This problem is known, AFAICT not fixed in -current, and I vaguely remember
there already is a PR open (but I'm not sure and can't check right now).

There is someone working on this, IIUC.

Martin