all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Andrea PIERRÉ via Bug reports for GNU Guix" <bug-guix@gnu.org>
To: 63938@debbugs.gnu.org
Subject: bug#63938: Inkscape 1.2.1: No module named 'lxml'
Date: Tue, 6 Jun 2023 15:26:34 -0400	[thread overview]
Message-ID: <7da01706-97b0-64ae-26fa-80ddcea67b29@zaclys.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 1085 bytes --]

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 #2: Type: text/html, Size: 4252 bytes --]

             reply	other threads:[~2023-06-07 23:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-06 19:26 Andrea PIERRÉ via Bug reports for GNU Guix [this message]
2023-07-24  9:38 ` bug#63938: Missing propagated (?) inputs Andreas Enge
2024-03-09 18:36   ` bug#63938: Inkscape 1.2.1: No module named 'lxml' Maxim Cournoyer

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=7da01706-97b0-64ae-26fa-80ddcea67b29@zaclys.net \
    --to=bug-guix@gnu.org \
    --cc=63938@debbugs.gnu.org \
    --cc=a.pierre@zaclys.net \
    /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.