[kwin] [Bug 487189] New: Pointer confinement temporarily lost when leaving fullscreen

https://bugs.kde.org/show_bug.cgi?id=487189 Bug ID: 487189 Summary: Pointer confinement temporarily lost when leaving fullscreen Classification: Plasma Product: kwin Version: 6.0.4 Platform: Other OS: Li

[kwin] [Bug 487189] Pointer confinement temporarily lost when leaving fullscreen

https://bugs.kde.org/show_bug.cgi?id=487189 --- Comment #1 from Frank Praznik --- To note, this works as expected in GNOME, Weston, and Sway, so not likely to be an SDL bug. -- You are receiving this mail because: You are watching all bug changes.

[kwin] [Bug 489983] New: Incorrect window size when restoring from a maximized state

https://bugs.kde.org/show_bug.cgi?id=489983 Bug ID: 489983 Summary: Incorrect window size when restoring from a maximized state Classification: Plasma Product: kwin Version: 6.1.1 Platform: Fedora RPMs O

[kwin] [Bug 489983] Incorrect window size when restoring from a maximized state

https://bugs.kde.org/show_bug.cgi?id=489983 --- Comment #1 from Frank Praznik --- Also to note, this behavior occurs with the scale factor at both 100% and 150%. -- You are receiving this mail because: You are watching all bug changes.

[kwin] [Bug 489983] Incorrect window size when restoring from a maximized state

https://bugs.kde.org/show_bug.cgi?id=489983 --- Comment #2 from Frank Praznik --- A case where this causes a crash can be reproduced by running ./testsprite --resizable --geometry 1x1 1. Press ctrl+m to maximize with window, since the window controls are too small to use 2. Un-maximize the

[kwin] [Bug 489983] Incorrect window size when restoring from a maximized state

https://bugs.kde.org/show_bug.cgi?id=489983 --- Comment #5 from Frank Praznik --- (In reply to Zamundaaa from comment #3) > > The window size sent in the configure event for floating windows is just a > > hint, so I don't think that SDL is in the wrong here by ignoring it in

[kwin] [Bug 489983] Incorrect window size when restoring from a maximized state

https://bugs.kde.org/show_bug.cgi?id=489983 --- Comment #7 from Frank Praznik --- (In reply to Zamundaaa from comment #6) > > There is always the option to not ack the configure event if the requested > > floating size is not precisely obeyed, but that results in the window no

[kwin] [Bug 461063] xdg_toplevel.set_fullscreen does not center surface and doesn't add black background/padding/bars

https://bugs.kde.org/show_bug.cgi?id=461063 Frank Praznik changed: What|Removed |Added CC||frank.praz...@gmail.com --- Comment #1 from

[kwin] [Bug 506412] A protocol error "xdg_surface must not have a buffer at creation" occurs with a null buffer attached to the surface

https://bugs.kde.org/show_bug.cgi?id=506412 --- Comment #2 from Frank Praznik --- I'm fairly certain this is caused by a race condition now, because if I add a sleep of just 1 millisecond in between attaching/committing the null buffer to the wl_surface and (re)creating the xdg_surface, it

[kwin] [Bug 506412] A protocol error "xdg_surface must not have a buffer at creation" occurs with a null buffer attached to the surface

https://bugs.kde.org/show_bug.cgi?id=506412 Frank Praznik changed: What|Removed |Added Ever confirmed|0 |1 Resolution|DOWNSTREAM

[kwin] [Bug 506412] A protocol error "xdg_surface must not have a buffer at creation" occurs with a null buffer attached to the surface

https://bugs.kde.org/show_bug.cgi?id=506412 Frank Praznik changed: What|Removed |Added Version First|6.1.1 |6.4.1 Reported In

[kwin] [Bug 506412] New: A protocol error "xdg_surface must not have a buffer at creation" occurs with a null buffer attached to the surface

https://bugs.kde.org/show_bug.cgi?id=506412 Bug ID: 506412 Summary: A protocol error "xdg_surface must not have a buffer at creation" occurs with a null buffer attached to the surface Classification: Plasma Product: kwin