tildearrow

@ptr1337 It's definitely not. This is an issue with unredirection, so it is not a bug in vanilla KWin.

> Nope it's not. lol There seems to be conflicting PIDs when second TTY starts in X, maybe it's a Garuda thing, but I got a bigger dog to chase...

In a summary, here is what you need to do in order to acquire a backtrace: 1. SSH to your machine 2. Type `DISPLAY=:0 gdb kwin_x11` on the SSH session....

Hmmm... that looks odd. Can you try disabling unredirection (System Settings > Display and Monitor > Compositor > Enable full-screen unredirection (X11)) and see if it still reproduces? If so,...

Full-screen unredirection now available with the latest KWin-lowlatency release I just pushed a bit ago.

Hmm... time to port kwin-lowlatency to 5.12...

If typing "xrandr" or restarting the compositor works around the issue, then this is related to/duplicate of #34.

I'm sorry to mention this, but at the moment there isn't any way to donate. Thanks for the intention, though!

> (BTW, did you talk to Nate Graham (the KDE usability guy who made quite a difference in the past 2 years) about the possibilities to get your work upstream...

Cannot reproduce (unless the window is full-screen). Excuse the delay :< Please try with KWin-lowlatency 5.22 or 5.23 and report.