public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Chris Carlson <cwcarlsonc@cox.net>
To: cygwin-xfree@cygwin.com
Subject: Re: X11 crashing - no errors in log file
Date: Thu, 09 Oct 2014 04:06:00 -0000	[thread overview]
Message-ID: <543609B7.90506@cox.net> (raw)
In-Reply-To: <0irt1p0182qVqVd01irvtT>

I also have been getting crashes, but I can't figure out what is causing 
it.  I opened Microsoft Word, and X just crashed in the background.  
It's happened twice now, but the first time, I can't remember what I did 
to make it happen.

Note that I have Cygwin 1.16 running on a Windows 7 laptop, and I often 
close the lid to hibernate until later.

I started X with -logverbose 3, but I haven't had it crash, yet. I'll 
send the log when it crashes, presuming it does before I run out of disk 
space. :-)

Chris Carlson


On 10/8/2014 11:51 AM, Nem W Schlecht wrote:
> X11 has been crashing on me in 2 cases since upgrading to 1.16.1-1
>
> 1) Using 'xv' on any image.  I compiled this myself and it was running
> fine in the past, but now when I try to open any image, all of X11
> crashes.  I tried to recompile it, but same issue.  Nothing is showing
> up in the XWin.0.log
>
> 2) Using 'rdesktop' to a remote Windows host and then selecting and
> hitting 'Ctrl-C' on a list of files.  About 2 seconds after the
> Ctrl-C, X11 crashes (again, nothing in XWin.0.log).
>
> Is there additional debugging I can turn on to try to catch the error
> that is happening?
>


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://x.cygwin.com/docs/
FAQ:                   http://x.cygwin.com/docs/faq/


       reply	other threads:[~2014-10-09  4:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <0irt1p0182qVqVd01irvtT>
2014-10-09  4:06 ` Chris Carlson [this message]
2014-10-08 18:51 Nem W Schlecht

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=543609B7.90506@cox.net \
    --to=cwcarlsonc@cox.net \
    --cc=cygwin-xfree@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).