just tested on kernel versions 6.5.0-1-amd64, 6.4.0-4-amd64, 6.4.0-3-amd64 & 
6.4.0-2-amd64
 and same bug present on all. So it is long standing, and not specific
 to 6.5.0-2.

 ael

Reply via email to