https://bugs.kde.org/show_bug.cgi?id=388628

Martin Flöser <mgraess...@kde.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
      Latest Commit|                            |https://commits.kde.org/kwi
                   |                            |n/b8f43618478437e52b5e4f7f5
                   |                            |cc50d1c689e6b1c
         Resolution|---                         |FIXED
             Status|UNCONFIRMED                 |RESOLVED

--- Comment #5 from Martin Flöser <mgraess...@kde.org> ---
Git commit b8f43618478437e52b5e4f7f5cc50d1c689e6b1c by Martin Flöser.
Committed on 13/01/2018 at 15:58.
Pushed by graesslin into branch 'master'.

Disable KActivities integration on Wayland

Once again KActivities causes a delay in the startup of KWin. This is
not the first time it happens, that has been a problem since the start
of the Wayland project.

In the past we added a compile time switch due to that and added a
runtime switch once it stoped freezing (20a9a2a247).
And now it broke again, so let's disable again.

KActivities doesn't make sense on Wayland anyway as there is no activity
support for Wayland windows. Once KActivities is able to be used without
freezing KWin on startup and being able to ensure that it won't break
again we can reenable. But I expect guarantees about that. This must be
ensured by proper autotest support to verify that in future usage of
KActivities in the display manager doesn't freeze it.

This is maintainer decision, due to that no pre-commit review.

CCMAIL: plasma-de...@kde.org

M  +1    -9    main_wayland.cpp

https://commits.kde.org/kwin/b8f43618478437e52b5e4f7f5cc50d1c689e6b1c

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to