https://bugs.kde.org/show_bug.cgi?id=426293
--- Comment #1 from Vlad Zahorodnii <vlad.zahorod...@kde.org> --- #8 QMessageLogger::fatal (this=this@entry=0x7ffd81cbcf60, msg=msg@entry=0x7fd149e3a0f8 "The Wayland connection experienced a fatal error: %s") at /home/apol/devel/frameworks/qt5/qtbase/src/corelib/global/qlogging.cpp:893 > wl_display@1: error 0: invalid object 19 > The Wayland connection experienced a fatal error: Invalid argument I believe the problem is that QtWayland tries to do something with an already destroyed xdg_output resource and libwayland doesn't like it. We should probably **not** destroy xdg_output resources if the associated wl_output global has been removed. It would be nice if we could install some dummy wl_resource implementation that only implements the destructor request or maybe let qtwaylandscanner generated code handle inert resources. -- You are receiving this mail because: You are watching all bug changes.
