Details
-
Bug
-
Resolution: Out of scope
-
P1: Critical
-
None
-
5.10.1, 5.11.0 Beta 2
-
None
-
Arch Linux
Plasma git (5.12.80) / Weston 3.0.0
Intel graphics
Description
If the application GUI thread is temporarily blocked by a time-consuming work and mouse is moved over it -> application crashes as soon as the thread gets unblocked. There is no backtrace to this, it ends with error
The Wayland connection broke. Did the Wayland compositor die?
It can be reproduced e.g. with Krusader:
- Start Krusader
- Click on "MountMan" toolbar button
- Immediately after that start moving your mouse over Krusader app.
- Krusader terminates
Try it with no mouse movement after the click and all should be fine.
This was reproduced on Plasma (git master) as well as Weston 3.0.0.
I'll provide a minimal example app. on demand.
Attachments
Issue Links
- is duplicated by
-
QTBUG-60170 QtWaylandClient::QWaylandDisplay::exitWithError() (this=this@entry=0x555555f294b0) at qwaylanddisplay.cpp:200
- Closed
- relates to
-
QTBUG-66075 Wayland event dispatcher multi-threading support
- Closed
For Gerrit Dashboard: QTBUG-66997 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
224622,3 | WIP: Client: Horrible hack to not fill up wayland socket when blocking | dev | qt/qtwayland | Status: ABANDONED | -2 | 0 |