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: Wed, 02 Nov 2022 02:37:58 +0100	[thread overview]
Message-ID: <20221102013758.JA9TqQy8j0wFFoC1094rogoUyTkM3mDMFWvPf8Zj7xg@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: 674 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**~~
~~**__GL_YIELD=USLEEP**~~  

EDIT:
Well, I am embarrassed to say that my "workarounds" do NOT work, because although I was using the latest nvidia drivers, I did not realize that I was running another (non-Void) partition at the time of these experiments, which worked with no modification.  I regret the confusion.  Still searching for clues in Void.  At least my first post here still stands.

  parent reply	other threads:[~2022-11-02  1:37 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 [this message]
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=20221102013758.JA9TqQy8j0wFFoC1094rogoUyTkM3mDMFWvPf8Zj7xg@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).