Symptoms

There are two things to explain this time.

Problem that Chrome drawing collapses after suspend ← Symptom disappears by restarting Chrome
Problem that the drawing of systemsettings5 is broken after suspending ← systemsettings5 does not heal even if restarted

↑ Problem that Chrome drawing is broken

↑ system settings5 (There is no screenshot of the broken screen, but this one)

Environment (only those that are likely to be relevant)

OS: Arch Linux (this probably doesn't matter, it's the same with Ubuntu)
GPU: Nvidia RTX GeForce 2070 Mobile
GPU Driver: 450 series
Desktop: KDE Plasma 5.19 series

TL;DR I tried both of the following two methods and it was cured (I will update the article if it reoccurs).

systemsettings5: ** Downgrade Nvidia Driver from 450 series to 440 series **
Chrome: ** Disable "Settings-> Advanced-> Enable Hardware Accelerator" in GUI **

Survey record

Advance preparation and warning

Due to graphics driver issues, you may be unable to boot due to a kernel panic during ** trial and error when investigating or applying to your own environment **. Before starting work, prepare an environment where you can chroot with an installer.

For system settings 5

This can be started with the following command, so it is easy to investigate.

When normal, systemsettings5 &> logOk
When something goes wrong systemsettings5 &> logNg

`logOk`


Cyclic dependency detected between "file:///usr/lib/qt/qml/org/kde/kirigami.2/styles/org.kde.desktop.plasma/Units.qml" and "file:///usr/lib/qt/qml/org/kde/kirigami.2/styles/org.kde.desktop.plasma/Units.qml"
file:///usr/share/kpackage/genericqml/org.kde.systemsettings.sidebar/contents/ui/SubCategoryPage.qml:141:9: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
file:///usr/share/kpackage/genericqml/org.kde.systemsettings.sidebar/contents/ui/SubCategoryPage.qml:131:9: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
file:///usr/lib/qt/qml/org/kde/kirigami.2/private/RefreshableScrollView.qml:143:13: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
file:///usr/lib/qt/qml/org/kde/kirigami.2/private/RefreshableScrollView.qml:143:13: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
Cyclic dependency detected between "file:///usr/lib/qt/qml/org/kde/kirigami.2/styles/org.kde.desktop.plasma/Units.qml" and "file:///usr/lib/qt/qml/org/kde/kirigami.2/styles/org.kde.desktop.plasma/Units.qml"
QQmlEngine::setContextForObject(): Object already has a QQmlContext
file:///usr/share/kpackage/genericqml/org.kde.systemsettings.sidebar/contents/ui/introPage.qml:109:27: QML IntroIcon (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "minimumHeight"
file:///usr/share/kpackage/genericqml/org.kde.systemsettings.sidebar/contents/ui/introPage.qml:109:27: QML IntroIcon (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "minimumHeight"

`logNg`


Cyclic dependency detected between "file:///usr/lib/qt/qml/org/kde/kirigami.2/styles/org.kde.desktop.plasma/Units.qml" and "file:///usr/lib/qt/qml/org/kde/kirigami.2/styles/org.kde.desktop.plasma/Units.qml"
file:///usr/share/kpackage/genericqml/org.kde.systemsettings.sidebar/contents/ui/SubCategoryPage.qml:141:9: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
file:///usr/share/kpackage/genericqml/org.kde.systemsettings.sidebar/contents/ui/SubCategoryPage.qml:131:9: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
file:///usr/lib/qt/qml/org/kde/kirigami.2/private/RefreshableScrollView.qml:143:13: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
file:///usr/lib/qt/qml/org/kde/kirigami.2/private/RefreshableScrollView.qml:143:13: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
Cyclic dependency detected between "file:///usr/lib/qt/qml/org/kde/kirigami.2/styles/org.kde.desktop.plasma/Units.qml" and "file:///usr/lib/qt/qml/org/kde/kirigami.2/styles/org.kde.desktop.plasma/Units.qml"
QQmlEngine::setContextForObject(): Object already has a QQmlContext
+ QQuickWidget: Failed to make context current
+ QQuickWidget::resizeEvent() no OpenGL context
+ QQuickWidget: Failed to make context current
file:///usr/share/kpackage/genericqml/org.kde.systemsettings.sidebar/contents/ui/introPage.qml:109:27: QML IntroIcon (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "minimumHeight"
file:///usr/share/kpackage/genericqml/org.kde.systemsettings.sidebar/contents/ui/introPage.qml:109:27: QML IntroIcon (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "minimumHeight"
+ QQuickWidget: Attempted to render scene with no context
+ QQuickWidget::invalidateRenderControl could not make context current

If you can identify the error message, you can just google. https://bbs.archlinux.org/viewtopic.php?id=258149 A forum like this hit and said, "I could go if I downgraded!" ... apparently ... Looking at the related threads, it seems to be a problem with the Nvidia 450 series and the KDE Plasma 5.19 series. By the way, the nvidia driver is deeply involved in the kernel, so it seems that you need to install the nvidia-dkms-like one.

I think that downgrading in Linux has a method for each OS, so I will write a record of what I did in my environment arch ref % 83% 91% E3% 83% 83% E3% 82% B1% E3% 83% BC% E3% 82% B8% E3% 81% AE% E3% 83% 80% E3% 82% A6% E3% 83 % B3% E3% 82% B0% E3% 83% AC% E3% 83% BC% E3% 83% 89).

`for archLinux`


yay -S nvidia-dkms downgrader # nvidia-dkms and nvidia-utils is installed
yay -R nvidia-dkms
downgrader nvidia-utils #Version with choice`440.100-1`Choose
yay -S nvidia-440xx-dkms
sudo reboot

For chrome

I was a little troubled because I couldn't find a clear error message here. ** The surest solution is to disable "Settings-> Advanced-> Enable Hardware Accelerator" in the GUI **. Doing this solves the problem as Chrome will not use GPU resources, but it will slow down drawing and consume more CPU resources.

Other

With chrome: // flags
Enable # ignore-gpu-blacklist or # ignore-gpu-blocklist
~~ # enable-vulkan enabled ~~

2020-09-19 Addendum The problem that the drawing of Chrome is broken has not been solved because another problem has occurred. Enabling ʻenable-vulkan` occasionally involves kwin and crashes.

combination

	systemsettings5	chrome
nvidia-450	NG	Heal with restart
nvidia-vulkan-450	NG	crash continues
nvidia-440xx-dkms	OK	Heal with restart
nvidia-vulkan-dkms-450	NG	crash continues

Chome crashes with the following ** in either case ** occasionally involving kwin (about once every three times it also involves a login session and crashes).

Use a vulkan type driver
enable-enable vulkan

_ Even if the login session crashed, the processes running within that session were still alive (!). I could not confirm it from other ttys, and I was able to confirm that it was alive with ps and that it worked normally. The only way to erase them is to kill. .. _

`Log when login session is not involved(part)`


# journalctl -b -p3
Sep 19 10:19:52 archlinux systemd-coredump[13418]: Process 12306 (chrome) of user 1000 dumped core.
                                                   Stack trace of thread 12306:
                                                   #0  0x00007f95b5915c7b n/a (libnvidia-glcore.so.440.100 + 0xee4c7b)
                                                   #1  0x00007f95b59184bd n/a (libnvidia-glcore.so.440.100 + 0xee74bd)
                                                   #2  0x00007f95b5918bfe n/a (libnvidia-glcore.so.440.100 + 0xee7bfe)
                                                   #3  0x00007f95b58b56da n/a (libnvidia-glcore.so.440.100 + 0xe846da)
                                                   #4  0x00007f95b586ac9e n/a (libnvidia-glcore.so.440.100 + 0xe39c9e)
                                                   #5  0x00007f95b5873fdf n/a (libnvidia-glcore.so.440.100 + 0xe42fdf)
                                                   #6  0x00007f95b54d4178 n/a (libnvidia-glcore.so.440.100 + 0xaa3178)
                                                   #7  0x00007f95b54d9068 n/a (libnvidia-glcore.so.440.100 + 0xaa8068)
                                                   #8  0x00007f95b54db97c n/a (libnvidia-glcore.so.440.100 + 0xaaa97c)
                                                   #9  0x00007f95b727cf81 n/a (libGLESv2.so + 0x410f81)
                                                   #10 0x00007f95b726f5a9 n/a (libGLESv2.so + 0x4035a9)
                                                   #11 0x00007f95b713f682 n/a (libGLESv2.so + 0x2d3682)
                                                   #12 0x00007f95b70af266 _ZN2gl22CheckFramebufferStatusEj (libGLESv2.so + 0x243266)
                                                   #13 0x00005567c65a8dad n/a (chrome + 0x633bdad)
(Omitted thereafter)

Problems with Chrome after suspending on Linux desktop KDE + Nvidia