GNOME Bugzilla – Bug 789635
gtk-demo.exe crashes for unknown reason
Last modified: 2018-05-02 19:23:53 UTC
Created attachment 362500 [details] gtk-demo.exe output Apologies, I was unsure of where to submit this bug in this bug tracking system. I am having trouble running Inkscape and after reporting the issue to them, they determined I was actually having an issue with GTK. Here is the Inkscape bug report: https://bugs.launchpad.net/inkscape/+bug/1719482 Briefly, when I launch Inkscape, nothing happens, and then the process quits. I was directed to try gtk-demo.exe from http://repo.msys2.org/mingw/x86_64/mingw-w64-x86_64-gtk2-2.24.31-4-any.pkg.tar.xz Which seems to fail, suggesting the problem originates with GTK (see attached). The person at Inkscape was unable to determine what the issue was from this output, and suggested I direct the question to you to see if it is possible to identify the problem. I am on a Windows 10 system with a NVIDIA Quadro K600 using the "385.69-quadro" drivers. Any help would be much appreciated.
GTK2 is dead (as GTK3 has been out for years) so I don't expect someone to investigate...
The trace is of little to no use without any debug symbols in it. I'm also confused by how you said you ran gtk-demo from MSYS2, yet the trace refers to DLLs in the Inkscape app directory. Do Inkscape use the same compiler? If not, crashing is to be expected. There could be conflicts in your PATH causing one or both of the observed issues. Without debug symbols and preferably the most reduced environment (PATH, etc.) possible, I think it's hard to make any guesses.
> The trace is of little to no use without any debug symbols in it. What do I need to do to get the debug symbols for you? > Do Inkscape use the same compiler? I'm just an end user (of Inkscape), I don't think I can answer this type of question, I just followed the instructions from the Inkscape bug report.
(In reply to André Klapper from comment #1) > GTK2 is dead (as GTK3 has been out for years) so I don't expect someone to > investigate... Just to correct the record here: gtk2 is in deep maintenance mode, but not 'dead'
Some answers (I'm the "downstream person" from Inkscape): > The trace is of little to no use without any debug symbols in it. Unfortunately MSYS2 does not offer packages with debug symbols as far as I'm aware so they need to be built manually. If Tristan is interested I could assist, but obviously this is not a typical "end user" task. > I'm also confused by how you said you ran gtk-demo from MSYS2, yet the trace > refers to DLLs in the Inkscape app directory. Do Inkscape use the same > compiler? Inkscape 0.92.2 was in fact compiled using MSYS2's mingw-w64 toolchain. I initially gave Tristan instructions on how to debug with the existing Inkscape distribution (which packages gtk2 and all dependencies), so I assume the backtrace comes from those tests. However Tristan confirmed the same crash occurs with a "clean" MSYS2 distribution (so a packaging issue - at least on Inkscape's part - should be ruled out)
great info, thanks - I'll try to have a look and see if I can get any further (can't promise much though)
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gtk/issues/963.