https://bugs.kde.org/show_bug.cgi?id=342326
Michael <k...@callthecomputerdoctor.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |kde@callthecomputerdoctor.c
| |om
--- Comment #48 from Michael <k...@callthecomputerdoctor.com> ---
> I resolve this by opening the Compositor settings and then toggling a radio
> button off and then on again, just so that the Apply button becomes enabled
> and allows me to trigger something. Perhaps this restarts the compositor or
> perhaps it does something less destructive, I don't know, but this has been
> the workaround I have been using several times per week for several years.
> It takes me only 20 seconds each time, but those 20 seconds add-up and so
> does the frustration.
This might help: pressing Alt-Shift-F12 twice does what you're doing but
faster. It's the KWin shortcut for "Suspend compositing".
> Also I am using an nVidia card, and the issue occurred on two different
> cards, both brand new. I don't know how the internals work, but I would be
> very surprised if this issue turned-out to be hardware-related.
I have a dual GPU laptop, with a Radeon iGPU and an NVidia dGPU.
I have been experiencing this exact same issue under X11 since I upgraded my
KDE neon laptop to Plasma 5.27. Never happened under 5.26, and now it's
happening almost every day. It seems to trigger after a long period of time on
its own, without any user interaction. I can be away from my computer for
awhile and come back and find that it appears to be unresponsive except for a
movable cursor; the screen is on.
Disabling the compositor with Shift+Alt+F12 is what gets my session usable
again, but the Plasma panels are non-responsive though I see that plasmashell
is still running with htop. I have to kill all the programs and reboot to get a
usable desktop again.
I've been trying to find a pattern for what causes it, and there is always at
least one program that seems to be in an unresponsive state when the compositor
stops working and needs to be forcibly killed. Correlation? I see that there
are other mentions of this issue:
https://bugs.kde.org/show_bug.cgi?id=366651 (ongoing from 2016-2021)
https://bugs.kde.org/show_bug.cgi?id=342326 (ongoing from
https://bugs.kde.org/show_bug.cgi?id=425557 (ongoing since 2020)
https://www.reddit.com/r/kde/comments/6ggjx8/windows_sometimes_stop_updating_content_kwin/
I was thinking the issue was some byproduct of the OpenGL drivers, so I
installed the Obiaf PPA to get the latest Mesa, but there was no change.
I saw one post from 2016 (https://bugs.kde.org/show_bug.cgi?id=366651#c6) where
Martin Flöser highlighted that the org.kde.kwin.aurorae was suspect and
suggested to "Please try to use the breeze window decoration." I found that I
had been using Aurorae, so I just now switched to Breeze for window
decorations. We'll see if this makes a difference.
I have lost so much work due to this bug, so I am fully committed to assisting
to get it fixed in any way I can.
I've created a set of information about KWin, my graphics drivers and my system
here:
https://invent.kde.org/-/snippets/2620
Please tell me what else you need to help nail this down.
--
You are receiving this mail because:
You are watching all bug changes.
