From: CameronNemo <CameronNemo@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] Ardour rendering and/or input issues with XWayland on Sway on Mesa/Panfrost
Date: Sun, 06 Mar 2022 02:22:10 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36002@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1070 bytes --]
New issue by CameronNemo on void-packages repository
https://github.com/void-linux/void-packages/issues/36002
Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System
* xuname: `Void 5.15.17_1 aarch64 Unknown uptodate rDFFFFFFF`
**NOTE**: specific platform is the Pinebook Pro, not sure if that is relevant
* package:
* ardour-6.9_1
* pipewire-0.3.47_1
* sway-1.7_1
* mesa-21.3.5_1
### Expected behavior
Ardour responds to user input and renders the UI correctly.
### Actual behavior
Severe rendering issues for the GUI and either blocked or extremely slow input.
### Steps to reproduce the behavior
Start ardour with `pw-jack ardour6`. Observe the session configuration screen being a blank window. Sometimes keyboard input works, or maybe always and the change is simply not rendered. But when able to get past the session config screen, more rendering issues with the timeline.
next reply other threads:[~2022-03-06 1:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-06 1:22 CameronNemo [this message]
2022-03-06 1:23 ` CameronNemo
2022-04-11 20:02 ` CameronNemo
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36002@inbox.vuxu.org \
--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).