all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Paul A. Patience" <paul@apatience.com>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: 57679@debbugs.gnu.org, "Ludovic Courtès" <ludo@gnu.org>
Subject: [bug#57679] [RFC PATCH] gnu: Add paraview.
Date: Wed, 28 Sep 2022 15:02:17 +0000	[thread overview]
Message-ID: <87k05n8rwf.fsf@apatience.com> (raw)
In-Reply-To: <87czbj6jmb.fsf@gmail.com>


Hi,

On 2022-09-25 20:54:04-04:00, Maxim Cournoyer wrote:
> Depends.  If it's because SVG icons are used, the SVG pixbuf backend
> will need to be available (librsvg present in a profile) (so that it is
> registered in the file point by the GDK_PIXBUF_MODULE_FILE environment
> variable).  If it uses standard icons that aren't include in the app, an
> icon theme will need to provide them (be installed by the user).

ParaView uses PNG icons (according to strace).
I installed the Adwaita icon theme and used qt5ct [1] to tell ParaView
to use it, and ran ParaView under strace.
Strace indicates that ParaView finds the icons, but they still don't
appear in the application.

I'm wondering if something is hardcoded in the source.
I'll investigate more at a later date.

Thanks for the help,
Paul

[1]: https://wiki.archlinux.org/title/qt#Configuration_of_Qt_5_applications_under_environments_other_than_KDE_Plasma





  reply	other threads:[~2022-09-28 16:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-08 15:24 [bug#57679] [RFC PATCH] gnu: Add paraview Paul A. Patience
2022-09-24 13:33 ` Ludovic Courtès
2022-09-26  0:54   ` Maxim Cournoyer
2022-09-28 15:02     ` Paul A. Patience [this message]
2022-11-02 16:50 ` Ricardo Wurmus
2022-11-03 15:04   ` Ludovic Courtès
2022-12-28 15:37 ` bug#57679: " Ricardo Wurmus

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87k05n8rwf.fsf@apatience.com \
    --to=paul@apatience.com \
    --cc=57679@debbugs.gnu.org \
    --cc=ludo@gnu.org \
    --cc=maxim.cournoyer@gmail.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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.