Bug 465665

Summary:	Snapping windows to corner visibly freezes the window
Product:	[Plasma] kwin	Reporter:	Matty Wyett-Simmonds <mattyws>
Component:	Quick Tiling	Assignee:	KWin default assignee <kwin-bugs-null>
Status:	RESOLVED FIXED
Severity:	grave	CC:	nate
Priority:	NOR
Version First Reported In:	5.26.5
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
Latest Commit:	https://invent.kde.org/plasma/kwin/-/commit/abd59be23274a0c76709a8c587d9ed14d154d995	Version Fixed/Implemented In:
Sentry Crash Report:

Description Matty Wyett-Simmonds 2023-02-13 12:04:14 UTC

SUMMARY
***
I have tried this on both Nobara and EndeavourOS fully up to date same result as of this weekend. When I try to snap an application to the corner of my screen to take up a quarter, the window will visible freeze but remain functional, until I unsnap it from the corner at which point the application visibly updates again.

I'm on nvidia drivers (3090) and x11, not wayland. Wayland is a no go for me in its current state
***


STEPS TO REPRODUCE
1. Log in
2. open any application
3. drag it to any corner of the screen to snap it to a quarter
4. try to use the application

OBSERVED RESULT
Window visibly freezes while still being responsive to input

EXPECTED RESULT
should not freeze?

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Latest Nobara and Arch
KDE Plasma Version: 5.26.5
KDE Frameworks Version: 5.102.0
Qt Version: 5.15.8

ADDITIONAL INFORMATION
I am on a 3090 nvidia graphics card and using x11. Sadly wayland is a piece of trash and has far more problems than this.

Comment 1 Vlad Zahorodnii 2023-02-15 09:45:47 UTC

> I'm on nvidia drivers (3090) and x11, not wayland. Wayland is a no go for me in its current state

I don't see how this rant is related. :/

---

Should be fixed in 5.27

Comment 2 Matty Wyett-Simmonds 2023-02-16 10:06:50 UTC

Sorry Vlad I was probably in a bad mood from asking around on various forums/discord channels and instead of helping, most people just said "use wayland" so I suppose thought I'd nip that in the bud before I got that response here too. I'll be more professional next time.

Glad to see the issue is resolved in the latest version!