From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Andreas Enge <andreas@enge.fr>
Cc: 63938-done@debbugs.gnu.org
Subject: bug#63938: Inkscape 1.2.1: No module named 'lxml'
Date: Sat, 09 Mar 2024 13:36:13 -0500 [thread overview]
Message-ID: <87frwzdzhe.fsf_-_@gmail.com> (raw)
In-Reply-To: <ZL5GeAfz5PkXp3Uw@jurong> (Andreas Enge's message of "Mon, 24 Jul 2023 11:38:00 +0200")
Hello,
Andreas Enge <andreas@enge.fr> writes:
> I get a text box with a similar, but not the same error:
>
> Traceback (most recent call last):
> File "/gnu/store/zjc4ijkrrp1b9v1va40a3fki0gkgcp6w-inkscape-1.2.1/share/inkscape/extensions/inkex/gui/__init__.py", line 38, in <module>
> import gi
> ModuleNotFoundError: No module named 'gi'
> During handling of the above exception, another exception occurred:
> Traceback (most recent call last):
> File "/gnu/store/zjc4ijkrrp1b9v1va40a3fki0gkgcp6w-inkscape-1.2.1/share/inkscape/extensions/inkman/inkman/manage_extensions.py", line 29, in <module>
> from inkex import gui
> File "/gnu/store/zjc4ijkrrp1b9v1va40a3fki0gkgcp6w-inkscape-1.2.1/share/inkscape/extensions/inkex/gui/__init__.py", line 42, in <module>
> raise DependencyError(
> inkex.utils.DependencyError: You are missing the required libraries for Gtk. Please report this problem to the Inkscape developers.
>
> Maybe we are missing propagated inputs or wrapping with some environment
> variable?
Yes, we needed GI_TYPELIB_PATH, as wrapped in commit
f4078087a69e4f57059fc6120332b47caef3aeaf ("gnu: inkscape: Fix Python
support.") on core-updates, as well as some other Python inputs.
Closing.
--
Thanks,
Maxim
prev parent reply other threads:[~2024-03-09 18:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-06 19:26 bug#63938: Inkscape 1.2.1: No module named 'lxml' Andrea PIERRÉ via Bug reports for GNU Guix
2023-07-24 9:38 ` bug#63938: Missing propagated (?) inputs Andreas Enge
2024-03-09 18:36 ` Maxim Cournoyer [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=87frwzdzhe.fsf_-_@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=63938-done@debbugs.gnu.org \
--cc=andreas@enge.fr \
/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).