https://bugs.kde.org/show_bug.cgi?id=426293
Vlad Zahorodnii <vlad.zahorod...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas
|ma/kwayland-server/commit/3 |ma/kwayland-server/commit/7
|987c0aecfb2f7e9e1222a61a75a |a8ac182d4ddcfbafe7badc89778
|d32a0b592c08 |ff5b6c375777
--- Comment #13 from Vlad Zahorodnii <vlad.zahorod...@kde.org> ---
Git commit 7a8ac182d4ddcfbafe7badc89778ff5b6c375777 by Vlad Zahorodnii.
Committed on 13/10/2020 at 18:06.
Pushed by vladz into branch 'Plasma/5.20'.
Properly handle destruction of XdgOutputV1Interface
The xdg-output spec omits whether the compositor has to destroy all xdg-
output resources when the associated wl_output global is removed.
This means that no xdg-output resource should be destroyed unless the
client has called the destructor request; otherwise the client may panic
due to protocol errors.
Starting with Qt 5.15.2, it's okay to destroy generated wrapper objects
without destroying associated resources. Destructor requests will be
handled behind the scenes for inert and orphaned resources by code that
is generated by qtwaylandscanner.
(cherry picked from commit 3987c0aecfb2f7e9e1222a61a75ad32a0b592c08)
M +4 -1 src/server/xdgoutput_v1_interface.cpp
https://invent.kde.org/plasma/kwayland-server/commit/7a8ac182d4ddcfbafe7badc89778ff5b6c375777
--
You are receiving this mail because:
You are watching all bug changes.
