mathog | 10 Jun 01:32 2016

new start method questions


With an older version of Cygwin I had constructed a cut down 
distribution which included only the minimum pieces needed to run X11.  
It was about 40Mb, installed.

Since the X11 server update the start method changed.  The .bat file 
which starts things now has this as its active line:

C:\cygwinX\bin\run.exe --quote /usr/bin/bash.exe -l -c "cd; exec 

Unfortunately this method creates a "/home/username" directory.  The 
startxwin part
isn't the culprit, just starting bash does it.  This is sufficient:

C:\cygwinX\bin\run.exe --quote /usr/bin/bash.exe -l -c "cd; ls"

Is there a way to run startxwin without allowing bash to make a new home 
directory? Leaving off the "-l" does not create the home directory - it 
also does not start the X11 server.

This distribution is intended to work with putty's ssh, not the ssh in 
cygwin.  To get putty to work these changes were made to startxwin:

defaultserverargs=" -listen tcp"

(Continue reading)


Fwd:Nunc Commodo Auctor Incorporated

See attached your agreement.

Nunc Commodo Auctor Incorporated
Attachment (t77ff96j.dotm): application/octet-stream, 131 KiB
Unsubscribe info:
Problem reports:
Stefan Katletz | 22 May 15:27 2016

Re: xfig: Warning: Missing charsets in String to FontSet conversion


I am now facing this (old) problem on a new installation under Windows
10. I tried 32 and 64 bit installations of cygwin, no difference: xfig
gives this warning, and crashes when I want to save/export the

$ Warning: Missing charsets in String to FontSet conversion

xfig3.2.5c: SIGSEGV signal trapped
xfig: attempting to save figure
xfig: 1 object(s) saved in "/home/kat/SAVE.fig"

At least the work is not all lost, I used xfig under linux to do export...

Does anybody know what's going on? I am happy to supply logs if
somebody cares. I was reading the old mails, but couldn't find a
solution. I tried to install all font packages in cygwin I was
offered, but the warning appears even when starting with an empty


Unsubscribe info:
Problem reports:

(Continue reading)

Hatten William | 19 May 07:13 2016

Private Letter From Hatten William.+2

Good Day, 

I am Hatten William (SGT. MAJ.), I am reaching you for an important discussion that will be of help to you.
Kindly drop your direct cell phone number or reply for more discussion in details.

Thank you. 
Hatten William (SGT. MAJ.)

Unsubscribe info:
Problem reports:

Denton Chang | 10 May 15:07 2016

Denton Chang

Please review your report attached.

Denton Chang
Attachment ( application/octet-stream, 307 KiB
Unsubscribe info:
Problem reports:
Ahmed Al-Zamil | 4 May 14:00 2016

Emailing: scan10001

Your message is ready to be sent with the following file or link


Note: To protect against computer viruses, e-mail programs may prevent
sending or receiving certain types of file attachments.  Check your e-mail
security settings to determine how attachments are handled.
Attachment (scan10001.rar): application/octet-stream, 7033 bytes
Unsubscribe info:
Problem reports:
ggvrsn | 3 Apr 17:34 2016

hi cygwin

Sup cygwin


Unsubscribe info:
Problem reports:

postmaster | 18 Feb 10:18 2016

Undeliverable Mail

Delivery Failed: jugal.c <at>

The mail server for does not accept E-mail with attachments that contain the CMD extension.

Original message follows:

Return-Path: <cygwin-xfree <at>>
Received: from (UnknownHost []) by with SMTP;
   Thu, 18 Feb 2016 01:17:56 -0800
From: cygwin-xfree <at>
To: jugal.c <at>
Subject: Returned mail: Data format error
Date: Thu, 18 Feb 2016 14:47:03 +0530
MIME-Version: 1.0
Content-Type: multipart/mixed;
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000

Unsubscribe info:
Problem reports:

John J Ottusch | 10 Dec 01:03 2015

Persistent CYGWIN/X server taskbar button with urxvt in CYGWIN-64, not rxvt in CYGWIN-32. Why?

Thanks for the tip.

First of all, using 'strace' I determined that testing is not advisable 
with the 'run.exe' executable named anything other than just 'run.exe'. 
Renaming the executable to 'runX.exe' ends up being interpreted as 'run X' 
and things go wrong from there.

The good news is that the version of 'run' Jon Turney provided does indeed 
withhold taskbar display of the CMD window from which urxvtermX.bat is 

The bad news is that I have to execute the target 
'C:\win64app\cygwin\bin\run.exe C:\win64app\cygwin\urxvtermX.bat' twice 
(or sometimes more). The first time through starts up 'Cygwin/X 
Server:0.0'. The second and any subsequent times it creates a new 'urxvt' 


Unsubscribe info:
Problem reports:

John J Ottusch | 29 Nov 03:56 2015

Persistent CYGWIN/X server taskbar button with urxvt in CYGWIN-64, not rxvt in CYGWIN-32. Why?

I use CYGWIN a lot with 64-bit Windows 7 and have been transitioning 
from 32-bit CYGWIN to 64-bit CYGWIN primarily in hopes of avoiding 

If I could set up 64-bit CYGWIN (= C64) to behave exactly the same way 
as my 32-bit CYGWIN (= C32) set up I would, but the applications don't 
match up exactly and they don't behave exactly the same way.

One difference I notice is that opening a urxvt in C64 creates a 
separate button associated with the Cygwin/X server process in the 
taskbar, whereas opening an rxvt in C32 does not. (rxvt is not available 
as a C64 application, but I would expect urxvt to operate similarly). In 
both cases an icon for the Cygwin/X server process shows up in the 
notification area.

Both are started from a Windows shortcut:

C32 target: 
C:\win32app\cygwin\bin\run.exe C:\win32app\cygwin\rxvtermX.bat

C64 target: 
C:\win64app\cygwin\bin\run.exe C:\win64app\cygwin\urxvtermX.bat

The batch files that run are similar. Both start 'XWin' if it is not 
already running, then run 'rxvt/urxvt'.

Contents of 'rxvterm.bat' (C32):
 <at> echo off
(Continue reading)

paul | 16 Oct 07:41 2015

Xserver corresponds to display :1.0 instead of :0.0

I have a very simple ~/.startxwinrc:

   xrdb -load $HOME/.Xresources
   xterm -display :0.0 # xterm &
   exec sleep infinity

Recently, I found that the xterm wasn't launching.  I googled, read
some cygwin threads about X authorities, but have to admit, I have a
lot to learn about X windows.  Anyway, since I could open an xterm by
right clicking on the Cygwin/Xserver:1.0 app in the notification area
of Windows 7, I sneakily (OK, it wasn't the craftiest thing in the
world) echo'd $DISPLAY.  Lo, it was 1.0, and the following works fine:

   xterm -display :1.0 &

Yes, I know it says 1.0 in the tip for the Cygwin/Xserver:1.0 app, but
I didn't actually look at that detail until now, as I'm posting.

A google for the following doesn't turn up anything:

   cygwin xterm "-display :0.0" "display :1.0"

I'm wondering if this was a planned change in how X-windows works or
if something is awry with my setup, causing a server with display :0.0
to fail, and making go to :1.0.  I did a browse of the cygin announce
list on gmane (since the X-windows announce list is now obsolete), but
no joy.  And I would have expected anything to show up in my google

Can anyone point me to the description of this change?  If it is not a
(Continue reading)