public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Jon TURNEY <jon.turney@dronecode.org.uk>
To: cygwin-xfree@cygwin.com
Cc: mikedep333@gmail.com
Subject: Re: [ANNOUNCEMENT] Updated: xorg-server-1.16.0-1 (TEST)
Date: Wed, 20 Aug 2014 11:19:00 -0000	[thread overview]
Message-ID: <53F48418.5090509@dronecode.org.uk> (raw)
In-Reply-To: <CAMKht8i6w8G6O=JYd_UbqRrdUTzofFXpda5EopCon=zNxn3+yQ@mail.gmail.com>

On 18/08/2014 14:43, Michael DePaulo wrote:
> On Sat, Aug 16, 2014 at 10:41 AM, Jon TURNEY wrote:
>>
>> The following packages have been updated in the Cygwin distribution:
>>
>> *** xorg-server-*1.16.0-1

> I think I found a bug:
>
> There is no stdout or stderr.
>
> So for example, "xwin --version" does not output anything.
>
> Nothing is logged to /var/log/xwin/Xorg.0.log when I type that
> command. This is the same as with xorg-server 1.15.
>
> If I specify an invalid argument (e.g. "xwin --foobar"). then I see
> the information dialog box, and the xwin usage info is outputted to
> that log file.
>
> I did all my testing with 32-bit Cygwin.

Thanks for reporting this.

Are you using the same terminal in both cases? (For obscure reasons, 
XWin --version doesn't work in a cmd.exe terminal, see [1])

You also seem to be using a separate cygwin installation to test 
xorg-server 1.16, which might also be related to this in some way.

[1] https://sourceware.org/bugzilla/show_bug.cgi?id=9763

-- 
Jon TURNEY
Volunteer Cygwin/X X Server maintainer

--
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-08-20 11:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-17  3:23 Jon TURNEY
2014-08-18 13:43 ` Michael DePaulo
2014-08-20 11:19   ` Jon TURNEY [this message]
2014-08-20 12:47     ` Michael DePaulo
2014-09-01 10:16 ` 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=53F48418.5090509@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=cygwin-xfree@cygwin.com \
    --cc=mikedep333@gmail.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).