Inkspace not open on Windows 10 (without any error message)

Bug #1716715 reported by Huupoke
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Inkscape
Fix Released
Undecided
Unassigned

Bug Description

I have tried both the installer (exe) and archived (7z) on version 0.92.2 but they didn't open.
It closed shortly after lauch (about 2sec) without any error message (not even in Event Viewer).
And I downloaded the 7z version 0.92.1 and it still functioning normally.
And I am having python version 3.6.1 installed and its path is included in Environment Variable (I had Python before install Inkspace).

Revision history for this message
Patrick Storz (ede123) wrote :

Some steps which might help to debug the issue:
- open a console window (cmd.exe)
- navigate to you Inkscape directory
- execute the command "set" (without quotes)
  and attach the output here
- execute the command
  "set PATH=C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem"
- start Inkscape using the command "inkscape.com -V"
  does it print version information?
  post error output here (if any).
- start Inkscape using the command "inkscape.com"
  post error output here (if any)

Revision history for this message
Huupoke (huupoke12) wrote :

"inkscape.com -V" didn't print out anything (No version and no error output)
"inkscape.com" didn't print out anything and inkscape didn't start (No output)

Revision history for this message
Patrick Storz (ede123) wrote :

OK, thanks.

"set" output does not reveal any obvious issues.

Just to be sure: Did you try to run Inkscape in ConEmu? While it shouln't you never know if it might cause issues...

Next step would be to debug using gdb and hope there's useful output.
(A compatible versions can be downloaded from [1] and [2] for 64- and 32-bit Inkscape; I can help you set it up later if you want to)

[1] http://repo.msys2.org/mingw/x86_64/mingw-w64-x86_64-gdb-8.0-2-any.pkg.tar.xz
[2] http://repo.msys2.org/mingw/i686/mingw-w64-i686-gdb-8.0-2-any.pkg.tar.xz

Revision history for this message
Huupoke (huupoke12) wrote :

Sorry for the late reply.
I have tried with original CMD but it didn't work too.
But when I compiled it with MSYS2 as in (http://wiki.inkscape.org/wiki/index.php/Compiling_Inkscape_on_Windows_with_MSYS2), it works.
The version I compiled is: Inkscape 0.92+devel (d437851688, 2017-10-28)

Revision history for this message
Patrick Storz (ede123) wrote :

Interesting...

Inkscape 0.92.2 is compiled with MSYS2, too, so it should be very similar to the version you compiled (main difference is gtk2 vs gtk3).

You could test a recent build of 0.92.x branch, to see if the issue is fixed there, too (if you don't want to build yourself you can download a nightly build from AppVeyor [1], e.g. [2]

[1] https://ci.appveyor.com/project/inkscape/inkscape/history
[2] https://ci.appveyor.com/project/inkscape/inkscape/build/0.92.x-617

Revision history for this message
Huupoke (huupoke12) wrote :
Revision history for this message
Patrick Storz (ede123) wrote :

OK, great!

I'm not sure what fixed it for you, the only "crash on startup" issue that was fixed since 0.92.x I'm aware of is bug #1716516 (maybe you hit that one? - should be apparent if there is a warning printed to command line now)

Other than that it could obviously been a bug in one of the many third-party libraries...

Changed in inkscape:
status: New → Fix Committed
milestone: none → 0.92.3
Bryce Harrington (bryce)
Changed in inkscape:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.