Bug 431343 - nvidia wayland looks, functions, and runs poorly
Summary: nvidia wayland looks, functions, and runs poorly
Status: RESOLVED NOT A BUG
Alias: None
Product: kwin
Classification: Plasma
Component: wayland-generic (show other bugs)
Version: 5.20.5
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-01-09 07:45 UTC by Wyatt Childers
Modified: 2021-01-24 22:16 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Kwin support information (6.84 KB, text/plain)
2021-01-09 07:47 UTC, Wyatt Childers
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Wyatt Childers 2021-01-09 07:45:09 UTC
BACKGROUND
I decided to make another attempt to switch to wayland using the nvidia proprietary driver. A quick summary of my history with wayland under nvidia:

- I originally filed Bug 408634 when first trying wayland via the nvidia driver. This issue has been fully resolved for me.

- I then suffered from Bug 428195. This issue has also been fully resolved for me.

CURRENT SITUATION

The current state of Wayland under nvidia, I can now use a Wayland session without a frozen black screen or excessive CPU usage (yay). However, the experience is unbelievably bad for Fedora 34 to be suggesting switching to it as the default, to the point where I suspect there's still something fringe lingering.

There are a number of bugs:
- As much as 40% CPU usage on a Ryzen 3950X from kwin_wayland just moving the mouse around
- Only the first kicker sub menu renders, moving the mouse to any other sub menu rerenders the previous menu
- Searching with kicker results in a blank kicker regardless of time waited
- Krunner is similarly unusable, with no results rendering 
- Artifacts from pop-overs, opening something like the calendar widget, as it disapears the center "1/8th" of the widget remains on the screen momentarily
- No transparency anywhere on the desktop, everything appears as if the compositor is disabled in the X11 world
- Yakuake renders uncentered, going to the left side of the current monitor
- Dragging a panel around/attempting to move it to a second monitor crashes the desktop
- Various things are inexplicably shaded very very dark (e.g. non-header half of notifications)
- Logging out and back in only works sometimes; sometimes things just "crash", one time I was shown the fedora + motherboard manufacter plymouth screen after attempting to relogin

----

Are these issues to be expected? (I expect not, so hopefully we can figure out why this plethora of problems is occurring :) ). See attachments for system information.
Comment 1 Wyatt Childers 2021-01-09 07:47:25 UTC
Created attachment 134674 [details]
Kwin support information
Comment 2 Vlad Zahorodnii 2021-01-11 08:00:14 UTC
Yeah, even though we do provide NVIDIA support on Wayland, it's highly untested and unstable.

Tracking multiple issues in a single bug report is difficult, can you file separate bug reports?
Comment 3 Samuel 2021-01-13 05:26:54 UTC
BTW do you have window decorations in Wayland session? Also Now after Plasma 5.20.5 and KDEF 5.78 update in my arch linux, the plasma wayland session logs in properly but just after moments from logging in, plasma shell crashes causing a black screen with only cursor :(
Comment 4 Samuel 2021-01-13 05:28:15 UTC
I only have window decorations for GTK apps but all QT apps have a blurred bar without any window decorations.
Comment 5 Wyatt Childers 2021-01-13 08:27:48 UTC
I recall having window decorations, that seemed to be working fine for me
Comment 6 Wyatt Childers 2021-01-24 22:16:06 UTC
Bugs have been filed:
- Bug 432053 
- Bug 432054  
- Bug 432055
- Bug 432057
- Bug 432058
- Bug 432059
- Bug 432060
- Bug 432061
- Bug 432062

I omitted the "Various things are inexplicably shaded very very dark (e.g. non-header half of notifications)" I'm going to attribute that to the transparency problems.