From: Leo Famulari <leo@famulari.name>
To: Marius Bakke <mbakke@fastmail.com>
Cc: 29905-done@debbugs.gnu.org
Subject: bug#29905: No icons in Krita
Date: Wed, 3 Jan 2018 12:31:14 -0500 [thread overview]
Message-ID: <20180103173114.GA666@jasmine.lan> (raw)
In-Reply-To: <87k1wz9bpz.fsf@fastmail.com>
[-- Attachment #1: Type: text/plain, Size: 1275 bytes --]
On Wed, Jan 03, 2018 at 04:57:28PM +0100, Marius Bakke wrote:
> Leo Famulari <leo@famulari.name> writes:
>
> > On Mon, Jan 01, 2018 at 04:55:34PM +0100, Marius Bakke wrote:
> >> Marius Bakke <mbakke@fastmail.com> writes:
> >>
> >> > Ricardo Wurmus <rekado@elephly.net> writes:
> >> >> It may require wrapping as in commit
> >> >> 9cc51d16cb22f8a0c50fe81c98abb3b9108db9ff. Before this commit librecad
> >> >> would not be able to render its icons as it had no runtime support for
> >> >> plugins provided by qtsvg, which are accessed via QT_PLUGIN_PATH.
> >> >
> >> > It looks like propagating qtsvg would work too (which adds a search path
> >> > for QT_PLUGIN_PATH). Maybe we should do that on packages that installs
> >> > icons as SVG files?
> >>
> >> Leo: Does installing qtsvg into your profile fix the problem?
> >
> > Both options work. Which do you think is the better one?
>
> Thanks for confirming. That means this issue is actually a duplicate of
> <https://bugs.gnu.org/22138>.
>
> I think wrapping Krita is better "for now", although propagating qtsvg
> somewhere could be a more general workaround.
>
> We should fix that long-standing bug though...
Okay, I pushed the wrapper as 990e93fce16a83e1603b9ec28123ec3edc7ea787.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2018-01-03 17:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-30 1:37 bug#29905: No icons in Krita Leo Famulari
2017-12-31 17:39 ` Ricardo Wurmus
2018-01-01 15:41 ` Marius Bakke
2018-01-01 15:55 ` Marius Bakke
2018-01-03 2:12 ` Leo Famulari
2018-01-03 6:55 ` Ricardo Wurmus
2018-01-03 15:57 ` Marius Bakke
2018-01-03 17:31 ` Leo Famulari [this message]
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=20180103173114.GA666@jasmine.lan \
--to=leo@famulari.name \
--cc=29905-done@debbugs.gnu.org \
--cc=mbakke@fastmail.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).