On 11/05/2018 18:24, Fabio Rossi wrote:
Il 11 maggio 2018 alle 19.12 Ken Brown <kbr...@cornell.edu> ha scritto:
On 5/11/2018 11:29 AM, 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:
[...]
It seems a problem with fontconfig. Any hint?
Could it be the same problem as this?
https://cygwin.com/ml/cygwin/2018-04/msg00325.html
Thanks for the reference, it seems the same problem. I have tried stracing the
problem, but I don't see a clear failure in the trace log. The size is quite
large, it's ~ 245 kB when bzipped, if someone is interested I can post it
somewhere later.
Yeah, this is the same problem, which is under investigation.
See also https://cygwin.com/ml/cygwin/2018-05/msg00152.html for another
workaround.
--
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