From: Philippe <philippe.raven@gmail.com>
To: cygwin@cygwin.com
Subject: Bug in libX11 or something near ?
Date: Tue, 18 Jun 2019 16:08:00 -0000 [thread overview]
Message-ID: <CAC-34C0eHbNVnKT9HV1JGd3MJ4R=njABKWavXkiYLAUkjcXvKQ@mail.gmail.com> (raw)
Hello Cygwin list !
I'm using Cygwin/X and identified a critical bug using some piece of
software.
I don't really know where to begin, but I'm able to crash some applications
via the application's menu, only with Cygwin/X (no crash with Xming, and no
crash under any Linux distributions).
For information, It goes through VirtualGL. I'll give the example on how to
reproduce it with a free software : Paraview (under linux).
So you open Paraview, then clic on "View" > show the "Toolbars" submenu,
then you move your mouse directly on the "Sources" or "Edit" menu, then it
crashes immediately. The only error message in the linux shell (from where
it was launched) is "paraview: Fatal IO error: client killed".
I got those lines in the XWin.0.log file :
SetupSysMenu: GetSystemMenu() failed for HWND 0x130746
winTopLevelWindowProc - WM_DESTROY - WM_WM_KILL
I'm on the last available libX11, libxcb1 etc .
If you have any idea, thanks :)
Philippe
--
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 reply other threads:[~2019-06-18 16:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-18 16:08 Philippe [this message]
2019-06-23 17:57 ` Jon Turney
2019-06-23 18:41 ` Philippe
2019-06-24 7:28 ` Philippe
2019-06-25 11:15 ` 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='CAC-34C0eHbNVnKT9HV1JGd3MJ4R=njABKWavXkiYLAUkjcXvKQ@mail.gmail.com' \
--to=philippe.raven@gmail.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).