From: TrueTechie <TrueTechie@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] KDE Wayland Broken on Latest Nvidia Driver
Date: Sun, 30 Oct 2022 19:35:05 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40235@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1271 bytes --]
New issue by TrueTechie on void-packages repository
https://github.com/void-linux/void-packages/issues/40235
Description:
### Is this a new report?
Yes
### System Info
Void 5.19.16_1 x86_64 GenuineIntel uptodate FFFFF
### Package(s) Affected
nvidia-515.65.01_2, plasma-wayland-protocols-1.9.0_1
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
_No response_
### Expected behaviour
The Plasma Wayland session works with `nvidia-drm` enabled just as other window managers such as Wayfire do.
### Actual behaviour
The desktop launches though it is incredibly slow and laggy, making it unusable. According to [this comment](https://www.reddit.com/r/voidlinux/comments/y86m7f/comment/iu5bkt7/?context=3) on Reddit, this does not happen with the 470 series of Nvidia drivers. I think this might be an EGL/GBM issue.
If there is a way to solve this issue without modifying the package, such as an environment variable, I haven't found it and it should be put somewhere in the docs.
### Steps to reproduce
1. Install Nvidia drivers
2. Enable kernel modesetting (`nvidia-drm`) on boot
3. Install `kde5` and the various packages required to run a Wayland session in Plasma
4. Launch the Wayland session from SDDM
next reply other threads:[~2022-10-30 18:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-30 18:35 TrueTechie [this message]
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
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40235@inbox.vuxu.org \
--to=truetechie@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).