Non-fatal 'unsupported hash type'
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Inkscape |
Fix Released
|
Low
|
Patrick Storz |
Bug Description
Inkscape 0.92.2 on Windows 7 64-bit
Existing Python installs: both 2.7.10 and 3.4.3 in C:\Python27\ and C:\Python34\ --- but I don't think these are causing any interference.
Uninstalled Inkscape entirely (made sure "C:\Program Files\Inkscape\" does not exist)
Performed normal install ("Optimal" and confirmed that "Python 2.7" is checked) with inkscape-
After install, "C:\Program Files\Inkscape\
Confirmed with Process Explorer that a running instance of Inkscape has the PYTHONPATH environment variable set to "C:\Program Files\Inkscape\
That is, this environment variable is pointing to several folders that don't exist.
Open Inkscape
Draw some path, e.g. draw rectangle, Path->Object to Path
With path selected, access from menu Extensions-
Keep default settings Font size: 20px, Dot size: 10px, Starting dot number: 1, Step: 1
Click Apply, get below hash errors message
Click OK to dismiss error dialog
Number Nodes command **works just fine**
Some other things that require running python do the same thing (e.g. opening file types that require UniConvertor)
The requested action seems to be completed just fine, but what's up with these errors?
As an aside, why is the PYTHONPATH variable pointing to folders that don't exist? It seems like Inkscape's python install is at "C:\Program Files\Inkscape\
Contents of error dialog:
Inkscape has received additional data from the script executed. The script did not return an error, but this may indicate the results will not be as expected.
ERROR:root:code for hash md5 was not found.
Traceback (most recent call last):
File "C:\Program Files\Inkscape\
globals(
File "C:\Program Files\Inkscape\
raise ValueError(
ValueError: unsupported hash type md5
ERROR:root:code for hash sha1 was not found.
Traceback (most recent call last):
File "C:\Program Files\Inkscape\
globals(
File "C:\Program Files\Inkscape\
raise ValueError(
ValueError: unsupported hash type sha1
ERROR:root:code for hash sha224 was not found.
Traceback (most recent call last):
File "C:\Program Files\Inkscape\
globals(
File "C:\Program Files\Inkscape\
raise ValueError(
ValueError: unsupported hash type sha224
ERROR:root:code for hash sha256 was not found.
Traceback (most recent call last):
File "C:\Program Files\Inkscape\
globals(
File "C:\Program Files\Inkscape\
raise ValueError(
ValueError: unsupported hash type sha256
ERROR:root:code for hash sha384 was not found.
Traceback (most recent call last):
File "C:\Program Files\Inkscape\
globals(
File "C:\Program Files\Inkscape\
raise ValueError(
ValueError: unsupported hash type sha384
ERROR:root:code for hash sha512 was not found.
Traceback (most recent call last):
File "C:\Program Files\Inkscape\
globals(
File "C:\Program Files\Inkscape\
raise ValueError(
ValueError: unsupported hash type sha512
Changed in inkscape: | |
status: | Fix Committed → Fix Released |
The errors above indicate an issue with Python not finding or finding the wrong modules. (Hash calculation is a binary component).
As you say you can use uniconvertor (which we do not bundle anymore) this hints towards a different Python being used instead of the bundled Python. There's a good chance the two versions are interfering.
I'd recommend to:
1. Check if you have PYTONPATH or PYTHONHOME environment variables set
and pointing toward some other Python installation on your system
2. Check which Python is spawned by Inkscape (e.g. with Process Explorer)
Regarding the strange value of PYTHONPATH after launching Inkscape: compatibility reasons (which does not hurt though as long as "C:\Program Files\Inkscape\ python" is empty).
This is a side-effect of our changed packaging in 0.92.2 which uses a different directory layout for Python. The environment variables are still set for the old packaging for backwards-