From: furryfixer <furryfixer@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: KDE Wayland Broken on Latest Nvidia Driver
Date: Wed, 02 Nov 2022 03:52:29 +0100 [thread overview]
Message-ID: <20221102025229.XeWdSne-AClNU-u0HYW-IDD7-gTIQS1qvmj7wYsxcR8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40235@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1660 bytes --]
New comment by furryfixer on void-packages repository
https://github.com/void-linux/void-packages/issues/40235#issuecomment-1296379968
Comment:
The reddit comment referred to above was mine. I have since installed Void Plasma Wayland with nvidia for myself to investigate (GeForce GTX 1660 Ti), and can confirm this issue with nvidia515.65.01 and kernel 5.19.16_1. If it helps, this is what I have found so far:
- Does not occur on Plasma X11
- Occurs with startx as well as SDDM login
- Downgrading to nvidia470 xbps packages fixes it
- kwin_wayland takes nearly 100% cpu during this
- Occurs with more than one theme and icon set
- A key pressed within both Konsole (wayland) and lxterminal (Xwayland) is sometimes echoed repeatedly to the terminal window.
- Briefly corrects and lowers CPU usage after showing **irq-130nvidia** interrupt in top?
Despite very slow startup, the latest version of kwin_wayland initially allows normal mouse cursor movement, but as soon as a cursor mouse-over on a desktop icon occurs, the issue arises. Weirdly, when mousing over certain Panel icons, the problem goes away after the popup notification disappears. Sometimes the popup seems to shift slightly just before disappearing, and then kwin CPU usage drops to normal, until trying to do almost anything but moving the mouse in an empty area of the desktop makes it recur.
EDIT
-nvidia515.65.01 FAILS for linux-lts kernel (5.10) as well
-nvidia-510.47.03_1 WORKS for linux-lts (won't build dkms module for linux 5.19)
This is helpful only because, while nvidia470 may still use EGL_streams?, I presume nvidia510 is using GBM, as is nvidia515.
next prev parent reply other threads:[~2022-11-02 2:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-30 18:35 [ISSUE] " TrueTechie
2022-10-30 23:38 ` furryfixer
2022-10-31 17:31 ` EwolBash
2022-11-01 10:27 ` furryfixer
2022-11-01 13:55 ` furryfixer
2022-11-02 1:37 ` furryfixer
2022-11-02 2:52 ` furryfixer [this message]
2022-11-23 16:17 ` furryfixer
2022-11-26 2:19 ` furryfixer
2022-11-26 14:07 ` cmhainesii
2022-11-26 18:12 ` kruceter
2022-11-26 18:22 ` [ISSUE] [CLOSED] " classabbyamp
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20221102025229.XeWdSne-AClNU-u0HYW-IDD7-gTIQS1qvmj7wYsxcR8@z \
--to=furryfixer@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).