From: Fabio Rossi <rossi.f@inwind.it>
To: cygwin@cygwin.com, Marco Atzeri <marco.atzeri@gmail.com>
Subject: Re: segfault in xwin-xdg-menu.exe
Date: Fri, 11 May 2018 16:26:00 -0000 [thread overview]
Message-ID: <2104721437.537760.1526054064612@mail.libero.it> (raw)
In-Reply-To: <2482367f-abbd-8aad-3cb7-55ef955244bd@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1345 bytes --]
> Il 11 maggio 2018 alle 17.37 Marco Atzeri <marco.atzeri@gmail.com> ha scritto:
>
> On 5/11/2018 5:29 PM, Fabio Rossi wrote:
>
> > I have just made a fresh cygwin installation on windows 10 pro 32bit using setup 2.891. I have selected xorg-server, xinit, vim and gdb packages. I have modified the Xwin server configuration as described in https://x.cygwin.com/docs/faq/cygwin-x-faq.html#q-startxwinrc-exit and later I have successfully started it by using the action "cygwin-x\xwin server" under Windows programs menu. The X server is running with display :0.0 and its icon is visible in the tray bar.
> >
> > On another system installed months ago I have the xdg menu application already running (it's automatically started by the xwin startup script) but I didn't need to follow the above mentioned trick described in the FAQ.
> >
> > In a cygwin terminal I then try starting manually xwin-xdg-menu by using:
> >
> > $ DISPLAY=:0 xwin-xdg-menu.exe
> >
> > but I get a segmentation fault. With gdb I get the following backtrace:
> >
> > $ DISPLAY=:0 gdb xwin-xdg-menu.exe
> >
> > ...
> >
> > It seems a problem with fontconfig. Any hint?
> >
> > --
>
> as suggested here
>
> > Problem reports: http://cygwin.com/problems.html
>
> provide the cygcheck.out as attachment
I missed that, sorry, here is the file attached as requested
[-- Attachment #2: cygcheck.out --]
[-- Type: chemical/x-gulp, Size: 31771 bytes --]
[-- Attachment #3: Type: text/plain, Size: 219 bytes --]
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2018-05-11 15:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-11 15:38 Fabio Rossi
2018-05-11 15:54 ` Marco Atzeri
2018-05-11 16:26 ` Fabio Rossi [this message]
2018-05-11 16:46 ` Marco Atzeri
2018-05-11 17:25 ` Ken Brown
2018-05-11 20:28 ` Fabio Rossi
2018-05-12 14:43 ` Jon Turney
2018-05-14 12:35 ` Fabio Rossi
2018-05-14 21:50 ` Jon Turney
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=2104721437.537760.1526054064612@mail.libero.it \
--to=rossi.f@inwind.it \
--cc=cygwin@cygwin.com \
--cc=marco.atzeri@gmail.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).