https://bugs.kde.org/show_bug.cgi?id=431343
Bug ID: 431343
Summary: nvidia wayland looks, functions, and runs poorly
Product: kwin
Version: 5.20.5
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: wayland-generic
Assignee: kwin-bugs-n...@kde.org
Reporter: dark...@nearce.com
Target Milestone: ---
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.
--
You are receiving this mail because:
You are watching all bug changes.
