https://bugs.kde.org/show_bug.cgi?id=365606
--- Comment #11 from Ivan Čukić <ivan.cu...@kde.org> --- Ok, the final problem found - ScriptEngine::desktopsForActivity tests whether the activity exists and it is called before the signal that the activity has been created arrived in plasma. The problematic situation: 1. The script requests activity creation 2. Activity manager registers a new activity 3. desktopsForActivity tests whether activity exists, it does not as far as plasma is concerned 4. Plasma gets the signal that the new activity has been created Now, this might be something to change in the activities framework - not to wait until the 'new activity' signal arrives before adding it to local cache, but I'm not sure it would be a good idea. There are currently no synchronization guarantees in kactivities. (the weekend is a lonely time on IRC, so I'm posting the real-time findings here :) ) -- You are receiving this mail because: You are watching all bug changes.
