public inbox for
help / color / mirror / Atom feed
From: Csaba Raduly <>
Subject: Re: segfault Xserver...current version (1.8)
Date: Sun, 07 Aug 2011 11:26:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Sat, Aug 6, 2011 at 8:01 PM, Linda Walsh  wrote:
> Jon TURNEY wrote:
>> Next time, please *attach* the *full* XWin.0.log
> ---
>        That was the full had been truncated -- perhaps by the
> failing
> processes...A full log from a "non-crashed version" (i.e. I haven't run
> yast2), is here:

To attach is to use "File->Attach->File..." or click the paperclip
icon, as opposed to pasting the log into the body of the message.

Also, please set Thunderbird to attach files correctly:

>        Yeah -- that's why I don't like to include cygcheck.out's
> They give out lots of info that isn't _entirely_ relevant.  It's not even an
> accurate package listing if one has installed packages w/tar by hand.

What you deem relevant may not match what others on this list deem
relevant. You might omit information that would have helped diagnosing
your problem.
There's a reason for what's written in

Problem reports:

GCS a+ e++ d- C++ ULS$ L+$ !E- W++ P+++$ w++$ tv+ b++ DI D++ 5++
The Tao of math: The numbers you can count are not the real numbers.
Life is complex, with real and imaginary parts.
"Ok, it boots. Which means it must be bug-free and perfect. " -- Linus Torvalds
"People disagree with me. I just ignore them." -- Linus Torvalds

Unsubscribe info:
Problem reports:

  reply	other threads:[~2011-08-07 11:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-05  0:04 Linda Walsh
2011-08-06 15:57 ` Jon TURNEY
2011-08-06 18:01   ` Linda Walsh
2011-08-07 11:26     ` Csaba Raduly [this message]
2011-08-08  6:37       ` Linda Walsh
2011-08-08 12:15     ` segfault Xserver...current version (1.10, not 1.8) Jon TURNEY
2011-08-08 23:40       ` Linda Walsh
2011-08-10 14:41         ` Jon TURNEY
2011-08-10  0:55       ` Linda Walsh
2011-08-10  5:11         ` Christopher Faylor
2011-08-16  7:16           ` Linda Walsh
2011-08-16 12:28             ` 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='' \ \ \

* 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).