Subject: Re: bug#63938: Inkscape 1.2.1: No module named 'lxml'
From: Maxim Cournoyer <[email-masked]>
To: Andreas Enge <[email-masked]>
Cc: [email-masked]
Date: Sat, 09 Mar 2024 13:36:13 -0500
List-Id: <debbugs-submit.debbugs.gnu.org>

Hello,

Andreas Enge <[email-masked]> 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