From: Robert Haskins <robert.haskins@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Installing X11 on a Dell E6440
Date: Mon, 29 Feb 2016 16:58:00 -0000 [thread overview]
Message-ID: <CANmBfsaHFCc8rbPXYtHpT+Z33ZrFRjD4CxPovt_EKLQXvUswow@mail.gmail.com> (raw)
In-Reply-To: <56D2A554.8090304@gmail.com>
On Sun, Feb 28, 2016 at 2:44 AM, Marco Atzeri <marco.atzeri@gmail.com> wrote:
> FYI: in this mailing list we post reply below. (bottom style)
>
> I see nothing strange on your installation,
> eventually you can just update it.
>
> xorg-server-1.18.1-1 was released 19 Feb
> and you have it, but cygwin is at 2.14.1
> https://cygwin.com/ml/cygwin-announce/2016-01/msg00025.html
> and you are at 2.4.0-1
>
> Just one curiosity ".babun" on your path has really a dot as
> first letter or is just a character that cygcheck don't know
> how to handle ?
>
> I forgot to ask you if you have a ".startxwinrc" on your home,
> but I assume no as you mention a installation.
> If yes please move it away and try again.
>
>
> Regards
> Marco
Re-installing Cygwin/X and then refactoring worked just great.
Thanks for your help!!
--
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:[~2016-02-29 16:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-27 13:57 Robert Haskins
2016-02-27 17:29 ` Marco Atzeri
2016-02-28 4:25 ` Robert Haskins
2016-02-28 7:44 ` Marco Atzeri
2016-02-29 16:58 ` Robert Haskins [this message]
2016-03-08 11:54 ` startx xauth unknown command (was Re: Installing X11 on a Dell E6440) Jon Turney
-- strict thread matches above, loose matches on Subject: below --
2016-02-27 0:05 Installing X11 on a Dell E6440 Robert Haskins
2016-02-27 5:09 ` Marco Atzeri
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=CANmBfsaHFCc8rbPXYtHpT+Z33ZrFRjD4CxPovt_EKLQXvUswow@mail.gmail.com \
--to=robert.haskins@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).