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: strata_ranger@hotmail.com
Subject: Re: Unable to start XWin with --nolock
Date: Thu, 26 Aug 2010 17:46:00 -0000 [thread overview]
Message-ID: <4C76A69B.1010309@dronecode.org.uk> (raw)
In-Reply-To: <SNT111-W27EE98B8F786089A1A84CD9C850@phx.gbl>
On 26/08/2010 18:18, Richard Gitschlag wrote:
> I am having trouble starting XWin on my system.
>
> It complains about being unable to "read lock" the file -- okay, so it resides on a FAT32 drive, no big. Just add --nolock to my command line and move on.
>
> But it doesn't work. But it does. But doesn't.
>
> I AM able to run XWin from inside cygwin's bash prompt:
>
> $ xinit -- -nolock -multiwindow
> $ startxwin -- -nolock
>
> But I can NOT run Xwin from a Windows command prompt or a Start Menu shortcut:
>
>> /cygwin/bin/run.exe /usr/bin/bash.exe -l -c /usr/bin/xinit -- -nolock -multiwindow
>
>> /cygwin/bin/run.exe /usr/bin/bash.exe -l -c /usr/bin/startxwin -- -nolock
>
> In these cases I am given the read-lock error, and:
>
> "XWin was started with the following command line: X :0"
>
> In other words, I am unable to pass my command-line options to XWin, so I cannot work around the error.
>
> Did I overlook something? What do I do next?
You need to quote the command after -c to prevent bash assuming those options
are meant for itself.
This has been answered a few times before, e.g. at [1]
I'm not sure if you arrived at using -nolock from reading FAQ 3.4 [2], perhaps
I need to improve that FAQ to give more guidance.
[1] http://sourceware.org/ml/cygwin-xfree/2010-04/msg00026.html
[2] http://x.cygwin.com/docs/faq/cygwin-x-faq.html#q-cant-read-lock-file
--
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/
prev parent reply other threads:[~2010-08-26 17:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-26 17:38 Richard Gitschlag
2010-08-26 17:46 ` Jon TURNEY [this message]
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=4C76A69B.1010309@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin-xfree@cygwin.com \
--cc=strata_ranger@hotmail.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).