Bug 462554 - Visual artifacts when moving Cryptomator's window
Summary: Visual artifacts when moving Cryptomator's window
Status: RESOLVED FIXED
Alias: None
Product: kwin
Classification: Plasma
Component: wayland-generic (other bugs)
Version First Reported In: 5.27.4
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-12-02 16:38 UTC by postix
Modified: 2023-08-02 11:04 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In: 5.27.7
Sentry Crash Report:

Attachments
Screen recording (224.14 KB, video/x-matroska)
2022-12-02 16:38 UTC, postix 		Details
kwin support info (6.93 KB, text/plain)
2022-12-02 16:38 UTC, postix 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description postix 2022-12-02 16:38:27 UTC 
Created attachment 154230 [details]
Screen recording

STEPS TO REPRODUCE
1. Install Crytpomator 1.6.15 via `flatpak install --user flathub org.cryptomator.Cryptomator`
2. Open it and move it's window around

OBSERVED RESULT
If moved fast enough or transitioned from a 2nd screen, visual artifacts, i.e. ~1px wide part of the app's window remain on the screen. Please see the screen recording.


SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20221128
KDE Plasma Version: 5.26.3
KDE Frameworks Version: 5.100.0
Qt Version: 5.15.7
Kernel Version: 6.0.8-1-default (64-bit)
Graphics Platform: Wayland
Graphics Processor: AMD Radeon RX 580 Series
Comment 1 postix 2022-12-02 16:38:51 UTC 
Created attachment 154231 [details]
kwin support info
Comment 2 Zamundaaa 2022-12-03 15:01:40 UTC 
Looks like the damage region is smaller than it should be. Is Cryptomator using X11 or Wayland?
Comment 3 postix 2022-12-03 15:31:21 UTC 
(In reply to Zamundaaa from comment #2)
> Looks like the damage region is smaller than it should be. Is Cryptomator
> using X11 or Wayland?

Looks like (according to xeyes) it's using X11 (XWayland).
Comment 4 Zamundaaa 2023-08-02 11:04:18 UTC 
There's change in KWin 5.27.7 that should fix this. If it still happens, please reopen