From: Tom Kacvinsky <tom.kacvinsky@vectorcast.com>
To: cygwin@cygwin.com
Subject: Re: failure notice
Date: Mon, 07 Dec 2015 14:01:00 -0000 [thread overview]
Message-ID: <CAAEKttzCvhKTa9tbORKfzzBujH4oNZakwBv+6wnXLLm_PrnwRA@mail.gmail.com> (raw)
In-Reply-To: <CAAEKttw6WETmKSviuX8VfZ-1MKUoZHo=MH=D+QGV8jm6izTQ-A@mail.gmail.com>
Hi.
On Fri, Dec 4, 2015 at 9:20 AM, Tom Kacvinsky
<tom.kacvinsky@vectorcast.com> wrote:
> Hi,
>
> We have an interesting problem whereby an Linux X client application
> crashes when running the X server on cygwin. We have a reproducer
> for the problem, but it is a Qt example application stored in a tarball.
>
> We have gathered the other information that would typically be requested.
> I just need to know the best way of getting this information to the list.
>
Bump. We like to know about this because if we are running into
problems, our customers will, too. I have an additional piece of
information. What we've test is:
Multiple windows (Doesn't Work)
One window (Works)
Full screen (Works)
One window without title bar (Works)
--
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:[~2015-12-07 14:01 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <56619fc2.83c1420a.10961.ffffb37fSMTPIN_ADDED_MISSING@mx.google.com>
2015-12-04 14:20 ` Fwd: " Tom Kacvinsky
2015-12-07 14:01 ` Tom Kacvinsky [this message]
2015-12-07 15:19 ` Jon Turney
2015-12-07 15:24 ` Tom Kacvinsky
2015-12-07 16:17 ` Tom Kacvinsky
2015-12-08 16:49 ` Jon Turney
2015-12-08 16:55 ` Tom Kacvinsky
2015-12-08 18:57 ` Tom Kacvinsky
2015-12-21 18:58 ` Tom Kacvinsky
2015-12-22 15:34 ` Tom Kacvinsky
2016-01-04 18:43 ` Tom Kacvinsky
2016-01-12 14:14 ` Tom Kacvinsky
2019-03-02 17:38 Failure notice Andy Perkins
2019-03-02 17:39 ` cygwinautoreply
[not found] <CAH8yC8nrV4i1wOzeBbXDKMJpdfsN-8ZubiN=R7Yow4cBDmG5wQ@mail.gmail.com>
[not found] ` <5ad17051.cf55650a.73c5d.c3e7SMTPIN_ADDED_MISSING@mx.google.com>
2018-04-14 3:11 ` failure notice Jeffrey Walton
2018-04-14 3:51 ` Brian Inglis
2018-04-14 5:00 ` R0b0t1
2018-04-14 7:27 ` David Stacey
2018-04-14 15:08 ` Brian Inglis
[not found] <5644019f.42dc420a.272e2.5d14SMTPIN_ADDED_MISSING@mx.google.com>
2015-11-12 3:07 ` Mario Roy
[not found] <CAG=EhJo-oJEFqnmYsuNgewpkq1kpJNnaEbs9AxgKRcfuOZkVjg@mail.gmail.com>
[not found] ` <545ee223.ea5f460a.2b39.ffff870aSMTPIN_ADDED_MISSING@mx.google.com>
2014-11-09 3:43 ` Theodore Si
[not found] <CAC8hJujotv3avbCppCX5sOfWjiVJmExfORgtLpKXQ6=eOtgmUQ@mail.gmail.com>
[not found] ` <4e49a66c.02b7960a.199e.ffffeaaeSMTPIN_ADDED@mx.google.com>
2011-08-15 23:08 ` Gary
-- strict thread matches above, loose matches on Subject: below --
2009-07-10 14:16 _
2002-09-07 22:48 Fred_Smith
[not found] <E04CF3F88ACBD5119EFE00508BBB2121015639E4@exch-01.noida.hcltech.com>
2002-01-28 14:39 ` Michael A Chase
1999-07-22 23:56 Teun Burgers
1999-07-26 10:31 ` Chris Faylor
1999-07-31 18:34 ` Chris Faylor
1999-07-31 18:34 ` Teun Burgers
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=CAAEKttzCvhKTa9tbORKfzzBujH4oNZakwBv+6wnXLLm_PrnwRA@mail.gmail.com \
--to=tom.kacvinsky@vectorcast.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).