Bug 434715 - After change animation speed Plasma Wayland Session + Nvidia just dies
Summary: After change animation speed Plasma Wayland Session + Nvidia just dies
Status: RESOLVED DUPLICATE of bug 428089
Alias: None
Product: kwin
Classification: Plasma
Component: wayland-generic (show other bugs)
Version: 5.21.3
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-03-21 12:16 UTC by Felipe Kinoshita
Modified: 2021-04-07 19:44 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
image showing observed result (475.94 KB, image/png)
2021-03-21 12:16 UTC, Felipe Kinoshita
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Felipe Kinoshita 2021-03-21 12:16:55 UTC
Created attachment 136913 [details]
image showing observed result

STEPS TO REPRODUCE
1. on System Settings > Workspace Behavior > General Behavior change animation speed

OBSERVED RESULT
Session just dies, it kinda renders the same thing over and over.

EXPECTED RESULT
Session shouldn't die.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: openSUSE Tumbleweed
(available in About System)
KDE Plasma Version: 5.21.3
KDE Frameworks Version: 5.80
Qt Version: 5.12.2
Comment 1 Felipe Kinoshita 2021-03-21 12:19:08 UTC
Also when rendering the same thing over and over sometimes it renders by itself and sometimes after user input like moving the cursor or typing something
Comment 2 Felipe Kinoshita 2021-03-23 06:14:51 UTC
Testing even further, this bug also occurs when enabling "Navigation wraps around" on System Settings > Workspace Behavior > Virtual Desktops.

It seems like changing some "important" setting might trigger this bug.
Comment 3 Vlad Zahorodnii 2021-04-01 08:04:52 UTC
Are you using the proprietary NVIDIA driver?
Comment 4 Vlad Zahorodnii 2021-04-01 08:05:34 UTC
Settings the NEEDSINFO status.
Comment 5 Felipe Kinoshita 2021-04-01 08:17:06 UTC
Yes!
Comment 6 Vlad Zahorodnii 2021-04-07 19:44:10 UTC

*** This bug has been marked as a duplicate of bug 428089 ***