I’ve read just about everything on the site about plasma flickering/blanking, etc. People keep posting that ver. 6.8.2 will fix it. Problem: I didn’t have any trouble with flickering until I updated to 6.8.2! Any time I move my mouse the monitor where the mouse is located flickers, the mouse doesn’t. Also, one or both monitors will black out randomly. Since I’m running tumbleweed, I don’t think reverting plasma is a safe option. geforce 1030 with nouveau driver Note: some people suggest switching the monitor connections, I can’t because the cabling is incompatible.
Does the flickering occur only when applications are running full-screen, or does it also happen with ordinary windowed applications and on the desktop?
Examine the journal and share here…
journalctl --user -b | grep -iE 'plasma|kwin|atomic'
sudo journalctl -b -k | grep -iE 'nouveau|drm|nvidia'
That might yield more useful clues.
In windows, on the desktop and the worst times are when I launch Konsole. Both monitors blank out, come back, blank, repeat; which makes checking logs, etc extremely difficult.
I’ll try, but Konsole is the absolute worse offender.
Direct scanout might be impacting here. It allows the graphics hardware to display an application’s frame directly to the monitor, bypassing the desktop compositor to lower latency and increase performance. However, with nouveau and recent Plasma 6.8 versions, there’s a known driver/KWin interaction where handling hardware cursor planes and scanout handoffs can cause the display output to fail intermittently and blank out.
If you haven’t tried this yet, you can force KWin to use a software cursor and disable direct scanout entirely.
Create ~/.config/environment.d/99-kwin-fix.conf
and add
KWIN_FORCE_SW_CURSOR=1
KWIN_DRM_NO_DIRECT_SCANOUT=1
Log out and back in. Does that help?
I’ll see if I can get the Konsole to work long enough to do this.
YES! Thank you.
I tried a similar fix from another thread, but it didn’t work.
Then we’ll need journal output to see what’s going on.
Oh, so that worked for you? Mark it up as solved it did. ![]()
The first command generated 1850 lines of output. The second only 83. Will this system barf if I posted them?
I’m confused, did the environment variables work or not?
Yes, they worked. We got out of sync and I thought you still wanted the journal. Thanks again.