I had this issue as well on mariadb version 10.6 after upgrading to 10.7.2 the issue resolved itself. I have found no other way to remedy it.