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):
inkscape-0.48.1-1.fc14.1.x86_64
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.
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.