Comment 5 for bug 1709729

Revision history for this message
Matthew Marcus (mamarcus) wrote : Re: [Bug 1709729] Re: On W7 machine dies immediately with internal error before displaying anything at all. True in 32+64-bit
  • inkscape.txt Edit (13.5 KiB, text/plain; charset=UTF-8; name="inkscape.txt")
  • paths.txt Edit (1.9 KiB, text/plain; charset=UTF-8; name="paths.txt")

Dear Eduard. Regarding yours of Thu, 10 Aug 2017 16:01:37 -0000:

Thanks for your prompt replies. Here is the result of typing 'inkscape' at the console. It does the same even after doing the set PATH command.

The results for the other permutations (after the set PATH):
inkscape Dies with voluminous error messages to the console (attached).
inkscape.com Same
inkscape.exe Dies with the 'internal error' dialog but no console output, after several seconds
inkscape.exe -V Dies with no output of any sort, in less than a second. Process ends, as seen with Task Manager.
inkscape.com -V Same

My installation is fresh, except that I had installed the 64-bit version, found the same startup problem, uninstalled it, and installed the 32-bit version, which is what I have now.
I have never had an installation of Inkscape before. The first I heard of it was on Tuesday, from a satisfied user (Ubuntu).

When I type 'path' after having done the set PATH, it still shows many directories (attached).

Sincerely,
    Matthew Marcus
>> I also tried just typing 'inkscape' at the command line (in the directory)
>> and it spat out a whole lot of Gtk-WARNINGs about missing actions and
>> died with internal error.
>
> Those are the messages we're interested in! Please copy the whole output
> (including the commands to produce it) into a .txt document and attach
> it here!
>
> Running "inkscape.exe" usually does not produce output on the console (that's what inkscape.com is for). Simply running "inkscape" will also call "inkscape.com" as cmd.exe loads the first executable it can find (sorting alphabetically).
> Either way, please attach the output from whatever program produces output for you.
>
>> I tried the command line you suggested
>
> I suggested three different invocations of inkscape - please be more
> specific!
>
>> Inkscape was not installed into C:\WINDOWS or C:\WINDOWS\system32.
>
> Absolutely (and you certainly should not) - the command I asked you to
> execute is intended to remove everything but those required directories
> from the search patch to rule out a path problem.
>
> Having Inkscape in (write protected) "C:\Program Files (x86)\Inkscape"
> or "C:\Program Files\Inkscape" is the default and should not cause any
> issues unless you installed into a "dirty" directory which contained
> files from a previous installation (which might cause issues; this can
> happen if you mix .msi and .exe installers without properly uninstalling
> first). For this reason please also try to install/run Inkscape from a
> fresh directory to make sure there are no interfering remnants from a
> previous installation.
>
>
> As I'm having a hard time following you (and you seem to have omitted some steps earlier), maybe it's best if you use the following template. Execute each command (without the quotes) and paste in the results:
>
> - "inkscape.com -V"
> - "inkscape.exe -V"
> - "inkscape.com"
> - "inkscape.exe"
> - "set PATH=C:\WINDOWS\system32;C:\WINDOWS"
> - "inkscape.com"
> - "inkscape.exe"
>
> (ideally do all that with a fresh installation - you could download the
> 7z archive and extract into an empty directory - just to be safe)
>