Incorrect PATH scan results in extensions not found
Bug #801568 reported by
Patrick Monnerat
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Inkscape |
Fix Released
|
Medium
|
Patrick Monnerat | ||
inkscape (Fedora) |
Won't Fix
|
Undecided
|
Bug Description
When the PATH environment variable contains a null component (to force current
dir lookup), subsequent components are not used for extension lookup.
This results in missing existing programs, thus disabling some importation
extensions.
Version: inkscape-
tags: | added: extensions-plugins |
tags: | added: backport-proposed |
Changed in inkscape: | |
status: | Fix Committed → Fix Released |
Changed in inkscape (Fedora): | |
importance: | Unknown → Undecided |
status: | Unknown → Won't Fix |
To post a comment you must log in.
Description of problem:
When the PATH environment variable contains a null component (to force current dir lookup), subsequent components are not used for extension lookup.
This results in missing existing programs, thus disabling some importation extensions.
Version-Release number of selected component (if applicable): 0.48.1- 1.fc14. 1.x86_64
inkscape-
How reproducible:
Always
Steps to Reproduce:
1. prefix the PATH value with a colon (:) 'export PATH=":$PATH"'
2. run inkscape
3. Try to open a postscript (.ps) file ...
Actual results:
Cannot import a postscript file.
Expected results:
Proper importation and conversion of a postscript file, even in case of null component in the PATH.
Additional info:
The attached patch fixes the problem.
I did NOT report the bug and the path upstream.