https://bugs.kde.org/show_bug.cgi?id=392376
magib...@hotmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |magib...@hotmail.com
--- Comment #6 from magib...@hotmail.com ---
This issue can be easily hit by anyone with a HDD. Dolphin, Systemsettings,
Kate, Falkon... almost every KDE application is vulnerable to this. This is my
most frequent crash in Wayland sessions.
I don't know if this adds anything new to the discussion, but I tracked down
the origin of the crash in libwayland.
Qt applications crash from QWaylandDisplay::checkError() after
wl_display_dispatch_pending returns negative. So I looked into the library to
see what was going on.
The error within libwayland takes place when recvmsg returns -1 with errno =
104 ("Connection reset by peer") in wl_os_recvmsg_cloexec (wayland-os.c). This
result goes through wl_connection_read (connection.c) until it is handled by
read_events (wayland-client.c).
I don't know how wayland or kwin work, so my questions might not make a lot of
sense: does the above mean that the connection is reset voluntarily by Kwin, or
is it a consequence of the buffer filling up? Can Kwin do anything to prevent
the connection from breaking?
--
You are receiving this mail because:
You are watching all bug changes.
