Hi,

I've encountered this bug on several machines after upgrading to the latest 
stable release (bullseye). Could you please backport this fix to bullseye so it 
can be fixed in a point release? Thank you!


Regards,

Timo

Reply via email to