From: Josselin Poiret via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Liliana Marie Prikler <liliana.prikler@gmail.com>,
Christian Miller <miller.christian@proton.me>,
56288@debbugs.gnu.org
Subject: bug#56288: Pitivi can't be started
Date: Thu, 30 Jun 2022 14:08:33 +0200 [thread overview]
Message-ID: <87tu82s69q.fsf@jpoiret.xyz> (raw)
In-Reply-To: <7195f1643eceb61d2a2b39a359b5e9c7259d40a1.camel@gmail.com>
Hello Lily and Christian,
This is unfortunately the usual gdk-pixbuf SVG loader not being found,
since it is part of librsvg. Some details are described in [1] already,
but to summarize: we need to propagate gdk-pixbuf so that the
search-path GDK_PIXBUF_MODULE_FILE is properly set for the profile.
Hence, I can reproduce the issue with
--8<---------------cut here---------------start------------->8---
guix shell --pure pitivi -- pitivi
--8<---------------cut here---------------end--------------->8---
but the following launches pitivi properly (didn't check further)
--8<---------------cut here---------------start------------->8---
guix shell --pure pitivi gdk-pixbuf hicolor-icon-theme adwaita-icon-theme -- pitivi
--8<---------------cut here---------------end--------------->8---
I think it's very impractical that we have to do this for all packages
that wish to load SVG files via gdk-pixbuf, because it's technical and
not a concern that upstream developers document, since they don't
encounter such behavior.
[1] https://debbugs.gnu.org/cgi/bugreport.cgi?bug=52044#41
(87zgozy59x.fsf@jpoiret.xyz)
HTH,
--
Josselin Poiret
next prev parent reply other threads:[~2022-06-30 12:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-28 17:52 bug#56288: Pitivi can't be started Christian Miller via Bug reports for GNU Guix
2022-06-29 4:28 ` Liliana Marie Prikler
2022-06-30 12:08 ` Josselin Poiret via Bug reports for GNU Guix [this message]
2022-06-30 15:27 ` Liliana Marie Prikler
2022-07-07 16:21 ` Maxim Cournoyer
2022-07-02 22:38 ` Christian Miller 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=87tu82s69q.fsf@jpoiret.xyz \
--to=bug-guix@gnu.org \
--cc=56288@debbugs.gnu.org \
--cc=dev@jpoiret.xyz \
--cc=liliana.prikler@gmail.com \
--cc=miller.christian@proton.me \
/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).