RE: [ANNOUNCEMENT] Server Test 61

[Harold Hunt]

I need someone with a graphics card capable of 15 bits per pixel to run Test
61 and tell us what happens.  Also, run XWin.exe with
'XWin -fullscreen -depth 15' (when you are running Windows in some depth
other than 15) and let us know what happens.

Both of these situations are expected to not go well, but I need some
specifics.

Thanks for testing,

Harold

RE: [ANNOUNCEMENT] Server Test 61

[Harold Hunt]

Okay, I'll stick with the current lenghty-when-necessary format.

I'm glad they are helping people,

Harold

> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Jean-Claude Gervais
> Sent: Thursday, June 27, 2002 10:14 PM
> To: [EMAIL PROTECTED]
> Subject: RE: [ANNOUNCEMENT] Server Test 61
> 
> 
> I second that.
> 
> -Original Message-
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED]]On
> Behalf Of Franz Wolfhagen
> Sent: Thursday, June 27, 2002 3:58 AM
> To: [EMAIL PROTECTED]
> Subject: RE: [ANNOUNCEMENT] Server Test 61
> 
> 
> Your long changelogs are doing a very nice educational reading for me at
> least - I appreciate them very much...
> 
> Med venlig hilsen / Regards
> Franz Wolfhagen
> 

RE: [ANNOUNCEMENT] Server Test 61

[Jean-Claude Gervais]

I second that.

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
Behalf Of Franz Wolfhagen
Sent: Thursday, June 27, 2002 3:58 AM
To: [EMAIL PROTECTED]
Subject: RE: [ANNOUNCEMENT] Server Test 61


Your long changelogs are doing a very nice educational reading for me at
least - I appreciate them very much...

Med venlig hilsen / Regards
Franz Wolfhagen

RE: New Xfree User Question

[Martin Bosticky]

This has worked perfectly. Thank you very much. I am thinking it could
go into the instalation instructions as I don't recall seeing it anywhere.

-Original Message-
From: Florimon van Putte [mailto:[EMAIL PROTECTED]]
Sent: Thursday, 27 June 2002 17:18
To: [EMAIL PROTECTED]
Cc: '[EMAIL PROTECTED]'
Subject: RE: New Xfree User Question





Martin Bosticky wrote:
> Harold,
> 
> I am doing as you have said. I have now also downloaded the 
> previous version
> of XFree and that seems to be working fine on the same machine.
> 
> So I have no clue but perhaps the latest release has 
> something funny with
> the configuration? I would not know how to tell.


I've had the same problem with the disappearing xterm. When you run xterm
with the -hold option, you'll see what's going on: right before freezing it
prints "setuid failed: Permission denied" . As some other posters pointed
out in the past couple of days, with the latest cygwin release security has
been tightened a bit. For things like xterm to work, an entry for the user
that you're logged in as, has to be present in /etc/passwd. The problem is
that, when you install Cygwin from scratch, at post-install time, it only
creates entries in /etc/passwd for all the local accounts. If you're logged
in as a (non-local) domain user, you'll have to add an entry for it yourself
to /etc/passwd. It's easy to do so, all I had to do to get my own 'fputte'
account added was (from a cygwin prompt) :  "mkpasswd -d -u fputte >>
/etc/passwd" . After this, exit Cygwin, restart it, and you should be able
to run xterm.

rgds,
Florimon



> 
> Martin.
> 
> -Original Message-
> From: Harold Hunt [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, 27 June 2002 11:22
> To: Martin Bosticky; [EMAIL PROTECTED]
> Subject: RE: New Xfree User Question
> 
> 
> You're not supposed to launch startxwin.bat from a Cygwin 
> prompt, you are
> supposed to double-click the batch file from Windows Explorer 
> or you can
> launch startxwin.bat from a Windows command prompt (not a 
> Cygwin command
> prompt).
> 
> Harold
> 
> > -Original Message-
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED]]On Behalf Of Martin Bosticky
> > Sent: Wednesday, June 26, 2002 9:14 PM
> > To: '[EMAIL PROTECTED]'
> > Subject: RE: New Xfree User Question
> >
> >
> > Dear XFree crew,
> >
> > can I add that i also have the same problem and that I 
> tried to get the
> > latest cygwin snapshot as described in a recent email and 
> it didn't help.
> > Perhaps i have missed something during configuration i suppose
> > but the bash
> > shell seems to be working fine. I am running Windows 2000
> >
> > Martin.
> >
> > >I have run into a problem when I started to learn / use Xfree on my
> > >XP laptop.
> > >
> > >When I launch via /usr/X11R6/bin/startxwin.bat at the 
> Cygwin prompt,
> > >I get the background window, but the terminal window, which on my
> > >Win98 machine is my shell running bash, appears to be iconized in
> > >the upper left corner, and when I click on it, it disappears.
> > >
> > >I apologize for the awkward and no doubt technically 
> incorrect way I
> > >have explained this, but I was hoping someone would say, oh, I know
> > >what that idiot is babbling about.
> > >
> > >Wayne Keen
> > >
> >
> >
> > Martin Bosticky
> > Software Engineer
> > Opcom
> > Office +61 7 3371 1311
> > Fax +61 7 3371 1257
> > Email [EMAIL PROTECTED]
> > Web www.opcom.com.au 
> >
> >
> 

Re: Progress? (again, please try a snapshot)

[Christopher Faylor]

On Thu, Jun 27, 2002 at 08:24:55PM -0400, Harold Hunt wrote:
>Chris,
>
>> Does the log file contain any useful information, by any chance?
>
>None.  Cygwin/XFree86 doesn't get an error, only xterm does.
>
>> Do you think you could do a
>>
>> strace -ox:\somewhere\strace.out sh startxwin.sh , bzip2 strace.out,
>> and send it to me?
>
>I'll try to tomorrow.
>
>>Just to be clear, this is just as simple as running the xserver and
>>opening up an xterm, right?  Unfortunately, that works fine for me
>>under 1.3.11 and the snapshot.  I am running on Windows XP.  Don't know
>>why that would make a difference, though.
>
>This problem doesn't happen on my home Windows 2000 machine, nor does
>it happen on my NT Workstation 4.0 machine at work (though I haven't
>upgraded cygwin1.dll in a week or more).  The problem only happens on a
>Windows 2000 machine that I use at work (which I just installed Cygwin
>on two days ago).  Both machines at work are members of a *domain*
>while my home machine is not in a domain.  Also, I can only logon to
>both machines at work as a domain user, as I have no local account and
>I don't have administrator priveleges to create one (and it'd blow my
>cover if I told them I needed a local account for debugging
>Cygwin/XFree86 :)

Hmm.  If you do a:

mount -f -X -b c:\cygwin\usr\X11R6\bin /usr/X11R6/bin

does the problem go away, perchance?  I would expect it to.

cgf

RE: Progress? (again, please try a snapshot)

[Harold Hunt]

Chris,

> Does the log file contain any useful information, by any chance?

None.  Cygwin/XFree86 doesn't get an error, only xterm does.

> Do you think you could do a
>
> strace -ox:\somewhere\strace.out sh startxwin.sh , bzip2 strace.out,
> and send it to me?

I'll try to tomorrow.

> Just to be clear, this is just as simple as running the xserver and
> opening up an xterm, right?  Unfortunately, that works fine for me
> under 1.3.11 and the snapshot.  I am running on Windows XP.  Don't
> know why that would make a difference, though.

This problem doesn't happen on my home Windows 2000 machine, nor does it
happen on my NT Workstation 4.0 machine at work (though I haven't upgraded
cygwin1.dll in a week or more).  The problem only happens on a Windows 2000
machine that I use at work (which I just installed Cygwin on two days ago).
Both machines at work are members of a *domain* while my home machine is not
in a domain.  Also, I can only logon to both machines at work as a domain
user, as I have no local account and I don't have administrator priveleges
to create one (and it'd blow my cover if I told them I needed a local
account for debugging Cygwin/XFree86 :)

Yes, this is just as simple as running Cygwin/XFree86 with an xterm.  The
options to xterm do not affect the outcome.  The only message from xterm is
if you run 'xterm -hold', which keeps the xterm window open after the
command shell has exited.  In this case the error message, as previously
reported by others, is something like "setuid failed: Permission Denied".
This message comes from line 3814 in the main () function of xterm's main.c.
A link to xterm's main.c is here:

http://cvsweb.xfree86.org/cvsweb/xc/programs/xterm/main.c


Note: Cygwin/XFree86 hasn't updated any source files or build files since
the XFree86 4.2.0 release, except for the XWin.exe source code and binary.
In other words, this is obviously not something that we caused :(

Thanks for any help,

Harold

Re: Progress? (again, please try a snapshot)

[Christopher Faylor]

On Thu, Jun 27, 2002 at 02:30:59PM -0400, Harold L Hunt wrote:
>Chris,
>
>I just (at 1430 EDT) tried:
>
>cygwin1-20020627.dll.bz2
>
>The problem is still present.

Just to be clear, this is just as simple as running the xserver and
opening up an xterm, right?  Unfortunately, that works fine for me
under 1.3.11 and the snapshot.  I am running on Windows XP.  Don't
know why that would make a difference, though.

Does the log file contain any useful information, by any chance?

Do you think you could do a

strace -ox:\somewhere\strace.out sh startxwin.sh , bzip2 strace.out,
and send it to me?

It's possible that xterm will "just work" when you do that.  If
so, then you'll probably be able to hear my scream.

cgf

RE: Mouse dragging slow in XWin-Test56 with -emulate3buttons

[Bradey Honsinger]

I think the only reason that I set the timeout so high was because it wasn't
working--I vaguely remember having trouble getting the simultaneous button
presses to work, which makes sense now. If the timeout was always 1ms, no
wonder I had trouble! 

An error message in the log certainly wouldn't hurt, but I think it'll be a
rare enough problem that there's probably no real need. Anyone who would
read the log would probably check the list, anyway. If anything, I'd
probably put a note in the documentation (Table 3-1) or the FAQ (question
3.4) to the effect of: 

"Note: setting the timeout too high (>100ms) will make it difficult to drag
windows or select text, since XWin will wait to process the button1-down
event until it's sure that it's not a button3-down event." 

That's all pretty obvious now that I realize what's going on, but it took me
a while to figure it out.

- Bradey


-Original Message-
From: Stuart Adamson [mailto:[EMAIL PROTECTED]]
Sent: Thursday, June 27, 2002 3:00 AM
To: '[EMAIL PROTECTED]'
Subject: RE: Mouse dragging slow in XWin-Test56 with -emulate3buttons


> I didn't diff the sources, but it sounds like XWin was never using the
> timeout parameter to -emulate3buttons until this typo was 
> fixed.

Worse than that - XWin was ignoring the parameter and also the default
50ms and setting the timeout to 1 millisecond.

> In any case, even if it is a bug, I don't need a fix

We could ErrorF("emulate3buttons timeout >100ms.  Is this really what you
want?");

but how many people would read /tmp/XWin.log to see that this is a problem?


Stuart

FW: xfree success!

[Keen Wayne A Contr AFRL/MNGG]

>  -Original Message-
> From: Keen Wayne A Contr AFRL/MNGG  
> Sent: Thursday, June 27, 2002 2:16 PM
> To:   '[EMAIL PROTECTED]'; '[EMAIL PROTECTED]'
> Subject:  xfree success!
> 
> (1) I downloaded the newest (at least a couple of hours ago) snapshot of
> cygwin1.dll, yes, I renamed it and copied it over
> to /bin
> (2) I used some ideas on the xfree list, for shorthand, I am going to use
> my_domain, my_name for my domain name and
> user name, substitute your own:
> mkpasswd -l > /etc/passwd
> mkpasswd -d my_domain | grep "my_name" >> /etc/passwd
> Now, a couple of important notes here:
> In the original hints, they just used -d, and I was to damn stupid to
> realize I had to give a domain name after that. Then I had to remember
> what it was.
> I am on a large network.  This took a very LONG time.  I gave up and went
> to a meeting, it was finished when I got back.
> (3) In another classic Wayne is a moron moment, I immediately tried
> /usr/X11R6/bin/startx.  It did not work, because I was in the
> same window I did the mkpasswd in.  I closed that, opened a new one, and
> it worked!
> (4) Note for the startx to work, you have to have one of those .xinitrc
> files in your home directory.  You can copy the one from
> /etc/X11/xinit to your home and start from there.  You also (in theory)
> need to have a file called .Xauthority, which has the kicker that it
> will work if you just have an empty file by that name.  Now, this file
> gave me some errors early on, I tried moving it a minute ago,
> and things worked without it.
> 
> I am still working some issues with bash, but it works pretty well.
> Thanks to all those who were patient with me, while I thrashed around.
> As I said earlier, I am not sure what fixed my problem, some of the stuff
> above may be unneccessary.  I do know it is working.
> 
> Wayne Keen
> 

Re: Progress? (again, please try a snapshot)

[Harold L Hunt]

Chris,

I just (at 1430 EDT) tried:

cygwin1-20020627.dll.bz2


The problem is still present.

Harold

Re: Progress? (again, please try a snapshot)

[Christopher Faylor]

On Thu, Jun 27, 2002 at 11:10:16AM -0400, Christopher Faylor wrote:
>On Thu, Jun 27, 2002 at 10:50:28AM -0400, Harold L Hunt wrote:
>>[Please be careful to only reply to [EMAIL PROTECTED], I am only sending
>>this to [EMAIL PROTECTED] so that the Cygwin folks know what is going on.]
>>
>>Non-xterm clients work fine.  xterm does not work.
>>
>>The base problem here is that xterm calls getuid () to find out what the
>>current process's user id is.  Then it later calls setuid (), passing the same
>>value that was returned by getuid ().  For some reason, regardless of whether
>>you have run 'mkpasswd -d -u user_name >> /etc/passwd', the call to setuid ()
>>fails with Permission Denied.
>>
>>This is not something that the Cygwin/XFree86 folks changed, rather it was
>>something that was changed in Cygwin proper (think cygwin1.dll).  From our
>>perspective, and probably from the perspective of the Cygwin developers,
>>cygwin1.dll is broken when Cygwin/XFree86 doesn't work right.
>>
>>Thus, I'm going to guess that the Cygwin folks are working on this and that
>>you need to start testing the latest cygwin1.dll snapshots to help them, and
>>us, figure out when the problem is fixed.  I've got a machine now that has the
>>same problem so I will be testing snapshots as well, once a compile job finishes.
>>
>>Here is some information on installing a snapshot release of cygwin1.dll:
>>http://cygwin.com/ml/cygwin-xfree/2002-06/msg00383.html
>
>Thanks for *trying* a snapshot, Harold, and reporting on your experiences.
>
>I guess we'll keep plugging at this.  My time is very limited but I'll
>try to debug this X problem as soon as I have a chance.
>
>Until then if someone could 1) Try the very latest snapshot (the
>2002-06-26 snapshot changed several times yesterday) and 2) post an
>strace from a failing xterm.  It would help enormously.

FWIW, I can't duplicate this failure either with 1.3.11 or with the current
snapshot.  However, there were changes in the current snapshot which may
fix the problem.

I hope someone will be brave enough to try one.

cgf

Snapshot installation instructions:

To install a snapshot:

  1) Download the latest cygwin-20020???.dll.bz2 file from
 http://cygwin.com/snapshots/ .

  2) bunzip2 cygwin-20020???.dll.bz2

  3) Stop any running cygwin applications (sshd, inetd, bash, apache, etc.).

  4) copy c:\cygwin\bin\cygwin1.dll c:\cygwin\bin\cygwin1.dll.saf

  5) copy cygwin-2002.dll c:\cygwin\bin\cygwin1.dll

Obviously, you have to replace the 'c:\cygwin\bin' with the ms-dos path
name of your /bin directory.  You also *must* use Windows tools (e.g.,
"copy" or GUI "drag and drop") to copy the DLL to its new home since you
can't easily overwrite a busy DLL.

mkpasswd hints (was: Unable to use X session under...)

[Dawson, David W]

FYI,

If you know your login id and account (and you probably do, because
you use it every day), you can reduce the time and resulting passwd
file size by using the correct parameters to mkpasswd:
   mkpasswd -u {username} -d {domainname} >> /etc/passwd
E.g. if your login name is "funkyuser" and your domain is "SOMEWHERE",
the command is:
   mkpasswd -u funkyuser -d SOMEWHERE >> /etc/passwd

Note that the home directory on the created line is probably NOT on your
local machine (/home/funkyuser) but the network server location your
domain administrator set up for you (G:\sharedrive\funkyuser).  So, you
may want to edit the /etc/passwd created and change the string between
the 5th and 6th colons (:) to a local path (/home/funkyuser)

Cheers,
-D.
-
David Dawson
[EMAIL PROTECTED]
703-367-3885


-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Thursday, June 27, 2002 11:16 AM
To: [EMAIL PROTECTED]
Subject: Re: Unable to use X session under cygwin 1.3.11-3 on NT 4.0 sp.
6


Problem solved !!!,

Thanks to van Putte, Wolfhagen, Habacker et al. that
had already discussed the matter under a different
title.  Sorry for the inconvenience.

A hint for those who, like me, do not know much about
this stuff check for error beyond X and into xterm
behaviour:

1- Step to diagnostic

The new version of cygwin 1.3.11 (try cygcheck -s |
grep "cygwin" to see the cygwin version) there is
some change in the implementation of the security
(that among other thing do not permit you to open
xterm sessions).  You must adjust your system
consequently by defining a "real" user and not some
kind of Administrator (before I was Administrateur
and now daniel (my real login name)).

To diagnose my problem I added the "-hold" option to
the command xterm (xterm -hold &)in my startup
scripts (startxwin.sh and .xinitrc). That's when I
realised that it was a Permission problem and not an
X problem.  

2- X and xterm related problems and cygwin security

To redefine users see the thread this month :
-> xterm fails to start with "setuid failed:
Permission denied"
and the mkpasswd command.  Basically what it does it
to make a new password file with users and network
information.  Cygwin uses it for the login. 
Attention!!! Watch for big network, the file could
end up very long.  Here is what I did :
mkpasswd -l > /etc/passwd
mkpasswd -d | grep "daniel" >> /etc/passwd
(I knew my login name to be daniel)
And voila, I am now daniel@mymachine and no longuer
Administrateur@mymachine.  And the best of it xterm
now works (after some tweeking, read on).

3- Tweeking scripts for optimum functionning
When I finally got my X working (with the steps
outlined above), I had to add "-e /usr/bin/bash" to
the xterm command in my startup scripts (xterm -e
/usr/bin/bash &) because it could not find bash in
/bin/bash (thanks to -hold option for the hint).  I
also added an alias to my .bashrc "alias xterm='xterm
-e /usr/bin/bash'.

Thanks again all,

Hope this will be useful and good luck to others

DCT

Re: Unable to use X session under cygwin 1.3.11-3 on NT 4.0 sp. 6

[dct-linuq]

Problem solved !!!,

Thanks to van Putte, Wolfhagen, Habacker et al. that
had already discussed the matter under a different
title.  Sorry for the inconvenience.

A hint for those who, like me, do not know much about
this stuff check for error beyond X and into xterm
behaviour:

1- Step to diagnostic

The new version of cygwin 1.3.11 (try cygcheck -s |
grep "cygwin" to see the cygwin version) there is
some change in the implementation of the security
(that among other thing do not permit you to open
xterm sessions).  You must adjust your system
consequently by defining a "real" user and not some
kind of Administrator (before I was Administrateur
and now daniel (my real login name)).

To diagnose my problem I added the "-hold" option to
the command xterm (xterm -hold &)in my startup
scripts (startxwin.sh and .xinitrc). That's when I
realised that it was a Permission problem and not an
X problem.  

2- X and xterm related problems and cygwin security

To redefine users see the thread this month :
-> xterm fails to start with "setuid failed:
Permission denied"
and the mkpasswd command.  Basically what it does it
to make a new password file with users and network
information.  Cygwin uses it for the login. 
Attention!!! Watch for big network, the file could
end up very long.  Here is what I did :
mkpasswd -l > /etc/passwd
mkpasswd -d | grep "daniel" >> /etc/passwd
(I knew my login name to be daniel)
And voila, I am now daniel@mymachine and no longuer
Administrateur@mymachine.  And the best of it xterm
now works (after some tweeking, read on).

3- Tweeking scripts for optimum functionning
When I finally got my X working (with the steps
outlined above), I had to add "-e /usr/bin/bash" to
the xterm command in my startup scripts (xterm -e
/usr/bin/bash &) because it could not find bash in
/bin/bash (thanks to -hold option for the hint).  I
also added an alias to my .bashrc "alias xterm='xterm
-e /usr/bin/bash'.

Thanks again all,

Hope this will be useful and good luck to others

DCT

Re: Progress? Still debugging [cgf or someone from cygwin list please comment]

[Christopher Faylor]

On Thu, Jun 27, 2002 at 10:50:28AM -0400, Harold L Hunt wrote:
>[Please be careful to only reply to [EMAIL PROTECTED], I am only sending
>this to [EMAIL PROTECTED] so that the Cygwin folks know what is going on.]
>
>Non-xterm clients work fine.  xterm does not work.
>
>The base problem here is that xterm calls getuid () to find out what the
>current process's user id is.  Then it later calls setuid (), passing the same
>value that was returned by getuid ().  For some reason, regardless of whether
>you have run 'mkpasswd -d -u user_name >> /etc/passwd', the call to setuid ()
>fails with Permission Denied.
>
>This is not something that the Cygwin/XFree86 folks changed, rather it was
>something that was changed in Cygwin proper (think cygwin1.dll).  From our
>perspective, and probably from the perspective of the Cygwin developers,
>cygwin1.dll is broken when Cygwin/XFree86 doesn't work right.
>
>Thus, I'm going to guess that the Cygwin folks are working on this and that
>you need to start testing the latest cygwin1.dll snapshots to help them, and
>us, figure out when the problem is fixed.  I've got a machine now that has the
>same problem so I will be testing snapshots as well, once a compile job finishes.
>
>Here is some information on installing a snapshot release of cygwin1.dll:
>http://cygwin.com/ml/cygwin-xfree/2002-06/msg00383.html

Thanks for *trying* a snapshot, Harold, and reporting on your experiences.

I guess we'll keep plugging at this.  My time is very limited but I'll
try to debug this X problem as soon as I have a chance.

Until then if someone could 1) Try the very latest snapshot (the
2002-06-26 snapshot changed several times yesterday) and 2) post an
strace from a failing xterm.  It would help enormously.

cgf

RE: Progress? Still debugging [cgf or someone from cygwin list please comment]

[Keen Wayne A Contr AFRL/MNGG]

This is a problem, possibly in addition to my sub-moronic 
idiocy?

Appreciate the update sir,

Wayne Keen

-Original Message-
From: Harold L Hunt [mailto:[EMAIL PROTECTED]]
Sent: Thursday, June 27, 2002 9:58 AM
To: Keen Wayne A Contr AFRL/MNGG; '[EMAIL PROTECTED]'
Subject: Re: Progress? Still debugging [cgf or someone from cygwin list
please comment]


Just a quick note:

This problem is not fixed in the 20020626 cygwin1.dll snapshot.

Harold

Re: Progress? Still debugging [cgf or someone from cygwin list please comment]

[Harold L Hunt]

Just a quick note:

This problem is not fixed in the 20020626 cygwin1.dll snapshot.

Harold

Re: Progress? Still debugging [cgf or someone from cygwin list please comment]

[Harold L Hunt]

Wayne,

[Please be careful to only reply to [EMAIL PROTECTED], I am only sending
this to [EMAIL PROTECTED] so that the Cygwin folks know what is going on.]

Non-xterm clients work fine.  xterm does not work.

The base problem here is that xterm calls getuid () to find out what the
current process's user id is.  Then it later calls setuid (), passing the same
value that was returned by getuid ().  For some reason, regardless of whether
you have run 'mkpasswd -d -u user_name >> /etc/passwd', the call to setuid ()
fails with Permission Denied.

This is not something that the Cygwin/XFree86 folks changed, rather it was
something that was changed in Cygwin proper (think cygwin1.dll).  From our
perspective, and probably from the perspective of the Cygwin developers,
cygwin1.dll is broken when Cygwin/XFree86 doesn't work right.

Thus, I'm going to guess that the Cygwin folks are working on this and that
you need to start testing the latest cygwin1.dll snapshots to help them, and
us, figure out when the problem is fixed.  I've got a machine now that has the
same problem so I will be testing snapshots as well, once a compile job finishes.

Here is some information on installing a snapshot release of cygwin1.dll:
http://cygwin.com/ml/cygwin-xfree/2002-06/msg00383.html


Until further notice, consider your bug acknowledged and in a state of being
repared.  Feel free to post your results with the latest snapshot to
[EMAIL PROTECTED], but don't expect any further information until the
problem is fixed.


Harold




Keen Wayne A Contr AFRL/MNGG <[EMAIL PROTECTED]> said:

> OK, I changed strategy a little bit. I started working down the startx path.
> I moved the .xinitrc to my home and ran
> startx from the bash prompt.  It then complained of no .XAuthority file.  I
> googled a bit, and found a reference to
> an empty file being OK.  So I created one.  This led to some progress, the
> window comes up, with the clock even, 
> but when I click on anything it bombs back out with a message about fatal IO
> error 113.
> 
> startxwin.bat is still behaving the same...
> 
> Wayne
> 

RE: x-windows

[Stuart Adamson]

 http://cygwin.com/xfree/docs/ug/using.html#using-starting


Stuart

On Thu, Jun 27, 2002 at 08:36:43AM -0500, Henning, Brian wrote:
>hello-
>I have installed the XFree86 package for cygwin.  how to I start up X?
>i have tried 'xterm' 'startx' and i get nothing.  I found an xterm
>binary but when I start it up i get an error about setting the display.
>thanks,
>brian

The Cygwin/XFree86 mailing list is [EMAIL PROTECTED]  I've
redirected this message there.

cgf



Evolution is the investment banking and venture 
capital industry's first choice for practical advice 
on strategy, business process and the application of 
advanced technology. 

EvolutionTel: +44 (0) 20 7664 6640 
Peninsular House Fax: +44 (0) 20 7664 6641 
30-36 Monument Street
London EC3R 8LJ  URL: http://www.evolution.net 
United Kingdom 
__ 
The information in this Internet e-mail is confidential 
and is intended solely for the addressee.  Access, 
copying or re-use of information in it by anyone else 
is unauthorised.  Any views or opinions presented are 
solely those of the author and do not necessarily 
represent those of Evolution or any of its affiliates. 
If you are not the intended recipient please contact 
Evolution, London, +44 (0) 20 7664 6640 
_

Re: x-windows

[Harold L Hunt]

First, wrong mailing list.  Use [EMAIL PROTECTED]

Second, RTFM:
http://xfree86.cygwin.com/docs/ug/using.html#using-starting

Harold

"Henning, Brian" <[EMAIL PROTECTED]> said:

> hello-
> I have installed the XFree86 package for cygwin. how to I start up X? i have
> tried 'xterm' 'startx'  and i get nothing. I found an xterm binary but when
> I start it up i get an error about setting the display.
> thanks,
> brian
> 
> --
> Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
> Bug reporting: http://cygwin.com/bugs.html
> Documentation: http://cygwin.com/docs.html
> FAQ:   http://cygwin.com/faq/
> 
> 

Re: x-windows

[Christopher Faylor]

On Thu, Jun 27, 2002 at 08:36:43AM -0500, Henning, Brian wrote:
>hello-
>I have installed the XFree86 package for cygwin.  how to I start up X?
>i have tried 'xterm' 'startx' and i get nothing.  I found an xterm
>binary but when I start it up i get an error about setting the display.
>thanks,
>brian

The Cygwin/XFree86 mailing list is [EMAIL PROTECTED]  I've
redirected this message there.

cgf

RE: New Xfree User Question

[CygX Forever]

I know that for a fact since early this year but I launch startxwin.bat from 
a Cygwin prompt anyway. The reason is that if I double-click the batch file 
from Windows Explorer, that batch file will *not* clean up my 
/tmp/.X11-unix/X0 file the next time, which means I cannot run it again 
subsequently. I'm on Windows XP. Apparently, my WinXP user priviledges are 
not the same as Cygwin priviledges even if the loginid are the same. How do 
I fix it so that I can launch from Windows Explorer?

Thanks
ewu


>From: "Harold Hunt" <[EMAIL PROTECTED]>
>To: "Martin Bosticky" <[EMAIL PROTECTED]>,<[EMAIL PROTECTED]>
>Subject: RE: New Xfree User Question
>Date: Wed, 26 Jun 2002 21:22:19 -0400
>
>You're not supposed to launch startxwin.bat from a Cygwin prompt, you are
>supposed to double-click the batch file from Windows Explorer or you can
>launch startxwin.bat from a Windows command prompt (not a Cygwin command
>prompt).
>
>Harold
>
> > -Original Message-
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED]]On Behalf Of Martin Bosticky
> > Sent: Wednesday, June 26, 2002 9:14 PM
> > To: '[EMAIL PROTECTED]'
> > Subject: RE: New Xfree User Question
> >
> >
> > Dear XFree crew,
> >
> > can I add that i also have the same problem and that I tried to get the
> > latest cygwin snapshot as described in a recent email and it didn't 
>help.
> > Perhaps i have missed something during configuration i suppose
> > but the bash
> > shell seems to be working fine. I am running Windows 2000
> >
> > Martin.
> >
> > >I have run into a problem when I started to learn / use Xfree on my
> > >XP laptop.
> > >
> > >When I launch via /usr/X11R6/bin/startxwin.bat at the Cygwin prompt,
> > >I get the background window, but the terminal window, which on my
> > >Win98 machine is my shell running bash, appears to be iconized in
> > >the upper left corner, and when I click on it, it disappears.
> > >
> > >I apologize for the awkward and no doubt technically incorrect way I
> > >have explained this, but I was hoping someone would say, oh, I know
> > >what that idiot is babbling about.
> > >
> > >Wayne Keen
> > >
> >
> >
> > Martin Bosticky
> > Software Engineer
> > Opcom
> > Office +61 7 3371 1311
> > Fax +61 7 3371 1257
> > Email [EMAIL PROTECTED]
> > Web www.opcom.com.au 
> >
> >


_
Join the world’s largest e-mail service with MSN Hotmail. 
http://www.hotmail.com

Progress? Still debugging

[Keen Wayne A Contr AFRL/MNGG]

OK, I changed strategy a little bit. I started working down the startx path.
I moved the .xinitrc to my home and ran
startx from the bash prompt.  It then complained of no .XAuthority file.  I
googled a bit, and found a reference to
an empty file being OK.  So I created one.  This led to some progress, the
window comes up, with the clock even, 
but when I click on anything it bombs back out with a message about fatal IO
error 113.

startxwin.bat is still behaving the same...

Wayne

Re: Unable to use X session under cygwin 1.3.11-3 on NT 4.0 sp. 6

[Bernt Guldbrandtsen]

Hello all,

I would like to add some information to this.

It is possible to lauch Xfree under Windows 2000 5.00.2195, SP 2 Danish 
version with cygwin 1.3.11-3 using xwin& twm&. However if I then try to 
launch an xterm I get the placement cursor. xterm dies without any error 
messages when I then click in order to place the xterm window.

Downgrading to cygwin 1.3.10 removes the problem.

Hence, it appears that the problem is caused by xterm in combination with 
cygwin 1.3.11-3.

Best regards,

Bernt Guldbrandtsen
8<--
Cygwin Package Information
Last downloaded files to: C:\Documents and Settings\bgu\Dokumenter\cygwin
Last downloaded files from: 
ftp://ftp.nas.nasa.gov/mirrors/cygwin.com/pub/cygwin

Package Version
XFree86-base4.2.0-1
XFree86-bin 4.2.0-1
XFree86-etc 4.2.0-1
XFree86-f1004.2.0-2
XFree86-fenc4.2.0-2
XFree86-fnts4.2.0-2
XFree86-fscl4.2.0-2
XFree86-lib 4.2.0-3
XFree86-man 4.2.0-1
XFree86-prog4.2.0-1
XFree86-startup-scripts4.2.0-2
XFree86-xserv   4.2.0-7
_update-info-dir00011-1
ash 20020131-1
autoconf2.53a-1
autoconf-devel  2.53a-1
autoconf-stable 2.13-4
automake1.6.1-1
automake-devel  1.6.1-3
automake-stable 1.4p5-5
bash2.05a-3
bc  1.06-1
binutils20011002-1
bison   1.35-1
byacc   1.9-1
bzip2   1.0.2-2
ccache  1.9-1
clear   1.0-1
cpio2.4.2
cron3.0.1-6
crypt   1.0-1
ctags   5.2-1
curl7.9.8-1
cvs 1.11.0-1
cygrunsrv   0.95-1
cygutils1.1.1-1
cygwin  1.3.11-3
cygwin-doc  1.0-1
db2 2.7.7-3
dejagnu 20010117-1
diff1.0-1
diffutils   2.8.1-1
ed  0.2-1
enscript1.6.3-2
expat   1.95.3-2
expect  20010117-1
file3.37-1
fileutils   4.1-1
findutils   4.1.7-4
flex2.5.4-2
gawk3.0.4-1
gcc 2.95.3-5
gdb 20010428-3
gdbm1.8.0-4
gettext 0.11.2-2
gnupg   1.0.7-1
gperf   0.0
grep2.5-1
groff   1.17.2-1
gsl 1.1.1-1
gzip1.3.2-1
indent  2.2.8-1
inetutils   1.3.2-17
jbigkit 1.2-6
jpeg6b-7
keychain1.8-1
less374-1
libbz2_01.0.2-1
libbz2_11.0.2-2
libdb2  2.7.7-3
libdb2-devel2.7.7-3
libiconv2   1.8-2
libintl 0.10.38-3
libintl10.10.40-1
libintl20.11.2-2
libncurses5 5.2-1
libncurses6 5.2-8
libpng  1.2.3-1
libpng101.0.13-3
libpng10-devel  1.0.13-3
libpng121.2.3-1
libpng12-devel  1.2.3-1
libpng2 1.0.12-1
libpopt01.6.4-4
libreadline44.1-2
libreadline54.2a-1
libtool 20020202a-1
libtool-devel   20020502-2
libtool-stable  1.4.2-2
libxml2 2.4.17-1
libxslt 1.0.13-1
links   0.96-1
login   1.4-3
lynx2.8.4-1
m4  0.0
make3.79.1-7
man 1.5g-2
mingw   20010917-1
mingw-runtime   2.0-2
mktemp  1.4-1
mt  2.0.1-1
ncftp   3.1.3-1
ncurses 5.2-8
newlib-man  20001118-1
opengl  1.1.0-6
openssh 3.4p1-1
openssl 0.9.6d-1
openssl-devel   0.9.6d-1
patch   2.5-3
pcre3.7-1
perl5.6.1-2
pkgconfig   0.12.0-1
popt1.6.4-4
python  2.2.1-1
rcs 5.7-3
readline4.2a-1
regex   4.4-2
rsync   2.5.5-1
rxvt2.7.2-10
sed 3.02-1
sh-utils2.0-2
sharutils   4.2.1-2
shellutils  0.0
shutdown1.2-2
swig1.3.11-1
tar 1.13.19-1
tcltk   20001125-1
tcsh6.11.00-4
termcap 20020403-1
terminfo5.2-3
texinfo 4.2-3
textutils   2.0.21-1
tiff3.5.7-1
time1.7-1
ttcp19980512-1
ucl 1.01-1
units   1.77-1
unzip   5.50-1
vim 6.1-2
w32api  1.5-1
wget1.8.1-1
which   1.5-1
xpm 4.0.0-2
xpm-nox 4.2.0-1
zip 2.3-2
zlib1.1.4-1
zsh 4.0.4-1


Cygwin Win95/NT Configuration Diagnostics
Current System Time: Thu Jun 27 15:30:33 2002

Windows 20

Continuing debug

[Keen Wayne A Contr AFRL/MNGG]

OK, I tried dropping to the previous version of Cygwin's xfree.  Same
problem.

Next, I tried Florimon's advice.  I was slightly confused, so I may have
screwed things up:

(1) First, I assumed 'fputte' was some account name that was personal to
that setup.  So, I tried to see who I am
throughwhoami.  It told me administrator, so I used that in the
suggested command, modified for Administrator,
i.e.

mkpasswd -d -u Administrator >> /etc/passwd

Cygwin informed me that it could not find that user.

(2) I tried running through startxwin.sh, same problem.

Wayne

Re: Next step in XFREE debug for New-B

[Nick THOMPSON]

Isn't this just another case of xterm not working in recent releases
(permission denied). Seems to be something to do with /etc/passwd not
having an entry for you user name and only seems to be a problem on
NT/Win2k (& XP?) which have better security. Look back at the last few
days posts. I've half heartedly tried these fixes, which don't seem to
work for me but YMMV.

Nick.

On Thu, 2002-06-27 at 13:30, Keen Wayne A Contr AFRL/MNGG wrote:
I was told I was doing it wrong, i.e.

"You're not supposed to launch startxwin.bat from a Cygwin prompt, you are
supposed to double-click the batch file from Windows Explorer or you can
launch startxwin.bat from a Windows command prompt (not a Cygwin command
prompt). 
Harold"

To keep you updated, when I did it correctly, the same result occurs, i.e.
the main window appears, acqua-marine background, with a small iconized
window labeled bash.  The main window is labeled Cygwin/XFree86.  The cursor
has the pattern of something designating the corner of something.  If I
click on the icon labeled bash, it disappears.  If I left click in the main
window, I get a menu which includes xterm.  If I click on that, I get an
icon labeled untitled, if I click on that, or click anywhere, it disappears.
The suiggestion was made last night to try the previous version of XFree,
which I will do.  I do wish to note that I have the new version of XFree on
my home computer, running Win98, and this does not occur.  This does not
occur even if I incorrectly call the batch file from the Cygwin prompt.
Will keep the list updated, and I appreciate the patience and help.

Wayne

Next step in XFREE debug for New-B

[Keen Wayne A Contr AFRL/MNGG]

I was told I was doing it wrong, i.e.

"You're not supposed to launch startxwin.bat from a Cygwin prompt, you are
supposed to double-click the batch file from Windows Explorer or you can
launch startxwin.bat from a Windows command prompt (not a Cygwin command
prompt). 
Harold"

To keep you updated, when I did it correctly, the same result occurs, i.e.
the main window appears, acqua-marine background, with a small iconized
window labeled bash.  The main window is labeled Cygwin/XFree86.  The cursor
has the pattern of something designating the corner of something.  If I
click on the icon labeled bash, it disappears.  If I left click in the main
window, I get a menu which includes xterm.  If I click on that, I get an
icon labeled untitled, if I click on that, or click anywhere, it disappears.
The suiggestion was made last night to try the previous version of XFree,
which I will do.  I do wish to note that I have the new version of XFree on
my home computer, running Win98, and this does not occur.  This does not
occur even if I incorrectly call the batch file from the Cygwin prompt.
Will keep the list updated, and I appreciate the patience and help.

Wayne

Unable to use X session under cygwin 1.3.11-3 on NT 4.0 sp. 6

[dct-linuq]

Hello all, thanks for listening,

I have a problem starting/working in Xfree under
cygwin.  I installed Xfree manually some time ago and
figured that it would be easier maintaining it under
the setup.exe by cygwin.  I uninstalled X and
proceeded to install it from scratch with the cygwin
utility setup.exe (selecting the base package).
Unfortunately, the new installation did not work
properly.  Unpon seeing that, I unsinstalled the
package unsing the standard setup.exe utility and
removed the /etc/X11 and the /usr/X11R6 branches (rm
-Rf) to make sure no old config files would remain. I
reinstalled the X base package with setup.exe and it
still does not work. I have tried to start X using
the startx and the startxwin.sh methods without
complete success. 
They result in different behaviours however...

1- Starting X with startxwin.sh from bash in
/dev/conin

When starting X with the command startxwin.sh I
manage to get X running with the main window with the
aquamarine4 background.  I even get the mouse shape
for to indicate the position of a new window (xterm).
 When I try to position the window (which is called
bash or unnamed), the mouse switch to the traditional
X but no xterm appears.  I can get the the twm menu
with most functionalities working (show iconmgr,
hide, move , delete, etc.) but no xterm.  I get the
mouse changing shape but no window appears.  Just in
case, I join the /tmp/Xwin.log file at the end.

2- Starting X with startx from bash in /dev/conin

Using startx command leaves me hanging for a few
second.  Then ne main window appears followed by the
clock that is specified in the .xinitrc file in ~/. 
X stop and the main window disapears with some error
messages :

waiting for X server to shut down XIO: fatal IO error
104  on X server ":0.0"
after 279 requests <278 known processed> with 2
events remaining.
XIO: fatal IO error 110  on X server ":0.0"
after 58 requests <49 known processed> with 0 events
remaining.

(the number of requests varies from time to time)

I provide at the end the ~/.xinitrc.  The
startxwin.sh is the standard one that comes with the
package.  I have added a few lines in the ~/.xinitrc
that were working in the old manual installation of
X. I also provide information that may be useful like
the version of packages.

I would truely appreciate any help to find and solve
this problem.  Any ideas or thoughts would be most
welcome.
==
Daniel Chamberland-Tremblay
==

FILES :

++
copy of /tmp/XWin.log

ddxProcessArgument () - Initializing default screens
winInitializeDefaultScreens - w 1280 h 960
winInitializeDefaultScreens - Returning
_XSERVTransmkdir: Owner of /tmp/.X11-unix should be
set to root
winDetectSupportedEngines () - Windows NT/2000
winDetectSupportedEngines () - DirectDraw installed
winDetectSupportedEngines () - Allowing PrimaryDD
winDetectSupportedEngines () - Returning, supported
engines 001b
winSetEngine () - Using Shadow DirectDraw
winAdjustVideoModeShadowDD () - Using Windows display
depth of 32 bits per pixel
winAdjustForAutoHide - Original WorkArea: 0 0 932
1280
winAdjustForAutoHide - Adjusted WorkArea: 0 0 932
1280
winCreateBoundingWindowWindowed () - WindowClient w
1274 h 907 r 1274 l 0 b 907 t 0
winCreateBoundingWindowWindowed () -  Returning
winInitVisualsShadowDD () - Masks 00ff ff00
00ff BPRGB 8 d 32
winCreateDefColormap () - Deferring to
fbCreateDefColormap ()
winScreenInit () - returning
Could not init font path element
/usr/X11R6/lib/X11/fonts/Speedo/, removing from list!
Could not init font path element
/usr/X11R6/lib/X11/fonts/Type1/, removing from list!
Could not init font path element
/usr/X11R6/lib/X11/fonts/100dpi/, removing from list!


++
copy of ~/.xinitrx

#!/bin/sh
# $Xorg: xinitrc.cpp,v 1.3 2000/08/17 19:54:30 cpqbld
Exp $ userresources=$HOME/.Xresources
usermodmap=$HOME/.Xmodmap.cf2
sysresources=/usr/X11R6/lib/X11/xinit/.Xresources
sysmodmap=/usr/X11R6/lib/X11/xinit/.Xmodmap # merge
in defaults and keymaps if [ -f $sysresources ]; then
xrdb -merge $sysresources
fi if [ -f $sysmodmap ]; then
xmodmap $sysmodmap
fi if [ -f $userresources ]; then
xrdb -merge $userresources
fi if [ -f $usermodmap ]; then
xmodmap $usermodmap
fi # start some nice programs twm &
xclock -geometry 50x50-1+1 &
#xterm -geometry 80x30+494+51 -bg black -fg white &
#xterm -geometry 80x20+494-0 -bg black -fg white &
#exec xterm -geometry 80x66+0+0 -bg black -fg white
-name login
INFO :
xterm is persent in /usr/X11R6/bin/xterm
$PATH is
/usr/X11R6/bin:/usr/local/bin:/usr/bin:/bin:/cygdrive
/c/WINNT/system32:/cygdrive/c/WINNT:/cygdrive/c/lgc/o
rant/bin:/cygdrive/c/WINNT/system32/nls/ENGLISH:?

Part of the cygcheck -s output :
Found: F:\unix\bin\bash.exe
Found: F:\unix\bin\cat.exe
Found: F:\unix\bin\cpp.exe
Found: F:\unix\usr\local\bin\find.exe
Found: F:\unix

RE: Mouse dragging slow in XWin-Test56 with -emulate3buttons

[Stuart Adamson]

> I didn't diff the sources, but it sounds like XWin was never using the
> timeout parameter to -emulate3buttons until this typo was 
> fixed.

Worse than that - XWin was ignoring the parameter and also the default
50ms and setting the timeout to 1 millisecond.

> In any case, even if it is a bug, I don't need a fix

We could ErrorF("emulate3buttons timeout >100ms.  Is this really what you
want?");

but how many people would read /tmp/XWin.log to see that this is a problem?


Stuart

Re: solaris XDMCP session freezing up

[J S]

I forgot to mention that this works on one Solaris box I'm trying but not on 
the other. They are both Solaris version 2.8.



>Hi,
>
>I'm trying to get a solaris box logon screen to run via xwin using the
>following command:
>
>xwin -query remotehostName -from localhostName -fp tcp/remotehostName:7100
>
>The problem is that after the solaris hourglass cursor appears the session
>seems to freeze up. I know the FAQ says this won't work on 24 bit depth, 
>but
>I've also tried 16 bit and 256 Colors (is that 8 bit?) and had no more 
>luck.
>
>Is there anything else I can try?
>
>Thanks for your help,
>
>JS.
>
>
>
>_
>MSN Photos is the easiest way to share and print your photos:
>http://photos.msn.com/support/worldwide.aspx
>


_
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp.

RE: [ANNOUNCEMENT] Server Test 61

[Franz Wolfhagen]

Your long changelogs are doing a very nice educational reading for me at
least - I appreciate them very much...

Med venlig hilsen / Regards
Franz Wolfhagen

solaris XDMCP session freezing up

[J S]

Hi,

I'm trying to get a solaris box logon screen to run via xwin using the 
following command:

xwin -query remotehostName -from localhostName -fp tcp/remotehostName:7100

The problem is that after the solaris hourglass cursor appears the session 
seems to freeze up. I know the FAQ says this won't work on 24 bit depth, but 
I've also tried 16 bit and 256 Colors (is that 8 bit?) and had no more luck.

Is there anything else I can try?

Thanks for your help,

JS.



_
MSN Photos is the easiest way to share and print your photos: 
http://photos.msn.com/support/worldwide.aspx