https://bugs.kde.org/show_bug.cgi?id=498837
Vlad Zahorodnii <vlad.zahorod...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|CONFIRMED |RESOLVED
Latest Commit| |https://invent.kde.org/plas
| |ma/kwin/-/commit/60275f4dbe
| |1a7648b855de3fa76b2f6b378d0
| |86b
Resolution|--- |FIXED
--- Comment #11 from Vlad Zahorodnii <vlad.zahorod...@kde.org> ---
Git commit 60275f4dbe1a7648b855de3fa76b2f6b378d086b by Vlad Zahorodnii.
Committed on 04/02/2025 at 09:03.
Pushed by vladz into branch 'master'.
xwayland: Keep ready fd until Xwayland is stopped
Xwayland writes the display name in two steps:
- first write the display name
- then write "\n"
Xwayland will quit if either write() fails. If the XwaylandLauncher
closes its endpoint of the displayfd after the first write(), then the
second write() may fail.
Given that we just want to know when Xwayland is ready, the ready fd
can be kept around until Xwayland is stopped.
The issue was introduced by 8e42599149bbd6e4e76baddd04b1c403131354ba
(kind of). Prior to that commit, kwin had been leaking the read endpoint
of the displayfd to Xwayland. So, even if kwin closes its endpoint,
Xwayland has it too so both write()s will succeed.
M +7 -8 src/xwayland/xwaylandlauncher.cpp
M +0 -2 src/xwayland/xwaylandlauncher.h
https://invent.kde.org/plasma/kwin/-/commit/60275f4dbe1a7648b855de3fa76b2f6b378d086b
--
You are receiving this mail because:
You are watching all bug changes.
