Github messages for voidlinux
 help / color / mirror / Atom feed
From: furryfixer <furryfixer@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: KDE Wayland Broken on Latest Nvidia Driver
Date: Tue, 01 Nov 2022 11:27:28 +0100	[thread overview]
Message-ID: <20221101102728.QDr3XGbDT-cCMHQVPHW397Ek95_s66p15yuHPItorNU@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: 678 bytes --]

New comment by furryfixer on void-packages repository

https://github.com/void-linux/void-packages/issues/40235#issuecomment-1298323748

Comment:
There is a workaround for now. Either of two environment variable settings may fix it:   

**__GL_MaxFramesAllowed=1**   
or   
**__GL_YIELD=USLEEP**   

This would initially suggest a regression in nvidia drivers or kwin (upstream). However, the issue does not occur in Gnome Wayland on Void with the same packages (nvidia), and does not seem to occur in Plasma Wayland on non-Void distros with same or similar packages (wayland/kwin/plasma/qt). 

I am uncertain of any negative consequences to using the above workaround.

  parent reply	other threads:[~2022-11-01 10:27 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 [this message]
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=20221101102728.QDr3XGbDT-cCMHQVPHW397Ek95_s66p15yuHPItorNU@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).