From: Demis Balbach <db@minikn.xyz>
To: Christopher Baines <mail@cbaines.net>
Cc: 59451@debbugs.gnu.org
Subject: [bug#59451] [PATCH] gnu: cura: Make it work on wayland.
Date: Mon, 28 Nov 2022 23:34:56 +0100 [thread overview]
Message-ID: <87fse23dyn.fsf@minikn.xyz> (raw)
In-Reply-To: <874juqrpoo.fsf@cbaines.net>
[-- Attachment #1: Type: text/plain, Size: 1147 bytes --]
On 2022-11-23 09:20, Christopher Baines wrote:
> Setting this environment variable here seems quite unusual. What's it
> doing, and would anyone want to set a different value?
>
> Thanks,
>
> Chris
Hello Chris,
unfortunately I can't help much with this. Cura is currently not running
under Wayland (XWayland). After doing a bit of research, I found
https://github.com/Ultimaker/Cura/issues/10815, and setting
`QT_QPA_PLATFORM` to `xcb` was the suggested workaround until wayland is
officially supported.
My QT knowledge is very limited, but the QT_QPA_PLATFORM env var seems
to allow for defining platform-specific features for the application
(https://doc.qt.io/qt-6/embedded-linux.html#specifying-additional-settings).
Setting it to `xcb` enables the XCB plugin
(https://doc.qt.io/qt-6/embedded-linux.html#xcb), which seems to be the
default X11 plugin.
Setting the env var to `wayland` doesn't work unfortunately. As an
alternative, I could create a package derivation `cura-wayland` and only
apply the patch there? Would that be more suitable?
--
Best regards / Mit freundlichen Grüßen,
Demis Balbach
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2022-11-28 22:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-21 17:14 [bug#59451] [PATCH] gnu: cura: Make it work on wayland Demis Balbach
2022-11-23 9:20 ` Christopher Baines
2022-11-28 22:34 ` Demis Balbach [this message]
2022-12-04 17:56 ` Morgan Smith
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fse23dyn.fsf@minikn.xyz \
--to=db@minikn.xyz \
--cc=59451@debbugs.gnu.org \
--cc=mail@cbaines.net \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).