Bug 371219 - Plasma going in to visual stasis when a game that block compositing, starts
Summary: Plasma going in to visual stasis when a game that block compositing, starts
Status: RESOLVED DUPLICATE of bug 353983
Alias: None
Product: plasmashell
Classification: Plasma
Component: general (show other bugs)
Version: 5.8.2
Platform: Arch Linux Linux
: NOR normal
Target Milestone: 1.0
Assignee: David Edmundson
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-10-19 13:14 UTC by Allan
Modified: 2017-09-19 22:45 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Allan 2016-10-19 13:14:57 UTC
After launching a game that blocks compositing:
- Plasma panels go greyish most of the times.
- Plasma is visually frozen -clock is frozen, apps in the task list remain as icon even after closing app.. But plasma is not frozen - it can be interacted with, you can click the clock to get the calender and so on.. 
- Plasma content reverts to the content of the first time it happened: Say you launch a game - plasma visually freeze, then close the game -delete some widgets, start new game -old widgets appear -but only visually - eg. they don't interact - like you are seeing an old kwin buffer or something - (so might be a kwin bug..).

Reproducible: Always

Steps to Reproduce:
1. Enable "Allow applications to block compositing"
2. Start game that blocks compositing (like springrts).

Actual Results:  
Plasma visually goes in to stasis.

Expected Results:  
Plasma should get updates to the screen buffer.

System information: Intel i7-6950x, Nvidia gtx970, 32gb ram, 64bit Arch Linux, dual monitor setup.
Comment 1 Anton Smirnov 2017-08-27 12:34:59 UTC
Same bug, Fedora, experienced this on both Nvidia 760 and 1060
Comment 2 Anton Smirnov 2017-08-27 12:36:21 UTC
May be a duplicate of https://bugs.kde.org/show_bug.cgi?id=353983
Comment 3 Christoph Feck 2017-09-19 22:45:23 UTC
Yes, thanks.

*** This bug has been marked as a duplicate of bug 353983 ***