Bug 399021

Summary:	[Wayland] "Desaturate unresponsive applications..." effect remains even when the window is no longer frozen
Product:	[Plasma] kwin	Reporter:	Patrick Silva <bugseforuns>
Component:	effects-various	Assignee:	KWin default assignee <kwin-bugs-null>
Status:	RESOLVED FIXED
Severity:	normal	CC:	alenertz, kde, notuxius, tromzy, veqz
Priority:	NOR
Version:	5.18.90
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Patrick Silva 2018-09-24 14:50:19 UTC

When a window freezes, it becomes black and white and its title bar shows "not responding...".
Under Wayland such situation remains even after the window to unfreeze. I need to minimize/unminimize the window to get rid of black and white coloration and "not reponding..." in the title bar.
I already noticed such behavior on both Arch Linux (plasma 5.14 beta) and neon dev unstable. Discover and K3b are examples of affected apps.

Comment 1 Alexander Mentyu 2018-09-28 19:20:33 UTC

How do you make Discover(or other) windows not responding?

Comment 2 Patrick Silva 2018-09-29 17:51:12 UTC

gdb can freeze the process, but I can not reproduce the behavior reported here by freezing a window intentionally.

I noticed that it's not necessary to minimize/unminimize the window to get rid of black and white coloration and "not reponding..." in the title bar.
Click the window is enough.

Comment 3 Kai Uwe Broulik 2018-10-01 07:23:31 UTC

Can't reproduce using kill -SIGSTOP

Comment 4 Patrick Silva 2018-10-15 15:41:36 UTC

I can reproduce with K3b.
I open K3b while a disc (audio cd) is into my optical deevice,
K3b changes to "Not responding..." state.
I need to click or minimize/restore its window to get rid of the "Not responding..." state.

K3b 18.08.2
Operating System: Arch Linux 
KDE Plasma Version: 5.14.0
Qt Version: 5.11.2
KDE Frameworks Version: 5.51.0
Kernel Version: 4.18.12-arch1-1-ARCH

Comment 5 Alexander Mentyu 2018-11-29 13:23:12 UTC

Can reproduce this bug with steps in https://bugs.kde.org/show_bug.cgi?id=401533

Comment 6 Vlad Zahorodnii 2018-11-29 14:07:57 UTC

So, the problem is we send the ping event only in two cases:
* when a client is closed;
* when a client takes focus.

If you'd like to unfreeze a window, just click somewhere in the window.

Comment 7 tromzy 2019-01-23 12:37:39 UTC

I can confirm this behaviour, especially with Kpatience who hangs very very often for some reason. Once it unfreezes, the window remains grey until I click somewhere in it.

Comment 8 tromzy 2019-06-05 11:34:54 UTC

I don't know if it is the same bug, but I noticed that on Plasma 5.15.90, when resuming the session, Kscreenlocker is always gray like it was not responding (although I can type my password to reopen my session).

Comment 9 Vlad Zahorodnii 2019-06-05 11:41:09 UTC

(In reply to tromzy from comment #8)
> I don't know if it is the same bug, but I noticed that on Plasma 5.15.90,
> when resuming the session, Kscreenlocker is always gray like it was not
> responding (although I can type my password to reopen my session).

What if you disable the Desaturate Unresponsive Applications effect?

Comment 10 tromzy 2019-06-05 11:58:17 UTC

(In reply to Vlad Zagorodniy from comment #9)
> (In reply to tromzy from comment #8)
> > I don't know if it is the same bug, but I noticed that on Plasma 5.15.90,
> > when resuming the session, Kscreenlocker is always gray like it was not
> > responding (although I can type my password to reopen my session).
> 
> What if you disable the Desaturate Unresponsive Applications effect?

Sorry, I cannot test now because I switched back to Plasma 5.15.5.

Comment 11 Patrick Silva 2019-06-05 21:42:16 UTC

I already noticed the same problem with the screen locker when running some versions of plama. But it never was consistently reproducible on my systems (Arch and neon).

Comment 12 Aleix Pol 2019-10-10 00:07:16 UTC

*** Bug 411757 has been marked as a duplicate of this bug. ***

Comment 13 Patrick Silva 2020-09-08 02:58:12 UTC

*** Bug 426294 has been marked as a duplicate of this bug. ***

Comment 14 Patrick Silva 2020-09-28 02:46:57 UTC

*** Bug 427046 has been marked as a duplicate of this bug. ***

Comment 15 Patrick Silva 2021-05-19 13:43:55 UTC

cannot reproduce on neon unstable.