From: "Clément Lassieur" <clement@lassieur.org>
To: Sergey Trofimov <sarg@sarg.org.ru>
Cc: Josselin Poiret <dev@jpoiret.xyz>, chris <chris@bumblehead.com>,
68483@debbugs.gnu.org
Subject: bug#68483: Qutebrowser QT platform plugin could not be initialized
Date: Tue, 16 Jan 2024 12:02:29 +0100 [thread overview]
Message-ID: <871qahsfqy.fsf@lassieur.org> (raw)
In-Reply-To: <871qahmu04.fsf@sarg.org.ru> (Sergey Trofimov's message of "Tue, 16 Jan 2024 11:47:22 +0100")
On Tue, Jan 16 2024, Sergey Trofimov wrote:
>> Would this work with non-wayland users too? (So that it would make
>> sense to add it to the main package?)
>>
>> Thanks,
>> Clément
>
> Yeah, it would work, but forcing the platform through parameters is not
> necessary. I added it just to be sure that wayland is being used instead of
> xcb. On the other hand I think adding qtwayland dependency to every qt-based
> gui program doesn't make sense. Maybe a qtwayland-home-service makes more
> sense which would install the dependency and set required environment
> variables. This way it would work for every Qt GUI program on wayland.
Ok, I see, thanks!
next prev parent reply other threads:[~2024-01-16 11:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-15 19:40 bug#68483: Qutebrowser QT platform plugin could not be initialized chris
2024-01-15 22:15 ` Josselin Poiret via Bug reports for GNU Guix
2024-01-15 22:44 ` chris
2024-01-16 6:38 ` Sergey Trofimov
2024-01-16 7:07 ` chris
2024-01-16 7:48 ` chris
2024-01-16 10:42 ` Clément Lassieur
2024-01-16 10:47 ` Sergey Trofimov
2024-01-16 11:02 ` Clément Lassieur [this message]
2024-01-16 11:35 ` Sergey Trofimov
2024-01-16 15:12 ` chris
2024-01-16 15:45 ` chris
2024-01-16 16:19 ` chris
2024-01-16 16:57 ` chris
2024-01-16 7:53 ` chris
2024-01-16 8:14 ` chris
2024-01-16 10:00 ` Sergey Trofimov
2024-01-16 16:27 ` bug#68483: closing chris
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=871qahsfqy.fsf@lassieur.org \
--to=clement@lassieur.org \
--cc=68483@debbugs.gnu.org \
--cc=chris@bumblehead.com \
--cc=dev@jpoiret.xyz \
--cc=sarg@sarg.org.ru \
/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).