Inkscape

Bug #1709729
Comment #2

Comment 2 for bug 1709729

Revision history for this message

Matthew Marcus (mamarcus) wrote on 2017-08-10: Re: [Bug 1709729] Re: On W7 machine dies immediately with internal error before displaying anything at all. True in 32+64-bit

Dear Eduard. Regarding yours of Wed, 09 Aug 2017 23:16:32 -0000:

Yes, the newest version posted.

I tried the command line you suggested and it returned immediately without any output. 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. I looked at the bug reports and others reported similar problems but I couldn't find a solution posted.
What reports the errors is inkscape.exe, not inkscape.com.

Inkscape was not installed into C:\WINDOWS or C:\WINDOWS\system32. It installed into C:\Program Files (x86)\Inkscape.

I used the .exe version. SHould I have used the MSI?

Something that may be relevant: the folder is read-only. I have Admin privilege and even so, when I uncheck Read-Only, hit Apply,
confirm Admin permission, then right-click again to get Properties, it comes right back as Read-Only. This is common behavior for folders
in Program Files. I suspect that there are different levels of Administrator.

Sincerely,
Matthew Marcus
> JFTR: I guess we're talking about 0.92.2?
>
> As a start: Could you try to
> - launch cmd.exe
> - navigate to the Inkscape directory
> - execute "inkscape.com -V"
> (it should print the version number but might also crash already)
> (does it print anything else to the console?)
> - if that worked excecute "inkscape.com"
> (does it print anything to the console?)
>
> If that does not change anything you could try the following (on the same console):
> - execute "set PATH=C:\WINDOWS\system32;C:\WINDOWS"
> - then again execute "inkscape.com"
> (and see if it solves the issue)
>
> With respect to Python 3: I have it on my own machine and it does not cause an issue.
> You could execute "set" on a cmd.exe though (it will print all environment variables so we can check if there's anything suspicious)
>
> ** Changed in: inkscape
> Importance: Undecided => High
>
> ** Tags added: cr win32 win64
>
> ** Tags removed: cr
> ** Tags added: crash
>

Dear Eduard.  Regarding yours of Wed, 09 Aug 2017 23:16:32 -0000:

Yes, the newest version posted.

I tried the command line you suggested and it returned immediately without any output.  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.  I looked at the bug reports and others reported similar problems but I couldn't find a solution posted.
What reports the errors is inkscape.exe, not inkscape.com.

Inkscape was not installed into C:\WINDOWS or C:\WINDOWS\system32.  It installed into C:\Program Files (x86)\Inkscape.

I used the .exe version. SHould I have used the MSI?

Something that may be relevant: the folder is read-only.  I have Admin privilege and even so, when I uncheck Read-Only, hit  Apply,
confirm Admin permission, then right-click again to get Properties, it comes right back as Read-Only.  This is common behavior for folders
in Program Files.  I suspect that there are different levels of Administrator.

Sincerely,
    Matthew Marcus
> JFTR: I guess we're talking about 0.92.2?
> 
> As a start: Could you try to
> - launch cmd.exe
> - navigate to the Inkscape directory
> - execute "inkscape.com -V"
>    (it should print the version number but might also crash already)
>    (does it print anything else to the console?)
> - if that worked excecute "inkscape.com"
>    (does it print anything to the console?)
> 
> If that does not change anything you could try the following (on the same console):
> - execute "set PATH=C:\WINDOWS\system32;C:\WINDOWS"
> - then again execute "inkscape.com"
>    (and see if it solves the issue)
> 
> With respect to Python 3: I have it on my own machine and it does not cause an issue.
> You could execute "set" on a cmd.exe though (it will print all environment variables so we can check if there's anything suspicious)
> 
> ** Changed in: inkscape
>     Importance: Undecided => High
> 
> ** Tags added: cr win32 win64
> 
> ** Tags removed: cr
> ** Tags added: crash
>