> Il 11 maggio 2018 alle 17.37 Marco Atzeri <marco.atz...@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
cygcheck.out
Description: chemical/gulp
-- 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
