Inkscape 1.2.1: No module named 'lxml'

  • Done
  • quality assurance status badge
Details
3 participants
  • Andrea PIERRÉ
  • Andreas Enge
  • Maxim Cournoyer
Owner
unassigned
Submitted by
Andrea PIERRÉ
Severity
normal
A
A
Andrea PIERRÉ wrote on 6 Jun 2023 21:26
(address . bug-guix@gnu.org)
7da01706-97b0-64ae-26fa-80ddcea67b29@zaclys.net
Hello,

I get the following error with Inkscape 1.2.1 (9c6d41e410, 2022-07-14)
when I click on the top menu on |Extensions > Manage Extensions|:

|Traceback (most recent call last): File
"/gnu/store/3lbv31vxj3y0d2dn7h2y5dna7dfhhrb5-inkscape-1.2.1/share/inkscape/extensions/inkman/inkman/manage_extensions.py",
line 29, in <module> from inkex import gui File
"/gnu/store/3lbv31vxj3y0d2dn7h2y5dna7dfhhrb5-inkscape-1.2.1/share/inkscape/extensions/inkex/__init__.py",
line 11, in <module> from .extensions import * File
"/gnu/store/3lbv31vxj3y0d2dn7h2y5dna7dfhhrb5-inkscape-1.2.1/share/inkscape/extensions/inkex/extensions.py",
line 34, in <module> from .elements import ( File
"/gnu/store/3lbv31vxj3y0d2dn7h2y5dna7dfhhrb5-inkscape-1.2.1/share/inkscape/extensions/inkex/elements/__init__.py",
line 9, in <module> from ._parser import SVG_PARSER, load_svg File
"/gnu/store/3lbv31vxj3y0d2dn7h2y5dna7dfhhrb5-inkscape-1.2.1/share/inkscape/extensions/inkex/elements/_parser.py",
line 30, in <module> from lxml import etree ModuleNotFoundError: No
module named 'lxml' |

Thanks!

?
Attachment: file
A
A
Andreas Enge wrote on 24 Jul 2023 11:38
Missing propagated (?) inputs
(address . 63938@debbugs.gnu.org)
ZL5GeAfz5PkXp3Uw@jurong
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?

Andreas
M
M
Maxim Cournoyer wrote on 9 Mar 19:36 +0100
Re: bug#63938: Inkscape 1.2.1: No module named 'lxml'
(name . Andreas Enge)(address . andreas@enge.fr)(address . 63938-done@debbugs.gnu.org)
87frwzdzhe.fsf_-_@gmail.com
Hello,

Andreas Enge <andreas@enge.fr> writes:

Toggle quote (17 lines)
> 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
Closed
?
Your comment

This issue is archived.

To comment on this conversation send an email to 63938@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 63938
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch