After some search, I found the root cause of such log line in #1140029 .

Then, it would be ingenerous to say that libkscreenlocker6 must be "fixed", rather "adapted"...

Reply via email to