Inkscape

Bug #1709729
Comment #4

Comment 4 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:

On http://www.inkscapeforum.com/viewtopic.php?t=18421, I found, pages down, a solution where somebody with Chinese fonts had my problem and fixed it by finding fonts with
special characters in the name and deleting those files:
>>>>>>>>>>>>>>>>>>>
by pengi » Tue Feb 17, 2015 2:25 am

hulf2012 wrote:
Hello,
I tried to search using parts of your log message in google.

A check list, based in the information provided, and the solution given for the MAC OS problem:
- Your system have a virus
- There are incompatibilities when Inkscape uses another lenguage (chinese)
-- But related to that, do you have a friend or friends with the same problem?
- Also related with that, may be that you installed some specials typefaces or fonts, that weren't before in your system... There are reports that Inkscape doesn't understand special characters in font names or in font files
- You may have another version of the GTK libraries installed in your system... but how to solve?? I don't know
- Your Inkscape's installation file somehow is corrupted... see if there is an option to check the integiry of your file
- None of the above

I just found out the cause, and it is exactly one of the reasons you pointed out!
My Windows contained a font file with special characters on the file name. I removed the file, and now I can start Inkscape!
Thank you very much indeed!
>>>>>>>>>>>>>>>>>>>>

I just tried that and see no fonts with special characters in the names in C:\Windows\Fonts. Is there another folder I should look in?
The Symbol Tiger font has files with spaces in the names, and some files have underscores. Are those problematic?

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:

On http://www.inkscapeforum.com/viewtopic.php?t=18421, I found, pages down, a solution where somebody with Chinese fonts had my problem and fixed it by finding fonts with
special characters in the name and deleting those files:
 >>>>>>>>>>>>>>>>>>>
by pengi » Tue Feb 17, 2015 2:25 am

hulf2012 wrote:
Hello,
I tried to search using parts of your log message in google.

I just tried that and see no fonts with special characters in the names in C:\Windows\Fonts.  Is there another folder I should look in?
The Symbol Tiger font has files with spaces in the names, and some files have underscores.  Are those problematic?

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
>