-
-
Notifications
You must be signed in to change notification settings - Fork 7
Description
System: Windows 10 x64
Inkscape Version: 1.1.1
I installed the latest version of inkscape-svgo and get this error ("File D:\drawing.svg" could not be saved."). I used Process Monitor to capture the command line arguments:
"[Path to custom Inkscape extensions directory]\inkscape-svgo.exe" --options=page_1 --precision=2 --pretty=false --enable=sortAttrs=false --multipass=true --enable=cleanupAttrs=true --enable=cleanupEnableBackground=true --enable=cleanupIDs=false --enable=cleanupNumericValues=true --enable=collapseGroups=true --enable=convertColors=true --enable=convertPathData=true --enable=convertShapeToPath=false --enable=convertStyleToAttrs=false --enable=convertTransform=true --enable=mergePaths=true --enable=minifyStyles=true --enable=moveElemsAttrsToGroup=false --enable=moveGroupAttrsToElems=false --enable=removeViewBox=false --enable=removeDimensions=false --enable=removeUnknownsAndDefaults=true --enable=removeUnusedNS=true --enable=removeUselessDefs=true --enable=removeUselessStrokeAndFill=true --enable=removeRasterImages=false --enable=removeScriptElement=false --enable=removeStyleElement=false --enable=removeTitle=true --enable=removeXMLNS=false --enable=removeXMLProcInst=true --enable=removeMetadata=true --enable=removeNonInheritableGroupAttrs=true --enable=removeComments=true --enable=removeDesc=true --enable=removeDoctype=true --enable=removeEditorsNSData=true --enable=removeEmptyAttrs=true --enable=removeEmptyContainers=true --enable=removeEmptyText=true --enable=removeHiddenElems=true D:\Users\[Username]\AppData\Local\Temp\ink_ext_XXXXXX.svgQRO0L1
When I try to run that command in a cmd window and with a real target file, it returns with no output or errors in the command line window. Target file unchanged.
Looking at the ProcMon capture of inkscape-svgo.exe, it calls Windows Error Reporting, so something definitely went wrong:
C:\Windows\system32\WerFault.exe -u -p 2412 -s 560
Unfortunately, inkscape-svgo.exe is a giant black box, so there is seemingly no way to get error data from it. Is there any way to create an unpackaged version for troubleshooting?