This bug was fixed. It does not exist in linux-image-5.4.0-1-amd64 (from sid) that works fine.

It still exist in linux-image-5.0 from Ubuntu.

So please, fix it in linux-image-4.19.

Regards

Alain Rpnpif

Reply via email to