Comment 6 for bug 1877568

Happened again:

    May 11 17:05:50 saegusa gnome-shell[3619]: WL: compositor bug: The compositor tried to use an object from one client in a 'wl_pointer.enter' for a different client.
    May 11 17:05:50 saegusa gnome-shell[3619]: WL: error in client communication (pid 5170)
    May 11 17:05:50 saegusa gnome-terminal-[5170]: Error reading events from display: Katkennut putki
    May 11 17:05:50 saegusa systemd[3544]: gnome-terminal-server.service: Main process exited, code=exited, status=1/FAILURE
    May 11 17:05:50 saegusa systemd[3544]: gnome-terminal-server.service: Failed with result 'exit-code'.
    May 11 17:05:50 saegusa systemd[3544]: vte-spawn-b269c64d-5376-49ec-83fc-9f4806ac4b30.scope: Succeeded.
    May 11 17:05:50 saegusa systemd[3544]: vte-spawn-3294a176-7b32-4995-a11b-fe0fea8b07bc.scope: Succeeded.
    May 11 17:05:50 saegusa systemd[3544]: vte-spawn-0b59afd0-1aed-4081-a7d1-801e7c405399.scope: Succeeded.
    May 11 17:05:51 saegusa systemd[3544]: Started Application launched by gnome-shell.

But there's still nothing in /var/crash, nor on the Error Tracker (aside from the aforementioned, unrelated crash from last week).