public inbox for firstname.lastname@example.org help / color / mirror / Atom feed
From: Jon TURNEY <email@example.com> To: firstname.lastname@example.org Cc: email@example.com Subject: Re: 64-bit xfree86 failing? Date: Mon, 02 Feb 2015 15:49:00 -0000 [thread overview] Message-ID: <54CF9C98.firstname.lastname@example.org> (raw) In-Reply-To: <EA219B8B-6749-48A0-BADA-2812AB204280@surrey.ac.uk> On 04/12/2014 02:53, email@example.com wrote: > working again. > > my mistake was in years of using > > startx -- -multiwindow -clipboard & > > because /usr/bin/startx no longer starts x I'm kind of surprised this used to work at all, since this is requesting both the internal multiwindow mode window manager, and whatever default window manager xinitrc decides to run. Sorry about breaking that. If you want a multiwindow mode session, the documented way to start it would be using startxwin, or the Start Menu link we provide to run that (See ) -clipboard has been the default for a number of years now, you don't need to explicitly provide it. > Once I switched to > > xinit -- -multiwindow -clipboard & > > I was fine. > > Remember that startx doesn't startx, on either 32- or 64-bit cygwin > (I did a fresh 32-bit install and checked) and you're good to go. I think that you will find that running 'startx' without options does work. While I'm sure sarcasm is very relieving for you, please don't use it here.  http://x.cygwin.com/docs/ug/using.html#using-starting-exe -- 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/
next prev parent reply other threads:[~2015-02-02 15:49 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <CAGZ6-67PP2LhWeeH6qGyNBfPJXmckWGyx3-s131O61QoGR66UQ@mail.gmail.com> 2014-12-02 4:34 ` l.wood 2014-12-04 2:53 ` l.wood 2015-02-02 15:49 ` Jon TURNEY [this message] 2014-12-01 9:49 l.wood
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=54CF9C98.firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.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: linkBe 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).