unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Marius Bakke <mbakke@fastmail.com>
To: Ricardo Wurmus <rekado@elephly.net>, Leo Famulari <leo@famulari.name>
Cc: 29905@debbugs.gnu.org
Subject: bug#29905: No icons in Krita
Date: Mon, 01 Jan 2018 16:55:34 +0100	[thread overview]
Message-ID: <87shbpa809.fsf@fastmail.com> (raw)
In-Reply-To: <87y3lha8mz.fsf@fastmail.com>

[-- Attachment #1: Type: text/plain, Size: 850 bytes --]

Marius Bakke <mbakke@fastmail.com> writes:

> Ricardo Wurmus <rekado@elephly.net> writes:
>
>> Leo Famulari <leo@famulari.name> writes:
>>
>>> I installed Krita, hicolor-icon-theme, adwaita-icon-theme, and
>>> oxygens-icons into my profile on a Debian system.
>>>
>>> Krita starts, and it can open files, but there are no icons in the Krita
>>> toolbox.
>>
>> 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?

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

  reply	other threads:[~2018-01-01 15:56 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 [this message]
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

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=87shbpa809.fsf@fastmail.com \
    --to=mbakke@fastmail.com \
    --cc=29905@debbugs.gnu.org \
    --cc=leo@famulari.name \
    --cc=rekado@elephly.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).