-
Bug
-
Resolution: Incomplete
-
Normal
-
None
-
None
-
None
-
Sway, Arch Linux
Under a Wayland environment, apps that block UI updates whilst performing a long operation are likely to be disconnected by the Wayland compositor. In the case of Picard, the UI crashes (although any on-going file operations continue in the background).
From #sway:
<johanhelsing> milkii: That bug is more of a core wayland issue than a qtwayland one <johanhelsing> if we work around it in qtwayland, then the same hack would be needed for all other toolkits (and I don't think they do) <johanhelsing> the answer I got over in the wayland irc is basically: applications shouldn't be blocking the gui thread for that long, they should do the heavy tasks on separate threads
See also: https://bugreports.qt.io/browse/QTBUG-66997
- has related issue
-
PICARD-1625 UI unresponsive while matching files to release
- Closed
-
PICARD-598 Interface unresponsive when saving files on slow filesystem
- Closed