Bug 415419 - kwin_x11/intel : screen flickers, large parts are black, sometimes show stale content
Summary: kwin_x11/intel : screen flickers, large parts are black, sometimes show stale...
Status: RESOLVED FIXED
Alias: None
Product: kwin
Classification: Plasma
Component: compositing (show other bugs)
Version: 5.14.5
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-12-21 00:53 UTC by stefan.schwarzer
Modified: 2022-03-09 11:36 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description stefan.schwarzer 2019-12-21 00:53:22 UTC
SUMMARY


STEPS TO REPRODUCE
1. log in / kde desktop

OBSERVED RESULT
see description, always reproducible

EXPECTED RESULT
well, what a compositing window manager should do...

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 5.3.0-3-amd64 #1 SMP Debian 5.3.15-1
(available in About System)
KDE Plasma Version: 5.14.5
KDE Frameworks Version: 5.62 (?)
Qt Version: 5.12.5

ADDITIONAL INFORMATION
Intel CPU with integrated graphics, nvidia optimus, nouveau blacklisted, no nvidia-drivers installed
(more info below)

The following is basically a quote from debbugs (#deb943585, 27 Oct 2019):

Right after login I get flickering black rectangles on the screen, which
may cover up to 90% of its area. Windows mostly remain black or their content
suddenly becomes visible, the task bar remains black and I see other residuals of the kde splash screen where windows should be drawn or the background wallpaper be restored. Swithing to a VT; all seems ok, kwin, the desktop and applications are running.

So far, my only clue as to what may be going on is a workaroud I found: if I start a terminal via keyboard shortcut and issue blindly
        DRI_PRIME=1 kwin_x11 --replace
then afterwards things behave mostly normally (Sometimes window content is
still not correctly updated). I just picked this line up from older bug reports
against kwin on the net without understanding what it does.

This is the output of kwin following this command in the hope that it helps

OpenGL vendor string:                   Intel Open Source Technology Center
OpenGL renderer string:                 Mesa DRI Intel(R) HD Graphics 530
(Skylake GT2)
OpenGL version string:                  4.5 (Core Profile) Mesa 19.2.1
OpenGL shading language version string: 4.50
Driver:                                 Intel
GPU class:                              Unknown
OpenGL version:                         4.5
GLSL version:                           4.50
Mesa version:                           19.2.1
X server version:                       1.20.4
Linux kernel version:                   5.3
Requires strict binding:                yes
GLSL shaders:                           yes
Texture NPOT support:                   yes
Virtual Machine:                        no



-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.3.0-1-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
  (tainted module is vmware kernel stuff (patched Workstation 14))
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Comment 1 Christoph Feck 2020-01-13 11:42:01 UTC
I remember getting this with older versions when
- disabling then re-enabling compositing by pressing Shift+Alt+F12 twice
- modifying window rules

I can no longer reproduce this with the current version from master branch.
Comment 2 stefan.schwarzer 2020-02-01 09:58:45 UTC
Hi Christoph,
  
thanks for your feedback. I have tried to compile a current version of kwin from the KDE repositories. Unfortunately, I will have to recompile some parts of kf5  to set up all dependencies (5.66 is required, 5.62 is the best my distribution would provide as is). This is currently out of scope for me. As I have a workaround, I will wait and report back once debian as progressed to that level.

Thanks again, 
Stefan
Comment 3 Vlad Zahorodnii 2020-02-06 11:40:25 UTC
It is also worth to mention that 5.14 is no longer supported by KDE.
Comment 4 postix 2022-03-04 12:46:13 UTC
Stefan, do you still experience this? Does it look like I have reported in #450329 ?
Comment 5 stefan.schwarzer 2022-03-08 21:45:03 UTC
Uuhps, ghosts from the past. 
No, I haven't seen this for a long time now. It doesn't at all look like your wayland issue in #450329.
From my POV the bug can be closed.
Comment 6 postix 2022-03-09 11:36:00 UTC
(In reply to stefan.schwarzer from comment #5)
> Uuhps, ghosts from the past. 
> From my POV the bug can be closed.

Great! :-)