I've just checked; the problem is still present in 5.3.0-2.

Any news from your side?

Thanks
Kendy

Reply via email to