Black borders around windows after resume

Hello,
I have had this problem for several months: when I resume, artifacts appear (black borders around windows). I think that the drivers are involved.

The famous artifacts (black borders are not the background):

inxi -SGxxxz

System:    Host: manjaro Kernel: 4.19.20-1-MANJARO x86_64 bits: 64 compiler: gcc v: 8.2.1 Desktop: KDE Plasma 5.14.5 
           tk: Qt 5.12.0 wm: kwin_x11 dm: SDDM Distro: Manjaro Linux 
Graphics:  Device-1: NVIDIA GP107 [GeForce GTX 1050 Ti] driver: nvidia v: 415.27 bus ID: 01:00.0 chip ID: 10de:1c82 
           Display: x11 server: X.Org 1.20.3 driver: nvidia compositor: kwin_x11 resolution: 1920x1080~60Hz 
           OpenGL: renderer: GeForce GTX 1050 Ti/PCIe/SSE2 v: 4.6.0 NVIDIA 415.27 direct render: Yes 
xrandr

Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 32767 x 32767
DVI-D-0 disconnected (normal left inverted right x axis y axis)
HDMI-0 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 477mm x 268mm
   1920x1080     60.00*+  59.94    50.00    60.00    50.04  
   1680x1050     59.95  
   1600x900      60.00  
   1440x576      50.08  
   1280x1024     75.02    60.02  
   1280x800      59.81  
   1280x720      60.00    59.94    50.00  
   1024x768      75.03    60.00  
   800x600       75.00    60.32  
   720x576       50.00  
   720x480       59.94  
   640x480       75.00    59.94    59.93  
DP-0 disconnected (normal left inverted right x axis y axis)
DP-1 disconnected (normal left inverted right x axis y axis)
grep -iE "(EE)|(WW)|Time|nvidia" /var/log/Xorg.0.log

[    12.654] Current Operating System: Linux manjaro 4.19.20-1-MANJARO #1 SMP PREEMPT Wed Feb 6 21:33:34 UTC 2019 x86_64
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[    12.654] (==) Log file: "/var/log/Xorg.0.log", Time: Thu Feb 14 20:53:14 2019
[    12.902] (**) |-->Screen "Screen0" (0)
[    12.994] (WW) The directory "/usr/share/fonts/OTF" does not exist.
[    12.994] (WW) The directory "/usr/share/fonts/Type1" does not exist.
[    12.995] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi".
[    12.995] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi".
[    12.995] (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
[    12.995] (WW) Disabling Keyboard0
[    12.995] (WW) Disabling Mouse0
[    12.996] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration
[    12.996] (II) xfree86: Adding drm device (/dev/dri/card0)
[    12.999] (**) OutputClass "nvidia" ModulePath extended to "/usr/lib/nvidia/xorg,/usr/lib/xorg/modules,/usr/lib/xorg/modules"
[    12.999] (**) OutputClass "nvidia" setting /dev/dri/card0 as PrimaryGPU
[    13.001] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[    13.019] (II) Loading /usr/lib/nvidia/xorg/libglx.so
[    13.312] (II) Module glx: vendor="NVIDIA Corporation"
[    13.316] (II) NVIDIA GLX Module  415.27  Thu Dec 20 17:12:23 CST 2018
[    13.321] (II) LoadModule: "nvidia"
[    13.359] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[    13.409] (II) Module nvidia: vendor="NVIDIA Corporation"
[    13.409] (II) NVIDIA dlloader X Driver  415.27  Thu Dec 20 17:12:39 CST 2018
[    13.409] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[    13.431] (**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
[    13.431] (==) NVIDIA(0): RGB weight 888
[    13.431] (==) NVIDIA(0): Default visual is TrueColor
[    13.431] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
[    13.431] (II) Applying OutputClass "nvidia" options to /dev/dri/card0
[    13.431] (**) NVIDIA(0): Option "Stereo" "0"
[    13.431] (**) NVIDIA(0): Option "nvidiaXineramaInfoOrder" "DFP-1"
[    13.431] (**) NVIDIA(0): Option "SLI" "Off"
[    13.431] (**) NVIDIA(0): Option "MultiGPU" "Off"
[    13.431] (**) NVIDIA(0): Option "BaseMosaic" "off"
[    13.431] (**) NVIDIA(0): Option "AllowEmptyInitialConfiguration"
[    13.431] (**) NVIDIA(0): Stereo disabled by request
[    13.431] (**) NVIDIA(0): NVIDIA SLI disabled.
[    13.431] (**) NVIDIA(0): NVIDIA Multi-GPU disabled.
[    13.431] (**) NVIDIA(0): Option "MetaModes" "1920x1080_60 +0+0 {ForceCompositionPipeline=On}"
[    13.431] (**) NVIDIA(0): Enabling 2D acceleration
[    14.387] (--) NVIDIA(0): Valid display device(s) on GPU-0 at PCI:1:0:0
[    14.387] (--) NVIDIA(0):     DFP-0
[    14.387] (--) NVIDIA(0):     DFP-1 (boot)
[    14.387] (--) NVIDIA(0):     DFP-2
[    14.387] (--) NVIDIA(0):     DFP-3
[    14.388] (II) NVIDIA(0): NVIDIA GPU GeForce GTX 1050 Ti (GP107-A) at PCI:1:0:0 (GPU-0)
[    14.388] (--) NVIDIA(0): Memory: 4194304 kBytes
[    14.388] (--) NVIDIA(0): VideoBIOS: 86.07.42.00.2c
[    14.388] (II) NVIDIA(0): Detected PCI Express Link width: 16X
[    14.388] (--) NVIDIA(GPU-0): DFP-0: disconnected
[    14.388] (--) NVIDIA(GPU-0): DFP-0: Internal TMDS
[    14.388] (--) NVIDIA(GPU-0): DFP-0: 330.0 MHz maximum pixel clock
[    14.388] (--) NVIDIA(GPU-0): 
[    14.418] (--) NVIDIA(GPU-0): BenQ GL2250H (DFP-1): connected
[    14.418] (--) NVIDIA(GPU-0): BenQ GL2250H (DFP-1): Internal TMDS
[    14.418] (--) NVIDIA(GPU-0): BenQ GL2250H (DFP-1): 600.0 MHz maximum pixel clock
[    14.418] (--) NVIDIA(GPU-0): 
[    14.418] (--) NVIDIA(GPU-0): DFP-2: disconnected
[    14.418] (--) NVIDIA(GPU-0): DFP-2: Internal DisplayPort
[    14.418] (--) NVIDIA(GPU-0): DFP-2: 1440.0 MHz maximum pixel clock
[    14.418] (--) NVIDIA(GPU-0): 
[    14.418] (--) NVIDIA(GPU-0): DFP-3: disconnected
[    14.418] (--) NVIDIA(GPU-0): DFP-3: Internal TMDS
[    14.418] (--) NVIDIA(GPU-0): DFP-3: 165.0 MHz maximum pixel clock
[    14.418] (--) NVIDIA(GPU-0): 
[    14.423] (II) NVIDIA(0): Validated MetaModes:
[    14.423] (II) NVIDIA(0):     "1920x1080_60+0+0{ForceCompositionPipeline=On}"
[    14.423] (II) NVIDIA(0): Virtual screen size determined to be 1920 x 1080
[    14.428] (--) NVIDIA(0): DPI set to (101, 101); computed from "UseEdidDpi" X config
[    14.428] (--) NVIDIA(0):     option
[    14.428] (II) NVIDIA: Using 24576.00 MB of virtual memory for indirect memory
[    14.428] (II) NVIDIA:     access.
[    14.431] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[    14.431] (II) NVIDIA(0):     may not be running or the "AcpidSocketPath" X
[    14.431] (II) NVIDIA(0):     configuration option may not be set correctly.  When the
[    14.431] (II) NVIDIA(0):     ACPI event daemon is available, the NVIDIA X driver will
[    14.431] (II) NVIDIA(0):     try to use it to receive ACPI event notifications.  For
[    14.431] (II) NVIDIA(0):     details, please see the "ConnectToAcpid" and
[    14.431] (II) NVIDIA(0):     "AcpidSocketPath" X configuration options in Appendix B: X
[    14.431] (II) NVIDIA(0):     Config Options in the README.
[    14.450] (II) NVIDIA(0): Setting mode "1920x1080_60+0+0{ForceCompositionPipeline=On}"
[    14.553] (==) NVIDIA(0): Disabling shared memory pixmaps
[    14.553] (==) NVIDIA(0): Backing store enabled
[    14.553] (==) NVIDIA(0): Silken mouse disabled
[    14.553] (**) NVIDIA(0): DPMS enabled
[    14.568] (WW) NVIDIA(0): Option "PrimaryGPU" is not used
[    14.569] (II) NVIDIA(0): [DRI2] Setup complete
[    14.569] (II) NVIDIA(0): [DRI2]   VDPAU driver: nvidia
[    14.571] (II) Initializing extension MIT-SCREEN-SAVER
[    14.572] (II) Initializing extension XFree86-VidModeExtension
[    14.572] (II) Initializing extension XFree86-DGA
[    14.572] (II) Initializing extension XFree86-DRI
[    15.151] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=3 (/dev/input/event13)
[    15.151] (II) This device may have been added with another device file.
[    15.151] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=7 (/dev/input/event14)
[    15.151] (II) This device may have been added with another device file.
[    15.152] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=8 (/dev/input/event15)
[    15.152] (II) This device may have been added with another device file.
[    15.246] (II) This device may have been added with another device file.
[    15.247] (II) This device may have been added with another device file.
[    15.340] (II) This device may have been added with another device file.
[    15.340] (II) This device may have been added with another device file.
[    15.341] (II) This device may have been added with another device file.
[    15.341] (II) This device may have been added with another device file.
[    15.341] (II) This device may have been added with another device file.
[    15.341] (II) This device may have been added with another device file.
[    62.568] (--) NVIDIA(GPU-0): DFP-0: disconnected
[    62.568] (--) NVIDIA(GPU-0): DFP-0: Internal TMDS
[    62.568] (--) NVIDIA(GPU-0): DFP-0: 330.0 MHz maximum pixel clock
[    62.568] (--) NVIDIA(GPU-0): 
[    62.598] (--) NVIDIA(GPU-0): BenQ GL2250H (DFP-1): connected
[    62.598] (--) NVIDIA(GPU-0): BenQ GL2250H (DFP-1): Internal TMDS
[    62.598] (--) NVIDIA(GPU-0): BenQ GL2250H (DFP-1): 600.0 MHz maximum pixel clock
[    62.598] (--) NVIDIA(GPU-0): 
[    62.598] (--) NVIDIA(GPU-0): DFP-2: disconnected
[    62.598] (--) NVIDIA(GPU-0): DFP-2: Internal DisplayPort
[    62.598] (--) NVIDIA(GPU-0): DFP-2: 1440.0 MHz maximum pixel clock
[    62.598] (--) NVIDIA(GPU-0): 
[    62.598] (--) NVIDIA(GPU-0): DFP-3: disconnected
[    62.598] (--) NVIDIA(GPU-0): DFP-3: Internal TMDS
[    62.598] (--) NVIDIA(GPU-0): DFP-3: 165.0 MHz maximum pixel clock
[    62.598] (--) NVIDIA(GPU-0): 
[    64.881] (--) NVIDIA(GPU-0): DFP-0: disconnected
[    64.881] (--) NVIDIA(GPU-0): DFP-0: Internal TMDS
[    64.881] (--) NVIDIA(GPU-0): DFP-0: 330.0 MHz maximum pixel clock
[    64.881] (--) NVIDIA(GPU-0): 
[    64.911] (--) NVIDIA(GPU-0): BenQ GL2250H (DFP-1): connected
[    64.911] (--) NVIDIA(GPU-0): BenQ GL2250H (DFP-1): Internal TMDS
[    64.911] (--) NVIDIA(GPU-0): BenQ GL2250H (DFP-1): 600.0 MHz maximum pixel clock
[    64.911] (--) NVIDIA(GPU-0): 
[    64.911] (--) NVIDIA(GPU-0): DFP-2: disconnected
[    64.911] (--) NVIDIA(GPU-0): DFP-2: Internal DisplayPort
[    64.911] (--) NVIDIA(GPU-0): DFP-2: 1440.0 MHz maximum pixel clock
[    64.911] (--) NVIDIA(GPU-0): 
[    64.911] (--) NVIDIA(GPU-0): DFP-3: disconnected
[    64.911] (--) NVIDIA(GPU-0): DFP-3: Internal TMDS
[    64.911] (--) NVIDIA(GPU-0): DFP-3: 165.0 MHz maximum pixel clock
[    64.911] (--) NVIDIA(GPU-0): 
[  3348.526] (II) event3  - HOLTEK Wireless USB Device Mouse: SYN_DROPPED event - some input events have been lost.
[  3351.086] (II) event3  - HOLTEK Wireless USB Device Mouse: SYN_DROPPED event - some input events have been lost.
[  3352.973] (II) event3  - HOLTEK Wireless USB Device Mouse: SYN_DROPPED event - some input events have been lost.
[  3371.739] (II) event3  - HOLTEK Wireless USB Device Mouse: SYN_DROPPED event - some input events have been lost.
[  3377.078] (II) event3  - HOLTEK Wireless USB Device Mouse: SYN_DROPPED event - some input events have been lost.
[  3377.078] (II) event3  - HOLTEK Wireless USB Device Mouse: WARNING: log rate limit exceeded (5 msgs per 30000ms). Discarding future messages.
[  3378.508] (II) event3  - HOLTEK Wireless USB Device Mouse: SYN_DROPPED event - some input events have been lost.
[  3984.690] (EE) client bug: timer event3 debounce: offset negative (-5ms)
[  3984.690] (EE) client bug: timer event3 debounce short: offset negative (-19ms)
[  4224.186] (EE) client bug: timer event3 debounce: offset negative (-502ms)
[  4224.186] (EE) client bug: timer event3 debounce short: offset negative (-515ms)
[  4588.027] (II) event3  - HOLTEK Wireless USB Device Mouse: SYN_DROPPED event - some input events have been lost.
[  4916.976] (II) event3  - HOLTEK Wireless USB Device Mouse: SYN_DROPPED event - some input events have been lost.
[  4935.835] (II) event3  - HOLTEK Wireless USB Device Mouse: SYN_DROPPED event - some input events have been lost.
[  5260.191] (EE) client bug: timer event3 debounce short: offset negative (-0ms)
[  7061.074] (--) NVIDIA(GPU-0): DFP-0: disconnected
[  7061.074] (--) NVIDIA(GPU-0): DFP-0: Internal TMDS
[  7061.074] (--) NVIDIA(GPU-0): DFP-0: 330.0 MHz maximum pixel clock
[  7061.074] (--) NVIDIA(GPU-0): 
[  7061.112] (--) NVIDIA(GPU-0): BenQ GL2250H (DFP-1): connected
[  7061.112] (--) NVIDIA(GPU-0): BenQ GL2250H (DFP-1): Internal TMDS
[  7061.112] (--) NVIDIA(GPU-0): BenQ GL2250H (DFP-1): 600.0 MHz maximum pixel clock
[  7061.112] (--) NVIDIA(GPU-0): 
[  7061.112] (--) NVIDIA(GPU-0): DFP-2: disconnected
[  7061.112] (--) NVIDIA(GPU-0): DFP-2: Internal DisplayPort
[  7061.112] (--) NVIDIA(GPU-0): DFP-2: 1440.0 MHz maximum pixel clock
[  7061.112] (--) NVIDIA(GPU-0): 
[  7061.112] (--) NVIDIA(GPU-0): DFP-3: disconnected
[  7061.112] (--) NVIDIA(GPU-0): DFP-3: Internal TMDS
[  7061.112] (--) NVIDIA(GPU-0): DFP-3: 165.0 MHz maximum pixel clock
[  7061.112] (--) NVIDIA(GPU-0): 
[  7166.189] (--) NVIDIA(GPU-0): DFP-0: disconnected
[  7166.190] (--) NVIDIA(GPU-0): DFP-0: Internal TMDS
[  7166.190] (--) NVIDIA(GPU-0): DFP-0: 330.0 MHz maximum pixel clock
[  7166.190] (--) NVIDIA(GPU-0): 
[  7166.220] (--) NVIDIA(GPU-0): BenQ GL2250H (DFP-1): connected
[  7166.220] (--) NVIDIA(GPU-0): BenQ GL2250H (DFP-1): Internal TMDS
[  7166.220] (--) NVIDIA(GPU-0): BenQ GL2250H (DFP-1): 600.0 MHz maximum pixel clock
[  7166.220] (--) NVIDIA(GPU-0): 
[  7166.220] (--) NVIDIA(GPU-0): DFP-2: disconnected
[  7166.220] (--) NVIDIA(GPU-0): DFP-2: Internal DisplayPort
[  7166.220] (--) NVIDIA(GPU-0): DFP-2: 1440.0 MHz maximum pixel clock
[  7166.220] (--) NVIDIA(GPU-0): 
[  7166.220] (--) NVIDIA(GPU-0): DFP-3: disconnected
[  7166.220] (--) NVIDIA(GPU-0): DFP-3: Internal TMDS
[  7166.220] (--) NVIDIA(GPU-0): DFP-3: 165.0 MHz maximum pixel clock
[  7166.220] (--) NVIDIA(GPU-0): 

you might try changing/experimenting with different compositor options. im not on kde at the moment but compositor options are somewhere in the system settings. test with each.

1 Like

I finally solved my artifacts issue by writing a sytemd service.

The only negative appears to be that for some reason it takes about 20 seconds before it goes into full suspend. However, it resumes instantly and the screen corruption is not present after resuming.

On a desktop this would seem to be a great solution. On a laptop the slow suspend might be annoying if you closed the lid and then changed your mind about suspending. This might lead to a delay before you could resume. I don't know for sure if that is the case, because I am not using this with a laptop.

A super easy to write one service file solution:

Create:

~/.config/systemd/user/plasma-restart.service

Systemd plasma-restart.service file contents:

#~/.config/systemd/user/plasma-restart.service
#systemctl --user enable plasma-restart.service
#systemctl --user start plasma-restart.service
#systemctl --user status plasma-restart.service
#systemctl --user stop plasma-restart.service
#sudo loginctl enable-linger <username>
#systemctl --user daemon-reload
#systemctl --user daemon-reexec 
[Unit]
Description=Restart plasmashell after resuming
After=suspend.target
StopWhenUnneeded=yes

[Service]
User=root
Type=oneshot
RemainAfterExit=yes 
ExecStart=/usr/bin/sudo -u $USER /bin/bash -lc 'kquitapp5 plasmashell'
ExecStop=/usr/bin/sudo -u $USER /bin/bash -lc 'plasmashell > /dev/null 2>&1 & disown; sleep 2; exit'

[Install]
WantedBy=sleep.target

Enable the plasma-restart.service:

systemctl --user enable  plasma-restart.service

Reboot.

3 Likes

i'll have to try that out on my kde install. i get artifacts (looks like HD static over icons) after resuming from suspend and restarting compositor/changing compositor does nothing. :+1:

1 Like

It should work for you. It took me a long time to figure out the fix on that service. I forgot to post that one on my systemd thread.

Hope it helps.

2 Likes

Thank you but this doesn't work...

I've just found that in the kernel log:

[ 1839.960839] snd_hdac_bus_update_rirb: 89 callbacks suppressed
[ 1839.960844] snd_hda_intel 0000:01:00.1: spurious response 0x80000000:0x0, last cmd=0x4f0900
[ 1839.992156] snd_hda_intel 0000:01:00.1: spurious response 0xc0000000:0x0, last cmd=0x4f2e08
[ 1839.992193] snd_hda_intel 0000:01:00.1: spurious response 0x5f:0x0, last cmd=0x4f2f00
[ 1839.992233] snd_hda_intel 0000:01:00.1: spurious response 0x80000010:0x0, last cmd=0x4f2f01
[ 1839.992275] snd_hda_intel 0000:01:00.1: spurious response 0x80000000:0x0, last cmd=0x4f2f02
[ 1839.992317] snd_hda_intel 0000:01:00.1: spurious response 0x80000008:0x0, last cmd=0x4f2f03
[ 1839.992358] snd_hda_intel 0000:01:00.1: spurious response 0x80000000:0x0, last cmd=0x4f2f04
[ 1839.992400] snd_hda_intel 0000:01:00.1: spurious response 0x8000006d:0x0, last cmd=0x4f2f05
[ 1839.992442] snd_hda_intel 0000:01:00.1: spurious response 0x80000010:0x0, last cmd=0x4f2f06
[ 1839.992484] snd_hda_intel 0000:01:00.1: spurious response 0x80000000:0x0, last cmd=0x4f2f07

thats, audio related. i just booted up my kde install to see if i can figure it out. my artifacts are different but both still graphical glitches after waking from suspend.

after suspend, this is what my dock looks like. same for the sddm lock/splash screen. 1 min

1 Like

@tbg those 2 commands in your service on their own did not work for my graphical glitches. adding a restart sddm did fix it, but it also means you lose and currently running apps?

#!/bin/sh

kquitapp5 plasmashell
sudo systemctl restart sddm
plasmashell > /dev/null 2>&1 & disown; sleep 2; exit
1 Like

You need to do it as a service exactly as it's written. Try the service as written. It works perfectly for me and the session is saved.

1 Like

i did, after it didnt work i just started toying with a script afterwards to see what i could make happen. yesterday someone had a similar issue with nvidia/sddm starting to fast was the problem. but only when using nvidia which is also the case with my graphical issues on wake, only happens on nvidia. when i run intel-only i dont get those issues. i barely use kde anymore but i know it can get annoying. i got used to just rebooting after i would wake the laptop.

i forget if i had the save session option disabled, i may have. im back in openbox now but thats also a possibility as to why my session didnt save.

@Beatussum did you ?

1 Like

If you want to test them as commands you need to open a root terminal. The commands must be initiated as root to simulate how they are executed as a system service (root perms).

Run as root, (not sudo):

sudo -u $USER /bin/bash -lc 'kquitapp5 plasmashell'; sudo -u $USER /bin/bash -lc 'plasmashell > /dev/null 2>&1 & disown; sleep 2; exit'

Please post:

systemctl --user status plasma-restart.service
1 Like

Holy Sh*t, I think I just figured out why this is Not working. I just re-enabled my service and it is also not working. I also lost the delay before suspend as well.

I've been testing out so many services I had a bunch of suspend services running together. I thought I'd better shut them all down, as I didn't want to taint my results by one service affecting another.

However, I think I had other services running at the same time I was testing this service. It wasn't until later that I decided to only run one suspend service at a time.

So, it must have been the interaction with another suspend service that made this work originally. I've tested out so many services in the last few weeks I'm not sure I'll ever find the combination that was working again. Duuuh.

Back to testing again. I'll let you know if I find the magic combo again. This might be a hard find after all the services I was testing. Literally hundreds of combos.

1 Like

not to worry, im sure there is only a few thousand possible combinations. :sunglasses:

another possibility, is there a way of force saving a session before restarting sddm? that would fix any graphical glitches related to sleep/wake cycle i would think.

any possible sddm configuration options that might stop this from happening? i dont know, ive never modified sddm configuration before, just an idea.

1 Like

I've found quite a few different ways to get rid of the corruption, but they all killed the session except this unit (when it was working).

I can't believe it , I had the fix then I lost it. :sob: :cry: :man_facepalming:

1 Like

@tbg It finally seems to be working: I'm running some tests first before.

@tbg @dglt I think to have determinated the problem: it comes from kwin_x11.

Please provide more details. From what I have read this is a known bug with the proprietary Nidia driver.

Any information you have would be greatly appreciated. Unfortunately I haven't been at home to perform further troubleshooting on my system.

On my system if I recall correctly restarting kwin does not fix this issue. Only a full plasma restart has corrected the problem on my system.

1 Like

Sorry, I misspoke: I meant that the command kwin_x11 --replace makes the artifacts disappear.
@tbg Is it possible to add this in a service?

1 Like

I'm not a home to test it, but you could certaily try replacing the plasma start command with that command in as service.

2 Likes

Forum kindly sponsored by