This is almost certainly a side-effect of using the snap, and not an Inkscape bug at all. Snaps are, by design, constrained in what system resources they can access, including restricting them to certain parts of the filesystem. See these couple of links for some more details:
If you're on Ubuntu or another Debian based Linux system then you may find it better to install from the PPA instead of using the snap - although this won't practically allow you to have both 0.92 and 1.0 installed at once.
+1 for using the PPA on Ubuntu. I had installed the v1.0 appimage (on Mint) and I couldn't find where anything (Inkscape system) was stored. I'm new to Linux tho.
Thank you for advice. I reinstalled InkScape v1. Now it can open svg-files from "/var/www/html"-folder.
But.
Now I have this famous InkScape-lxml problem.
When I try to use text-splitting script from Extentions - I get this error:
//-------------------------------------------------------------------------------------------------------- Traceback (most recent call last): File "text_split.py", line 21, in <module> import inkex File "/usr/share/inkscape/extensions/inkex/__init__.py", line 11, in <module> from .extensions import * File "/usr/share/inkscape/extensions/inkex/extensions.py", line 33, in <module> from .elements import load_svg, BaseElement, ShapeElement, Group, Layer, Grid, \ File "/usr/share/inkscape/extensions/inkex/elements/__init__.py", line 8, in <module> from ._base import SVG_PARSER, load_svg, ShapeElement, BaseElement File "/usr/share/inkscape/extensions/inkex/elements/_base.py", line 31, in <module> from lxml import etree ModuleNotFoundError: No module named 'lxml' //--------------------------------------------------------------------------------------------------------
I understand - since InkScape is free, so the InkScape-programmers are free to bash users with "surprises" like that.
Like TD I also still use 0.92 for daily operations. I have the 1.0 snap installed for testing, but the snap also has issues that make it unsuitable for taking screenshots for my articles (missing icons, which I have reported), so I also have 1.0 from the PPA in a virtual machine.
I'm in two minds about issues with extensions. On the one hand, they're extensions. They're not part of the core Inkscape code, so perhaps shouldn't be held to the same standards. On the other hand the distinction is somewhat lost when you ship them as part of the product by default.
Having said that, the Split Text extension works for me both with the snap version of 1.0 and with the PPA, both on Ubuntu Mate. Perhaps some more information about your OS might help to either diagnose the problem, or at least give some useful details if you file a bug.
Okay, ladies and gentlemen. You know what I did? I've googled my inkscape-lxml-problem and it helped me.
https://forum.manjaro.org/t/inkscape-extentions-and-python-lxml-solution/119966/2 There some conversation about python2 and python3 and this legendary lxml-library in different versions and so on... So, I typed sudo apt-get install python3-lxml and now my lovely InkBloodyScape1 can split text and I will be happy for a while.
InkScape 0.9 worked fine with folders like /var/www/html
InkScape 1 (installed through "snap") is so shy that can't open SVG files from /var/www/html
Please, help me and write - how to create_edt_open files in /var/www/html folder.
Ups - I forgot to put some information.
When I type in Terminal something like:
ima@ima-HP:~$ inkscape /var/www/html/boo1.svg
** (org.inkscape.Inkscape:12707): WARNING **: 09:20:38.127: Can't open file: /var/www/html/boo1.svg (doesn't exist)
** (org.inkscape.Inkscape:12707): WARNING **: 09:20:38.127: Can't open file: /var/www/html/boo1.svg (doesn't exist)
ink_file_open: '/var/www/html/boo1.svg' cannot be opened!
InkscapeApplication::document_open: Failed to open: /var/www/html/boo1.svg
ConcreteInkscapeApplication::on_open: failed to create document!
ima@ima-HP:~$
but the command:
ima@ima-HP:~$ cat /var/www/html/boo1.svg
works fine
This is almost certainly a side-effect of using the snap, and not an Inkscape bug at all. Snaps are, by design, constrained in what system resources they can access, including restricting them to certain parts of the filesystem. See these couple of links for some more details:
https://snapcraft.io/docs/snap-confinement
https://askubuntu.com/questions/1033344/how-to-give-snaps-access-to-somedir
If you're on Ubuntu or another Debian based Linux system then you may find it better to install from the PPA instead of using the snap - although this won't practically allow you to have both 0.92 and 1.0 installed at once.
+1 for using the PPA on Ubuntu. I had installed the v1.0 appimage (on Mint) and I couldn't find where anything (Inkscape system) was stored. I'm new to Linux tho.
Thank you for advice. I reinstalled InkScape v1. Now it can open svg-files from "/var/www/html"-folder.
But.
Now I have this famous InkScape-lxml problem.
When I try to use text-splitting script from Extentions - I get this error:
//--------------------------------------------------------------------------------------------------------
Traceback (most recent call last):
File "text_split.py", line 21, in <module>
import inkex
File "/usr/share/inkscape/extensions/inkex/__init__.py", line 11, in <module>
from .extensions import *
File "/usr/share/inkscape/extensions/inkex/extensions.py", line 33, in <module>
from .elements import load_svg, BaseElement, ShapeElement, Group, Layer, Grid, \
File "/usr/share/inkscape/extensions/inkex/elements/__init__.py", line 8, in <module>
from ._base import SVG_PARSER, load_svg, ShapeElement, BaseElement
File "/usr/share/inkscape/extensions/inkex/elements/_base.py", line 31, in <module>
from lxml import etree
ModuleNotFoundError: No module named 'lxml'
//--------------------------------------------------------------------------------------------------------
I understand - since InkScape is free, so the InkScape-programmers are free to bash users with "surprises" like that.
The developers want the best it can be, but big changes bring risks.
I still use .92.xx for daily operations. I have v1.0 on three machines for testing.
Like TD I also still use 0.92 for daily operations. I have the 1.0 snap installed for testing, but the snap also has issues that make it unsuitable for taking screenshots for my articles (missing icons, which I have reported), so I also have 1.0 from the PPA in a virtual machine.
I'm in two minds about issues with extensions. On the one hand, they're extensions. They're not part of the core Inkscape code, so perhaps shouldn't be held to the same standards. On the other hand the distinction is somewhat lost when you ship them as part of the product by default.
Having said that, the Split Text extension works for me both with the snap version of 1.0 and with the PPA, both on Ubuntu Mate. Perhaps some more information about your OS might help to either diagnose the problem, or at least give some useful details if you file a bug.
Hi.
$ cat /etc/*-release
DISTRIB_ID=LinuxMint
DISTRIB_RELEASE=19.1
DISTRIB_CODENAME=tessa
DISTRIB_DESCRIPTION="Linux Mint 19.1 Tessa"
NAME="Linux Mint"
VERSION="19.1 (Tessa)"
ID=linuxmint
ID_LIKE=ubuntu
PRETTY_NAME="Linux Mint 19.1"
VERSION_ID="19.1"
HOME_URL="https://www.linuxmint.com/"
SUPPORT_URL="https://forums.ubuntu.com/"
BUG_REPORT_URL="http://linuxmint-troubleshooting-guide.readthedocs.io/en/latest/"
PRIVACY_POLICY_URL="https://www.linuxmint.com/"
VERSION_CODENAME=tessa
UBUNTU_CODENAME=bionic
I will try to reinstall my LinuxMint and reinstall InkScape1. Anyway, thank you people.
Okay, ladies and gentlemen.
You know what I did?
I've googled my inkscape-lxml-problem and it helped me.
https://forum.manjaro.org/t/inkscape-extentions-and-python-lxml-solution/119966/2
There some conversation about python2 and python3 and this legendary lxml-library in different versions and so on...
So, I typed
sudo apt-get install python3-lxml
and now my lovely InkBloodyScape1 can split text and I will be happy for a while.