Stalled wayland connection causes exit, contrary to Client API documentation
I've had apps crash on me when the shell was momentarily blocked. Apparently an EAGAIN
from wl_display_flush
isn't handled correctly.
The Wayland Client API docs mention:
if all data could not be written, errno will be set to EAGAIN and -1 returned. In that case, use poll on the display file descriptor to wait for it to become writable again.
However, the current implementation exits the application in this case.
Version information
- Arch Linux
- GTK+ 3.22.29-4-gb485cf91
- GNOME Shell 3.28.0
Additional information
gnome-terminal-[13903]: Error flushing display: Resource temporarily unavailable
systemd[13194]: gnome-terminal-server.service: Main process exited, code=exited, status=1/FAILURE
Edited by Jan Alexander Steffens