https://bugs.kde.org/show_bug.cgi?id=411506
Bug ID: 411506
Summary: Kwin requires constant restart after weeks of uptime
to refresh windows
Product: kwin
Version: 5.13.0
Platform: Archlinux Packages
OS: Linux
Status: REPORTED
Severity: major
Priority: NOR
Component: compositing
Assignee: kwin-bugs-n...@kde.org
Reporter: mich...@butash.net
Target Milestone: ---
SUMMARY:
Long-time user of kde, when it actually works, but a normal issue is it has
never been able to deal with a very large framebuffer which is a constant issue
from 4.x days. It appears to be a systemic issue that has never been
addressed, as this has been the same for over 10 years that it cannot deal with
large frame buffers, prior 11520x1080 resolution (6x 1080 displays), upgraded
now to 11520x2160 (3x 4k displays). It still destabilizes the same from 4.x
days into current.
STEPS TO REPRODUCE
1. Connect 3x 4k displays with an nvidia display, any driver version (currently
430.34-2).
2. Use with uptime over a week or three.
3. Watch for windows to stop refreshing when interacted with.
OBSERVED RESULT:
Windows stop refreshing when interacted with, such as clicking, typing in
consoles, anything inside KDE. Browsers, console sessions, anything expected
to be instantly refreshed upon click/type/change, and watch them not do so
until minimized or otherwise forcibly refreshed. This is most noticeable using
a browser, clicking on things the display never changes, until minimized and
brought back to change to the new page, or same for a terminal session with
konsole that doesn't show typed commands until minimized and brought back.
EXPECTED RESULT:
Updates to the windows as typing, clicking, other occur. They do not when kwin
gets wonky.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 5.16.3-1
KDE Frameworks Version: 5.60.0-1
Qt Version: 5.13.0-1
ADDITIONAL INFORMATION:
This condition has existed from the beginning of time, and always ignored when
reported in various ways. As a core component of the DE, it's pretty sad this
persists, but does without resolution. I normally just switch between
Cinnamon, Mate, or KDE, depending on which is more stable, but I really like
KDE, when it's not terrible to use. This condition sometimes depending on
version manifests itself quickly (within an hour) to weeks (best-case).
Work-around for me is restarting compositing regularly, where after a few weeks
of uptime, is every 3-4 days. Switching in display/compositor settings from
OpenGL 2.1 and 3.0, back and forth fixes it, for a while again. Neither is
better, just switching between either resolves it until it destabilizes again.
--
You are receiving this mail because:
You are watching all bug changes.
