https://bugs.kde.org/show_bug.cgi?id=527328
Bug ID: 527328
Summary: Screen goes black/flickers on mouse movement
Classification: Plasma
Product: kwin
Version First 6.8.0
Reported In:
Platform: Neon
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
DESCRIPTION
With the update to 6.8.0, mouse movement causes the screen to go black or to
flicker between black & the normal rendering. The mouse pointer itself is
always visible normal.
Sometimes the black screen is dominant, sometimes not, so stopping the mouse
can land on normal screen or black screen. Switching windows or opening the
start menu by keyboard restores the normal screen when it was black.
As long as the mouse does not move, everything is normal.
The issue is already there at the login screen, but not at the following splash
screen (as there is no mouse pointer, I suspect).
STEPS TO REPRODUCE
0. Update KDE Neon from Plasma 6.7.5 to 6.8.0
1. Start Session
2. Move mouse
OBSERVED RESULT
Screen goes black or flickers between black & normal.
EXPECTED RESULT
Screen should not go black.
SOFTWARE/OS VERSIONS
Operating System: KDE neon User Edition
KDE Plasma Version: 6.8.0
KDE Frameworks Version: 6.31.0
Qt Version: 6.11.1
Kernel Version: 7.0.0-38-generic (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7 CPU 870 @ 2.93GHz
Memory: 8 GiB of RAM (7.7 GiB usable)
Graphics Processor: NVD9
ADDITIONAL INFORMATION
Similar issue descriptions are found here:
https://discuss.kde.org/t/kde-plasma-6-8-beta-2-caused-the-screen-to-go-black-flicker-movimg-constantely-stops-the-problem/50728
Although, the details are a bit different.
In one case, constant mouse movement shows the normal screen, whereas for me,
mouse movement mainly triggers the problem. Or at least flickers between black
& normal screen.
Also mentioned is the shaky pointer, I did not see different behavior when the
shaky pointer is used, not actively used or even disabled + reboot.
Common seems to be usage of the nouveau driver and nvidia cards.
In journalctl, I see the following error logs, not sure if related.
The first one was already reported before the update, in 6.7.5
The second one seems to be new.
```
Oct 18 08:16:47 xps-8100 kwin_wayland[1432]: drmSetClientCap for Atomic Mode
Setting failed. Using legacy mode on GPU "/dev/dri/card1"
Oct 18 08:16:47 xps-8100 kwin_wayland[1432]: Failed to gain real time thread
priority (See CAP_SYS_NICE in the capabilities(7) man page). error: Operation
not permitted
```
--
You are receiving this mail because:
You are watching all bug changes.
