Re: problems with octave 8.2.0-1 and plotting

[Fabio Rossi via Cygwin]

Hello Brian,
thanks for your suggestions, eventually I solved the problem with Achim's hint 
of using opengl software rendering because the graphics card is not supporting 
all opengl requirements.

I have followed this guide:

https://x.cygwin.com/docs/ug/using-glx.html


Fabio


> Il 27/04/2023 18:30 Brian Inglis  ha scritto:
> 
>  
> Hi Fabio,
> 
> Are you running from a bash shell under a terminal started from the XWin 
> Server 
> shortcut or X Applications Menu?
> 
> Those variables are defined in my shell:
> 
>   $ echo $XDG_CURRENT_DESKTOP $XDG_MENU_PREFIX $XDG_RUNTIME_DIR
>   X-Cygwin xwin- /run/user/##/
> 
> -- 
> Take care. Thanks, Brian Inglis  Calgary, Alberta, Canada
> 
> La perfection est atteinte   Perfection is achieved
> non pas lorsqu'il n'y a plus rien à ajouter  not when there is no more to add
> mais lorsqu'il n'y a plus rien à retirer but when there is no more to cut
>      -- Antoine de Saint-Exupéry
> 
> 
> On 2023-04-27 10:15, Fabio Rossi wrote:
> > Hello Brians,
> > thanks for the suggestions. I had already installed the xorg server and all 
> > the packages you mentioned. But nevertheless I get the errors reported in 
> > the original email, both if I start octave from the shell or by using the 
> > XDG menu which starts octave with the GUI.
> > 
> > In particular, in the second case I confirm all the opengl messages already 
> > reported and I get the following results in the octave command line:
> > 
> >>> getenv('XDG_CURRENT_DESKTOP')
> > ans = X-Cygwin
> >>> getenv('XDG_MENU_PREFIX')
> > ans = xwin-
> >>> getenv('XDG_RUNTIME_DIR')
> > ans =
> > 
> >>From the shell all of the previous variables are of course empty. With the 
> >>past versions of octave it was plotting when run from the bash.
> > 
> > Thanks,
> > Fabio
> > 
> >> Il 27/04/2023 17:48 Brian Inglis  ha scritto:
> >>
> >>   
> >> Hi Fabio,
> >>
> >> Some packages include non-GUI or native GUI interfaces that do not require
> >> window system support.
> >>
> >> Others may dynamically support window systems if they are installed, or 
> >> have
> >> separate executables for console or GUI, as octave does: octave and 
> >> octave-cli.
> >>
> >> If you are using octave GUI, as it is linked against X window libraries, 
> >> you
> >> need to install the X window system.
> >>
> >> If you install xinit, that will install the X Window server xorg-server, 
> >> XDG
> >> components xdg-user-dirs, xwin-xdg-menu, X Window clients.
> >>
> >> If you then run it via the XWin Server Start Menu shortcut, it will define
> >> $XDG_CURRENT_DESKTOP, $XDG_MENU_PREFIX, and $XDG_RUNTIME_DIR.
> >>
> >> That should allow you to run octave GUI and display plot windows.
> >>
> >> -- 
> >> Take care. Thanks, Brian Inglis  Calgary, Alberta, Canada
> >>
> >> La perfection est atteinte   Perfection is achieved
> >> non pas lorsqu'il n'y a plus rien à ajouter  not when there is no more to 
> >> add
> >> mais lorsqu'il n'y a plus rien à retirer but when there is no more to 
> >> cut
> >>   -- Antoine de Saint-Exupéry
> >>
> >>
> >> On 2023-04-27 07:58, Fabio Rossi via Cygwin wrote:
> >>> I forgot to mention that the test machine is running Windows 10 Pro 64 
> >>> bit with a ATI FirePro 3800 graphics card. On the same machine, octave 
> >>> built for Windows executes correctly the same command. I have observed 
> >>> the same behaviour also on other Windows machines running Win7 or other 
> >>> graphic adapters.
> >>>
> >>> Fabio
> >>>> Il 26/04/2023 15:34 Fabio Rossi  ha scritto:
> >>>>
> >>>>
> >>>> I have installed latest test version of octave 8.2.0-1. When I try to 
> >>>> plot using a simple command like "plot(1,1)" I get the following errors 
> >>>> from the command line
> >>>>
> >>>> $ octave
> >>>> QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to 
> >>>> '/tmp/runtime-+user'
> >>>> GNU Octave, version 8.2.0
> >>>> Copyright (C) 1993-2023 The Octave Project De

Re: problems with octave 8.2.0-1 and plotting

[Fabio Rossi via Cygwin]

Hello Brians,
thanks for the suggestions. I had already installed the xorg server and all the 
packages you mentioned. But nevertheless I get the errors reported in the 
original email, both if I start octave from the shell or by using the XDG menu 
which starts octave with the GUI.

In particular, in the second case I confirm all the opengl messages already 
reported and I get the following results in the octave command line:

>> getenv('XDG_CURRENT_DESKTOP')
ans = X-Cygwin
>> getenv('XDG_MENU_PREFIX')
ans = xwin-
>> getenv('XDG_RUNTIME_DIR')
ans =

From the shell all of the previous variables are of course empty. With the past 
versions of octave it was plotting when run from the bash.

Thanks,
Fabio

> Il 27/04/2023 17:48 Brian Inglis  ha scritto:
> 
>  
> Hi Fabio,
> 
> Some packages include non-GUI or native GUI interfaces that do not require 
> window system support.
> 
> Others may dynamically support window systems if they are installed, or have 
> separate executables for console or GUI, as octave does: octave and 
> octave-cli.
> 
> If you are using octave GUI, as it is linked against X window libraries, you 
> need to install the X window system.
> 
> If you install xinit, that will install the X Window server xorg-server, XDG 
> components xdg-user-dirs, xwin-xdg-menu, X Window clients.
> 
> If you then run it via the XWin Server Start Menu shortcut, it will define 
> $XDG_CURRENT_DESKTOP, $XDG_MENU_PREFIX, and $XDG_RUNTIME_DIR.
> 
> That should allow you to run octave GUI and display plot windows.
> 
> -- 
> Take care. Thanks, Brian Inglis  Calgary, Alberta, Canada
> 
> La perfection est atteinte   Perfection is achieved
> non pas lorsqu'il n'y a plus rien à ajouter  not when there is no more to add
> mais lorsqu'il n'y a plus rien à retirer but when there is no more to cut
>  -- Antoine de Saint-Exupéry
> 
> 
> On 2023-04-27 07:58, Fabio Rossi via Cygwin wrote:
> > I forgot to mention that the test machine is running Windows 10 Pro 64 bit 
> > with a ATI FirePro 3800 graphics card. On the same machine, octave built 
> > for Windows executes correctly the same command. I have observed the same 
> > behaviour also on other Windows machines running Win7 or other graphic 
> > adapters.
> > 
> > Fabio
> >> Il 26/04/2023 15:34 Fabio Rossi  ha scritto:
> >>
> >>   
> >> I have installed latest test version of octave 8.2.0-1. When I try to plot 
> >> using a simple command like "plot(1,1)" I get the following errors from 
> >> the command line
> >>
> >> $ octave
> >> QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to 
> >> '/tmp/runtime-+user'
> >> GNU Octave, version 8.2.0
> >> Copyright (C) 1993-2023 The Octave Project Developers.
> >> This is free software; see the source code for copying conditions.
> >> There is ABSOLUTELY NO WARRANTY; not even for MERCHANTABILITY or
> >> FITNESS FOR A PARTICULAR PURPOSE.  For details, type 'warranty'.
> >>
> >> Octave was configured for "x86_64-pc-cygwin".
> >>
> >> Additional information about Octave is available at https://www.octave.org.
> >>
> >> Please contribute if you find this software useful.
> >> For more information, visit https://www.octave.org/get-involved.html
> >>
> >> Read https://www.octave.org/bugs.html to learn how to submit bug reports.
> >> For information about changes from previous versions, type 'news'.
> >>
> >> octave:1> plot(1,1)
> >> wglMakeCurrent error: 0006
> >> wglMakeCurrent error: 0006
> >> warning: opengl_renderer: Error 'invalid operation' (1282) occurred in 
> >> init_gl_context
> >> warning: called from
> >>  __uiobject_split_args__ at line 61 column 9
> >>  uimenu at line 94 column 13
> >>  __add_default_menu__ at line 59 column 5
> >>  figure at line 97 column 5
> >>  newplot at line 120 column 10
> >>  plot at line 234 column 9
> >>
> >> warning: opengl_renderer: Error 'invalid operation' (1282) occurred 
> >> drawing 'uimenu' object
> >> warning: called from
> >>  __uiobject_split_args__ at line 61 column 9
> >>  uimenu at line 94 column 13
> >>  __add_default_menu__ at line 59 column 5
> >>  figure at line 97 column 5
> >>  newplot at line 120 column 10
> >>  plot at line 234 colu

Re: problems with octave 8.2.0-1 and plotting

[Fabio Rossi via Cygwin]

I forgot to mention that the test machine is running Windows 10 Pro 64 bit with 
a ATI FirePro 3800 graphics card. On the same machine, octave built for Windows 
executes correctly the same command. I have observed the same behaviour also on 
other Windows machines running Win7 or other graphic adapters.

Fabio
> Il 26/04/2023 15:34 Fabio Rossi  ha scritto:
> 
>  
> I have installed latest test version of octave 8.2.0-1. When I try to plot 
> using a simple command like "plot(1,1)" I get the following errors from the 
> command line
> 
> $ octave
> QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to 
> '/tmp/runtime-+user'
> GNU Octave, version 8.2.0
> Copyright (C) 1993-2023 The Octave Project Developers.
> This is free software; see the source code for copying conditions.
> There is ABSOLUTELY NO WARRANTY; not even for MERCHANTABILITY or
> FITNESS FOR A PARTICULAR PURPOSE.  For details, type 'warranty'.
> 
> Octave was configured for "x86_64-pc-cygwin".
> 
> Additional information about Octave is available at https://www.octave.org.
> 
> Please contribute if you find this software useful.
> For more information, visit https://www.octave.org/get-involved.html
> 
> Read https://www.octave.org/bugs.html to learn how to submit bug reports.
> For information about changes from previous versions, type 'news'.
> 
> octave:1> plot(1,1)
> wglMakeCurrent error: 0006
> wglMakeCurrent error: 0006
> warning: opengl_renderer: Error 'invalid operation' (1282) occurred in 
> init_gl_context
> warning: called from
> __uiobject_split_args__ at line 61 column 9
> uimenu at line 94 column 13
> __add_default_menu__ at line 59 column 5
> figure at line 97 column 5
> newplot at line 120 column 10
> plot at line 234 column 9
> 
> warning: opengl_renderer: Error 'invalid operation' (1282) occurred drawing 
> 'uimenu' object
> warning: called from
> __uiobject_split_args__ at line 61 column 9
> uimenu at line 94 column 13
> __add_default_menu__ at line 59 column 5
> figure at line 97 column 5
> newplot at line 120 column 10
> plot at line 234 column 9
> 
> warning: opengl_renderer: Error 'invalid operation' (1282) occurred drawing 
> 'figure' object
> warning: called from
> __uiobject_split_args__ at line 61 column 9
> uimenu at line 94 column 13
> __add_default_menu__ at line 59 column 5
> figure at line 97 column 5
> newplot at line 120 column 10
> plot at line 234 column 9
> 
> wglMakeCurrent error: 0006
> warning: opengl_renderer: Error 'invalid operation' (1282) occurred in 
> init_gl_context
> warning: called from
> __add_default_menu__ at line 165 column 3
> figure at line 97 column 5
> newplot at line 120 column 10
> plot at line 234 column 9
> 
> warning: opengl_renderer: Error 'invalid operation' (1282) occurred drawing 
> 'uimenu' object
> warning: called from
> __add_default_menu__ at line 165 column 3
> figure at line 97 column 5
> newplot at line 120 column 10
> plot at line 234 column 9
> 
> warning: opengl_renderer: Error 'invalid operation' (1282) occurred drawing 
> 'uimenu' object
> warning: called from
> __add_default_menu__ at line 165 column 3
> figure at line 97 column 5
> newplot at line 120 column 10
> plot at line 234 column 9
> 
> warning: opengl_renderer: Error 'invalid operation' (1282) occurred drawing 
> 'uimenu' object
> warning: called from
> __add_default_menu__ at line 165 column 3
> figure at line 97 column 5
> newplot at line 120 column 10
> plot at line 234 column 9
> 
> warning: opengl_renderer: Error 'invalid operation' (1282) occurred drawing 
> 'uitoolbar' object
> warning: called from
> __add_default_menu__ at line 165 column 3
> figure at line 97 column 5
> newplot at line 120 column 10
> plot at line 234 column 9
> 
> warning: opengl_renderer: Error 'invalid operation' (1282) occurred drawing 
> 'figure' object
> warning: called from
> __add_default_menu__ at line 165 column 3
> figure at line 97 column 5
> newplot at line 120 column 10
> plot at line 234 column 9
> 
> warning: opengl_renderer: Error 'invalid operation' (1282) occurred in 
> init_gl_context
> warning: called from
> __add_default_menu__ at line 165 column 3
> figure at line 97 column 5
> newplot at line 120 column 10
> plot at line 234 column 9
> 
> w

problems with octave 8.2.0-1 and plotting

[Fabio Rossi via Cygwin]

I have installed latest test version of octave 8.2.0-1. When I try to plot 
using a simple command like "plot(1,1)" I get the following errors from the 
command line

$ octave
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-+user'
GNU Octave, version 8.2.0
Copyright (C) 1993-2023 The Octave Project Developers.
This is free software; see the source code for copying conditions.
There is ABSOLUTELY NO WARRANTY; not even for MERCHANTABILITY or
FITNESS FOR A PARTICULAR PURPOSE.  For details, type 'warranty'.

Octave was configured for "x86_64-pc-cygwin".

Additional information about Octave is available at https://www.octave.org.

Please contribute if you find this software useful.
For more information, visit https://www.octave.org/get-involved.html

Read https://www.octave.org/bugs.html to learn how to submit bug reports.
For information about changes from previous versions, type 'news'.

octave:1> plot(1,1)
wglMakeCurrent error: 0006
wglMakeCurrent error: 0006
warning: opengl_renderer: Error 'invalid operation' (1282) occurred in 
init_gl_context
warning: called from
__uiobject_split_args__ at line 61 column 9
uimenu at line 94 column 13
__add_default_menu__ at line 59 column 5
figure at line 97 column 5
newplot at line 120 column 10
plot at line 234 column 9

warning: opengl_renderer: Error 'invalid operation' (1282) occurred drawing 
'uimenu' object
warning: called from
__uiobject_split_args__ at line 61 column 9
uimenu at line 94 column 13
__add_default_menu__ at line 59 column 5
figure at line 97 column 5
newplot at line 120 column 10
plot at line 234 column 9

warning: opengl_renderer: Error 'invalid operation' (1282) occurred drawing 
'figure' object
warning: called from
__uiobject_split_args__ at line 61 column 9
uimenu at line 94 column 13
__add_default_menu__ at line 59 column 5
figure at line 97 column 5
newplot at line 120 column 10
plot at line 234 column 9

wglMakeCurrent error: 0006
warning: opengl_renderer: Error 'invalid operation' (1282) occurred in 
init_gl_context
warning: called from
__add_default_menu__ at line 165 column 3
figure at line 97 column 5
newplot at line 120 column 10
plot at line 234 column 9

warning: opengl_renderer: Error 'invalid operation' (1282) occurred drawing 
'uimenu' object
warning: called from
__add_default_menu__ at line 165 column 3
figure at line 97 column 5
newplot at line 120 column 10
plot at line 234 column 9

warning: opengl_renderer: Error 'invalid operation' (1282) occurred drawing 
'uimenu' object
warning: called from
__add_default_menu__ at line 165 column 3
figure at line 97 column 5
newplot at line 120 column 10
plot at line 234 column 9

warning: opengl_renderer: Error 'invalid operation' (1282) occurred drawing 
'uimenu' object
warning: called from
__add_default_menu__ at line 165 column 3
figure at line 97 column 5
newplot at line 120 column 10
plot at line 234 column 9

warning: opengl_renderer: Error 'invalid operation' (1282) occurred drawing 
'uitoolbar' object
warning: called from
__add_default_menu__ at line 165 column 3
figure at line 97 column 5
newplot at line 120 column 10
plot at line 234 column 9

warning: opengl_renderer: Error 'invalid operation' (1282) occurred drawing 
'figure' object
warning: called from
__add_default_menu__ at line 165 column 3
figure at line 97 column 5
newplot at line 120 column 10
plot at line 234 column 9

warning: opengl_renderer: Error 'invalid operation' (1282) occurred in 
init_gl_context
warning: called from
__add_default_menu__ at line 165 column 3
figure at line 97 column 5
newplot at line 120 column 10
plot at line 234 column 9

warning: opengl_renderer: Error 'invalid operation' (1282) occurred drawing 
'uimenu' object
warning: called from
__add_default_menu__ at line 165 column 3
figure at line 97 column 5
newplot at line 120 column 10
plot at line 234 column 9

warning: opengl_renderer: Error 'invalid operation' (1282) occurred drawing 
'uimenu' object
warning: called from
__add_default_menu__ at line 165 column 3
figure at line 97 column 5
newplot at line 120 column 10
plot at line 234 column 9

warning: opengl_renderer: Error 'invalid operation' (1282) occurred drawing 
'uimenu' object
warning: called from
__add_default_menu__ at line 165 column 3
figure at line 97 column 5
newplot at line 120 column 10
plot at line 234 column 9

warning: opengl_renderer: Error 'invalid operation' (1282) occurred drawing 
'uitoolbar' object
warning: called from
__add_default_menu__ at line 165 column 3
figure at line 97 column 5
newplot at line 120 column 10
plot at line 234 column 9

warning: opengl_renderer: Error 'invalid operation' (1282) occurred drawing 
'figure' object
warning: called from
__add_default_menu__ at line 165 

Re: segfault in xwin-xdg-menu.exe

[Fabio Rossi]

> Il 12 maggio 2018 alle 16.27 Jon Turney  ha 
> scritto:
> 
> Yeah, this is the same problem, which is under investigation.
> 
> See also https://cygwin.com/ml/cygwin/2018-05/msg00152.html for another 
> workaround.

I have recompiled fontconfig and solved the issue as suggested in the other 
topic. Is it possible to update the binary packages installed by setup.exe?

--
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

Re: segfault in xwin-xdg-menu.exe

[Fabio Rossi]

> Il 11 maggio 2018 alle 19.12 Ken Brown  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:
> > 
> > $ DISPLAY=:0 gdb xwin-xdg-menu.exe
> > 
> > GNU gdb (GDB) (Cygwin 7.10.1-1) 7.10.1
> > Copyright (C) 2015 Free Software Foundation, Inc.
> > License GPLv3+: GNU GPL version 3 or later 
> > <http://gnu.org/licenses/gpl.html>
> > This is free software: you are free to change and redistribute it.
> > There is NO WARRANTY, to the extent permitted by law. Type "show copying"
> > and "show warranty" for details.
> > This GDB was configured as "i686-pc-cygwin".
> > Type "show configuration" for configuration details.
> > For bug reporting instructions, please see:
> > <http://www.gnu.org/software/gdb/bugs/>.
> > Find the GDB manual and other documentation resources online at:
> > <http://www.gnu.org/software/gdb/documentation/>.
> > For help, type "help".
> > Type "apropos word" to search for commands related to "word"...
> > Reading symbols from xwin-xdg-menu.exe...(no debugging symbols 
> > found)...done.
> > (gdb) run
> > Starting program: /usr/bin/xwin-xdg-menu.exe
> > [New Thread 6888.0x1578]
> > [New Thread 6888.0xecc]
> > [New Thread 6888.0x404]
> > [New Thread 6888.0x1bdc]
> > [New Thread 6888.0x6f4]
> > [New Thread 6888.0xdd4]
> > [New Thread 6888.0x1b04]
> > [New Thread 6888.0xf38]
> > 
> > Program received signal SIGSEGV, Segmentation fault.
> > 0x6d0af8f0 in cygfontconfig-1!FcFreeTypeQueryFace () from 
> > /usr/bin/cygfontconfig-1.dll
> > (gdb) bt
> > 
> > #0 0x6d0af8f0 in cygfontconfig-1!FcFreeTypeQueryFace () from 
> > /usr/bin/cygfontconfig-1.dll
> > 
> > #1 0x6d0ab98b in cygfontconfig-1!FcFileScanConfig () from 
> > /usr/bin/cygfontconfig-1.dll
> > 
> > #2 0x6d0abd59 in cygfontconfig-1!FcFileScanConfig () from 
> > /usr/bin/cygfontconfig-1.dll
> > 
> > #3 0x6d0abfb6 in cygfontconfig-1!FcDirCacheScan () from 
> > /usr/bin/cygfontconfig-1.dll
> > 
> > #4 0x6d0a762c in cygfontconfig-1!FcConfigAddCache () from 
> > /usr/bin/cygfontconfig-1.dll
> > 
> > #5 0x6d0a76d6 in cygfontconfig-1!FcConfigBuildFonts () from 
> > /usr/bin/cygfontconfig-1.dll
> > 
> > #6 0x6d0b0cce in cygfontconfig-1!FcInitLoadOwnConfigAndFonts () from 
> > /usr/bin/cygfontconfig-1.dll
> > 
> > #7 0x6d0b0cff in cygfontconfig-1!FcInitLoadConfigAndFonts () from 
> > /usr/bin/cygfontconfig-1.dll
> > 
> > #8 0x6d0a4845 in cygfontconfig-1!FcConfigDestroy () from 
> > /usr/bin/cygfontconfig-1.dll
> > 
> > #9 0x6d0a63ce in cygfontconfig-1!FcConfigSubstituteWithPat () from 
> > /usr/bin/cygfontconfig-1.dll
> > 
> > #10 0x6d0a6d97 in cygfontconfig-1!FcConfigSubstitute () from 
> > /usr/bin/cygfontconfig-1.dll
> > 
> > #11 0x6c0a5cc5 in pango_cairo_fc_font_get_type () from 
> > /usr/bin/cygpangocairo-1.0-0.dll
> > 
> > #12 0x6c084c87 in pango_fc_font_get_raw_extents () from 
> > /usr/bin/cygpangoft2-1.0-0.dll
> > 
> > #13 0x6c0cc090 in pango_color_parse () from /usr/bin/cygpango-1.0-0.dll
> > 
> > #14 0x6c0cd68a in pango_itemize_with_base_dir () from 
> > /usr/bin/cygpango-1.0-0.dll
> > 
> > #15 0x6c0d5c89 in pango_layout_line_get_extents () from 
> > /usr/bin/cygpango-1.0-0.dll
> > 
> > #16 0x6c0d7c72 in pango_layout_move_cursor_visually () from 
> > /usr/bin/cygpango-1.0-0.dll
> > 
> > #17 0x6c0d8204 in pango_layout_get_size () from /usr/bin/cygpango-1.0-0.dll
&g

Re: segfault in xwin-xdg-menu.exe

[Fabio Rossi]

> Il 11 maggio 2018 alle 17.37 Marco Atzeri  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

segfault in xwin-xdg-menu.exe

[Fabio Rossi]

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

GNU gdb (GDB) (Cygwin 7.10.1-1) 7.10.1
Copyright (C) 2015 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-pc-cygwin".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from xwin-xdg-menu.exe...(no debugging symbols found)...done.
(gdb) run
Starting program: /usr/bin/xwin-xdg-menu.exe
[New Thread 6888.0x1578]
[New Thread 6888.0xecc]
[New Thread 6888.0x404]
[New Thread 6888.0x1bdc]
[New Thread 6888.0x6f4]
[New Thread 6888.0xdd4]
[New Thread 6888.0x1b04]
[New Thread 6888.0xf38]

Program received signal SIGSEGV, Segmentation fault.
0x6d0af8f0 in cygfontconfig-1!FcFreeTypeQueryFace () from 
/usr/bin/cygfontconfig-1.dll
(gdb) bt
#0  0x6d0af8f0 in cygfontconfig-1!FcFreeTypeQueryFace () from 
/usr/bin/cygfontconfig-1.dll
#1  0x6d0ab98b in cygfontconfig-1!FcFileScanConfig () from 
/usr/bin/cygfontconfig-1.dll
#2  0x6d0abd59 in cygfontconfig-1!FcFileScanConfig () from 
/usr/bin/cygfontconfig-1.dll
#3  0x6d0abfb6 in cygfontconfig-1!FcDirCacheScan () from 
/usr/bin/cygfontconfig-1.dll
#4  0x6d0a762c in cygfontconfig-1!FcConfigAddCache () from 
/usr/bin/cygfontconfig-1.dll
#5  0x6d0a76d6 in cygfontconfig-1!FcConfigBuildFonts () from 
/usr/bin/cygfontconfig-1.dll
#6  0x6d0b0cce in cygfontconfig-1!FcInitLoadOwnConfigAndFonts () from 
/usr/bin/cygfontconfig-1.dll
#7  0x6d0b0cff in cygfontconfig-1!FcInitLoadConfigAndFonts () from 
/usr/bin/cygfontconfig-1.dll
#8  0x6d0a4845 in cygfontconfig-1!FcConfigDestroy () from 
/usr/bin/cygfontconfig-1.dll
#9  0x6d0a63ce in cygfontconfig-1!FcConfigSubstituteWithPat () from 
/usr/bin/cygfontconfig-1.dll
#10 0x6d0a6d97 in cygfontconfig-1!FcConfigSubstitute () from 
/usr/bin/cygfontconfig-1.dll
#11 0x6c0a5cc5 in pango_cairo_fc_font_get_type () from 
/usr/bin/cygpangocairo-1.0-0.dll
#12 0x6c084c87 in pango_fc_font_get_raw_extents () from 
/usr/bin/cygpangoft2-1.0-0.dll
#13 0x6c0cc090 in pango_color_parse () from /usr/bin/cygpango-1.0-0.dll
#14 0x6c0cd68a in pango_itemize_with_base_dir () from 
/usr/bin/cygpango-1.0-0.dll
#15 0x6c0d5c89 in pango_layout_line_get_extents () from 
/usr/bin/cygpango-1.0-0.dll
#16 0x6c0d7c72 in pango_layout_move_cursor_visually () from 
/usr/bin/cygpango-1.0-0.dll
#17 0x6c0d8204 in pango_layout_get_size () from /usr/bin/cygpango-1.0-0.dll
#18 0x6b8bd65a in rsvg_state_reconstruct () from /usr/bin/cygrsvg-2-2.dll
#19 0x6b8bd569 in rsvg_state_reconstruct () from /usr/bin/cygrsvg-2-2.dll
#20 0x6b8bd936 in rsvg_state_reconstruct () from /usr/bin/cygrsvg-2-2.dll
#21 0x6b8b742c in rsvg_new_ellipse () from /usr/bin/cygrsvg-2-2.dll
#22 0x6b8b78ad in rsvg_new_ellipse () from /usr/bin/cygrsvg-2-2.dll
#23 0x6b8b8332 in rsvg_node_draw () from /usr/bin/cygrsvg-2-2.dll
#24 0x6b8c5834 in rsvg_handle_render_cairo_sub () from /usr/bin/cygrsvg-2-2.dll
#25 0x6b8c600f in rsvg_handle_get_pixbuf_sub () from /usr/bin/cygrsvg-2-2.dll
#26 0x6b8c60a7 in rsvg_handle_get_pixbuf () from /usr/bin/cygrsvg-2-2.dll
#27 0x6a5112e9 in ?? () from 
/usr/lib/gdk-pixbuf-2.0/2.10.0/loaders/cygpixbufloader-svg.dll
#28 0x6cb89918 in gdk_pixbuf_loader_close () from 
/usr/bin/cyggdk_pixbuf-2.0-0.dll
#29 0x6cb8620c in gdk_pixbuf_format_copy () from 
/usr/bin/cyggdk_pixbuf-2.0-0.dll
#30 0x6cb871cb in gdk_pixbuf_new_from_stream_at_scale () from 
/usr/bin/cyggdk_pixbuf-2.0-0.dll
#31 0x6bbae43d in gtk_icon_info_free () from /usr/bin/cyggtk-x11-2.0-0.dll
#32 0x6bbb169c in gtk_icon_info_load_icon () from /usr/bin/cyggtk-x11-2.0-0.dll
#33 0x00401eee in ?? ()
#34 0x004023ce in ?? ()
#35 0x0040249f in ?? ()
#36 0x004025fb in ?? ()
#37 0x00403bf3 in ?? 

vim 7.4.838 doesn't source system wide config file

[Fabio Rossi]

I have created a system wide config file in /etc/vimrc but vim is not sourcing 
it. The same config file works like a charm if I put it into ~HOME/.vimrc

$ vim -V

...
could not source "$VIM/vimrc"
...

It seems to be a difference between vi and vim, the former uses directly /etc 
while the latter refers to $VIM

$ vi --version

...
system vimrc file: "/etc/virc"
fallback for $VIM: "/etc"
..

$ vim --version

...
system vimrc file: "$VIM/vimrc"
fallback for $VIM: "/etc"


--
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