For me, this bug occurs when using Awesome 4.2 on Tumbleweed. https://github.com/awesomeWM/awesome/issues/2540 Others commented that arch also ran across this a few weeks ago.