[Differential] [Request, 42 lines] D1734: [server] Properly handle the case that a PlasmaWindow is unmapped before client bound it

graesslin (Martin Gräßlin) noreply at phabricator.kde.org
Wed Jun 1 13:43:36 UTC 2016


graesslin created this revision.
graesslin added a reviewer: Plasma.
Restricted Application added a project: Plasma.
Restricted Application added a subscriber: plasma-devel.

REVISION SUMMARY
  So far we directly destroyed the resource on the server side. But this
  causes a wayland error when the client tries to cleanup. This results in
  the client being destroyed. A problem which brings down plasmashell
  regularly when short living windows are shown. This happens e.g. in
  Dolphin with the adress auto complete.
  
  This change addresses the problem by creating a temporary
  PlasmaWindowInterface for the already unmapped window. It doesn't get
  added to the list of known windows and it's only purpose is to properly
  handle the unmap and the destroy of the just created resource.

REPOSITORY
  rKWAYLAND KWayland

BRANCH
  plasma-window-destroy

REVISION DETAIL
  https://phabricator.kde.org/D1734

AFFECTED FILES
  autotests/client/test_wayland_windowmanagement.cpp
  src/server/plasmawindowmanagement_interface.cpp

EMAIL PREFERENCES
  https://phabricator.kde.org/settings/panel/emailpreferences/

To: graesslin, #plasma
Cc: plasma-devel, sebas
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/plasma-devel/attachments/20160601/bf0edcf0/attachment.html>


More information about the Plasma-devel mailing list