run.exe at Win 7 x86_64 seems to ignore custom X server parameters

2014-11-25 Thread hostalp 
Hello,
to disable the host based access control, I've always been starting X server 
as follows:
D:\cygwin\bin\run.exe /usr/bin/bash.exe -l -c /usr/bin/startxwin.exe -- -ac
Which matches the description from here by the way: 
http://x.cygwin.com/docs/faq/cygwin-x-faq.html#q-command-line-args

However since some recent update (most likely since updating to 
run-1.3.2-1.tar.xz or later - see below), the -ac server argument stopped to 
have any effect.
In XWin log I can see it starts as follows:
XWin was started with the following command line:

X :0 -multiwindow


Whereas previously it was (as one would expect):
XWin was started with the following command line:

X -ac :0 -multiwindow


While testing launching the X server the same way from Windows command line 
and from the Cygwin shell I found out that the problem always occurs when 
there's run.exe involved (e.g. executing /usr/bin/bash.exe -l -c 
/usr/bin/startxwin.exe -- -ac from the Cygwin shell works as expected).

Did the behavior change so it has to be started with additional server 
parameters differently now? If so, it isn't documented correctly. If not, it's
 most likely a bug.

Running Cygwin x86_64, currently up to date, see attached cygcheck.out for 
more information.

Best regards,
Peter
Cygwin Configuration Diagnostics
Current System Time: Tue Nov 25 17:03:36 2014

Windows 7 Professional Ver 6.1 Build 7601 Service Pack 1

Path:   D:\cygwin\usr\local\bin
D:\cygwin\bin
C:\ProgramData\Oracle\Java\javapath
C:\Program Files\Common Files\Microsoft Shared\Windows Live
C:\Program Files (x86)\Common Files\Microsoft Shared\Windows Live
C:\Windows\system32
C:\Windows
C:\Windows\System32\Wbem
C:\Windows\System32\WindowsPowerShell\v1.0
C:\Program Files\WIDCOMM\Bluetooth Software
C:\Program Files\WIDCOMM\Bluetooth Software\syswow64
C:\Program Files (x86)\Windows Live\Shared
C:\Program Files (x86)\Common Files\Roxio Shared\DLLShared
C:\Program Files (x86)\Common Files\Roxio Shared\OEM\DLLShared
C:\Program Files (x86)\Common Files\Roxio Shared\OEM\DLLShared
C:\Program Files (x86)\Common Files\Roxio Shared\OEM\12.0\DLLShared
C:\Program Files (x86)\Roxio\OEM\AudioCore
C:\Program Files (x86)\Intel\Services\IPT
C:\Program Files (x86)\Intel\OpenCL SDK\2.0\bin\x86
C:\Program Files (x86)\Intel\OpenCL SDK\2.0\bin\x64
C:\Program Files\TortoiseSVN\bin
C:\Program Files (x86)\Intel\OpenCL SDK\2.0\bin\x86
C:\Program Files (x86)\Intel\OpenCL SDK\2.0\bin\x64
C:\Program Files (x86)\Intel\OpenCL SDK\2.0\bin\x86
C:\Program Files (x86)\Intel\OpenCL SDK\2.0\bin\x64
C:\Program Files (x86)\Intel\OpenCL SDK\2.0\bin\x86
C:\Program Files (x86)\Intel\OpenCL SDK\2.0\bin\x64
C:\Program Files (x86)\Intel\OpenCL SDK\2.0\bin\x86
C:\Program Files (x86)\Intel\OpenCL SDK\2.0\bin\x64
C:\Program Files (x86)\Intel\OpenCL SDK\2.0\bin\x86
C:\Program Files (x86)\Intel\OpenCL SDK\2.0\bin\x64
C:\ProgramData\Oracle\Java\javapath
C:\Program Files\Common Files\Microsoft Shared\Windows Live
C:\Program Files (x86)\Common Files\Microsoft Shared\Windows Live
C:\Windows\system32
C:\Windows
C:\Windows\System32\Wbem
C:\Windows\System32\WindowsPowerShell\v1.0
C:\Program Files\WIDCOMM\Bluetooth Software
C:\Program Files\WIDCOMM\Bluetooth Software\syswow64
C:\Program Files (x86)\Windows Live\Shared
C:\Program Files (x86)\Common Files\Roxio Shared\DLLShared
C:\Program Files (x86)\Common Files\Roxio Shared\OEM\DLLShared
C:\Program Files (x86)\Common Files\Roxio Shared\OEM\DLLShared
C:\Program Files (x86)\Common Files\Roxio Shared\OEM\12.0\DLLShared
C:\Program Files (x86)\Roxio\OEM\AudioCore
C:\Program Files (x86)\Intel\Services\IPT
C:\Program Files (x86)\Intel\OpenCL SDK\2.0\bin\x86
C:\Program Files (x86)\Intel\OpenCL SDK\2.0\bin\x64
C:\Program Files\TortoiseSVN\bin
C:\Program Files (x86)\Intel\OpenCL SDK\2.0\bin\x86
C:\Program Files (x86)\Intel\OpenCL SDK\2.0\bin\x64
C:\Program Files (x86)\Intel\OpenCL SDK\2.0\bin\x86
C:\Program Files (x86)\Intel\OpenCL SDK\2.0\bin\x64
C:\Program Files (x86)\Intel\OpenCL SDK\2.0\bin\x86
C:\Program Files (x86)\Intel\OpenCL SDK\2.0\bin\x64
C:\Program Files (x86)\Intel\OpenCL SDK\2.0\bin\x86
C:\Program Files (x86)\Intel\OpenCL SDK\2.0\bin\x64
C:\Program Files (x86)\Intel\OpenCL SDK\2.0\bin\x86
C:\Program Files (x86)\Intel\OpenCL SDK\2.0\bin\x64
C:\Program Files\Sysinternals

Output from D:\cygwin\bin\id.exe
UID: 15266(user) GID: 10513(Domain Users)
10513(Domain Users)  545(Users)   1002(Netmon Users)

SysDir: C:\Windows\system32
WinDir: C:\Windows

USER = 'user'
PWD = '/home/user'
HOME =

Re: run.exe at Win 7 x86_64 seems to ignore custom X server parameters

2014-11-25 Thread hostalp 
A little update.

I rolled back to run-1.3.1-1 (from local backup) and it started to work again.
 Then I searched further and found these messages:
https://cygwin.com/ml/cygwin-xfree/2014-09/msg00026.html
https://cygwin.com/ml/cygwin/2014-09/msg00127.html
https://cygwin.com/ml/cygwin/2014-09/msg00401.html
https://cygwin.com/ml/cygwin/2014-10/msg00040.html
https://cygwin.com/ml/cygwin/2014-10/msg00170.html

So I updated to run-1.3.3-1 again and tested:

1. D:\cygwin\bin\run.exe --quote /usr/bin/bash.exe -l -c 
/usr/bin/startxwin.exe -- -ac
2. D:\cygwin\bin\run.exe /usr/bin/bash.exe -l -c \/usr/bin/startxwin.exe -- 
-ac\

Which both work, while the original form:

3. D:\cygwin\bin\run.exe /usr/bin/bash.exe -l -c /usr/bin/startxwin.exe -- 
-ac

doesn't (it works with run up to 1.3.1-1).

Best regards,
Peter

--
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/

Re: cygwin emacs failing siletnly

2014-11-25 Thread Gulliver Smith 
Thanks for all of the advice on fc-cache, but it doesn't help my emacs
run. Does anyone else have any ideas why the fonts are causing emacs
to blow up?

Thanks
Gulliver

On Mon, Oct 13, 2014 at 8:18 PM, Gulliver Smith
gulliver.m.sm...@gmail.com wrote:
 Follow up:

 It is only emacs for X-windows that fails silently.

 emacs-nox works perfectly.

 As I said, the silent failure has no core dump and no log messages
 anywhere. Nothing is displayed in the shell window.

 Thanks
 Gulliver

--
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/

Re: cygwin emacs failing siletnly

2014-11-25 Thread Ken Brown 

On 11/25/2014 8:54 PM, Gulliver Smith wrote:

Thanks for all of the advice on fc-cache, but it doesn't help my emacs
run. Does anyone else have any ideas why the fonts are causing emacs
to blow up?


You said in one of your messages of October 13 that fc-cache is failing. 
emacs-X11 is not going to be able to find any fonts if there's something wrong 
with your fontconfig setup.  You might try running fc-cache under strace to see 
if that gives any clues.


Ken

--
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/