From: CameronNemo <CameronNemo@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Ardour rendering and/or input issues with XWayland on Sway on Mesa/Panfrost
Date: Mon, 11 Apr 2022 22:02:13 +0200 [thread overview]
Message-ID: <20220411200213.Ke-j81qzykN5ddD836a_JBj43K3tdAB_x9DNpIiKNYM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36002@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 297 bytes --]
New comment by CameronNemo on void-packages repository
https://github.com/void-linux/void-packages/issues/36002#issuecomment-1095510763
Comment:
I do not know what happened but this is not an issue for me anymore. One thing I did is update pipewire and I think wlroots so that may have been it.
next prev parent reply other threads:[~2022-04-11 20:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-06 1:22 [ISSUE] " CameronNemo
2022-03-06 1:23 ` CameronNemo
2022-04-11 20:02 ` CameronNemo [this message]
2022-04-11 20:02 ` [ISSUE] [CLOSED] " CameronNemo
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=20220411200213.Ke-j81qzykN5ddD836a_JBj43K3tdAB_x9DNpIiKNYM@z \
--to=cameronnemo@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).