https://bugs.kde.org/show_bug.cgi?id=450551
--- Comment #27 from tani.giovo...@minutestep.com --- (In reply to Nate Graham from comment #26) > Yes, it's possible some ThinkPad hardware triggers the same Kernel > condition. Once we write the value out on every boot, this will be fixed > automatically for everyone. I might have just been super sleep deprived and am misremembering, but I thought I saw a reply to my original comment saying that a fix was already in the latest Kwin; I've since updated again (literally about 2 hrs ago on EndeavourOS) and rebooted and am still having the issue. Based on your phrasing here, it sounds like a fix has been created, and it's just not made it's way downstream to users yet, is that the case or am I totally misreading it? If so, is there an estimate for when it will start being deployed? I know there is no real way of KDE impacting when distros start putting the update in their repos so I don't expect any exact answers, but I'm just generally curious since it sounds like the issue has been more or less solved and it's just a matter of it being distributed. (again though, I'm not a developer so I could be totally misreading this, and the comment that I thought I remembered saying that the fix was already in kwin isn't there anymore so for all I know I might have just hallucinated it entirely, no misreading necessary.) -- You are receiving this mail because: You are watching all bug changes.
