From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Morgan Smith <Morgan.J.Smith@outlook.com>
Cc: 57742@debbugs.gnu.org
Subject: bug#57742: QT plugins from profile not found (QT_PLUGIN_PATH)
Date: Fri, 07 Oct 2022 15:39:48 -0400 [thread overview]
Message-ID: <877d1b5sor.fsf@gmail.com> (raw)
In-Reply-To: <87illq11il.fsf@gmail.com> (Maxim Cournoyer's message of "Wed, 14 Sep 2022 10:17:39 -0400")
Hi,
Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:
> [re-sending again, this time with debbugs in CC]
>
> Hello,
>
> Morgan Smith <Morgan.J.Smith@outlook.com> writes:
>
>> Hello!
>>
>> Ever since commit 1f466ed6be932526fc69e72ffd50390691d0d382 we don't look
>> at the user's value of QT_PLUGIN_PATH. The comment says this is to
>> prevent plugin confusion between Qt5 and Qt6 stuff.
>
> Yes; unfortunately Qt doesn't seem to have thought about making that
> variable usable with both Qt5 and Qt6 at the same time. It's probably
> worth reporting the issue upstream.
Reported upstream with https://bugreports.qt.io/browse/QTBUG-107459.
--
Thanks,
Maxim
next prev parent reply other threads:[~2022-10-07 19:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-11 20:53 bug#57742: QT plugins from profile not found (QT_PLUGIN_PATH) Morgan Smith
2022-09-14 14:17 ` Maxim Cournoyer
2022-10-07 19:39 ` Maxim Cournoyer [this message]
2022-11-30 14:57 ` kiasoc5 via Bug reports for GNU Guix
2023-02-17 16:25 ` Marek Paśnikowski via Bug reports for GNU Guix
2023-03-07 0:55 ` Maxim Cournoyer
2023-03-07 13:39 ` Maxim Cournoyer
2023-03-28 23:53 ` Maxim Cournoyer
2023-03-29 0:05 ` bug#57742: [PATCH core-updates] build: qt-utils: Add prefix when wrapping QT_PLUGIN_PATH variable Antero Mejr via Bug reports for GNU Guix
2023-03-29 0:21 ` bug#57742: QT plugins from profile not found (QT_PLUGIN_PATH) Maxim Cournoyer
2023-03-29 0:15 ` bug#57742: [PATCH core-updates] build: qt-utils: Add prefix when wrapping QT_PLUGIN_PATH variable Antero Mejr via Bug reports for GNU Guix
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=877d1b5sor.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=57742@debbugs.gnu.org \
--cc=Morgan.J.Smith@outlook.com \
/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).