From: Mark Geisert <mark@maxrnd.com>
To: Cygwin <cygwin@cygwin.com>
Subject: Re: inkscape installed but does nothing.
Date: Thu, 23 Nov 2023 17:50:02 -0800 [thread overview]
Message-ID: <f76f2c41-d5a3-d563-c66e-be5edcb97ef2@maxrnd.com> (raw)
In-Reply-To: <351a8397-5a21-4abf-8cfd-f76ba6a7f072@gmail.com>
FWIW I can reproduce the issue. See below...
René Berber via Cygwin wrote:
> On 11/22/2023 10:27 PM, J.F. Huesman via Cygwin wrote:
>
>> (I tried to reply to this message twice and got mailer-daemon failure
>> notices both times. My apologies if this is a duplicate message.) Yes, they are
>> installed. which xwin xinit/usr/bin/xwin/usr/bin/xinit
>>
>> When I try to run inkscape, I don't get any errors and there were no
>> messages about missing programs or dependencies when I ran the
>> installer. I'm not trying to start a GUI. I have a script that I used
>> to batch convert svg images in a folder to png. When that script
>> wouldn't work (I've used it on other machines, including this one
>> years ago using 32-bit cygwin instead of 64-bit that I'm using now) I
>> started trying to invoke it from the command line, and that's when I
>> discovered it's not doing anything. If I start Cygwin64 WindowMaker
>> and type "inkscape" into the right-click run dialogue, I get a popup
>> window, ErrorCould not execute command: inkscape
>
> OK, then start from the basics:
>
> $ ldd $(which inkscape)
>
> Look at the output. Is any dll shown as missing?
>
> In the answer is no, then next check your anti-virus. Is it blocking the program?
> Is it injecting a dll?
>
> Another set of tests would be, is the program installed correctly? i.e. is it
> executable? Is not corrupt? A bit more difficult: is it loading libraries into
> valid space (non colliding, in available memory).
I installed inkscape and tried running the .exe. It returns to shell prompt but
its exit code is 127, indicating a problem starting the process up. ldd doesn't
show anything amiss; as an aside that's an unusually long list of DLLs.
I ran 'strace -o inkscape.out inkscape -V' and looked at the traced output.
It ends with:
--- Process 11940 (pid: 11940), exception c0000139 at 00007ffaecf324f6
--- Process 11940 (pid: 11940) thread 1172 exited with status 0xc0000139
--- Process 11940 (pid: 11940) thread 1888 exited with status 0xc0000139
--- Process 11940 (pid: 11940) thread 5544 exited with status 0xc0000139
--- Process 11940 (pid: 11940) exited with status 0xc0000139
I grep'd /usr/include/w32api/ntstatus.h for that status and got:
#define STATUS_ENTRYPOINT_NOT_FOUND ((NTSTATUS)0xC0000139)
I then tried running inkscape.exe from a Command Prompt window and got a popup:
"The procedure entry point g_cclosure_marshal_VOID__BOOLEAN could not be located
in the dynamic link library C:\cygwin64\bin\inkscape.exe."
Why this happens, I leave to somebody experienced with building inkscape itself.
HTH,
..mark
next prev parent reply other threads:[~2023-11-24 1:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2032069619.3870454.1700713626880.ref@mail.yahoo.com>
2023-11-23 4:27 ` J.F. Huesman
2023-11-23 17:04 ` René Berber
2023-11-24 1:50 ` Mark Geisert [this message]
[not found] <1219644356.4008002.1700795338917.ref@mail.yahoo.com>
2023-11-24 3:08 ` J.F. Huesman
2023-11-24 3:42 ` Backwoods BC
2023-11-24 5:10 ` Mark Geisert
2023-11-26 5:54 ` Mark Geisert
2023-12-01 6:11 ` Mark Geisert
[not found] <1567827764.3979915.1700782855144.ref@mail.yahoo.com>
2023-11-23 23:40 ` J.F. Huesman
[not found] <390805164.3627445.1700626992321.ref@mail.yahoo.com>
2023-11-22 4:23 ` J.F. Huesman
2023-11-22 4:33 ` René Berber
2023-11-22 6:45 ` Brian Inglis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f76f2c41-d5a3-d563-c66e-be5edcb97ef2@maxrnd.com \
--to=mark@maxrnd.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).