Bug 402241 - KMail Wayland UI drawing flakiness
Summary: KMail Wayland UI drawing flakiness
Status: RESOLVED DUPLICATE of bug 387313
Alias: None
Product: kmail2
Classification: Applications
Component: UI (show other bugs)
Version: Git (master)
Platform: Neon Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords: wayland
Depends on:
Blocks:
 
Reported: 2018-12-17 14:51 UTC by groot
Modified: 2019-01-23 11:10 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description groot 2018-12-17 14:51:43 UTC
SUMMARY
KMail interacts very strangely with other applications under Wayland, and seems to "fight" with others about drawing on the visible screen.

STEPS TO REPRODUCE
1. Install KDE neon git-unstable, start a Wayland session.
2. Start KMail. Have a KMail main window on the screen.
3. Start Spectacle.

OBSERVED RESULT
When mousing over the spectacle window, sometimes the KMail window is repainted over the spectacle window. Then when mousing over input elements in Spectacle (e.g. dropdowns) those are re-painted on-top of the bits of KMail.

Same happens with Quassel client, but also KMail message composer windows which will be obscured by the painting of the main window (behind).

EXPECTED RESULT
That KMail on Wayland behaves like on X11: the main window isn't painted overtop of other, active, windows.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: KDE neon git unstable
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 5.54
Qt Version: 

ADDITIONAL INFORMATION
Screenshots are kind of hard to make of this; I suppose I could do a movie with an external camera. I've only tested this on a Slimbook, i.e. Intel graphics.
Comment 1 John Scott 2019-01-06 15:50:06 UTC
I'm experiencing this on Intel graphics too, on Debian Testing. KMail becomes difficult to use when opening multiple KMail windows; they fight with each other if I don't minimize one.
Comment 2 Patrick Silva 2019-01-23 11:10:44 UTC

*** This bug has been marked as a duplicate of bug 387313 ***