Testing CygWin XFree86 with multiple monitors

[Øyvind Harboe]

(This is a repost, but with link to source + binary this time).

I'm using CygWin XFree86 with a dual monitor setup and a single monitor
setup. In my experience there are, not surprisingly, more problems with
the dual monitor setup. 

This made me think a bit about how multi-monitor CygWin XFree86 could
get more testing.

Is there any interest amongst CygWin XFree86 testers/developers in a
virtual device driver that will do the following?

- allow adding of any number of virtual video cards. E.g. test CygWin
XFree86 with 10 video cards? No problem! :-)
- the video cards are "visible" indirectly by using e.g. the
Accessibility->Magnifier
- resolution is currently fixed at ~4000x2000x32bit, but it could be
made configurable
- the virtual device driver works by allocating a RAM buffer where all
rendering takes place. Windows does all the rendering and it seems to be
feature complete. OpenGL works, though I wouldn't hold my breath for
DirectX apps.

The source code is currently collecting dust, and I'm sure I could
convince the owner to contribute it to the open source community if
there is enough interest.


Source and binaries are available for download here:

http://www.zylin.com/videodriver.tar.bz2

-- 
Øyvind Harboe
http://www.zylin.com

Re: Testing CygWin XFree86 with multiple monitors

[Alexander Gottwald]

On Mon, 16 Aug 2004, Øyvind Harboe wrote:

> I'm using CygWin XFree86 with a dual monitor setup and a single monitor
> setup. In my experience there are, not surprisingly, more problems with
> the dual monitor setup. 
> 
> This made me think a bit about how multi-monitor CygWin XFree86 could
> get more testing.
> 
> Is there any interest amongst CygWin XFree86 testers/develoeprs in a
> virtual device driver that will do the following?
> 
> - allow adding of any number of virtual video cards. E.g. test CygWin
> XFree86 with 10 video cards? No problem! :-)
> - the video cards are "visible" indirectly by using e.g. the
> Accessibility->Magnifier
> - resolution is currently fixed at ~4000x2000x32bit, but it could be
> made configurable
> - the virtual device driver works by allocating a RAM buffer where all
> rendering takes place. Windows does all the rendering and it seems to be
> feature complete. OpenGL works, though I wouldn't hold my breath for
> DirectX apps.
> 
> The source code is currently collecting dust, and I'm sure I could
> convince the owner to contribute it to the open source community if
> there is enough interest.

It sounds promising. Unfortunatly I don't have the possibility to test
such a setup but I'll see if I can get access to one.

bye
ago
-- 
 [EMAIL PROTECTED] 
 http://www.gotti.org   ICQ: 126018723

Testing CygWin XFree86 with multiple monitors

[Øyvind Harboe]

I'm using CygWin XFree86 with a dual monitor setup and a single monitor
setup. In my experience there are, not surprisingly, more problems with
the dual monitor setup. 

This made me think a bit about how multi-monitor CygWin XFree86 could
get more testing.

Is there any interest amongst CygWin XFree86 testers/develoeprs in a
virtual device driver that will do the following?

- allow adding of any number of virtual video cards. E.g. test CygWin
XFree86 with 10 video cards? No problem! :-)
- the video cards are "visible" indirectly by using e.g. the
Accessibility->Magnifier
- resolution is currently fixed at ~4000x2000x32bit, but it could be
made configurable
- the virtual device driver works by allocating a RAM buffer where all
rendering takes place. Windows does all the rendering and it seems to be
feature complete. OpenGL works, though I wouldn't hold my breath for
DirectX apps.

The source code is currently collecting dust, and I'm sure I could
convince the owner to contribute it to the open source community if
there is enough interest.


-- 
Øyvind Harboe
http://www.zylin.com

Re: Problem with Gnuplot under Cygwin/XFree86

[Dr. Volker Zell]

> "Harold" == Harold L Hunt writes:

Harold> Have you tried the Cygwin/X gnuplot package instead of the one that
Harold> you compiled?  It is possible that Volker has already fixed this
Harold> problem in his Cygwin-specific patch.  If not, he reads this list and
Harold> maybe he will want to try to fix it.  ;)

I can confirm that my version also exhibits this problem :-(

Harold> Harold

Ciao
  Volker

Re: Problem with Gnuplot under Cygwin/XFree86

[Harold L Hunt II]

Have you tried the Cygwin/X gnuplot package instead of the one that you 
compiled?  It is possible that Volker has already fixed this problem in 
his Cygwin-specific patch.  If not, he reads this list and maybe he will 
want to try to fix it.  ;)

Harold

I described a problem with Gnuplot under Cygwin/XFree86 here:



http://groups.google.com/groups?dq=&hl=en&lr=&ie=UTF-8&threadm=c3mrn7%24oko%241%40nets3.rz.RWTH-Aachen.DE&prev=/groups%3Fhl%3Den%26lr%3D%26ie%3DUTF-8%26group%3Dcomp.graphics.apps.gnuplot





In the opinion of one of the Gnuplot gurus (Hans BB), it's a Cygwin/XFree86 problem not a Gnuplot problem. I don't know. Do any of the cygwin-xfree86 authorities agree? Either way, I'd like to be able to resolve it.



BTW, is there an FAQ that describes the correct way to post a reply to a message in this group so it registers as a follow-up message.



Thanks,



jjo

Problem with Gnuplot under Cygwin/XFree86

[ncokwqc02]

I described a problem with Gnuplot under Cygwin/XFree86 here:



http://groups.google.com/groups?dq=&hl=en&lr=&ie=UTF-8&threadm=c3mrn7%24oko%241%40nets3.rz.RWTH-Aachen.DE&prev=/groups%3Fhl%3Den%26lr%3D%26ie%3DUTF-8%26group%3Dcomp.graphics.apps.gnuplot





In the opinion of one of the Gnuplot gurus (Hans BB), it's a Cygwin/XFree86 problem 
not a Gnuplot problem. I don't know. Do any of the cygwin-xfree86 authorities agree? 
Either way, I'd like to be able to resolve it.



BTW, is there an FAQ that describes the correct way to post a reply to a message in 
this group so it registers as a follow-up message.



Thanks,



jjo





--

Protect yourself from spam, 

use http://sneakemail.com

Use ReflectionX client with Cygwin/XFree86 X server?

[ncokwqc02]

Is it possible to set up my PC so that Cygwin/XFree86 is the X server and ReflectionX 
is the X client?





I have Cygwin and WRQ/ReflectionX both installed on my PC.



There are certain aspects of how XFree86 handles X clients that I don't like compared 
to how ReflectionX can handle them, so I don't generally use XFree86 with Cygwin.





However, I think I have an application that would benefit from a local X11 server.



I would like to build an X11 version of gnuplot under Cygwin, so I can start an 
'xterm' on my PC from Cygwin and run gnuplot locally.



If I can use Cygwin/XFree86 to create the X window commands and use ReflectionX to 
display them, that would satisfy my requirements.





Any suggestions or pointers to a relevant FAQ would be appreciated.



Thanks,



jjo

Re: cygwin/xfree86/emacs problems after upgrading

[Igor Pechtchanski]

On Thu, 26 Feb 2004, Takuma Murakami wrote:

> Igor,
>
> > Yes, it's a neat trick *if* the only thing people changed was the install
> > drive.  If they change the path, all bets are off.  I'm surprised you
> > don't actually customize startxwin.bat (and similar files, like
> > startxdmcp.bat) in a postinstall script (which can run under a Cygwin
> > shell, and thus know the root of the install).  You could choose a
> > template value, e.g. "%$CYGWIN_ROOT$%", and replace that with "`cygpath -w
> > /`" using, say, sed.  If you're interested, I could whip up an example
> > postinstall script for you in the next week or so.
>
> I'm interested in that trick out of curiosity.
> Could you show me your boilerplate?
>
> Takuma Murakami

Well, something like the script below (untested) should do...  This uses
'%$CYGWIN_ROOT$%' as the template string.
HTH,
Igor

-- BEGIN /etc/postinstall/fix-startxwin.sh --
#!/bin/sh

fix_cygwin_root() {
  TMPNAME="$1.$$" && \
  mv "$1" "$TMPNAME" && \
  sed 's/%\$CYGWIN_ROOT\$%/"'"`cygpath -w /`"'"/' "$TMPNAME" > "$1" && \
  rm "$TMPNAME"
}

cd /usr/X11R6/bin && \
for i in startxwin.bat startxdmcp.bat; do \
  fix_cygwin_root "$i" \
done
- Note: cutting here may damage your screen surface -

-- 
http://cs.nyu.edu/~pechtcha/
  |\  _,,,---,,_[EMAIL PROTECTED]
ZZZzz /,`.-'`'-.  ;-;;,_[EMAIL PROTECTED]
 |,4-  ) )-,_. ,\ (  `'-'   Igor Pechtchanski, Ph.D.
'---''(_/--'  `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster."  -- Patrick Naughton

Re: cygwin/xfree86/emacs problems after upgrading

[Igor Pechtchanski]

On Thu, 26 Feb 2004, Igor Pechtchanski wrote:

> On Thu, 26 Feb 2004, Takuma Murakami wrote:
>
> > Igor,
> >
> > > Yes, it's a neat trick *if* the only thing people changed was the install
> > > drive.  If they change the path, all bets are off.  I'm surprised you
> > > don't actually customize startxwin.bat (and similar files, like
> > > startxdmcp.bat) in a postinstall script (which can run under a Cygwin
> > > shell, and thus know the root of the install).  You could choose a
> > > template value, e.g. "%$CYGWIN_ROOT$%", and replace that with "`cygpath -w
> > > /`" using, say, sed.  If you're interested, I could whip up an example
> > > postinstall script for you in the next week or so.
> >
> > I'm interested in that trick out of curiosity.
> > Could you show me your boilerplate?
> >
> > Takuma Murakami
>
> Well, something like the script below (untested) should do...  This uses
> '%$CYGWIN_ROOT$%' as the template string.
> HTH,
> Igor
>
> -- BEGIN /etc/postinstall/fix-startxwin.sh --
> #!/bin/sh
>
> fix_cygwin_root() {
>   TMPNAME="$1.$$" && \
>   mv "$1" "$TMPNAME" && \
>   sed 's/%\$CYGWIN_ROOT\$%/"'"`cygpath -w /`"'"/' "$TMPNAME" > "$1" && \
>   rm "$TMPNAME"
> }
>
> cd /usr/X11R6/bin && \
> for i in startxwin.bat startxdmcp.bat; do \
>   fix_cygwin_root "$i" \
^
s/ \\$/ ; \\/

> done
> - Note: cutting here may damage your screen surface -

I did say it was untested...
Igor
-- 
http://cs.nyu.edu/~pechtcha/
  |\  _,,,---,,_[EMAIL PROTECTED]
ZZZzz /,`.-'`'-.  ;-;;,_[EMAIL PROTECTED]
 |,4-  ) )-,_. ,\ (  `'-'   Igor Pechtchanski, Ph.D.
'---''(_/--'  `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster."  -- Patrick Naughton

Re: cygwin/xfree86/emacs problems after upgrading

[Takuma Murakami]

Igor,

> Yes, it's a neat trick *if* the only thing people changed was the install
> drive.  If they change the path, all bets are off.  I'm surprised you
> don't actually customize startxwin.bat (and similar files, like
> startxdmcp.bat) in a postinstall script (which can run under a Cygwin
> shell, and thus know the root of the install).  You could choose a
> template value, e.g. "%$CYGWIN_ROOT$%", and replace that with "`cygpath -w
> /`" using, say, sed.  If you're interested, I could whip up an example
> postinstall script for you in the next week or so.

I'm interested in that trick out of curiosity.
Could you show me your boilerplate?

Takuma Murakami

Re: cygwin/xfree86/emacs problems after upgrading

[Jari Aalto+mail.linux]

This is your copy. Article has been posted to the newsgroup(s).

* Tue 2004-02-03 Thomas L Roche  us.ibm.com> gnu.emacs.help
* 
| 
| [Cygwin]
| $ emacs --debug-init &
| $ start XWin -multiwindow -clipboard -emulate3buttons
| 
| I typically run 2 emacs windows (second created with C-x 5 b) and 
| 1 xterm, all of which usually overlap ... until the emacs windows
| disappear, apparently randomly, although lately I'm convinced that 
| emacs crashes are more likely when I'm either resizing or 
| minimizing its windows. I've so far run 2 cygwin sessions today,
| once at home (with access to shared drives via a VPN) and once at
| work (directly on ethernet), and the xterm traces have been:

You're not alone. Windowed version of Emacs doesn't work under latest
Cygwin/Xfree. It either core dumps or Emacs just kills itself by
removing all frames from the display.

Perhaps Cygwin Emacs maintainer have ideas. I've CC'd him.

Jari


-- 
http://tiny-tools.sourceforge.net/
Swatch @time   http://www.mir.com.my/iTime/itime.htm
   http://www.ryanthiessen.com/swatch/resources.htm
Use Licenses!  http://www.linuxjournal.com/article.php?sid=6225
Which Licence? http://www.linuxjournal.com/article.php?sid=4825
OSI Licences   http://www.opensource.org/licenses/

Re: cygwin/xfree86/emacs problems after upgrading

[Igor Pechtchanski]

On Wed, 4 Feb 2004, Harold L Hunt II wrote:

> Igor,
>
> > This (and the existence of CYGWIN_ROOT in your environment) is an artifact
> > of using startxwin.bat.  Unless you have a default directory for the
> > Cygwin root, you can't use that file OOTB -- you'll have to edit it and
> > replace "\cygwin" with the value of your Cygwin root (in your case,
> > "d:\ProgramFiles\Cygwin".
> >
> >> CYGWIN_ROOT = `\cygwin'
> >
>
> Well, you can always just set CYGWIN_ROOT to \ProgramFiles\Cygwin, with
> no leading drive letter and colon.  I think you probably knew that
> already...  I am still amazed at the number of times I have seen people
> go in and change \cygwin to c:\cygwin when they have problems... even
> after reading my comment immediately above it that describes why doing
> this is not necessary.  Sheesh, I thought it was a quite beautiful trick
> to allow the path to be set correctly no matter what drive the cygwin
> folder is on.  :)
>
> Harold

Yes, it's a neat trick *if* the only thing people changed was the install
drive.  If they change the path, all bets are off.  I'm surprised you
don't actually customize startxwin.bat (and similar files, like
startxdmcp.bat) in a postinstall script (which can run under a Cygwin
shell, and thus know the root of the install).  You could choose a
template value, e.g. "%$CYGWIN_ROOT$%", and replace that with "`cygpath -w
/`" using, say, sed.  If you're interested, I could whip up an example
postinstall script for you in the next week or so.
Igor
-- 
http://cs.nyu.edu/~pechtcha/
  |\  _,,,---,,_[EMAIL PROTECTED]
ZZZzz /,`.-'`'-.  ;-;;,_[EMAIL PROTECTED]
 |,4-  ) )-,_. ,\ (  `'-'   Igor Pechtchanski, Ph.D.
'---''(_/--'  `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster."  -- Patrick Naughton

Re: cygwin/xfree86/emacs problems after upgrading

[Harold L Hunt II]

Igor,

This (and the existence of CYGWIN_ROOT in your environment) is an artifact
of using startxwin.bat.  Unless you have a default directory for the
Cygwin root, you can't use that file OOTB -- you'll have to edit it and
replace "\cygwin" with the value of your Cygwin root (in your case,
"d:\ProgramFiles\Cygwin".
CYGWIN_ROOT = `\cygwin'

Well, you can always just set CYGWIN_ROOT to \ProgramFiles\Cygwin, with 
no leading drive letter and colon.  I think you probably knew that 
already...  I am still amazed at the number of times I have seen people 
go in and change \cygwin to c:\cygwin when they have problems... even 
after reading my comment immediately above it that describes why doing 
this is not necessary.  Sheesh, I thought it was a quite beautiful trick 
to allow the path to be set correctly no matter what drive the cygwin 
folder is on.  :)

Harold

Re: cygwin/xfree86/emacs problems after upgrading

[Igor Pechtchanski]

On Tue, 3 Feb 2004, Thomas L Roche wrote:

> [snip]
> Note that I run emacs via
>
> emacs --debug-init &
>
> from bash in an xterm which I launch with
>
> start XWin -multiwindow -clipboard -emulate3buttons

Not quite.  Judging from your cygcheck output, you use startxwin.bat.
More below.

> [snip]
> However I'm also, again only since upgrading, having problems with
> unzip, e.g.
>
> >   inflating:
> /d/eclipse/builds/20040121_1953-WB213-AD-V512D-00/eclipse/plugins/com.ibm.etools.j2ee.ui/build/pluginBuild/commonbld/com/ibm/etools/ejb/ui/presentation/EJBEditorOutlineContentProvider.class
>
> > 735 [main] unzip 1820 cmalloc: cmalloc returned NULL
> > error:  zipfile probably corrupt (segmentation violation)
>
> which I get even unzip'ing a known-good file (i.e. one that I unzip'ed
> successfully before upgrading from 1.5.5-1).

Do you have a small testcase that would allow others to reproduce this?
Perhaps a (small) sample .zip file?

> [snip]
> So it seems plausible that there is also a (base) cygwin problem, which
> might be causing the emacs and unzip problems. Or that the emacs and
> unzip problems are unrelated.

They most likely are unrelated.

> What should I try next?

I'd suspect the unzip issue has to do with the path length to the file.
You can try confirming it by creating a file in a deeply nested directory,
putting that one file in a .zip, and then trying to unzip it into some
place even deeper in the directory hierarchy.  Can't help you with the
emacs issue, as I don't use emacs.

> [snip]
> (Note that cygcheck shows
>
> d:\cygwin\bin
> d:\cygwin\usr\X11R6\bin
>
> at the head of my PATH; those dirs don't exist, and they're not in my
> windows path.)

This (and the existence of CYGWIN_ROOT in your environment) is an artifact
of using startxwin.bat.  Unless you have a default directory for the
Cygwin root, you can't use that file OOTB -- you'll have to edit it and
replace "\cygwin" with the value of your Cygwin root (in your case,
"d:\ProgramFiles\Cygwin".

> CYGWIN_ROOT = `\cygwin'

Hope this helps,
Igor
-- 
http://cs.nyu.edu/~pechtcha/
  |\  _,,,---,,_[EMAIL PROTECTED]
ZZZzz /,`.-'`'-.  ;-;;,_[EMAIL PROTECTED]
 |,4-  ) )-,_. ,\ (  `'-'   Igor Pechtchanski, Ph.D.
'---''(_/--'  `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster."  -- Patrick Naughton

cygwin/xfree86/emacs problems after upgrading

[Thomas L Roche]

summary: I am still experiencing post-upgrade problems with my
cygwin emacs; output from cygcheck and report-emacs-bug attached.
What to do?

details:

I was annoyed by some shortcomings of my cygwin emacs (21.1? whatever
version was included around the time of cygwin-1.5.5-1), such as lack
of electricity with kill-ring-save and oddity with multiline kill'ing,
so ~29 Jan I upgraded to cygwin-1.5.6-1, emacs-21.2.1, and whatever
the latest XFree86 was then, along with the other goodness cygwin's
setup advised me to get. Since then emacs life has been bad, but I'm
not sure why, since available evidence seems to point in several
directions.

Note that I run emacs via

emacs --debug-init &

from bash in an xterm which I launch with

start XWin -multiwindow -clipboard -emulate3buttons

I typically run 2 emacs windows (second created with C-x 5 b) and 
1 xterm, all of which usually overlap ... until the emacs windows
disappear, apparently randomly, although lately I'm convinced that 
emacs crashes are more likely when I'm either resizing or 
minimizing its windows. I've so far run 2 cygwin sessions today,
once at home (with access to shared drives via a VPN) and once at
work (directly on ethernet), and the xterm traces have been:

home:
bash-2.05b$ emacs --debug-init &
[1] 1643
bash-2.05b$ emacs --debug-init &
[2] 1460
[1]   Segmentation fault  emacs --debug-init
bash-2.05b$ emacs --debug-init &
[3] 1932
[2]   Aborted (core dumped) emacs --debug-init
bash-2.05b$ emacs --debug-init &
[4] 308
[3]   Aborted (core dumped) emacs --debug-init
bash-2.05b$ X protocol error: BadLength (poly request too large or 
internal Xlib length error) on protocol request 56

work:
bash-2.05b$ emacs --debug-init &
[1] 1868
bash-2.05b$ emacs --debug-init &
[2] 1396
[1]   Segmentation fault  emacs --debug-init
bash-2.05b$ X protocol error: BadLength (poly request too large or 
internal Xlib length error) on protocol request 56
bash-2.05b$ emacs --debug-init &
[3] 1156
[2]   Exit 70 emacs --debug-init

The X errors tend to make me suspect it. However I'm also, again only
since upgrading, having problems with unzip, e.g.

>   inflating: 
/d/eclipse/builds/20040121_1953-WB213-AD-V512D-00/eclipse/plugins/com.ibm.etools.j2ee.ui/build/pluginBuild/commonbld/com/ibm/etools/ejb/ui/presentation/EJBEditorOutlineContentProvider.class
 
 
> 735 [main] unzip 1820 cmalloc: cmalloc returned NULL
> error:  zipfile probably corrupt (segmentation violation)

which I get even unzip'ing a known-good file (i.e. one that I unzip'ed
successfully before upgrading from 1.5.5-1). I noted

Christopher Faylor Sat, 31 Jan 2004 00:43:54 -0500 (EST)
> Changes since 1.5.6-1:

> - Fix malloc overflow problem which caused random SEGVs.
>   (Christopher Faylor)

and installed cygwin 1.5.7-1 (along with other then-updated packages,
which included XFree86) early 1 Feb: this has not solved either the
unzip or the emacs problems. So it seems plausible that there is also
a (base) cygwin problem, which might be causing the emacs and unzip
problems. Or that the emacs and unzip problems are unrelated.

What should I try next? If possible, please post me directly as well
as the list (I'm on the digest). Note that output of report-emacs-bug
(edited for clarity in this context) follows, then output of cygcheck
-srvh (slightly edited for security) follows that to end of post.
(Note that cygcheck shows

d:\cygwin\bin
d:\cygwin\usr\X11R6\bin

at the head of my PATH; those dirs don't exist, and they're not in my
windows path.)

output of report-emacs-bug
--
In GNU Emacs 21.2.1 (i686-pc-cygwin, X toolkit)
 of 2003-01-23 on DRACO
configured using `configure  --prefix=/usr --bindir=/usr/bin 
--sysconfdir=/etc --libexecdir=/usr/sbin --localstatedir=/var 
--datadir=/usr/share --without-toolkit-scroll-bars'
Important settings:
  value of $LC_ALL: nil
  value of $LC_COLLATE: nil
  value of $LC_CTYPE: nil
  value of $LC_MESSAGES: nil
  value of $LC_MONETARY: nil
  value of $LC_NUMERIC: nil
  value of $LC_TIME: nil
  value of $LANG: nil
  locale-coding-system: nil
  default-enable-multibyte-characters: t

Recent input:
  C-g C-g C-h a b u g  C-x 0  


C-SPC   C-SPC 
   M-w   




   
  C-s  M-x r e p o SPC 
r t SPC e m SPC  

Recent messages:
Wrote /t/tlroche/notReallyJunk
call-interactively: Quit
keyboard-quit: Quit
Loading apropos...done
Type C-x 1 to remove help window.  C-M-v to scroll the help.
Mark set [3 times]
Saving file /t/tlroche/notReallyJunk...
Wrote /t/tlroche/notReallyJunk
Making completion list...
Loading emacsbug...done
--
output of cygcheck -srvh
--
Cygwin Win95/NT Configuration Diagnostics
Current System Time: Tue Feb 03 15:00:22 2004

Windows 2

Re: 1.5.6-1: WinXP and cygwin/xfree86

[Igor Pechtchanski]

On Tue, 27 Jan 2004 ennisagdlscom wrote:

> Has anyone had issues with cygwin utterly destroying the file system of a
> WinXP(prof.) machine?  I'm not sure what happened, but I got a BSoD,
> rebooted, and the HD wasn't recognizable by anything (I'm in the process of
> re-installing XP now).
>
> Adrian

.  Cygwin cannot cause a BSOD.  BSOD's
are caused by bugs in Windows (a faulty driver would be my guess).  Cygwin
can only trigger it, just like any other program can.  You got unlucky.
Igor
-- 
http://cs.nyu.edu/~pechtcha/
  |\  _,,,---,,_[EMAIL PROTECTED]
ZZZzz /,`.-'`'-.  ;-;;,_[EMAIL PROTECTED]
 |,4-  ) )-,_. ,\ (  `'-'   Igor Pechtchanski, Ph.D.
'---''(_/--'  `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster."  -- Patrick Naughton

1.5.6-1: WinXP and cygwin/xfree86

[ennisa]

Has anyone had issues with cygwin utterly destroying the file system of a
WinXP(prof.) machine?  I'm not sure what happened, but I got a BSoD,
rebooted, and the HD wasn't recognizable by anything (I'm in the process of
re-installing XP now).

Adrian
London, ON

Cygwin XFree86 featured in Danish Computer Magazine

[Franz Wolfhagen]

Well, it had to happen sometimes - the danish computer magazine "Alt om
Data" www.aod.dk has metioned/included Cygwin Xfree86 on their monthly
CDRom with their magazine along with a lot of the cygwin tools.

The only problem as I see it - they have no sourcecode available on the
CDRom - neither is it possible to see where it should obtained.

They can be contacted on the mail address cdromaod.dk

Med venlig hilsen / Regards
Franz Wolfhagen

Re: Cygwin XFree86 startx Problem

[Harold L Hunt II]

Igor,

Cool.  Thanks!

Harold

Igor Pechtchanski wrote:

On Sat, 29 Nov 2003, Igor Pechtchanski wrote:


On Sat, 22 Nov 2003, Harold L Hunt II wrote:


Igor,

Igor Pechtchanski wrote:

On Fri, 21 Nov 2003, Harold L Hunt II wrote:


Igor,

Igor Pechtchanski wrote:



On Fri, 21 Nov 2003, Chan Seng Loong wrote:


hi again...

Thanks to Mr. Igor Pechtchanski, the "[: Seng: unknown
operand" problem is eleminated with the power of ""
qutoes :-D
Good.  Harold, how do you want to go about incorporating the patch?
As you suspected, I think this is actually a generated file.  Granted,
the input is similar to the output, but it is a different file that
needs to be patched.  Again, I cannot check this right now.
As far as what to do with the patch, it is hard to say.  Are you just
asking about how it will get into my next release?  That should be easy.
As far as finding it an upstream home, we still have to wait for the
tree on freedesktop.org to finish being setup.
Harold
Ok, I'll try to checkout the CVS tree at some point soon and produce this
patch off the correct file.
Base the patch off of the SourceForge tree that we have for now:

http://sourceforge.net/projects/xoncygwin/

That's what I essentially do my builds from, so it should work.
Hopefully the file in question is actually in that tree... if not, then
just wait until our freedesktop.org tree is ready.
Harold
Harold,

The file (startx.cpp) is in xc/programs/xinit, and the xoncygwin tree only
has xc/programs/Xserver.  Are you going to use the tree on freedesktop.org
(which is already set up at "xorg") for further builds of the non-server
parts?  If so, should I use the MAIN branch there, or the XORG-CURRENT
branch?
   Igor


Harold,

Here's a patch against the HEAD of the MAIN branch in the xorg tree at
freedesktop.org.  ChangeLog is below.  Let me know if there's a problem.
Igor
==
ChangeLog:
2003-12-02  Igor Pechtchanski  <[EMAIL PROTECTED]>
* xc/programs/xinit/startx.cpp: Make space-friendly.




--- xc/programs/xinit/startx.cpp-orig	2003-12-02 13:10:12.0 -0500
+++ xc/programs/xinit/startx.cpp	2003-12-02 13:45:06.566899200 -0500
@@ -48,8 +48,9 @@ fi
 scoclientrc=$HOME/.startxrc
 #endif
 
-userclientrc=$HOME/.xinitrc
-userserverrc=$HOME/.xserverrc
+userclientrc="$HOME/.xinitrc"
+userserverrc="$HOME/.xserverrc"
+/* Note: XINITDIR and BINDIR should be space-free */
 sysclientrc=XINITDIR/xinitrc
 sysserverrc=XINITDIR/xserverrc
 defaultclient=BINDIR/xterm
@@ -64,19 +65,19 @@ if [ -f $scoclientrc ]; then
 defaultclientargs=$scoclientrc
 else
 #endif
-if [ -f $userclientrc ]; then
-defaultclientargs=$userclientrc
-elif [ -f $sysclientrc ]; then
-defaultclientargs=$sysclientrc
+if [ -f "$userclientrc" ]; then
+defaultclientargs="\"$userclientrc\""
+elif [ -f "$sysclientrc" ]; then
+defaultclientargs="\"$sysclientrc\""
 fi
 #ifdef SCO
 fi
 #endif
 
-if [ -f $userserverrc ]; then
-defaultserverargs=$userserverrc
-elif [ -f $sysserverrc ]; then
-defaultserverargs=$sysserverrc
+if [ -f "$userserverrc" ]; then
+defaultserverargs="\"$userserverrc\""
+elif [ -f "$sysserverrc" ]; then
+defaultserverargs="\"$sysserverrc\""
 fi
 
 whoseargs="client"
@@ -86,15 +87,15 @@ while [ x"$1" != x ]; do
 /''*|\./''*)
 	if [ "$whoseargs" = "client" ]; then
 	if [ x"$clientargs" = x ]; then
-		client="$1"
+		client="\"$1\""
 	else
-		clientargs="$clientargs $1"
+		clientargs="$clientargs \"$1\""
 	fi
 	else
 	if [ x"$serverargs" = x ]; then
-		server="$1"
+		server="\"$1\""
 	else
-		serverargs="$serverargs $1"
+		serverargs="$serverargs \"$1\""
 	fi
 	fi
 	;;
@@ -103,14 +104,14 @@ while [ x"$1" != x ]; do
 	;;
 *)
 	if [ "$whoseargs" = "client" ]; then
-	clientargs="$clientargs $1"
+	clientargs="$clientargs \"$1\""
 	else
 	XCOMM display must be the FIRST server argument
 	if [ x"$serverargs" = x ] && @@
 		 expr "$1" : ':[0-9][0-9]*$' > /dev/null 2>&1; then
-		display="$1"
+		display="\"$1\""
 	else
-		serverargs="$serverargs $1"
+		serverargs="$serverargs \"$1\""
 	fi
 	fi
 	;;
@@ -124,7 +125,7 @@ if [ x"$client" = x ]; then
 if [ x"$clientargs" = x ]; then
 	client="$defaultclientargs"
 else
-	client=$defaultclient
+	client="$defaultclient"
 fi
 fi
 
@@ -134,12 +135,12 @@ if [ x"$server" = x ]; then
 if [ x"$serverargs" = x -a x"$display" = x ]; then
 	server="$defaultserverargs"
 else
-	server=$defaultserver
+	server="$defaultserver"
 fi
 fi
 
 if [ x"$XAUTHORITY" = x ]; then
-XAUTHORITY=$HOME/.Xauthority
+XAUTHORITY="$HOME/.Xauthority"
 export XAUTHORITY
 fi
 
@@ -172,9 +173,13 @@ EOF
 done
 #endif
 
-xinit $client $clientargs -- $server $display $serverargs
+XCOMM correctly process quotes, etc
+eval "set -- $client $clientargs -- $server $display $serverargs"
+
+xinit "$@"
 
 i

Re: Cygwin XFree86 startx Problem

[Igor Pechtchanski]

On Sat, 29 Nov 2003, Igor Pechtchanski wrote:

> On Sat, 22 Nov 2003, Harold L Hunt II wrote:
>
> > Igor,
> >
> > Igor Pechtchanski wrote:
> > > On Fri, 21 Nov 2003, Harold L Hunt II wrote:
> > >
> > >>Igor,
> > >>
> > >>Igor Pechtchanski wrote:
> > >>
> > >>
> > >>>On Fri, 21 Nov 2003, Chan Seng Loong wrote:
> > >>>
> > hi again...
> > 
> > Thanks to Mr. Igor Pechtchanski, the "[: Seng: unknown
> > operand" problem is eleminated with the power of ""
> > qutoes :-D
> > >>>
> > >>>Good.  Harold, how do you want to go about incorporating the patch?
> > >>
> > >>As you suspected, I think this is actually a generated file.  Granted,
> > >>the input is similar to the output, but it is a different file that
> > >>needs to be patched.  Again, I cannot check this right now.
> > >>
> > >>As far as what to do with the patch, it is hard to say.  Are you just
> > >>asking about how it will get into my next release?  That should be easy.
> > >>  As far as finding it an upstream home, we still have to wait for the
> > >>tree on freedesktop.org to finish being setup.
> > >>
> > >>Harold
> > >
> > > Ok, I'll try to checkout the CVS tree at some point soon and produce this
> > > patch off the correct file.
> >
> > Base the patch off of the SourceForge tree that we have for now:
> >
> > http://sourceforge.net/projects/xoncygwin/
> >
> > That's what I essentially do my builds from, so it should work.
> > Hopefully the file in question is actually in that tree... if not, then
> > just wait until our freedesktop.org tree is ready.
> >
> > Harold
>
> Harold,
>
> The file (startx.cpp) is in xc/programs/xinit, and the xoncygwin tree only
> has xc/programs/Xserver.  Are you going to use the tree on freedesktop.org
> (which is already set up at "xorg") for further builds of the non-server
> parts?  If so, should I use the MAIN branch there, or the XORG-CURRENT
> branch?
> Igor

Harold,

Here's a patch against the HEAD of the MAIN branch in the xorg tree at
freedesktop.org.  ChangeLog is below.  Let me know if there's a problem.
Igor
==
ChangeLog:
2003-12-02  Igor Pechtchanski  <[EMAIL PROTECTED]>
* xc/programs/xinit/startx.cpp: Make space-friendly.

-- 
http://cs.nyu.edu/~pechtcha/
  |\  _,,,---,,_[EMAIL PROTECTED]
ZZZzz /,`.-'`'-.  ;-;;,_[EMAIL PROTECTED]
 |,4-  ) )-,_. ,\ (  `'-'   Igor Pechtchanski, Ph.D.
'---''(_/--'  `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster."  -- Patrick Naughton--- xc/programs/xinit/startx.cpp-orig   2003-12-02 13:10:12.0 -0500
+++ xc/programs/xinit/startx.cpp2003-12-02 13:45:06.566899200 -0500
@@ -48,8 +48,9 @@ fi
 scoclientrc=$HOME/.startxrc
 #endif
 
-userclientrc=$HOME/.xinitrc
-userserverrc=$HOME/.xserverrc
+userclientrc="$HOME/.xinitrc"
+userserverrc="$HOME/.xserverrc"
+/* Note: XINITDIR and BINDIR should be space-free */
 sysclientrc=XINITDIR/xinitrc
 sysserverrc=XINITDIR/xserverrc
 defaultclient=BINDIR/xterm
@@ -64,19 +65,19 @@ if [ -f $scoclientrc ]; then
 defaultclientargs=$scoclientrc
 else
 #endif
-if [ -f $userclientrc ]; then
-defaultclientargs=$userclientrc
-elif [ -f $sysclientrc ]; then
-defaultclientargs=$sysclientrc
+if [ -f "$userclientrc" ]; then
+defaultclientargs="\"$userclientrc\""
+elif [ -f "$sysclientrc" ]; then
+defaultclientargs="\"$sysclientrc\""
 fi
 #ifdef SCO
 fi
 #endif
 
-if [ -f $userserverrc ]; then
-defaultserverargs=$userserverrc
-elif [ -f $sysserverrc ]; then
-defaultserverargs=$sysserverrc
+if [ -f "$userserverrc" ]; then
+defaultserverargs="\"$userserverrc\""
+elif [ -f "$sysserverrc" ]; then
+defaultserverargs="\"$sysserverrc\""
 fi
 
 whoseargs="client"
@@ -86,15 +87,15 @@ while [ x"$1" != x ]; do
 /''*|\./''*)
if [ "$whoseargs" = "client" ]; then
if [ x"$clientargs" = x ]; then
-   client="$1"
+   client="\"$1\""
else
-   clientargs="$clientargs $1"
+   clientargs="$clientargs \"$1\""
fi
else
if [ x"$serverargs" = x ]; then
-   server="$1"
+   server="\"$1\""
else
-   serverargs="$serverargs $1"
+   serverargs="$serverargs \"$1\""
fi
fi
;;
@@ -103,14 +104,14 @@ while [ x"$1" != x ]; do
;;
 *)
if [ "$whoseargs" = "client" ]; then
-   clientargs="$clientargs $1"
+   clientargs="$clientargs \"$1\""
else
XCOMM display must be the FIRST server argument
if [ x"$serverargs" = x ] && @@
 expr "$1" : ':[0-9][0-9]*$' > /dev/null 2>&1; then
-   display="$1"
+   display="\"$1\""
   

Re: Cygwin XFree86 startx Problem

[Igor Pechtchanski]

On Sat, 22 Nov 2003, Harold L Hunt II wrote:

> Igor,
>
> Igor Pechtchanski wrote:
> > On Fri, 21 Nov 2003, Harold L Hunt II wrote:
> >
> >>Igor,
> >>
> >>Igor Pechtchanski wrote:
> >>
> >>
> >>>On Fri, 21 Nov 2003, Chan Seng Loong wrote:
> >>>
> hi again...
> 
> Thanks to Mr. Igor Pechtchanski, the "[: Seng: unknown
> operand" problem is eleminated with the power of ""
> qutoes :-D
> >>>
> >>>Good.  Harold, how do you want to go about incorporating the patch?
> >>
> >>As you suspected, I think this is actually a generated file.  Granted,
> >>the input is similar to the output, but it is a different file that
> >>needs to be patched.  Again, I cannot check this right now.
> >>
> >>As far as what to do with the patch, it is hard to say.  Are you just
> >>asking about how it will get into my next release?  That should be easy.
> >>  As far as finding it an upstream home, we still have to wait for the
> >>tree on freedesktop.org to finish being setup.
> >>
> >>Harold
> >
> > Ok, I'll try to checkout the CVS tree at some point soon and produce this
> > patch off the correct file.
>
> Base the patch off of the SourceForge tree that we have for now:
>
> http://sourceforge.net/projects/xoncygwin/
>
> That's what I essentially do my builds from, so it should work.
> Hopefully the file in question is actually in that tree... if not, then
> just wait until our freedesktop.org tree is ready.
>
> Harold

Harold,

The file (startx.cpp) is in xc/programs/xinit, and the xoncygwin tree only
has xc/programs/Xserver.  Are you going to use the tree on freedesktop.org
(which is already set up at "xorg") for further builds of the non-server
parts?  If so, should I use the MAIN branch there, or the XORG-CURRENT
branch?
Igor
-- 
http://cs.nyu.edu/~pechtcha/
  |\  _,,,---,,_[EMAIL PROTECTED]
ZZZzz /,`.-'`'-.  ;-;;,_[EMAIL PROTECTED]
 |,4-  ) )-,_. ,\ (  `'-'   Igor Pechtchanski, Ph.D.
'---''(_/--'  `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster."  -- Patrick Naughton

Re: Cygwin XFree86 startx Problem

[Igor Pechtchanski]

On Mon, 24 Nov 2003, Hans Dekker wrote:

> Hi,
>
> Don't know if I am answering to the right question/ problem, but I see
> some referrals to passwd, username etc. To get to login to a Unix box
> with X you can use the following script, after starting X and getting
> into the xterm box of your local machine:
>
>  > xhost + > /dev/null
>  > export IPADDR=`ipconfig | grep Address | grep "10\." | cut -f 2 -d ":" | cut -f 2 
> -d " "`
>  > rsh  -l ${USERNAME} "export DISPLAY=\"${IPADDR}:0.0\";cd $HOME; xterm"

Make that "${USERNAME}" (the username may contain spaces too).  However,
why bother, if you can make "$USER" be without spaces in /etc/passwd?
Igor

> Use a modified startxwin.bat like:
>
>  > start XWin -multiwindow
>  > xterm -T "your app initialisation screen" -e 
>
>
> Note that the bash shell copies the MS-Windows environment to it as you
> start it. That's the referral to ${USERNAME}. We have the same usernames
> for the MS-Windows environment as well as the Unix box logging in to.
> You can fill out your username on the remote Unix box as needed.
>
> The string Address is what grep looks for in the output of ipconfig.
> Maybe different in your locale. Check ipconfig output in your bash box.
>
> 10\. is part of our IP-address range in the Unix/ Windows network. It's
> useful to scan your IP adresses when you have more than 1 NIC or more
> than 1 IP-address.
>
> In case you have a $HOME on the remote machine with spaces in it try cd
> \"${HOME}\" in the script.
>
> Regards, Hans.
>
> Igor Pechtchanski escribio:
> > Robert,
> >
> > Sorry, but no.  Cygwin doesn't care about the Windows username, it looks
> > in /etc/passwd.  If you change the name of the Windows account, you'd have
> > to regenerate the appropriate entry in /etc/passwd anyway, so why not just
> > eliminate the middle step and change /etc/passwd directly?  Simply remove
> > the spaces from the username and the home directory in /etc/passwd (and
> > make sure you rename the directory itself), and it should be fine.
> >   Igor
> >
> > On Fri, 21 Nov 2003, Robert McNulty Junior wrote:
> >
> >
> >>I think these names with spaces come from when they originally set up
> >>Windows NT, 2000, XP, Server 2000 with thier full name when asked create
> >>users in NT, 2000, XP or 2003 Server.
> >>Correct this by going into the Windows Users' account setup in Control
> >>Panel, and create a user without the spaces in the name.
> >>Chan, use chansengloong as your new user name. Must be done in administrater
> >>mode.
> >>Over all effect will be a new account under Cygwin though windows.
> >>
> >>
> >>-Original Message-
> >>From: [EMAIL PROTECTED]
> >>[mailto:[EMAIL PROTECTED] Behalf Of Andrew Markebo
> >>Sent: Friday, November 21, 2003 10:35 PM
> >>To: [EMAIL PROTECTED]
> >>Subject: Re: Cygwin XFree86 startx Problem
> >>
> >>
> >>/ Chan Seng Loong <[EMAIL PROTECTED]> wrote:
> >>|[...]
> >>| $ startx
> >>| + userclientrc=/home/Chan Seng Loong/.xinitrc
> >>| + userserverrc=/home/Chan Seng Loong/.xserverrc
> >>
> >>just a wild thought, homedir with space in it, try without.. edit
> >>/etc/passwd.
> >>
> >>/A

-- 
http://cs.nyu.edu/~pechtcha/
  |\  _,,,---,,_[EMAIL PROTECTED]
ZZZzz /,`.-'`'-.  ;-;;,_[EMAIL PROTECTED]
 |,4-  ) )-,_. ,\ (  `'-'   Igor Pechtchanski, Ph.D.
'---''(_/--'  `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster."  -- Patrick Naughton

Re: Cygwin XFree86 startx Problem

[Hans Dekker]

Hi,

Don't know if I am answering to the right question/ problem, but I see 
some referrals to passwd, username etc. To get to login to a Unix box 
with X you can use the following script, after starting X and getting 
into the xterm box of your local machine:

> xhost + > /dev/null
> export IPADDR=`ipconfig | grep Address | grep "10\." | cut -f 2 -d 
":" | cut -f 2 -d " "`
> rsh  -l ${USERNAME} "export DISPLAY=\"${IPADDR}:0.0\";cd $HOME; 
xterm"

Use a modified startxwin.bat like:

> start XWin -multiwindow
> xterm -T "your app initialisation screen" -e 
Note that the bash shell copies the MS-Windows environment to it as you 
start it. That's the referral to ${USERNAME}. We have the same usernames 
for the MS-Windows environment as well as the Unix box logging in to. 
You can fill out your username on the remote Unix box as needed.

The string Address is what grep looks for in the output of ipconfig. 
Maybe different in your locale. Check ipconfig output in your bash box.

10\. is part of our IP-address range in the Unix/ Windows network. It's 
useful to scan your IP adresses when you have more than 1 NIC or more 
than 1 IP-address.

In case you have a $HOME on the remote machine with spaces in it try cd 
\"${HOME}\" in the script.

Regards, Hans.

Igor Pechtchanski escribió:
Robert,

Sorry, but no.  Cygwin doesn't care about the Windows username, it looks
in /etc/passwd.  If you change the name of the Windows account, you'd have
to regenerate the appropriate entry in /etc/passwd anyway, so why not just
eliminate the middle step and change /etc/passwd directly?  Simply remove
the spaces from the username and the home directory in /etc/passwd (and
make sure you rename the directory itself), and it should be fine.
Igor
On Fri, 21 Nov 2003, Robert McNulty Junior wrote:


I think these names with spaces come from when they originally set up
Windows NT, 2000, XP, Server 2000 with thier full name when asked create
users in NT, 2000, XP or 2003 Server.
Correct this by going into the Windows Users' account setup in Control
Panel, and create a user without the spaces in the name.
Chan, use chansengloong as your new user name. Must be done in administrater
mode.
Over all effect will be a new account under Cygwin though windows.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Andrew Markebo
Sent: Friday, November 21, 2003 10:35 PM
To: [EMAIL PROTECTED]
Subject: Re: Cygwin XFree86 startx Problem
/ Chan Seng Loong <[EMAIL PROTECTED]> wrote:
|[...]
| $ startx
| + userclientrc=/home/Chan Seng Loong/.xinitrc
| + userserverrc=/home/Chan Seng Loong/.xserverrc
just a wild thought, homedir with space in it, try without.. edit
/etc/passwd.
   /A

--
  Democracy is two hungry wolves and one sheep discussing what's for
dinner. Liberty is a well-armed sheep willing to contest the decision.

RE: Cygwin XFree86 startx Problem

[Igor Pechtchanski]

Robert,

Sorry, but no.  Cygwin doesn't care about the Windows username, it looks
in /etc/passwd.  If you change the name of the Windows account, you'd have
to regenerate the appropriate entry in /etc/passwd anyway, so why not just
eliminate the middle step and change /etc/passwd directly?  Simply remove
the spaces from the username and the home directory in /etc/passwd (and
make sure you rename the directory itself), and it should be fine.
Igor

On Fri, 21 Nov 2003, Robert McNulty Junior wrote:

> I think these names with spaces come from when they originally set up
> Windows NT, 2000, XP, Server 2000 with thier full name when asked create
> users in NT, 2000, XP or 2003 Server.
> Correct this by going into the Windows Users' account setup in Control
> Panel, and create a user without the spaces in the name.
> Chan, use chansengloong as your new user name. Must be done in administrater
> mode.
> Over all effect will be a new account under Cygwin though windows.
>
>
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of Andrew Markebo
> Sent: Friday, November 21, 2003 10:35 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Cygwin XFree86 startx Problem
>
>
> / Chan Seng Loong <[EMAIL PROTECTED]> wrote:
> |[...]
> | $ startx
> | + userclientrc=/home/Chan Seng Loong/.xinitrc
> | + userserverrc=/home/Chan Seng Loong/.xserverrc
>
> just a wild thought, homedir with space in it, try without.. edit
> /etc/passwd.
>
> /A
>
> --
>Democracy is two hungry wolves and one sheep discussing what's for
> dinner. Liberty is a well-armed sheep willing to contest the decision.
>
>
>

-- 
http://cs.nyu.edu/~pechtcha/
  |\  _,,,---,,_[EMAIL PROTECTED]
ZZZzz /,`.-'`'-.  ;-;;,_[EMAIL PROTECTED]
 |,4-  ) )-,_. ,\ (  `'-'   Igor Pechtchanski, Ph.D.
'---''(_/--'  `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster."  -- Patrick Naughton

Re: Cygwin XFree86 startx Problem

[Harold L Hunt II]

Igor,

Igor Pechtchanski wrote:
On Fri, 21 Nov 2003, Harold L Hunt II wrote:


Igor,

Igor Pechtchanski wrote:


On Fri, 21 Nov 2003, Chan Seng Loong wrote:



hi again...

Thanks to Mr. Igor Pechtchanski, the "[: Seng: unknown
operand" problem is eleminated with the power of ""
qutoes :-D


Good.  Harold, how do you want to go about incorporating the patch?
As you suspected, I think this is actually a generated file.  Granted,
the input is similar to the output, but it is a different file that
needs to be patched.  Again, I cannot check this right now.
As far as what to do with the patch, it is hard to say.  Are you just
asking about how it will get into my next release?  That should be easy.
 As far as finding it an upstream home, we still have to wait for the
tree on freedesktop.org to finish being setup.
Harold


Ok, I'll try to checkout the CVS tree at some point soon and produce this
patch off the correct file.
Base the patch off of the SourceForge tree that we have for now:

http://sourceforge.net/projects/xoncygwin/

That's what I essentially do my builds from, so it should work. 
Hopefully the file in question is actually in that tree... if not, then 
just wait until our freedesktop.org tree is ready.

Harold

Re: Cygwin XFree86 startx Problem

[Igor Pechtchanski]

On Fri, 21 Nov 2003, Harold L Hunt II wrote:

> Igor,
>
> Igor Pechtchanski wrote:
>
> > On Fri, 21 Nov 2003, Chan Seng Loong wrote:
> >
> >
> >>hi again...
> >>
> >>Thanks to Mr. Igor Pechtchanski, the "[: Seng: unknown
> >>operand" problem is eleminated with the power of ""
> >>qutoes :-D
> >
> >
> > Good.  Harold, how do you want to go about incorporating the patch?
>
> As you suspected, I think this is actually a generated file.  Granted,
> the input is similar to the output, but it is a different file that
> needs to be patched.  Again, I cannot check this right now.
>
> As far as what to do with the patch, it is hard to say.  Are you just
> asking about how it will get into my next release?  That should be easy.
>   As far as finding it an upstream home, we still have to wait for the
> tree on freedesktop.org to finish being setup.
>
> Harold

Ok, I'll try to checkout the CVS tree at some point soon and produce this
patch off the correct file.
Igor
-- 
http://cs.nyu.edu/~pechtcha/
  |\  _,,,---,,_[EMAIL PROTECTED]
ZZZzz /,`.-'`'-.  ;-;;,_[EMAIL PROTECTED]
 |,4-  ) )-,_. ,\ (  `'-'   Igor Pechtchanski, Ph.D.
'---''(_/--'  `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster."  -- Patrick Naughton

RE: Cygwin XFree86 startx Problem

[Robert McNulty Junior]

I think these names with spaces come from when they originally set up
Windows NT, 2000, XP, Server 2000 with thier full name when asked create
users in NT, 2000, XP or 2003 Server.
Correct this by going into the Windows Users' account setup in Control
Panel, and create a user without the spaces in the name.
Chan, use chansengloong as your new user name. Must be done in administrater
mode.
Over all effect will be a new account under Cygwin though windows.


-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Andrew Markebo
Sent: Friday, November 21, 2003 10:35 PM
To: [EMAIL PROTECTED]
Subject: Re: Cygwin XFree86 startx Problem


/ Chan Seng Loong <[EMAIL PROTECTED]> wrote:
|[...]
| $ startx
| + userclientrc=/home/Chan Seng Loong/.xinitrc
| + userserverrc=/home/Chan Seng Loong/.xserverrc

just a wild thought, homedir with space in it, try without.. edit
/etc/passwd.

/A

--
   Democracy is two hungry wolves and one sheep discussing what's for
dinner. Liberty is a well-armed sheep willing to contest the decision.

Re: Cygwin XFree86 startx Problem

[Andrew Markebo]

/ Chan Seng Loong <[EMAIL PROTECTED]> wrote:
|[...]
| $ startx
| + userclientrc=/home/Chan Seng Loong/.xinitrc
| + userserverrc=/home/Chan Seng Loong/.xserverrc

just a wild thought, homedir with space in it, try without.. edit
/etc/passwd.

/A

-- 
   Democracy is two hungry wolves and one sheep discussing what's for
dinner. Liberty is a well-armed sheep willing to contest the decision.

Re: Cygwin XFree86 startx Problem

[David Andersen]

One of the messages may be from xclock - I also get the *Warning: Cannot
convert string "" to type XftFont* message everytime I load xclock (from
.xinitrc or from an xterm).   It doesn't seem to hurt anything, but it would
be nice to know what causes it.

- Original Message - 
From: "Chan Seng Loong" <[EMAIL PROTECTED]>
Newsgroups: gmane.os.cygwin.xfree
Sent: Friday, November 21, 2003 8:02 PM
Subject: Re: Cygwin XFree86 startx Problem
...
> + xclock -geometry 50x50-1+1
...
> Fontconfig error: Cannot load default config file
> Warning: Cannot convert string "" to type XftFont

Re: Cygwin XFree86 startx Problem

[Chan Seng Loong]

hiagain

I check the setup.exe and it say that I already
installed:

libconfig-devel
libfontconfig1
libfreetype2-devel
libfreetype26

packages...

still I got the fontconfig problem:

Chan Seng [EMAIL PROTECTED] ~
$ startx
+ userclientrc=/home/Chan Seng Loong/.xinitrc
+ userserverrc=/home/Chan Seng Loong/.xserverrc
+ sysclientrc=/usr/X11R6/lib/X11/xinit/xinitrc
+ sysserverrc=/usr/X11R6/lib/X11/xinit/xserverrc
+ defaultclient=/usr/X11R6/bin/xterm
+ defaultserver=/usr/X11R6/bin/X
+ defaultclientargs=
+ defaultserverargs=
+ clientargs=
+ serverargs=
+ [ -f /home/Chan Seng Loong/.xinitrc ]
+ defaultclientargs="/home/Chan Seng Loong/.xinitrc"
+ [ -f /home/Chan Seng Loong/.xserverrc ]
+ [ -f /usr/X11R6/lib/X11/xinit/xserverrc ]
+ whoseargs=client
+ [ x != x ]
+ [ x = x ]
+ [ x = x ]
+ client="/home/Chan Seng Loong/.xinitrc"
+ [ x = x ]
+ [ x = x -a x = x ]
+ server=
+ [ x = x ]
+ XAUTHORITY=/home/Chan Seng Loong/.Xauthority
+ export XAUTHORITY
+ removelist=
+ eval set -- "/home/Chan Seng Loong/.xinitrc"  --
+ set -- /home/Chan Seng Loong/.xinitrc --
+ xinit /home/Chan Seng Loong/.xinitrc --

+ userresources=/home/Chan Seng Loong/.Xresources
+ usermodmap=/home/Chan Seng Loong/.Xmodmap
+ sysresources=/usr/X11R6/lib/X11/xinit/.Xresources
+ sysmodmap=/usr/X11R6/lib/X11/xinit/.Xmodmap
+ [ -f /usr/X11R6/lib/X11/xinit/.Xresources ]
+ [ -f /usr/X11R6/lib/X11/xinit/.Xmodmap ]
+ [ -f /home/Chan Seng Loong/.Xresources ]
+ [ -f /home/Chan Seng Loong/.Xmodmap ]
+ twm
+ xclock -geometry 50x50-1+1
+ xterm -geometry 80x50+494+51
+ xterm -geometry 80x20+494-0
+ exec xterm -geometry 80x66+0+0 -name login
Fontconfig error: Cannot load default config file
Warning: Cannot convert string "" to type XftFont

Well, i check the /etc/x11/fs/config:

# font server configuration file
# $Xorg: config.cpp,v 1.3 2000/08/17 19:54:19 cpqbld
Exp $

clone-self = on
use-syslog = off
catalogue =
/usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/Speedo/,/usr/X11R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/CID/,/usr/X11R6/lib/X11/fonts/75dpi/,/usr/X11R6/lib/X11/fonts/100dpi/
error-file = /var/log/xfs.log
# in decipoints
default-point-size = 120
default-resolutions = 75,75,100,100

# font cache control, specified in KB
cache-hi-mark = 2048
cache-low-mark = 1433
cache-balance = 70




__
Do you Yahoo!?
Protect your identity with Yahoo! Mail AddressGuard
http://antispam.yahoo.com/whatsnewfree

Re: Cygwin XFree86 startx Problem

[Harold L Hunt II]

Igor,

Igor Pechtchanski wrote:

On Fri, 21 Nov 2003, Chan Seng Loong wrote:


hi again...

Thanks to Mr. Igor Pechtchanski, the "[: Seng: unknown
operand" problem is eleminated with the power of ""
qutoes :-D


Good.  Harold, how do you want to go about incorporating the patch?
As you suspected, I think this is actually a generated file.  Granted, 
the input is similar to the output, but it is a different file that 
needs to be patched.  Again, I cannot check this right now.

As far as what to do with the patch, it is hard to say.  Are you just 
asking about how it will get into my next release?  That should be easy. 
 As far as finding it an upstream home, we still have to wait for the 
tree on freedesktop.org to finish being setup.

Harold

Re: Cygwin XFree86 startx Problem

[Igor Pechtchanski]

On Fri, 21 Nov 2003, Chan Seng Loong wrote:

> hi again...
>
> Thanks to Mr. Igor Pechtchanski, the "[: Seng: unknown
> operand" problem is eleminated with the power of ""
> qutoes :-D

Good.  Harold, how do you want to go about incorporating the patch?

> [snip]
> Fontconfig error: Cannot load default config file
> Warning: Cannot convert string "" to type XftFont
>
> Now the problem is the Fontconfig and freetype2 packages
> yes, I'm doing the "Install from Internet"
> but in the XFree86 category... I only find:
> [snip]

They're both in the Libs category.

> Hmmm...
>
> maybe they should include a search package
> option..
> can't find the Fontconfig and freetype2...
>
> Btw, is fontconfig file in etc/X11 directory?

First off, there's a package search page on the internet:
.  You can also use the "Full" view in the
setup program to see all packages in alphabetical order (or the "Not
installed" view to limit the packages to those not on your system).
HTH,
Igor
-- 
http://cs.nyu.edu/~pechtcha/
  |\  _,,,---,,_[EMAIL PROTECTED]
ZZZzz /,`.-'`'-.  ;-;;,_[EMAIL PROTECTED]
 |,4-  ) )-,_. ,\ (  `'-'   Igor Pechtchanski, Ph.D.
'---''(_/--'  `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster."  -- Patrick Naughton

Re: Cygwin XFree86 startx Problem

[Chan Seng Loong]

hi again...

Thanks to Mr. Igor Pechtchanski, the "[: Seng: unknown
operand" problem is eleminated with the power of ""
qutoes :-D

Chan Seng [EMAIL PROTECTED] ~
$ startx
+ userclientrc=/home/Chan Seng Loong/.xinitrc
+ userserverrc=/home/Chan Seng Loong/.xserverrc
+ sysclientrc=/usr/X11R6/lib/X11/xinit/xinitrc
+ sysserverrc=/usr/X11R6/lib/X11/xinit/xserverrc
+ defaultclient=/usr/X11R6/bin/xterm
+ defaultserver=/usr/X11R6/bin/X
+ defaultclientargs=
+ defaultserverargs=
+ clientargs=
+ serverargs=
+ [ -f /home/Chan Seng Loong/.xinitrc ]
+ defaultclientargs="/home/Chan Seng Loong/.xinitrc"
+ [ -f /home/Chan Seng Loong/.xserverrc ]
+ [ -f /usr/X11R6/lib/X11/xinit/xserverrc ]
+ whoseargs=client
+ [ x != x ]
+ [ x = x ]
+ [ x = x ]
+ client="/home/Chan Seng Loong/.xinitrc"
+ [ x = x ]
+ [ x = x -a x = x ]
+ server=
+ [ x = x ]
+ XAUTHORITY=/home/Chan Seng Loong/.Xauthority
+ export XAUTHORITY
+ removelist=
+ eval set -- "/home/Chan Seng Loong/.xinitrc"  --
+ set -- /home/Chan Seng Loong/.xinitrc --
+ xinit /home/Chan Seng Loong/.xinitrc --

+ userresources=/home/Chan Seng Loong/.Xresources
+ usermodmap=/home/Chan Seng Loong/.Xmodmap
+ sysresources=/usr/X11R6/lib/X11/xinit/.Xresources
+ sysmodmap=/usr/X11R6/lib/X11/xinit/.Xmodmap
+ [ -f /usr/X11R6/lib/X11/xinit/.Xresources ]
+ [ -f /usr/X11R6/lib/X11/xinit/.Xmodmap ]
+ [ -f /home/Chan Seng Loong/.Xresources ]
+ [ -f /home/Chan Seng Loong/.Xmodmap ]
+ twm
+ xclock -geometry 50x50-1+1
+ xterm -geometry 80x50+494+51
+ xterm -geometry 80x20+494-0
+ exec xterm -geometry 80x66+0+0 -name login
Fontconfig error: Cannot load default config file
Warning: Cannot convert string "" to type XftFont

Now the problem is the Fontconfig and freetype2
packages yes, I'm doing the "Install from
Internet"
but in the XFree86 category... I only find:

WindowMaker
XFree86-base
XFree86-bin
XFree86-bin-icons
XFree86-doc
XFree86-etc
XFree86-f100
XFree86-fcyr
XFree86-fenc
XFree86-fnts
XFree86-fscl
XFree86-fsrv
XFree86-html
XFree86-jdoc
XFree86-lib
XFree86-lib-compact
XFree86-man
XFree86-nest
XFree86-prog
XFree86-prt
XFree86-ps
XFree86-startup-script
XFree86-xserv
XFree86-xwinclip
Xaw3d
cgoban
fvwm
grace
gv
lessitf
libProplist
openbox
x2x
xfig
xfig-base
xfig-bin
xfig-doc
xfig-etc
xfig-lib
xfig-man
xgraph
xwinclip

Hmmm...

maybe they should include a search package
option..
can't find the Fontconfig and freetype2...

Btw, is fontconfig file in etc/X11 directory?


__
Do you Yahoo!?
Protect your identity with Yahoo! Mail AddressGuard
http://antispam.yahoo.com/whatsnewfree

Re: Cygwin XFree86 startx Problem

[Harold L Hunt II]

They are in the XFree86 category.  Should be sorted towards the top of 
the list.  You are doing an "Install from Internet", right?

Harold

Chan Seng Loong wrote:

hi... again

I tried using the "$HOME" -> qutoesbut failed

where can i get the fontconfig and freetype2
packages.. which category there in
can't find them in the cygwin setup...
Thanks

John

__
Do you Yahoo!?
Protect your identity with Yahoo! Mail AddressGuard
http://antispam.yahoo.com/whatsnewfree

Re: Cygwin XFree86 startx Problem

[Chan Seng Loong]

hi... again

I tried using the "$HOME" -> qutoesbut failed

where can i get the fontconfig and freetype2
packages.. which category there in
can't find them in the cygwin setup...


Thanks

John


__
Do you Yahoo!?
Protect your identity with Yahoo! Mail AddressGuard
http://antispam.yahoo.com/whatsnewfree

Re: Cygwin XFree86 startx Problem

[Igor Pechtchanski]

On Thu, 20 Nov 2003, Chan Seng Loong wrote:

> hi...
>
> I having problem using startx to startx the X window
> or X server...
>
> here are the error:
>
> Chan Seng [EMAIL PROTECTED] ~
> $ startx
> + userclientrc=/home/Chan Seng Loong/.xinitrc
> + userserverrc=/home/Chan Seng Loong/.xserverrc
> + sysclientrc=/usr/X11R6/lib/X11/xinit/xinitrc
> + sysserverrc=/usr/X11R6/lib/X11/xinit/xserverrc
> + defaultclient=/usr/X11R6/bin/xterm
> + defaultserver=/usr/X11R6/bin/X
> + defaultclientargs=
> + defaultserverargs=
> + clientargs=
> + serverargs=
> + [ -f /home/Chan Seng Loong/.xinitrc ]
> [: Seng: unknown operand
> + [ -f /usr/X11R6/lib/X11/xinit/xinitrc ]
> + defaultclientargs=/usr/X11R6/lib/X11/xinit/xinitrc
> + [ -f /home/Chan Seng Loong/.xserverrc ]
> [: Seng: unknown operand
> + [ -f /usr/X11R6/lib/X11/xinit/xserverrc ]
> + whoseargs=client
> + [ x != x ]
> + [ x = x ]
> + [ x = x ]
> + client=/usr/X11R6/lib/X11/xinit/xinitrc
> + [ x = x ]
> + [ x = x -a x = x ]
> + server=
> + [ x = x ]
> + XAUTHORITY=/home/Chan Seng Loong/.Xauthority
> + export XAUTHORITY
> + removelist=
> + xinit /usr/X11R6/lib/X11/xinit/xinitrc --
>
> + userresources=/home/Chan Seng Loong/.Xresources
> + usermodmap=/home/Chan Seng Loong/.Xmodmap
> + sysresources=/usr/X11R6/lib/X11/xinit/.Xresources
> + sysmodmap=/usr/X11R6/lib/X11/xinit/.Xmodmap
> + [ -f /usr/X11R6/lib/X11/xinit/.Xresources ]
> + [ -f /usr/X11R6/lib/X11/xinit/.Xmodmap ]
> + [ -f /home/Chan Seng Loong/.Xresources ]
> [: Seng: unknown operand
> + [ -f /home/Chan Seng Loong/.Xmodmap ]
> [: Seng: unknown operand
> + twm
> + xclock -geometry 50x50-1+1
> + xterm -geometry 80x50+494+51
> + xterm -geometry 80x20+494-0
> + exec xterm -geometry 80x66+0+0 -name login
> Fontconfig error: Cannot load default config file
> Warning: Cannot convert string "" to type XftFont
>
> I tried to fix the probelm using the XF86Config and .xinitrc file.
> but failed.
>
> Can someone help me to solve the problem..?
>
> Thanks
> John

John,

Your username (and, consequently, your home directory) has spaces in it.
The startx script is not space-in-filename friendly (missing quotes), and
thus some parts of it don't run correctly.  Below is a patch to the startx
script that should make it work with home dirs containing spaces
(untested).  Please save the attached patch as /tmp/startx.patch and run
'cd /usr/X11R6/bin && patch -p0 < /tmp/startx.patch'.  You should then be
able to use the script.

Harold, this patch is against /usr/X11R6/bin/startx from
XFree86-bin-4.3.0-7 (CVS revision "XFree86: startx.cpp 3.16"). I have a
feeling this file is auto-generated (haven't looked at the build process).
I don't know if you can incorporate this patch as-is as Cygwin-specific,
or if you need a patch to the original source, startx.cpp (either for
Cygwin or to send upstream).  Let me know either way, and I'll either
create a ChangeLog for this patch, or create one against the CVS source.
HTH,
Igor
-- 
http://cs.nyu.edu/~pechtcha/
  |\  _,,,---,,_[EMAIL PROTECTED]
ZZZzz /,`.-'`'-.  ;-;;,_[EMAIL PROTECTED]
 |,4-  ) )-,_. ,\ (  `'-'   Igor Pechtchanski, Ph.D.
'---''(_/--'  `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster."  -- Patrick Naughton--- startx-orig 2003-10-28 12:10:43.0 -0500
+++ startx  2003-11-20 12:11:31.068496000 -0500
@@ -14,8 +14,8 @@
 # $XFree86: xc/programs/xinit/startx.cpp,v 3.16 2003/01/24 21:30:02 herrb Exp $
 
 
-userclientrc=$HOME/.xinitrc
-userserverrc=$HOME/.xserverrc
+userclientrc="$HOME/.xinitrc"
+userserverrc="$HOME/.xserverrc"
 sysclientrc=/usr/X11R6/lib/X11/xinit/xinitrc
 sysserverrc=/usr/X11R6/lib/X11/xinit/xserverrc
 defaultclient=/usr/X11R6/bin/xterm
@@ -30,19 +30,16 @@ serverargs=""
 
 
 
-if [ -f $userclientrc ]; then
-defaultclientargs=$userclientrc
-elif [ -f $sysclientrc ]; then
-defaultclientargs=$sysclientrc
+if [ -f "$userclientrc" ]; then
+defaultclientargs="\"$userclientrc\""
+elif [ -f "$sysclientrc" ]; then
+defaultclientargs="\"$sysclientrc\""
 fi
 
-
-
-
-if [ -f $userserverrc ]; then
-defaultserverargs=$userserverrc
-elif [ -f $sysserverrc ]; then
-defaultserverargs=$sysserverrc
+if [ -f "$userserverrc" ]; then
+defaultserverargs="\"$userserverrc\""
+elif [ -f "$sysserverrc" ]; then
+defaultserverargs="\"$sysserverrc\""
 fi
 
 whoseargs="client"
@@ -52,15 +49,15 @@ while [ x"$1" != x ]; do
 /''*|\./''*)
if [ "$whoseargs" = "client" ]; then
if [ x"$clientargs" = x ]; then
-   client="$1"
+   client="\"$1\""
else
-   clientargs="$clientargs $1"
+   clientargs="$clientargs \"$1\""
fi
else
if [ x"$serverargs" = x ]; then
-   server="$1"
+   server="\"$1\""
 

Re: Cygwin XFree86 startx Problem

[Harold L Hunt II]

Henrik,

Henrik Schultz wrote:

With that being said, looks like you are missing the fontconfig and 
freetype2 packages.


No, they just need to enclose long file names with spaces in quotes ...
Not so sure about that.  That may fix some of the problems, but what 
about the last problem in the list:

Fontconfig error: Cannot load default config file
Warning: Cannot convert string "" to type XftFont
Harold

RE: Cygwin XFree86 startx Problem

[Henrik Schultz]

>With that being said, looks like you are missing the fontconfig and 
>freetype2 packages.

No, they just need to enclose long file names with spaces in quotes ...

- Henrik

Re: Cygwin XFree86 startx Problem

[Harold L Hunt II]

John,

I recommend using startxwin.bat.  I don't recommend using startx.

With that being said, looks like you are missing the fontconfig and 
freetype2 packages.

Harold

Chan Seng Loong wrote:

hi...

I having problem using startx to startx the X window
or X server...
here are the error:

Chan Seng [EMAIL PROTECTED] ~
$ startx
+ userclientrc=/home/Chan Seng Loong/.xinitrc
+ userserverrc=/home/Chan Seng Loong/.xserverrc
+ sysclientrc=/usr/X11R6/lib/X11/xinit/xinitrc
+ sysserverrc=/usr/X11R6/lib/X11/xinit/xserverrc
+ defaultclient=/usr/X11R6/bin/xterm
+ defaultserver=/usr/X11R6/bin/X
+ defaultclientargs=
+ defaultserverargs=
+ clientargs=
+ serverargs=
+ [ -f /home/Chan Seng Loong/.xinitrc ]
[: Seng: unknown operand
+ [ -f /usr/X11R6/lib/X11/xinit/xinitrc ]
+ defaultclientargs=/usr/X11R6/lib/X11/xinit/xinitrc
+ [ -f /home/Chan Seng Loong/.xserverrc ]
[: Seng: unknown operand
+ [ -f /usr/X11R6/lib/X11/xinit/xserverrc ]
+ whoseargs=client
+ [ x != x ]
+ [ x = x ]
+ [ x = x ]
+ client=/usr/X11R6/lib/X11/xinit/xinitrc
+ [ x = x ]
+ [ x = x -a x = x ]
+ server=
+ [ x = x ]
+ XAUTHORITY=/home/Chan Seng Loong/.Xauthority
+ export XAUTHORITY
+ removelist=
+ xinit /usr/X11R6/lib/X11/xinit/xinitrc --
+ userresources=/home/Chan Seng Loong/.Xresources
+ usermodmap=/home/Chan Seng Loong/.Xmodmap
+ sysresources=/usr/X11R6/lib/X11/xinit/.Xresources
+ sysmodmap=/usr/X11R6/lib/X11/xinit/.Xmodmap
+ [ -f /usr/X11R6/lib/X11/xinit/.Xresources ]
+ [ -f /usr/X11R6/lib/X11/xinit/.Xmodmap ]
+ [ -f /home/Chan Seng Loong/.Xresources ]
[: Seng: unknown operand
+ [ -f /home/Chan Seng Loong/.Xmodmap ]
[: Seng: unknown operand
+ twm
+ xclock -geometry 50x50-1+1
+ xterm -geometry 80x50+494+51
+ xterm -geometry 80x20+494-0
+ exec xterm -geometry 80x66+0+0 -name login
Fontconfig error: Cannot load default config file
Warning: Cannot convert string "" to type XftFont
I tried to fix the probelm using the XF86Config and
.xinitrc file. but
failed.
d
Can someone help me to solve the problem..?
Thanks

John

__
Do you Yahoo!?
Protect your identity with Yahoo! Mail AddressGuard
http://antispam.yahoo.com/whatsnewfree

Cygwin XFree86 startx Problem

[Chan Seng Loong]

hi...

I having problem using startx to startx the X window
or X server...

here are the error:

Chan Seng [EMAIL PROTECTED] ~
$ startx
+ userclientrc=/home/Chan Seng Loong/.xinitrc
+ userserverrc=/home/Chan Seng Loong/.xserverrc
+ sysclientrc=/usr/X11R6/lib/X11/xinit/xinitrc
+ sysserverrc=/usr/X11R6/lib/X11/xinit/xserverrc
+ defaultclient=/usr/X11R6/bin/xterm
+ defaultserver=/usr/X11R6/bin/X
+ defaultclientargs=
+ defaultserverargs=
+ clientargs=
+ serverargs=
+ [ -f /home/Chan Seng Loong/.xinitrc ]
[: Seng: unknown operand
+ [ -f /usr/X11R6/lib/X11/xinit/xinitrc ]
+ defaultclientargs=/usr/X11R6/lib/X11/xinit/xinitrc
+ [ -f /home/Chan Seng Loong/.xserverrc ]
[: Seng: unknown operand
+ [ -f /usr/X11R6/lib/X11/xinit/xserverrc ]
+ whoseargs=client
+ [ x != x ]
+ [ x = x ]
+ [ x = x ]
+ client=/usr/X11R6/lib/X11/xinit/xinitrc
+ [ x = x ]
+ [ x = x -a x = x ]
+ server=
+ [ x = x ]
+ XAUTHORITY=/home/Chan Seng Loong/.Xauthority
+ export XAUTHORITY
+ removelist=
+ xinit /usr/X11R6/lib/X11/xinit/xinitrc --

+ userresources=/home/Chan Seng Loong/.Xresources
+ usermodmap=/home/Chan Seng Loong/.Xmodmap
+ sysresources=/usr/X11R6/lib/X11/xinit/.Xresources
+ sysmodmap=/usr/X11R6/lib/X11/xinit/.Xmodmap
+ [ -f /usr/X11R6/lib/X11/xinit/.Xresources ]
+ [ -f /usr/X11R6/lib/X11/xinit/.Xmodmap ]
+ [ -f /home/Chan Seng Loong/.Xresources ]
[: Seng: unknown operand
+ [ -f /home/Chan Seng Loong/.Xmodmap ]
[: Seng: unknown operand
+ twm
+ xclock -geometry 50x50-1+1
+ xterm -geometry 80x50+494+51
+ xterm -geometry 80x20+494-0
+ exec xterm -geometry 80x66+0+0 -name login
Fontconfig error: Cannot load default config file
Warning: Cannot convert string "" to type XftFont

I tried to fix the probelm using the XF86Config and
.xinitrc file. but
failed.

Can someone help me to solve the problem..?

Thanks

John


__
Do you Yahoo!?
Protect your identity with Yahoo! Mail AddressGuard
http://antispam.yahoo.com/whatsnewfree

RE: [Cygwin/XFree86] Duplicate keystrokes in X Server

[Pille Geert (bizvdm)]

Hallo Harold,

I've finally installed Cygwin/XFree86 with setup, until this morning I was
still using a version that I installed manually (ahum).

Haven't spotted the duplicate keystrokes (yet?).

After setup, I installed XWin-4.3.0-20-Test01.exe, since I experienced the
"no key input".  This didn't help, as you already know.  Bugger, I hate the
mouse (don't like cats neither, I've got a dog).

I was sorry to read that you were not granted commit rights into the xfree86
organisation.  This is hard to imagine.  Do you know why?   Didn't they like
the colour of your tie?

Geert

> -Original Message-
> From: Harold L Hunt II [mailto:[EMAIL PROTECTED]
> Sent: zondag 21 september 2003 20:59
> To: cygx
> Subject: [Cygwin/XFree86] Duplicate keystrokes in X Server
> 
> 
> [BCCing seven people that have asked about this bug somewhat recently]
> 
> This bug has been around for a long time, but it was thought to be a 
> Cygwin/XFree86-specific bug.  However, I recently learned 
> that this is a 
> general XFree86 bug that is reproducible on, probably, all 
> other platforms.
> 
> Ivan Pascal submitted a patch to XFree86 that fixes the problem.  His 
> description of the problem and his patch can be found in this 
> archive of 
> his email:
> 
> http://www.mail-archive.com/devel%40xfree86.org/msg03245.html
> 
> 
> XFree86's Bugzilla Bug #301 also has information and discussion about 
> this bug:
> 
> http://bugs.xfree86.org/show_bug.cgi?id=301
> 
> 
> Finally, Ivan's patch was applied to XFree86-xserv-4.3.0-13, 
> which can 
> be downloaded and installed via Cygwin's setup.exe.  The "Test100" 
> release notes describe the other changes made in 4.3.0-13:
> 
> http://xfree86.cygwin.com/devel/shadow/changelog.html
> 
> 
> Enjoy,
> 
> Harold
> 


===
This email is confidential and intended solely for the use of the individual to whom 
it is addressed. 
If you are not the intended recipient, be advised that you have received this email in 
error and that any use, dissemination, forwarding, printing, or copying of this email 
is strictly prohibited.
You are explicitly requested to notify the sender of this email that the intended 
recipient was not reached.

Re: Cygwin/XFree86 - No longer associated with XFree86.org

[Jason Dufair]

I'll also chime in as a lurker to say that you have kicked some major
ass for us Cygwin/XFree86 users, Harold, and I think you've been nothing
but helpful and responsive on the list.  I think your plea on the
XFree86 list was reasonable.  Good luck as you explore other options.

Harold L Hunt II <[EMAIL PROTECTED]> writes:

> Egbert,
>
> Egbert Eich wrote:
>
>> Harold,
>> I find it sad that you had to make this decision.
>> I've just been absent for a little more than two weeks and
>> was unable to commit patches - look what came out of it.
>
> Egbert, I am sorry, I want to make it absolutely clear that my raising
> the issue with XFree86.org and subsequent decision had nothing to do
> with you.  You were actually a great help to me, I appreciate the work
> that you did with me very much.  There was a larger problem
> here... one that had nothing to do with you.
>
>> I understand that the level of frustration among contributors
>> has risen to a point that people are starting to use bad words.
>> I've tried to get support from individual core team members
>> for giving you commit rights. After I was unable to do so (maybe
>> I asked the wrong ones) I decided to no longer persue the issue.
>> None of the initiatives I've made so far have been accepted.
>
> I appreciate that Egbert.  That really gets to the heart of the
> matter: this isn't about cvs commit access, this is about the
> arbitrary, subjective, and unresponsive manner in which the project is
> being managed.
>
>> I don't understand why people cannot deal with issues on the
>> pragmatic level by looking at how one can best distribute
>> the workload so that the burdeon on each individual volunteer
>> is reduced.
>
> I really wish they could have seen that too.
>
>> The discussion always turns to who owes what to whom. This is
>> the wrong question. All or most of us are volunteers. Therefore
>> noone owes anything to anybody.
>> I get more and more the impression that David is working on
>> narrowing down the scope of XFree86. There are alternatives in sight
>> and I hope something will be in place before too long that will
>> again serve a place where
>> people interested in X can meet and work together.
>
> Yes, I am beginning to work with some other developers who have left
> XFree86.org as well.  It is so unfortunate that XFree86.org is pushing
> away developers one-by-one, only to assemble the same group
> elsewhere. That is a pointless waste of time; that sort of thing
> should not have to happen.
>
> I was a little surprised too to see that my request was interpreted as
> being owed something :)  Jeez, not only is the process of getting cvs
> commit access undefined, it is a veritable mine field; you cannot
> possibly ask in a humble enough manner for their taste.
>
> Anyhow, I want to reiterate again that I enjoy working with you Egbert
> and that I hope we continue to work together in the future.
>
> Thanks for your input,
>
> Harold

-- 
Jason Dufair - [EMAIL PROTECTED]
http://www.dufair.org/
"Time flies like an arrow. Fruit flies like a banana."
-- Groucho Marx

Re: cygwin xfree86 split

[Harold L Hunt II]

Leo,

Leo Mekenkamp wrote:
Hi Harold,

You probably have never heard about me, and until an hour ago I had
never heard about you, but that does not stop me to climb into my
keyboard and send you this email.
I read 'the thread' on the mailing list, and what I can conclude on it
can be simply summarized as: You seem to be doing your best in making a
very usefull free piece of software; 'they' seem to be high up in some
ivory tower thinking that all the x code base are belong to them.
Such a pity. Instead of trying to resolve your issues the only thing the
xfree guys seem to do is push you to a certain state where 'your
emotions take over' and you let out a 'fuck you', and then they very
childishly respond that they will not listen to you anymore when you let
out such insults.
I can only conclude that the xfree guys have lost touch with the
positive side of themselves and have let arrogance take over. An
oss/free software project should be all about working together; they are
certainly not doing their best to work together.
So, to keep with your words: 'fuck them'; maybe the xouvert guys will
appreciate your contributions? I do hope this whole thing does not take
away your spirit in working on cygwin.
Heh heh... Thanks for your support.

Don't worry, I haven't lost the spirit.  I have a set number of hours to 
work on Cygwin/X per month and now I won't be spending any of those 
hours trying to keep the XFree86 CVS tree in synch.

We will be working with some other X Window System projects.  I will 
make a more formal announcement later, but I want to just code for a few 
days.

Thanks again,

Harold

cygwin xfree86 split

[Leo Mekenkamp]

Hi Harold,

You probably have never heard about me, and until an hour ago I had
never heard about you, but that does not stop me to climb into my
keyboard and send you this email.

I read 'the thread' on the mailing list, and what I can conclude on it
can be simply summarized as: You seem to be doing your best in making a
very usefull free piece of software; 'they' seem to be high up in some
ivory tower thinking that all the x code base are belong to them.

Such a pity. Instead of trying to resolve your issues the only thing the
xfree guys seem to do is push you to a certain state where 'your
emotions take over' and you let out a 'fuck you', and then they very
childishly respond that they will not listen to you anymore when you let
out such insults.

I can only conclude that the xfree guys have lost touch with the
positive side of themselves and have let arrogance take over. An
oss/free software project should be all about working together; they are
certainly not doing their best to work together.

So, to keep with your words: 'fuck them'; maybe the xouvert guys will
appreciate your contributions? I do hope this whole thing does not take
away your spirit in working on cygwin.

Cheers & good luck,
Leo Mekenkamp

Re: Cygwin/XFree86 - No longer associated with XFree86.org

[Harold L Hunt II]

Daniel,

Armbrust, Daniel C. wrote:

Harold, 

I have been lurking on this list for a while now.  I don't know much about XFree86, or the politics, or any history.  But I read the threads that led up to your decision.  I applaud you.  You asked for something completely reasonable, and (pardon the language) David Dawes came off as a complete jackass.  

I have worked with Jakarta Ant, the Eclipse Project, and Jakarta Lucene to varying degrees.  And I have never seen someone on any of those mailing lists get treated like you were.  And, as an example of a well functioning open source project, when someone new came to lucene, he turned in some quality patches over the course of about a month.  About the equivalent to what I see you commit on this mailing list in a week.  And they made him a full fledged committer.  No problems, no insults, no lie detector tests.  They voted, and it was done.

That it how it is supposed to work.  

The XFree86 organization looks like it is being run by a bunch of power hungry fools.

Thanks for all of your time and work, 
No problem.  I enjoy it.

Thanks for your support.

Harold

RE: Cygwin/XFree86 - No longer associated with XFree86.org

[Armbrust, Daniel C.]

Harold, 

I have been lurking on this list for a while now.  I don't know much about XFree86, or 
the politics, or any history.  But I read the threads that led up to your decision.  I 
applaud you.  You asked for something completely reasonable, and (pardon the language) 
David Dawes came off as a complete jackass.  

I have worked with Jakarta Ant, the Eclipse Project, and Jakarta Lucene to varying 
degrees.  And I have never seen someone on any of those mailing lists get treated like 
you were.  And, as an example of a well functioning open source project, when someone 
new came to lucene, he turned in some quality patches over the course of about a 
month.  About the equivalent to what I see you commit on this mailing list in a week.  
And they made him a full fledged committer.  No problems, no insults, no lie detector 
tests.  They voted, and it was done.

That it how it is supposed to work.  

The XFree86 organization looks like it is being run by a bunch of power hungry fools.

Thanks for all of your time and work, 

Dan

Re: Cygwin/XFree86 - No longer associated with XFree86.org

[Harold L Hunt II]

Egbert,

Egbert Eich wrote:

Harold,

I find it sad that you had to make this decision.
I've just been absent for a little more than two weeks and
was unable to commit patches - look what came out of it.
Egbert, I am sorry, I want to make it absolutely clear that my raising 
the issue with XFree86.org and subsequent decision had nothing to do 
with you.  You were actually a great help to me, I appreciate the work 
that you did with me very much.  There was a larger problem here... one 
that had nothing to do with you.

I understand that the level of frustration among contributors
has risen to a point that people are starting to use bad words.
I've tried to get support from individual core team members
for giving you commit rights. After I was unable to do so (maybe
I asked the wrong ones) I decided to no longer persue the issue.
None of the initiatives I've made so far have been accepted.
I appreciate that Egbert.  That really gets to the heart of the matter: 
this isn't about cvs commit access, this is about the arbitrary, 
subjective, and unresponsive manner in which the project is being managed.

I don't understand why people cannot deal with issues on the
pragmatic level by looking at how one can best distribute
the workload so that the burdeon on each individual volunteer
is reduced.
I really wish they could have seen that too.

The discussion always turns to who owes what to whom. This is
the wrong question. All or most of us are volunteers. Therefore
noone owes anything to anybody.
I get more and more the impression that David is working on
narrowing down the scope of XFree86. 
There are alternatives in sight and I hope something will be 
in place before too long that will again serve a place where
people interested in X can meet and work together.
Yes, I am beginning to work with some other developers who have left 
XFree86.org as well.  It is so unfortunate that XFree86.org is pushing 
away developers one-by-one, only to assemble the same group elsewhere. 
That is a pointless waste of time; that sort of thing should not have to 
happen.

I was a little surprised too to see that my request was interpreted as 
being owed something :)  Jeez, not only is the process of getting cvs 
commit access undefined, it is a veritable mine field; you cannot 
possibly ask in a humble enough manner for their taste.

Anyhow, I want to reiterate again that I enjoy working with you Egbert 
and that I hope we continue to work together in the future.

Thanks for your input,

Harold

Re: Cygwin/XFree86 - No longer associated with XFree86.org

[Egbert Eich]

Harold,

I find it sad that you had to make this decision.
I've just been absent for a little more than two weeks and
was unable to commit patches - look what came out of it.

I understand that the level of frustration among contributors
has risen to a point that people are starting to use bad words.
I've tried to get support from individual core team members
for giving you commit rights. After I was unable to do so (maybe
I asked the wrong ones) I decided to no longer persue the issue.
None of the initiatives I've made so far have been accepted.

I don't understand why people cannot deal with issues on the
pragmatic level by looking at how one can best distribute
the workload so that the burdeon on each individual volunteer
is reduced.
The discussion always turns to who owes what to whom. This is
the wrong question. All or most of us are volunteers. Therefore
noone owes anything to anybody.
I get more and more the impression that David is working on
narrowing down the scope of XFree86. 
There are alternatives in sight and I hope something will be 
in place before too long that will again serve a place where
people interested in X can meet and work together.

Cheers,
Egbert.

Re: xouvert? (was Re: Cygwin/XFree86 - No longer associated with XFree86.org)

[David Fraser]

Harold L Hunt II wrote:

Mitch,

Mitchell Skinner wrote:

I followed the [EMAIL PROTECTED] discussion and the xwin.org and
xouvert.org bits, and at first I wasn't sure if the complainers had a
real beef or if the hubbub was the outcome of some bizarre historical
politics, but it's becoming clearer and clearer that the xfree86 guys
are dropping the ball.  Lots of long-time, serious contributors are all
saying the same thing; hopefully all those that have a problem with the
old system can get together and start a single new mainline rather than
splinter into a bunch of different groups.


It looks like people are regrouping.  Keith Packard and Jim Gettys are 
over at freedesktop.org.  They have most of the libs (that aren't 
maintained elsewhere) imported and autotooled.  I think that is going 
to be my long-term destination for our bits... but I am going to work 
in an xc/ style repository in the mean time.  It will take a few 
months to whip the autotooled build into shape, and I don't want to 
forgo having a CVS tree during that period.

xouvert is using Arch.  I am not really familiar with Arch; I don't 
even know if it works on Cygwin.  I personally don't think I would 
have the time to invest in setting up and maintaining a version of the 
code in xouvert... but I would not be opposed to someone else doing 
this and tracking my patches.  That would be advantageous to us and them.
I've tried Arch, but quite a while ago.
It has some fantastic features, much much better than CVS.
Unfortunately though it wasn't working with cygwin then, but can't say 
if that's been fixed.
I think it was mostly due to them choosing strange names for directories 
like {arch} etc.

David

Re: xouvert? (was Re: Cygwin/XFree86 - No longer associated with XFree86.org)

[Harold L Hunt II]

Mitch,

Mitchell Skinner wrote:
FWIW,

I read the cygwin-xfree mailing list archives from time to time, and I
just read the [EMAIL PROTECTED] thread linked from /., and it looks to
me like Harold was being pretty reasonable and was getting a terrible
response.
Thanks.  It was so weird to write what I thought was a reasonable reply 
only to be essentially shouted at in response.  It is reassuring to get 
messages from people saying that my posts were in fact reasonable.

I followed the [EMAIL PROTECTED] discussion and the xwin.org and
xouvert.org bits, and at first I wasn't sure if the complainers had a
real beef or if the hubbub was the outcome of some bizarre historical
politics, but it's becoming clearer and clearer that the xfree86 guys
are dropping the ball.  Lots of long-time, serious contributors are all
saying the same thing; hopefully all those that have a problem with the
old system can get together and start a single new mainline rather than
splinter into a bunch of different groups.
It looks like people are regrouping.  Keith Packard and Jim Gettys are 
over at freedesktop.org.  They have most of the libs (that aren't 
maintained elsewhere) imported and autotooled.  I think that is going to 
be my long-term destination for our bits... but I am going to work in an 
xc/ style repository in the mean time.  It will take a few months to 
whip the autotooled build into shape, and I don't want to forgo having a 
CVS tree during that period.

xouvert is using Arch.  I am not really familiar with Arch; I don't even 
know if it works on Cygwin.  I personally don't think I would have the 
time to invest in setting up and maintaining a version of the code in 
xouvert... but I would not be opposed to someone else doing this and 
tracking my patches.  That would be advantageous to us and them.

Speaking of which, since the xouvert guys announced their intention to
fork, I've been wondering which way cygwin-xfree86 would go.  What do
cygwin-xfree subscribers think about that?
Oops, I think I told you above :)

Harold

xouvert? (was Re: Cygwin/XFree86 - No longer associated with XFree86.org)

[Mitchell Skinner]

FWIW,

I read the cygwin-xfree mailing list archives from time to time, and I
just read the [EMAIL PROTECTED] thread linked from /., and it looks to
me like Harold was being pretty reasonable and was getting a terrible
response.

I followed the [EMAIL PROTECTED] discussion and the xwin.org and
xouvert.org bits, and at first I wasn't sure if the complainers had a
real beef or if the hubbub was the outcome of some bizarre historical
politics, but it's becoming clearer and clearer that the xfree86 guys
are dropping the ball.  Lots of long-time, serious contributors are all
saying the same thing; hopefully all those that have a problem with the
old system can get together and start a single new mainline rather than
splinter into a bunch of different groups.

Speaking of which, since the xouvert guys announced their intention to
fork, I've been wondering which way cygwin-xfree86 would go.  What do
cygwin-xfree subscribers think about that?

Mitch

Re: Problems with shared lesstif and shared Xt on Cygwin/XFree86

[Harold L Hunt II]

Matthieu,

Matthieu Herrb wrote:

Torrey Lyons wrote (in a message from Saturday 25)
 > The issue on Mac OS X is that most shared libraries want to be built 
 > as "two-level namespace" images. Two-level namespace images have 
 > significant advantages in loading speed, but they require that they 
 > have no unresolved symbols when linking the library. This is why the 
 > darwinLib.tmpl contains a complete list of every library's 
 > dependencies. Unfortunately this causes a problem with two shared 
 > libraries, Xt and Xfont. The problem is that these libraries are 
 > designed to have certain symbols undefined and to have theses 
 > references resolved at application link time by one of various other 
 > library choices. In the case of Xt, SM and ICE provide the default 
 > resolution of these symbols in darwinLib.tmpl (and cygwin.tmpl), but 
 > symbols with the same names from lesstif should be used instead when 
 > the application is linked with it. Two-level namespace libraries 
 > don't allow you to do that since all symbols get resolved at library 
 > link time, not application link time. Thus we fixed this problem by 
 > building libXt and libXfont as flat namespace images, which have the 
 > same linking semantics that most people on other *nixes are used to.

Weak symbols can be used on systems that support them to solve this
kind of issues. Does cygwin support them ? 
That sounds like a good idea... but I don't know that answer about 
whether we support them or not.

If so libXt and libXfont can be patched to provide weak definitions of
the SM/ICE functions it needs instead of linking libXt against those
libs. 
That would be nice, if Cygwin support them.  I will try to find out.

Thanks for your input,

Harold

AW: Problems with shared lesstif and shared Xt on Cygwin/XFree86

[Ralf Habacker]

Hi
> Harold L Hunt II wrote:
>
> > I tried a build without $(SMLIB) and $(ICELIB) in SharedXtReqs, but it
> > fails to link due to unresolved symbols (all symbols must be resolved at
> > library link time in DLLs on Windows).
> >
> > I will have to consult with the rest of the Cygwin people to see what we
> > should do now.
>
> I'm working on a similar problem with libXfont. The more I think about it,
> the more problems I see and I think this is a feature, which ld
> must provide.
>
> The cases where the symbol is undefined in the shared library might get
> resolved with dispatch functions and code in the program which changes
> the pointer which is used by the dispatch code.
>
This might be possible, but how could ld find the propper library ?

Let me explain a few notes to this topic, may be this helps to understand
the relating things a little bit more.

linux and other unix os uses a runtime search for such symbols through
ld.so, ldconfig and friends.  (see
http://www.cs.princeton.edu/cgi-bin/man2html?ld.so.1:1 and
http://www.cs.princeton.edu/cgi-bin/man2html?ld.so.1:1  for more
informations)

Beside the recommended linker patch, something like the above mentioned
ld.so functionality has to be implemented too. There must be a runtime
specific code located somewhere in the (mingw- and cygwin's) applications
startup library (like the pseudo-runtime-reloc code see
http://www.cygwin.com/ml/cygwin-patches/2002-q4/msg00205.html) or somewhere
else.

As far as I can see the runtime stuff could be implemented in two manners:

1. when the dll is loaded by the dll startup code. The loading stuff
searches the PATH (or using an newly introduced LD_LIBRARY_PATH) environment
var for dll's and their exported symbols to find a valid symbol and resolves
this reference.

2. at the time an unresolved symbol is called (lazy binding, ms and other
native win32 linkers are supporting such a mode). Unfortunally this work
only with functions symbols and not with data symbols, because of the
different accessing mode (call versus content loading/writing).

Both cases increases the loading time of an application and may end up in
seg faults in case more than one dll exports the requested symbol and the
search path is searched in an unwanted order. The increased loading time
could be reduced by a dependency cache like ldconfig does, but this decision
could be reached in real test scenarios. For the dll ordering problem
currently I have no idea how to fix, may be someone else can help with this.

The linker patch should contain the following parts:
1. a command line options to enable/disable dynamic-runtime-linking support
( --[no-]allow-shlib-undefined  seems to be usable)
2. it has to detect unresolved symbols and shuld build internal code stubs
(like the regular function import stub) to solve symbol requests. For the
runtime stuff  is has to provide internal tables (the dynamic import table)
allowing the runtime stuff to find and resolve this dependencies. These
import tables are probably not be visible in the PE-dll supplied import,
they are only internal defined.

Another approach seems to be to link all such undefined symbols to one known
symbol in an specific helper dll, augmented with the original symbol in an
currently unspecified decoration, so that this dll is able to solve the
undefined symbol. The advantage of this solution is that there is no
specific runtime stuff in each dll or application necessary. All this stuff
is located in one dll and could be upgraded and improved independently from
the real application or dll's (for cygwin this dll will be probably
cygwin1.dll, for mingw the mingwxx.dll).

BTW: I've cc'ed this email to the binutils list, because there are more
people with ld knowledge, who can give some more informations/solutions for
this issue.

Hope that help
Ralf



(It may be possible to us a dummy dll'

Re: Problems with shared lesstif and shared Xt on Cygwin/XFree86

[Matthieu Herrb]

Torrey Lyons wrote (in a message from Saturday 25)
 > The issue on Mac OS X is that most shared libraries want to be built 
 > as "two-level namespace" images. Two-level namespace images have 
 > significant advantages in loading speed, but they require that they 
 > have no unresolved symbols when linking the library. This is why the 
 > darwinLib.tmpl contains a complete list of every library's 
 > dependencies. Unfortunately this causes a problem with two shared 
 > libraries, Xt and Xfont. The problem is that these libraries are 
 > designed to have certain symbols undefined and to have theses 
 > references resolved at application link time by one of various other 
 > library choices. In the case of Xt, SM and ICE provide the default 
 > resolution of these symbols in darwinLib.tmpl (and cygwin.tmpl), but 
 > symbols with the same names from lesstif should be used instead when 
 > the application is linked with it. Two-level namespace libraries 
 > don't allow you to do that since all symbols get resolved at library 
 > link time, not application link time. Thus we fixed this problem by 
 > building libXt and libXfont as flat namespace images, which have the 
 > same linking semantics that most people on other *nixes are used to.

Weak symbols can be used on systems that support them to solve this
kind of issues. Does cygwin support them ? 

If so libXt and libXfont can be patched to provide weak definitions of
the SM/ICE functions it needs instead of linking libXt against those
libs. 



Matthieu

Re: Problems with shared lesstif and shared Xt on Cygwin/XFree86

[Alexander Gottwald]

Harold L Hunt II wrote:

> I tried a build without $(SMLIB) and $(ICELIB) in SharedXtReqs, but it
> fails to link due to unresolved symbols (all symbols must be resolved at
> library link time in DLLs on Windows).
>
> I will have to consult with the rest of the Cygwin people to see what we
> should do now.

I'm working on a similar problem with libXfont. The more I think about it,
the more problems I see and I think this is a feature, which ld must provide.

The cases where the symbol is undefined in the shared library might get
resolved with dispatch functions and code in the program which changes
the pointer which is used by the dispatch code.

bye
ago
-- 
 [EMAIL PROTECTED]
 http://www.gotti.org   ICQ: 126018723

Re: host cygwin/xfree86 code on sources.redhat.com

[Harold L Hunt II]

I have thought about it.

There are really two phases to this:

1) Maintain a fork of the 4.3.0 tree for builds and bug fixes for a few 
months.

2) Work in parallel on autotooling the Cygwin/X build so we can build on 
the xserver tree on freedesktop.org.  This is more of an experimental 
setup.  It will require a lot of work and won't be ready for some time.

I don't want to get into all of the details right now... I am still 
thinking about this.

Thanks for your insight,

Harold

Nicholas Wourms wrote:

Harold,

It just makes sense, considering everything else is hosted there as 
well.  CGF has made offers in the past to host serious projects' code, 
I'm sure Cygwin/XFree86 qualifies.

It saddens me to see that we cannot get the time of day from the XFree86 
people.  Shame on them for that!

Cheers,
Nicholas

host cygwin/xfree86 code on sources.redhat.com

[Nicholas Wourms]

Harold,

It just makes sense, considering everything else is hosted there as 
well.  CGF has made offers in the past to host serious projects' code, 
I'm sure Cygwin/XFree86 qualifies.

It saddens me to see that we cannot get the time of day from the XFree86 
people.  Shame on them for that!

Cheers,
Nicholas

Re: Cygwin/XFree86 - No longer associated with XFree86.org

[Harold L Hunt II]

Alan Hourihane wrote:

On Mon, Oct 27, 2003 at 11:35:20AM -0500, Harold L Hunt II wrote:

6) Alternatives are being evaluated for hosting Cygwin/XFree86 code in 
CVS.  Hosts that can provide CVS commit access for at least five 
Cygwin/XFree86 developers will be given priority.


Harold,

I thought you already had the CVS for Cygwin/XFree86 sorted out, by
using what you'd already setup in http://sf.net/projects/xoncygwin ?
It is something I am looking into.

It all depends on if we want to have to import and maintain the clients.

You and Alexander Gottwald (and myself) have already been using this for
quite some time now. Couldn't you give Kensuke et al commit access there rather 
than seeking out yet another repository ?
Looking into it.

Harold

Re: Cygwin/XFree86 - No longer associated with XFree86.org

[Alan Hourihane]

On Mon, Oct 27, 2003 at 11:35:20AM -0500, Harold L Hunt II wrote:
> 6) Alternatives are being evaluated for hosting Cygwin/XFree86 code in 
> CVS.  Hosts that can provide CVS commit access for at least five 
> Cygwin/XFree86 developers will be given priority.

Harold,

I thought you already had the CVS for Cygwin/XFree86 sorted out, by
using what you'd already setup in http://sf.net/projects/xoncygwin ?

You and Alexander Gottwald (and myself) have already been using this for
quite some time now. Couldn't you give Kensuke et al commit access there rather 
than seeking out yet another repository ?

Alan.

Cygwin/XFree86 - No longer associated with XFree86.org

[Harold L Hunt II]

It seems that David Dawes has made his decision not to let the 
Cygwin/XFree86 project commit patches directly to the XFree86.org CVS 
tree; he doesn't seem to want to go on record saying this, but he has 
written several messages during this discussion about ftp servers, cvs 
servers, etc., while making no attempt to provide a direct answer to my 
question.  Had he intended otherwise he could have easily said, "Gotta 
wait until the next board meeting", or "Sorry, server died, gonna have 
to wait a couple days".  I can only interpret his ignoring the issue as 
a passive refusal to grant Cygwin/XFree86 CVS commit access.

In the interests of providing a more open development model, the 
Cygwin/XFree86 project will no longer be maintaining code in the 
XFree86.org CVS tree.  Maintaining code in XFree86.org's CVS tree 
provides little benefit in relation to the amount of time required to do 
so; XFree86.org is passively unwilling to work with Cygwin/XFree86 to 
reduce the amount of time required.

What this means for Cygwin/XFree86 users and developers
===
1) No major changes to the files currently distributed with 
Cygwin/XFree86 for at least a month.

2) The Cygwin/XFree86 mailing lists and project pages will stay at 
cygwin.com.

3) Builds will continue to be made from the 4.3.0 snapshot, patched with 
the latest Cygwin/XFree86 patches.

4) A 4.4.0 snapshot may be pulled to make builds from.

5) Patches for Cygwin-specific code will no longer be sent to 
XFree86.org.  Non Cygwin-specific patches should still be sent, to be 
dealt with as XFree86 pleases.

6) Alternatives are being evaluated for hosting Cygwin/XFree86 code in 
CVS.  Hosts that can provide CVS commit access for at least five 
Cygwin/XFree86 developers will be given priority.

What this means for Cygwin
==
Nothing.  Nada.  Zilch.  They were not involved in this at all.
What this means for XFree86
===
Some will say nothing.  Some will say good riddance.  Some will say this 
is the beginning of the end.  Who knows?  Who cares?  Let /. figure it out.

Harold

Re: Cygwin/XFree86 - Staying or leaving XFree86.org? [Was: Re: Cygwin/XFree86 Bugs?]

[Harold L Hunt II]

David,

Without getting involved in the disagreement, what about Xouvert?
Oh yeah, alternatives are being looked into.  More on that later.

Harold

Re: Cygwin/XFree86 - Staying or leaving XFree86.org? [Was: Re: Cygwin/XFree86 Bugs?]

[David Fraser]

Harold L Hunt II wrote:

Michel DÃnzer wrote:

Well, you know, XFree86's disregard for offers to help made by 
developers that have been with the project for over two years are 
certainly part of the problem.


Err, this is about bug triage, which you can do just as well as
everybody else.


No, this is about my submitting Cygwin-specific bugs that can't 
actually be assigned to me for committing them, even though I am the 
"expert" on Cygwin/XFree86.  This thread started to point out the 
hypocrisy of the situation and to see what the official response to 
this was.

I agree that you should be able to commit Cygwin stuff yourself (but I
can't do anything about it), I'm afraid your rants and threats won't do
much good there though.


Thanks for your agreement.

Hmm... rants and threats isn't very polite.  I have asked numerous 
people to both "elect" me to get commit access and I have asked people 
with the power to do so to set me up with it (all privately, off list, 
as it should be).  Nothing has ever happened from any of those requests.

What else am I supposed to do?  I have made a decision that my family 
deserves the time that XFree86 is having me waste being a patch nanny.

In light of that decision, I am either going to commit my bugs 
directly to XFree86's CVS, or I am going to leave the project.  It is 
not a "rant" or "threat" to tell people this.  This is simply the way 
it is going to be, from my standpoint.  As I said, I have made a 
decision to give this time back to my family, and I am going to do 
that, regardless of what other people decide their role in this will be.

Either way this plays out, I get to spend less time developing on X 
for the same amount of impact, and my family recovers three or four 
hours a month.  When you are in a graduate degree program and working 
30-40 hours per week, that is a *lot* of time.

So here is the choice to be made again:
1) Set me up with CVS commit access with the understanding that I 
commit only Cygwin-specific patches and all others get sent in through 
bugs.xfree86.org for review by other developers.  -or-

2) I will stop sending patches for Cygwin support.  It is simply not 
worth my time and I feel that the XFree86 project has no right to take 
that time away from me or my family.

I ask that the CVS commit access be granted within 2 months if it is 
going to be granted.

If access is not going to be granted, then a short note telling me to 
piss off would be appreciated so that I can start setting up my tree 
elsewhere.

Thank you very much for *your* time,

Harold

Without getting involved in the disagreement, what about Xouvert?

David

Cygwin/XFree86 - Staying or leaving XFree86.org? [Was: Re: Cygwin/XFree86 Bugs?]

[Harold L Hunt II]

Michel DÃnzer wrote:
Well, you know, XFree86's disregard for offers to help made by 
developers that have been with the project for over two years are 
certainly part of the problem.
Err, this is about bug triage, which you can do just as well as
everybody else.
No, this is about my submitting Cygwin-specific bugs that can't actually 
be assigned to me for committing them, even though I am the "expert" on 
Cygwin/XFree86.  This thread started to point out the hypocrisy of the 
situation and to see what the official response to this was.

I agree that you should be able to commit Cygwin stuff yourself (but I
can't do anything about it), I'm afraid your rants and threats won't do
much good there though.
Thanks for your agreement.

Hmm... rants and threats isn't very polite.  I have asked numerous 
people to both "elect" me to get commit access and I have asked people 
with the power to do so to set me up with it (all privately, off list, 
as it should be).  Nothing has ever happened from any of those requests.

What else am I supposed to do?  I have made a decision that my family 
deserves the time that XFree86 is having me waste being a patch nanny.

In light of that decision, I am either going to commit my bugs directly 
to XFree86's CVS, or I am going to leave the project.  It is not a 
"rant" or "threat" to tell people this.  This is simply the way it is 
going to be, from my standpoint.  As I said, I have made a decision to 
give this time back to my family, and I am going to do that, regardless 
of what other people decide their role in this will be.

Either way this plays out, I get to spend less time developing on X for 
the same amount of impact, and my family recovers three or four hours a 
month.  When you are in a graduate degree program and working 30-40 
hours per week, that is a *lot* of time.

So here is the choice to be made again:
1) Set me up with CVS commit access with the understanding that I commit 
only Cygwin-specific patches and all others get sent in through 
bugs.xfree86.org for review by other developers.  -or-

2) I will stop sending patches for Cygwin support.  It is simply not 
worth my time and I feel that the XFree86 project has no right to take 
that time away from me or my family.

I ask that the CVS commit access be granted within 2 months if it is 
going to be granted.

If access is not going to be granted, then a short note telling me to 
piss off would be appreciated so that I can start setting up my tree 
elsewhere.

Thank you very much for *your* time,

Harold

Re: Cygwin/XFree86 Bugs?

[Harold L Hunt II]

Thomas Dickey wrote:

On Sat, 25 Oct 2003, Harold L Hunt II wrote:


Seriously, I don't know why I waste my time submitting patches that are
specific to my platform and then wait up to three weeks for them to be
committed.  It is a waste of my time and an insult that I am made to do


well, when you graduate and (presumably) find a real job, you'll have
a chance to get an idea of where time goes.
> the patches _are_ applied, right?

Thanks for your amazing support Thomas.

You don't know anything about me, so you can keep your blanket 
statements about where you time goes to yourself.

By the way, how often do you have to go to the doctor's office?  How 
often do you have to get prescriptions refiled?  How often do you have 
to change the tubing for a medical device that is attached to you?  Huh? 
 Didn't think so.  So, please take this as kindly as possible when I 
say: Go fuck yourself.

The funny thing here is that I am volunteering to take care of my own 
patches and I am personally insulted that my offer is being ignored.

Harold

Re: Cygwin/XFree86 Bugs?

[Thomas Dickey]

On Sat, 25 Oct 2003, Harold L Hunt II wrote:

> Seriously, I don't know why I waste my time submitting patches that are
> specific to my platform and then wait up to three weeks for them to be
> committed.  It is a waste of my time and an insult that I am made to do

well, when you graduate and (presumably) find a real job, you'll have
a chance to get an idea of where time goes.

the patches _are_ applied, right?

-- 
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net

Re: Cygwin/XFree86 Bugs?

[Michel Dänzer]

On Sat, 2003-10-25 at 19:53, Harold L Hunt II wrote:
> Michel DÃnzer wrote:
> > On Wed, 2003-10-22 at 17:13, Egbert Eich wrote: 
> > 
> >>Marc Aurele La France writes:
> >> > 
> >> > [EMAIL PROTECTED] is an ML anyone can subscribe to.  I am, and, I
> >> > believe, so is Egbert.
> >>
> >>No, not currently. I usually go to the web interface and 
> >>look at the open bugs, process new ones that can be handled 
> >>quickly, or try to assign them to an expert on the specific 
> >>area.
> >>
> >>There are a lot more areas than we have experts - in these
> >>cases I try to work on the ticket myself. This, and the
> >>low quality of some of the submissions, consumes a 
> >>considerable amount of time.
> > 
> > 
> > Indeed, you're doing most of the bugzilla work alone; it's a pity there
> > aren't more people helping with that.
> 
> Well, you know, XFree86's disregard for offers to help made by 
> developers that have been with the project for over two years are 
> certainly part of the problem.

Err, this is about bug triage, which you can do just as well as
everybody else.

I agree that you should be able to commit Cygwin stuff yourself (but I
can't do anything about it), I'm afraid your rants and threats won't do
much good there though.


-- 
Earthling Michel DÃnzer   \  Debian (powerpc), XFree86 and DRI developer
Software libre enthusiast  \ http://svcs.affero.net/rm.php?r=daenzer

Re: Problems with shared lesstif and shared Xt on Cygwin/XFree86

[Harold L Hunt II]

Thanks Torrey.

I tried a build without $(SMLIB) and $(ICELIB) in SharedXtReqs, but it 
fails to link due to unresolved symbols (all symbols must be resolved at 
library link time in DLLs on Windows).

I will have to consult with the rest of the Cygwin people to see what we 
should do now.

Thanks again,

Harold

Torrey Lyons wrote:

The issue on Mac OS X is that most shared libraries want to be built as 
"two-level namespace" images. Two-level namespace images have 
significant advantages in loading speed, but they require that they have 
no unresolved symbols when linking the library. This is why the 
darwinLib.tmpl contains a complete list of every library's dependencies. 
Unfortunately this causes a problem with two shared libraries, Xt and 
Xfont. The problem is that these libraries are designed to have certain 
symbols undefined and to have theses references resolved at application 
link time by one of various other library choices. In the case of Xt, SM 
and ICE provide the default resolution of these symbols in 
darwinLib.tmpl (and cygwin.tmpl), but symbols with the same names from 
lesstif should be used instead when the application is linked with it. 
Two-level namespace libraries don't allow you to do that since all 
symbols get resolved at library link time, not application link time. 
Thus we fixed this problem by building libXt and libXfont as flat 
namespace images, which have the same linking semantics that most people 
on other *nixes are used to.

In your case, I suspect that including $(SMLIB) and $(ICELIB) in the 
following line from cygwin.tmpl is causing your problem:

#define SharedXtReqs $(LDPRELIB) $(SMLIB) $(ICELIB) $(XLIBONLY)

If Cygwin's linker does not complain when you removed these two, you 
should be fine. As it is all of the references which are supposed to 
remain undefined are likely being satisfied at library link time so 
nothing from lesstif is being included at application link time.

--Torrey

At 2:43 AM -0400 10/25/03, Harold L Hunt II wrote:

Torrey,

Looks like you may have had the same sort of trouble that we are now 
having with regards to building a shared version of the lesstif 
libraries that link to a shared version of the Xt library.  The 
particular error message, when starting a lesstif app is:

XmManager ClassInitialize: XmeTraitSet failed

Nicholas Wourms has been looking into this problem (his notes are 
below) and he seems to think that an OS/X-specific fix may have been 
made to one of the XFree86 libs to alleviate this problem with lesstif.

Do you recall anything related to this problem?  If so, could you 
describe the fix or point us to a message describing the fix?

Thanks in advance,

Harold



*SIGH* I spoke too soon, after building nedit and trying some other
tests, I'm experiencing the "XmManager ClassInitialize: XmeTraitSet
failed" problem.  Apparently the MacOSX people went through this ordeal
last year, but unfortunately that doesn't help us.  They had two 
solutions:
1) Pass "-force_flat_namespace" which is part of OSX's proprietary
   linker.
2) Downgrade to XFree86-4.1 libs of some sort or upgrade to latest cvs.

Of course, in-depth information on why this is happening is nonexistant,
all I could find were:
http://oroborosx.sourceforge.net/faq.html#q5p1
http://www.geocrawler.com/mail/msg.php3?msg_id=8230372&list=8629
Given that information, I'm willing to bet that an OSX-only fix was
checked in sometime after July of last year to resolve this.  Finding
out what it is will be difficult I'm willing to bet.  Of course it could
just be Xt misbehaving or an auto-import/psuedo-ops failure.  Heh, oh
well, I'm going to further investigate this tommorrow...  Sorry that it
isn't working properly :-(.
One last thought, perhaps we should CC Brian Ford in on this since
another fresh perspective might be good.
Cheers,
Nicholas

Re: Cygwin/XFree86 Bugs?

[Harold L Hunt II]

Michel Dänzer wrote:
On Wed, 2003-10-22 at 17:13, Egbert Eich wrote: 

Marc Aurele La France writes:
> 
> [EMAIL PROTECTED] is an ML anyone can subscribe to.  I am, and, I
> believe, so is Egbert.

No, not currently. I usually go to the web interface and 
look at the open bugs, process new ones that can be handled 
quickly, or try to assign them to an expert on the specific 
area.

There are a lot more areas than we have experts - in these
cases I try to work on the ticket myself. This, and the
low quality of some of the submissions, consumes a 
considerable amount of time.


Indeed, you're doing most of the bugzilla work alone; it's a pity there
aren't more people helping with that.
Well, you know, XFree86's disregard for offers to help made by 
developers that have been with the project for over two years are 
certainly part of the problem.

Seriously, I don't know why I waste my time submitting patches that are 
specific to my platform and then wait up to three weeks for them to be 
committed.  It is a waste of my time and an insult that I am made to do 
this while other platform maintainers made the luck of the draw and get 
to commit their patches directly.  Here it is: Let me commit my own 
patches within two months or I am going to let 
xc/programs/Xserver/hw/xwin die; I will stop sending updates, I will 
request that you remove hw/xwin and stop advertising that you support 
Cygwin.

Harold

Re: Cygwin/XFree86 Website Design (Possible Deuglification?)

[Colin Harrison]

Hi Harold,

I've captured again

Starting from a 1280x1024 capture my shrinker gives me (preserving aspect
ratio):-
http://www.straightrunning.com/desktop1280

800x640
http://www.straightrunning.com/desktop800

750x600
http://www.straightrunning.com/desktop750

200x160
http://www.straightrunning.com/desktop200


On my IE browser (screen 1280x1024) the 750x600 one looks the best for me.

Looks as good as original from this morning (but no spam on my screen this
time!)

Colin

Re: Cygwin/XFree86 Website Design (Possible Deuglification?)

[Harold L Hunt II]

Colin,

Great screen shot.

I have the following suggestions:

1) Make a full resolution version (1280x1024).  Keep the shrunk version, 
but maybe standardize on 800 x 600?

2) Can you make a thumbnail while you are at it?  Say 200 pixels wide?

3) Run 'uname' or 'uname -a' in the local xterm so that people realize 
it is running on your Windows machine.

4) Open an xterm on a remote host (or in your KDE session) and run 
'uname' or 'uname -a' in it.  Again, so people don't have to think :)

I think this could be a great shot.

Harold

Colin Harrison wrote:

Hi,

While I was zapping spam this morning did a screen capture of XWin in use.

File attached (too large...rejected 1st time by sources.redhat.com >50k)is
the capture shrunk to 25cm width (~700 pixels wide) and saved as a .png
230KB. Did the shrink as it didn't look too good full size on my IE browser
(1280 x 1024 screen). I've posted the result also on an experimental (play
not pay!) website of mine:-
http://www.straightrunning.com/desktop/desktop.png

(This is not always up, 24/7 as it's on my development machine and via a DSL
link)
The capture shows both XDMCP and multiwindow modes in action:-

1) A Windows XP desktop (tamed to remove all Telly Tubby/Early Learning
Centre themes and garbage :)).
2) A XDMCP KDE session to a remote RedHat linux box running Mozilla.
3) A remote Konsole shell being used to monitor spam being zapped on my
mailserver!
4) A remote Ethereal session being used to sniff my firewall traffic.
5) A local cygwin/xfree86 xterm.
6) A local cygwin/xfree86 xeyes showing shaped window/transparency.
7) My custom X selection menu from the XWin system tray icon.
I can post more of the same if you want (more web friendly or different
format/quality/size etc)? 

Colin

Re: Cygwin/XFree86 Website Design (Possible Deuglification?)

[Colin Harrison]

Hi,

While I was zapping spam this morning did a screen capture of XWin in use.

File attached (too large...rejected 1st time by sources.redhat.com >50k)is
the capture shrunk to 25cm width (~700 pixels wide) and saved as a .png
230KB. Did the shrink as it didn't look too good full size on my IE browser
(1280 x 1024 screen). I've posted the result also on an experimental (play
not pay!) website of mine:-

http://www.straightrunning.com/desktop/desktop.png

(This is not always up, 24/7 as it's on my development machine and via a DSL
link)

The capture shows both XDMCP and multiwindow modes in action:-

1) A Windows XP desktop (tamed to remove all Telly Tubby/Early Learning
Centre themes and garbage :)).
2) A XDMCP KDE session to a remote RedHat linux box running Mozilla.
3) A remote Konsole shell being used to monitor spam being zapped on my
mailserver!
4) A remote Ethereal session being used to sniff my firewall traffic.
5) A local cygwin/xfree86 xterm.
6) A local cygwin/xfree86 xeyes showing shaped window/transparency.
7) My custom X selection menu from the XWin system tray icon.

I can post more of the same if you want (more web friendly or different
format/quality/size etc)? 

Colin

Cygwin/XFree86 Website Design (Possible Deuglification?)

[Harold L Hunt II]

The Cygwin/XFree86 website is looking pretty tired:

http://xfree86.cygwin.com/

Things I don't like
===
1) The green and black header.  Yuk!
2) The hideous X logo.  Yuk!

3) All the crap on the front page.  Most of that stuff should be put on 
secondary pages.

4) News needs its own page.

5) The Screenshots page needs work.  Most of the screenshots are out of 
date.  Several new features need to be shown to entice new users.

6) Screenshots need thumbnails.  People don't like following blind links 
to images.  We should have some thumbnails linking to the images.



Philosophy for changes
==
1) Content is king.  If we don't have anything to say, we don't need a 
webpage.  The whole point of the webpage is to showcase our information. 
 With that in mind, we aim to make the webpage less ugly, but we can't 
forget that the whole point is to share information.

2) Plain-text bodies are good.  I like being able to add a lot of 
information on a web page without having to deal with stylistic issues.

3) Eye-candy should be relegated to the left-bar, header, right-bar (if 
we want one), footer, and link sections within pages.

4) HTML compliance is a must.  All pages should validate.

5) Don't assume much of web browsers.  Keep away from JavaScript if we 
can (we don't use any yet).  CSS is okay.  DHTML may be pushing it too 
far.  I don't want to spend a lot of time making sure it works with a 
lot of web browsers.

Example sites that I would like to emulate
==
1) http://www.kde.org/ - Good use of color, nice link sections around 
page and in page itself.

2) Huh... couldn't find another example.

Example sites that I do not want to emulate
===
1) http://www.gnome.org/ - Too plain, too dark, not enough info on the 
front page, no link sections, etc.

2) http://xfree86.org/ - This is an example of how I never want our page 
to look.  :)

Next steps
==
1) Does anyone want to help?
2) Would someone like to make some professional screenshots showcasing 
our most recent new features (Earle's customizable tray-icon menu, 
Alexander putting the -query string in the title bar, multi-window mode, 
the 'always on top' option in the right-click menu in mutli-window mode, 
and the list of icons created by the XFree86-bin-icons package)?

3) Would someone like to pick an overall color scheme and set of styles? 
 Just mock-up the front page for me and send me your .html and .css 
files and I can see what I can do with it.  This would be a huge help.

Let me know what you think,

Harold

RE: FW: XFree86-bin-icons .. believe cygwin xfree86 a "red" herring ... this is I believe a cygwin problem

[Alan Miles]

Alex,

I have no where on the web to put these files.

However, I have uploaded a new item with some compressed versions -
see http://cygwin.com/ml/cygwin/2003-09/msg01823.html

However, this item does not contain the setup.log.full versions, which
people might want.

Alan
-Original Message-
From: Alexander Gottwald
[mailto:[EMAIL PROTECTED]
Sent: September 30, 2003 05:31
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: FW: XFree86-bin-icons .. believe cygwin xfree86 a "red"
herring ... this is I believe a cygwin problem


On Tue, 30 Sep 2003, Alan Miles wrote:

> All,
>
> This is attempt 4 - I cannot seem to get the attachment there, since I
get:
>
> <[EMAIL PROTECTED]>:
> ezmlm-reject: fatal: Sorry, I don't accept messages larger than 5
bytes
> (#5.2.3)

You can place the files somewhere on the web and post a link to these files.

I dislike having to pull 700kb over a 64k line

bye
ago
--
 [EMAIL PROTECTED]
 http://www.gotti.org   ICQ: 126018723

Re: FW: XFree86-bin-icons .. believe cygwin xfree86 a "red" herring ... this is I believe a cygwin problem

[Alexander Gottwald]

On Tue, 30 Sep 2003, Alan Miles wrote:

> All,
> 
> This is attempt 4 - I cannot seem to get the attachment there, since I get:
> 
> <[EMAIL PROTECTED]>:
> ezmlm-reject: fatal: Sorry, I don't accept messages larger than 5 bytes
> (#5.2.3)

You can place the files somewhere on the web and post a link to these files.

I dislike having to pull 700kb over a 64k line

bye
ago
-- 
 [EMAIL PROTECTED] 
 http://www.gotti.org   ICQ: 126018723

FW: XFree86-bin-icons .. believe cygwin xfree86 a "red" herring ... this is I believe a cygwin problem

[Alan Miles]

All,

This is attempt 4 - I cannot seem to get the attachment there, since I get:

Hi. This is the qmail-send program at sources.redhat.com.
I'm afraid I wasn't able to deliver your message to the following addresses.
This is a permanent error; I've given up. Sorry it didn't work out.

<[EMAIL PROTECTED]>:
ezmlm-reject: fatal: Sorry, I don't accept messages larger than 10 bytes
(#5.2.3)

<[EMAIL PROTECTED]>:
ezmlm-reject: fatal: Sorry, I don't accept messages larger than 5 bytes
(#5.2.3)

--- Enclosed are the original headers of the message.

and according to my emailer the attachment is 777kB.

I did try and send the cygcheck etc.
-Original Message-
From: Alan Miles [mailto:[EMAIL PROTECTED]
Sent: September 29, 2003 23:34
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: FW: XFree86-bin-icons .. believe cygwin xfree86 a "red" herring
... this is I believe a cygwin problem


All,

This is attempt 3 ... the previous attempts failed because the emailer said
the messages, with the uncompressed log files was too big, and thus would
send them.

I have tarred and compressed them into the logs.tgz file - manifest:

logs/
logs/cygcheck_results_machine1_works.txt
logs/cygcheck_results_machine2_doesnt_work.txt
logs/setup_machine1_works.log
logs/setup_machine1_works.log.full
logs/setup_machine2_doesnt_work.log
logs/setup_machine2_doesnt_work.log.full


Alan
-Original Message-
From: Alan Miles [mailto:[EMAIL PROTECTED]
Sent: September 29, 2003 23:11
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: RE: XFree86-bin-icons .. believe cygwin xfree86 a "red" herring
... this is I believe a cygwin problem


All,

I believe this problem relates to the items listed in

http://cygwin.com/ml/cygwin/2003-09/msg01680.html - RE: Install gets to 99%
and then stops
http://www.cygwin.com/ml/cygwin/2003-09/msg00747.html - Setup 2.358 Hangs
During Post-Install Script

Additionally I have two separate machines, one fully updated on 26-Sep-2003
(which exhibits the problem) and one updated today that doesn't.

Differences:

1/ The 26-Sep-2003 machine uses the ** latest ** setup.exe (files labelled
machine2, doesnt_work)
2/ Today's update use the previous older version (file labelled
machine1_work)
3/ I built special private install packages for 26-Sep-2003 machine which I
have uses successfully for several months which do ** NOT ** involve
XFree86 and these packages also exhibit:

Something strange is going on here... setup.exe says "Running: No
Package /etc/postinstal/".  What is up with the "No
Package"?

My packages deal with my special problem with the password file (published
on this list), the jar command, script etc. The setup.log.full contains the
/usr/bin/bash -x dump of the /etc/postinstall/ files.
4/ When investigating, the problem in 3, I to found the 'cygpath' problem in
** my ** private packages (which as stated do ** NOT ** involve XFree86)

This leads me to believe that there is some kind of interaction between the
new setup.exe and cygpath that is causing the problem.

I am attaching both sets of setup.log, setup.log.full, and the cygcheck
output for both machines.

Also I noticed within the file setup_machine2_doesnt_work.log.full:

Transcript written on amstex.log.
fmtutil: /usr/share/texmf/web2c/lambda.oft installed.
fmtutil: /usr/share/texmf/web2c/omega.oft installed.
fmtutil: /usr/share/texmf/web2c/amstex.fmt installed.
fmtutil: /usr/share/texmf/web2c/latex.fmt installed.
fmtutil: /usr/share/texmf/web2c/pdflatex.fmt installed.
fmtutil: /usr/share/texmf/web2c/pdftex.fmt installed.
fmtutil: /usr/share/texmf/web2c/tex.fmt installed.
fmtutil: /usr/share/texmf/web2c/elatex.efmt installed.
fmtutil: /usr/share/texmf/web2c/etex.efmt installed.
fmtutil: /usr/share/texmf/web2c/pdfelatex.efmt installed.
fmtutil: /usr/share/texmf/web2c/pdfetex.efmt installed.
fmtutil: /usr/share/texmf/web2c/mpost.mem installed.
fmtutil: /usr/share/texmf/web2c/mf.base installed.
fmtutil: /usr/share/texmf/web2c/mfw.base installed.
install_link failed for /usr/bin/latex. File already exists.
Checking for psfonts.map in config.ps... no.  Adding ... done
2003/09/27 00:32:49 running: H:\cygwin\bin\sh.exe -c
/etc/postinstall/postinstall-lilypond.sh
find: paths must precede expression
Usage: find [path...] [expression]
rm: too few arguments
Try `rm --help' for more information.
2003/09/27 00:32:50 running: H:\cygwin\bin\sh.exe -c
/etc/postinstall/proftpd.sh
2003/09/27 00:32:50 running: H:\cygwin\bin\sh.exe -c
/etc/postinstall/robots.sh
2003/09/27 00:32:51 running: H:\cygwin\bin\sh.exe -c /etc/postinstall/rpm.sh
2003/09/27 00:32:52 running: H:\cygwin\bin\sh.exe -c
/etc/postinstall/splint.sh
2003/09/27 00:32:52 running: H:\cygwin\bin\sh.exe -c
/etc/postinstall/squid-postinstall.sh
will not overwrite existing /etc/squid.conf
will not overwrite existing /etc/mime.conf
2003/09/27 00:32:52 running: H:\cygwin\bin\sh.exe -c

Re: [Cygwin/XFree86] Duplicate keystrokes in X Server

[Lev Bishop]

Thanks, that's very interesting. I found that the suggested "xset r off" 
worked well for me, by completely disabling the X autorepeat stuff, since 
there's already windows autorepeat. But it's good to get to the bottom of 
these subtle race-condition type bugs.

Lev

RE: [Cygwin/XFree86] Duplicate keystrokes in X Server

[Pille Geert (bizvdm)]

Hallo Harold,

Thanks for the input.  Maybe the solution to this minor itch will be enough
incentive for me to start following the evolution of Xwin again: I'm stuck
on a pre-setup version (nov.2002).

You wouldn't happen to have some guidelines floating around about how to
move from a pre-setup to a setup version of Cygwin/XFree86?  I'm sure I
could handle it myself, I wouldn't like to count the hours I spent
installing X on different OS's, but I don't like to reinvent the warm water.
There are some other things I have to do while at work.  If you don't, I'll
try it at home first.  Just yesterday I rediscovered my first Cygwin
installation on one of my PC's, so this one could serve for a trial.

I tried to read Ivan's explanation, but he lost me halfway.  Monday morning
or I am getting too old for this shit.

Geert

> -Original Message-
> From: Harold L Hunt II [mailto:[EMAIL PROTECTED]
> Sent: zondag 21 september 2003 20:59
> To: cygx
> Subject: [Cygwin/XFree86] Duplicate keystrokes in X Server
> 
> 
> [BCCing seven people that have asked about this bug somewhat recently]
> 
> This bug has been around for a long time, but it was thought to be a 
> Cygwin/XFree86-specific bug.  However, I recently learned 
> that this is a 
> general XFree86 bug that is reproducible on, probably, all 
> other platforms.
> 
> Ivan Pascal submitted a patch to XFree86 that fixes the problem.  His 
> description of the problem and his patch can be found in this 
> archive of 
> his email:
> 
> http://www.mail-archive.com/devel%40xfree86.org/msg03245.html
> 
> 
> XFree86's Bugzilla Bug #301 also has information and discussion about 
> this bug:
> 
> http://bugs.xfree86.org/show_bug.cgi?id=301
> 
> 
> Finally, Ivan's patch was applied to XFree86-xserv-4.3.0-13, 
> which can 
> be downloaded and installed via Cygwin's setup.exe.  The "Test100" 
> release notes describe the other changes made in 4.3.0-13:
> 
> http://xfree86.cygwin.com/devel/shadow/changelog.html
> 
> 
> Enjoy,
> 
> Harold
> 


===
This email is confidential and intended solely for the use of the individual to whom 
it is addressed. 
If you are not the intended recipient, be advised that you have received this email in 
error and that any use, dissemination, forwarding, printing, or copying of this email 
is strictly prohibited.
You are explicitly requested to notify the sender of this email that the intended 
recipient was not reached.

[Cygwin/XFree86] Duplicate keystrokes in X Server

[Harold L Hunt II]

[BCCing seven people that have asked about this bug somewhat recently]

This bug has been around for a long time, but it was thought to be a 
Cygwin/XFree86-specific bug.  However, I recently learned that this is a 
general XFree86 bug that is reproducible on, probably, all other platforms.

Ivan Pascal submitted a patch to XFree86 that fixes the problem.  His 
description of the problem and his patch can be found in this archive of 
his email:

http://www.mail-archive.com/devel%40xfree86.org/msg03245.html

XFree86's Bugzilla Bug #301 also has information and discussion about 
this bug:

http://bugs.xfree86.org/show_bug.cgi?id=301

Finally, Ivan's patch was applied to XFree86-xserv-4.3.0-13, which can 
be downloaded and installed via Cygwin's setup.exe.  The "Test100" 
release notes describe the other changes made in 4.3.0-13:

http://xfree86.cygwin.com/devel/shadow/changelog.html

Enjoy,

Harold

[ANNOUNCEMENT] Cygwin/XFree86 Documentation 0.9.11

[Harold L Hunt II]

Links:

I just posted release 0.9.11 to the documentation development page:
http://xfree86.cygwin.com/devel/documentation/
Documentation, formatted, direct links:

Contributor's Guide http://xfree86.cygwin.com/docs/cg
User's Guide http://xfree86.cygwin.com/docs/ug/
FAQ http://xfree86.cygwin.com/docs/faq/
Documentation source releases are now available via the
sources.redhat.com ftp mirror network
(http://cygwin.com/mirrors.html) in the
pub/cygwin/xfree/devel/documentation/ directory.  You may wish to
note the desired filename in the links below, then download from
your closest mirror (http://cygwin.com/mirrors.html).
Documentation source, direct link:
http://www.msu.edu/~huntharo/xwin/docs/cygwin-xfree-doc-0.9.11.tar.gz
(680 KiB)
Changes:

1) CG - Change base directory for cross compiling from /cygwin to
/home/my_login/cygwin.  This allows non-root users to cross compile.
(Harold L Hunt II)
2) CG - Change CROSSCOMPILEDIR passed to make when cross compiling.
(Harold L Hunt II)
3) CG - Add a section that contains the source for a script that
creates links to the cross compilation tools and describe how to run
that script.  (Harold L Hunt II)


Enjoy,

Harold

[ANNOUNCEMENT] Cygwin/XFree86 Documentation 0.9.10

[Harold L Hunt II]

Links:

I just posted release 0.9.10 to the documentation development page:
http://xfree86.cygwin.com/devel/documentation/
Documentation, formatted, direct links:

Contributor's Guide http://xfree86.cygwin.com/docs/cg
User's Guide http://xfree86.cygwin.com/docs/ug/
FAQ http://xfree86.cygwin.com/docs/faq/
Documentation source releases are now available via the
sources.redhat.com ftp mirror network
(http://cygwin.com/mirrors.html) in the
pub/cygwin/xfree/devel/documentation/ directory.  You may wish to
note the desired filename in the links below, then download from
your closest mirror (http://cygwin.com/mirrors.html).
Documentation source, direct link:
http://www.msu.edu/~huntharo/xwin/docs/cygwin-xfree-doc-0.9.10.tar.gz
(680 KiB)
Changes:

1) CG - Add cygipc and expat to list of required packages for
development.  (Harold L Hunt II)
2) UG - Add new Window Managers section that describes how
Cygwin/XFree86 works with different types of window managers
(e.g. internal, local external, xdmcp, remote).  (Harold L Hunt
II)
3) UG - Add Clipboard Integration section that describes how the
clipboard integration system is used and why it has a certain
deficiency.  (Harold L Hunt II)
4) UG - Add Shared Memory Support (MIT-SHM Extension) section that
describes how to enable shared memory support at run-time.  (Harold L
Hunt II)
5) UG - Update list of command-line parameters.  Add -clipboard,
-clipupdates, -ignoreinput, -multimonitors, -multiwindow, -rootless,
-scrollbars, -[no]trayicon, -xf86config, and -keyboard.  (Harold L
Hunt II)


Enjoy,

Harold

[ANNOUNCEMENT] Cygwin/XFree86 Documentation 0.9.9

[Harold L Hunt II]

Links:

I just posted release 0.9.9 to the documentation development page:
http://xfree86.cygwin.com/devel/documentation/
Documentation, formatted, direct links:

Contributor's Guide http://xfree86.cygwin.com/docs/cg
User's Guide http://xfree86.cygwin.com/docs/ug/
FAQ http://xfree86.cygwin.com/docs/faq/
Documentation source releases are now available via the
sources.redhat.com ftp mirror network
(http://cygwin.com/mirrors.html) in the
pub/cygwin/xfree/devel/documentation/ directory.  You may wish to
note the desired filename in the links below, then download from
your closest mirror (http://cygwin.com/mirrors.html).
Documentation source, direct link:
http://www.msu.edu/~huntharo/xwin/docs/cygwin-xfree-doc-0.9.9.tar.gz 
(678 KiB)

Changes:

1) FAQ - Updated the entries about non U.S. keyboard layouts.
(Alexander Gottwald)
2) FAQ - Added troubleshooting info for X11Forwarding and keyboard
layouts.  (Alexander Gottwald)
3) General - Imported documentation sources to cygwin-xfree-doc CVS
repository (link below) on the xoncygwin SourceForge project.  (Alexander
Gottwald)
http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/xoncygwin/cygwin-xfree-doc/



Enjoy,

Harold

Re: non us keyboards with cygwin, xfree86, Xwin -query XDMCP

[pnews]

> On Tue, 2 Sep 2003, pbs wrote:
> gives the error:
>   Couldn't load XKB keymap, falling back to pre-XKB keymap

Well I've worked that one out from another post in the archive:

: These files should reside in /etc/X11/xkb and there should be a symlink to
: this directory at /usr/X11R6/lib/X11/xkb. If you don't have these files
: I'd suggest reinstalling the XFree packages with the cygwin setup. The
: XFree86-etc packaged should contain the files.

The symbolic link /usr/X11R6/lib/X11/xkb was broken. I've fixed it
and the error message 
Couldn't load XKB keymap, falling back to pre-XKB keymap
has gone away.

Without a config file, the log file now reads:
 (==) Using preset keyboard for "English (United Kingdom)" (0809), type "4"
 (EE) No primary keyboard configured
 (==) Using compiletime defaults for keyboard

BUT the characters at the login prompt are still US :-(

On Tue, 2 Sep 2003, Alexander Gottwald wrote:
> On Tue, 2 Sep 2003, pbs wrote:
> 
>> Setup an out of the box cygwin installation with Xfree86
>>   bash-prompt$ uname -a
>>   CYGWIN_95-4.0 local_host 1.3.22(0.78/3/2) 2003-03-18 09:20 i586[snip]
> 
> Which version of XFree86 is installed?
> 
> cygcheck -c XFree86-bin
> cygcheck -c XFree86-etc

Cygwin Package Information
Package  Version
XFree86-bin  4.2.0-3

Cygwin Package Information
Package  Version
XFree86-etc  4.2.0-1

> 
>  
>> The log file "/tmp/XWinrl.log"  contains the following error:
>>(==) Using preset keyboard for "English (United Kingdom)" (0809), 
>> type "4"
> 
> The configfile is not required. Your keyboard layout is preconfigured in 
> the xserver.

Thanks for the info I've moved the config file out of the way.

[snip]
> is /tmp mounted in textmode? 

I have no idea what this means. (I'll RTFM)
Ah! I see!  How I dislike the VMS way of doing things!

> mount -b c:/windows/temp /tmp
>
> is the layout correct after switching to binmode?

Yes it works keys are what I expect them to be :-)

Thanks for your help. It is much appreciated.

Regards Philip

Re: non us keyboards with cygwin, xfree86, Xwin -query XDMCP

[Alexander Gottwald]

On Tue, 2 Sep 2003, pbs wrote:

> Setup an out of the box cygwin installation with Xfree86
>   bash-prompt$ uname -a
>   CYGWIN_95-4.0 local_host 1.3.22(0.78/3/2) 2003-03-18 09:20 i586[snip]

Which version of XFree86 is installed?

cygcheck -c XFree86-bin
cygcheck -c XFree86-etc

 
> The log file "/tmp/XWinrl.log"  contains the following error:
>(==) Using preset keyboard for "English (United Kingdom)" (0809), 
> type "4"

The configfile is not required. Your keyboard layout is preconfigured in 
the xserver.


>(EE) No primary keyboard configured
>(==) Using compiletime defaults for keyboard
>Rules = "xfree86" Model = "pc105" Layout = "gb" Variant = "(null)" 
> Options = "(null)"
> Couldn't load XKB keymap, falling back to pre-XKB keymap

is /tmp mounted in textmode? 
is the layout correct after switching to binmode?

mount -b c:/windows/temp /tmp

bye
ago
-- 
 [EMAIL PROTECTED] 
 http://www.gotti.org   ICQ: 126018723

non us keyboards with cygwin, xfree86, Xwin -query XDMCP

[pbs]

Setup an out of the box cygwin installation with Xfree86
 bash-prompt$ uname -a
 CYGWIN_95-4.0 local_host 1.3.22(0.78/3/2) 2003-03-18 09:20 i586[snip]
Question Short version:
--
With or without:
/etc/x11/XF86Config-4 installed with
   Option "XkbLayout"  "gb"
gives the error:
   Couldn't load XKB keymap, falling back to pre-XKB keymap
What do I have to do to get Xwin.exe to read the gb XKB keymap?
Question Long version:
--
My cygwin bash pompt is configured for a "gb" keyboard
-- If I press the @ key I get an "@".
If I run the following command from a bash prompt
  Xwin.exe -emulate3buttons -query remote_host &
The log file "/tmp/XWinrl.log"  contains the following error:
  (==) Using preset keyboard for "English (United Kingdom)" (0809), 
type "4"
  (EE) No primary keyboard configured
  (==) Using compiletime defaults for keyboard
  Rules = "xfree86" Model = "pc105" Layout = "gb" Variant = "(null)" 
Options = "(null)"
   Couldn't load XKB keymap, falling back to pre-XKB keymap

If I open an xterm and press the "@" key I get a double quote
key -- which is to be expected with the above error as it is what a
US key mapping gives.
I have gone throught archive and the previous thread which
came closes to answering my question was:
the post by Alexander Gottwald
  http://sources.redhat.com/ml/cygwin-xfree/2003-02/msg00185.html
with a URL to a minimal XF86Config
  http://www.tu-chemnitz.de/~goal/xfree/XF86Config.bz2
I have installed the file as /etc/x11/XF86Config-4 then uncommented
and modified the lines
  #  Option "XkbRules"   "xfree86"
  #  Option "XkbModel"   "pc105"
  #  Option "XkbLayout"  "de"
to
Option "XkbRules"   "xfree86"
Option "XkbModel"   "pc105"
Option "XkbLayout"  "gb"
Now when I run:
  Xwin.exe -emulate3buttons -query remote_host &
The log file contains:
  [snip]
  (==) Using config file: "/etc/X11/XF86Config-4"
  [snip]
  (==) Using preset keyboard for "English (United Kingdom)" (0809), 
type "4"
  (**) Using keyboard "Keyboard1" as primary keyboard
  (**) Option "XkbRules" "xfree86"
  (**) XKB: rules: "xfree86"
  (**) Option "XkbModel" "pc105"
  (**) XKB: model: "pc105"
  (**) Option "XkbLayout" "gb"
  (**) XKB: layout: "gb"
  Rules = "xfree86" Model = "pc105" Layout = "gb" Variant = "(null)" 
Options = "(null)"
  Couldn't load XKB keymap, falling back to pre-XKB keymap

What do I have to do to get Xwin.exe to read the gb XKB keymap?

BTW: Yes I know that I can run xmodmap as a client application. But
I would like to get the correct keyboard into the server without
doing this, so that the remote login clients(s) have access to the
correct key bindings.
Regards Philip

cygwin-xfree86 on WinXP

[richard kovars]

Hello,
 
I just installed the latest version of cygwin/XFree86. 
Everything was working before the upgrade.  Now when I 
startx (with any of the scripts) the keyboard is dead.  I 
have tried several of the thread leads to no avail.  Has 
anyone seen this recently? (I have a WIN2K box and 
everything works fine).  
 
/tmp/XWin.log
 
ddxProcessArgument - Initializing default screens
winInitializeDefaultScreens - w 1280 h 1024
winInitializeDefaultScreens - Returning
OsVendorInit - Creating bogus screen 0
(EE) Unable to locate/open config file
InitOutput - Error reading config file
winDetectSupportedEngines - Windows NT/2000/XP
winDetectSupportedEngines - DirectDraw installed
winDetectSupportedEngines - Allowing PrimaryDD
winDetectSupportedEngines - DirectDraw4 installed
winDetectSupportedEngines - Returning, supported engines 
001f
InitOutput - g_iNumScreens: 1 iMaxConsecutiveScreen: 1
winSetEngine - Multi Window => ShadowGDI
winAdjustVideoModeShadowGDI - Using Windows display depth 
of 32 bits per pixel
winCreateBoundingWindowWindowed - User w: 1280 h: 1024
winCreateBoundingWindowWindowed - Current w: 1280 h: 1024
winAdjustForAutoHide - Original WorkArea: 0 0 996 1280
winAdjustForAutoHide - Adjusted WorkArea: 0 0 996 1280
winCreateBoundingWindowWindowed - WindowClient w 1280 h 
996 r 1280 l 0 b 996 t 0
winCreateBoundingWindowWindowed -  Returning
winAllocateFBShadowGDI - Creating DIB with width: 1280 
height: 996 depth: 32
winAllocateFBShadowGDI - Dibsection width: 1280 height: 
996 depth: 32 size image: 5099520
winAllocateFBShadowGDI - Created shadow stride: 1280
winFinishScreenInitFB - Masks: 00ff ff00 00ff
winInitVisualsShadowGDI - Masks 00ff ff00 00ff 
BPRGB 8 d 24 bpp 32
winCreateDefColormap - Deferring to fbCreateDefColormap ()
null screen fn ReparentWindow
null screen fn RestackWindow
winFinishScreenInitFB - Calling winInitWM.
InitQueue - Calling pthread_mutex_init
InitQueue - pthread_mutex_init returned
InitQueue - Calling pthread_cond_init
InitQueue - pthread_cond_init returned
winInitWM - Returning.
winFinishScreenInitFB - returning
winScreenInit - returning
InitOutput - Returning.
(EE) No primary keyboard configured
(==) Using compiletime defaults for keyboard
Rules = "xfree86" Model = "pc101" Layout = "us" Variant = 
"(null)" Options = "(null)"
winInitMultiWindowWM - Hello
winInitMultiWindowWM - Calling pthread_mutex_lock ()
winMultiWindowXMsgProc - Hello
winMultiWindowXMsgProc - Calling pthread_mutex_lock ()
winPointerWarpCursor - Discarding first warp: 640 498
winBlockHandler - Releasing pmServerStarted
winInitMultiWindowWM - pthread_mutex_lock () returned.
DetectUnicodeSupport - Windows NT/2000/XP
winInitMultiWindowWM - Calling setlocale ()
winBlockHandler - pthread_mutex_unlock () returned
winInitMultiWindowWM - setlocale () returned
winInitMultiWindowWM - XInitThreads () returned.
winMultiWindowXMsgProc - pthread_mutex_lock () returned.
winMultiWindowXMsgProc - pthread_mutex_unlock () returned.
winMultiWindowXMsgProc - DISPLAY=127.0.0.1:0.0
winInitMultiWindowWM - pthread_mutex_unlock () returned.
winInitMultiWindowWM - DISPLAY=127.0.0.1:0.0
winInitMultiWindowWM - XOpenDisplay () returned and 
successfully opened the display.
winMultiWindowXMsgProc - XOpenDisplay () returned and 
successfully opened the display.
 
 
Cygwin, itself, seems to operate fine.  Any suggestions?
 
Thanks.
 
Please omit my e-mail.  Thanks.

Re: -clipboard mark-region cut and paste xemacs dilemma in cygwin xfree86

[Cary Jamison]

"terrence brannon" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> (How's that for a google-searchable title :))
> 
> I am between a rock and a hard place. If I start X-windows without
> the -clipboard option, then I cannot cut and paste between my windows
web
> browser (mozilla) and my x-terminals using the middle mouse button.
> 
> If I do start X-windows with the -clipboard option, then Xemacs seems
to not
> be able to mark the region. Or rather, just after marking the region
via the
> mouse or by hitting ctrl-space and moving to the other end of the
region, I
> cannot use the region with the error: "Region is not active now"

(As Harold mentions, this has been discussed before, including my
suggestion below.)

You might want to consider not using -clipboard and starting/stopping
xwinclip as needed.
This works for me, because I find I do not need to do a lot of
copying/pasting between X
and Windows, and prefer to have selection work properly in emacs and
xterms.

Cary

-clipboard mark-region cut and paste xemacs dilemma in cygwin xfree86

[terrence brannon]

(How's that for a google-searchable title :))

I am between a rock and a hard place. If I start X-windows without
the -clipboard option, then I cannot cut and paste between my windows web
browser (mozilla) and my x-terminals using the middle mouse button.

If I do start X-windows with the -clipboard option, then Xemacs seems to not
be able to mark the region. Or rather, just after marking the region via the
mouse or by hitting ctrl-space and moving to the other end of the region, I
cannot use the region with the error: "Region is not active now"

This is my cygwin X-windows startup file

export DISPLAY=localhost:0.0



#XWin -unixkill -rootless -emulate3buttons -clipboard &
#XWin -unixkill  -emulate3buttons -clipboard &
XWin -unixkill  -emulate3buttons  &


wmaker &
#openbox &
#fvwm &

# lesstiff *

xterm -sb -bg white -fg darkblue -cr red -ms red -bd red -geometry
80x20+532+0 -name center &
xterm -sb -bg white -fg darkblue -cr red -ms red -bd red -geometry
80x20+1033+0 -name right &
xterm -sb -bg white -fg darkblue -cr red -ms red -bd red -geometry
80x20-70+0 -name large &
#xterm -sb -bg white -fg darkblue -cr red -ms red -bd red -geometry
215x88-70+0 -name large &

xhost +
ipconfig /all
.

Re: Download full Cygwin/XFree86

[Harold L Hunt II]

Download it to disk and burn it to a CD.

Harold

Asaf Bokish wrote:
Hello,
My name is Asaf, and I'm wan't to install Cygwin/XFree86 on my computer.
The computer I want to install the Cygwin/XFree86 on is not connected to the Internet, 
so I need a full version of the installation.
Where can I get such intallation?
  Tx
  Asaf Bokish
  [EMAIL PROTECTED]

Free 20MB Web Site Hosting and Personalized E-mail Service!
Get It Now At Doteasy.com http://www.doteasy.com/et/

Download full Cygwin/XFree86

[Asaf Bokish]

Hello,
My name is Asaf, and I'm wan't to install Cygwin/XFree86 on my computer.
The computer I want to install the Cygwin/XFree86 on is not connected to the Internet, 
so I need a full version of the installation.
Where can I get such intallation?

  Tx
  Asaf Bokish
  [EMAIL PROTECTED]



Free 20MB Web Site Hosting and Personalized E-mail Service!
Get It Now At Doteasy.com http://www.doteasy.com/et/

Re: [Fwd: Cygwin/XFree86 patch in XFree86 Bugzilla] Earle - This is for you

[Earle F. Philhower III]

Hello Harold, and a very belated congratulations!  I've been out of
the country for a few weeks and reading email was not one of my
prerogatives...
At 03:09 PM 7/9/2003 -0400, you wrote:
Does your patch fail gracefully if run on non-NT-based OSes?
If so, I will give my go-ahead.  If not, please modify it so that it
exits if not running on Windows NT-based OSes.
Yes, it dynamically queries for the existence of a DLL and then the
requisite function calls inside.  If these fail it just returns a
dummy value (1.0) for the load.  Safe to compile and run under any
Windoze OS.

Thanks,

Harold

 Original Message 
Subject: Cygwin/XFree86  patch in XFree86 Bugzilla
Date: Wed, 9 Jul 2003 17:21:08 +0200
From: Egbert Eich
To: Harold L Hunt II
Hi Harold,

there is a patch in the XFree86 bugzilla

http://bugs.xfree86.org//cgi-bin/bugzilla/show_bug.cgi?id=305

adding support for Windows NT like OSes to xload. I assume that
this will not work on non-NT-like Windows systems as the required
performance counters are not available there.
I would like to commit this code to the XFree86 CVS but I would
like to get an opinion form somebody on the Cygwin team.
If you would rather keep this code in your repository and merge
it at some later time please let me know.
Cheers,
Egbert.


-Earle F. Philhower, III
 [EMAIL PROTECTED]
 cdrlabel - ZipLabel - FlpLabel
 http://www.cdrlabel.com

Problems related to Cygwin/Xfree86-0:0

[Vijay Sheth]

Hi,

When executing

Xwin -query mirage

from the Cygwin window, the new window comes up, but it does not get the
desktop of "mirage".

Could you please help?

This installation works for our colleagues.

Thanks,

Vijay
12601 Fair Lakes, #4141
W: 703-227-6709

[Fwd: Cygwin/XFree86 patch in XFree86 Bugzilla] Earle - This isfor you

[Harold L Hunt II]

Earle,

Does your patch fail gracefully if run on non-NT-based OSes?

If so, I will give my go-ahead.  If not, please modify it so that it
exits if not running on Windows NT-based OSes.
Thanks,

Harold

 Original Message 
Subject: Cygwin/XFree86  patch in XFree86 Bugzilla
Date: Wed, 9 Jul 2003 17:21:08 +0200
From: Egbert Eich
To: Harold L Hunt II
Hi Harold,

there is a patch in the XFree86 bugzilla

http://bugs.xfree86.org//cgi-bin/bugzilla/show_bug.cgi?id=305

adding support for Windows NT like OSes to xload. I assume that
this will not work on non-NT-like Windows systems as the required
performance counters are not available there.
I would like to commit this code to the XFree86 CVS but I would
like to get an opinion form somebody on the Cygwin team.
If you would rather keep this code in your repository and merge
it at some later time please let me know.
Cheers,
Egbert.

Re: Fw: Bug in Cygwin/XFree86 Frequently Asked Questions

[Igor Pechtchanski]

Harold,

His suggestion is equivalent to having a .inputrc with the lines he passes
to "bind".  Two of the options ("show-all-if-ambiguous" and
"expand-tilde") have nothing to do with 8-bit characters, the other three
are the same as in the FAQ entry.  In other words, the FAQ entry *is*
correct, and don't bother changing it.

As for the distinction between bash and sh -- .inputrc is used by the
readline library, and, FWICS, ash (the /bin/sh in Cygwin) does not use
readline at all (but bash does).  So I don't see why the FAQ suggestion
didn't work for Arne in bash, and how it could possibly work in sh (unless
he tried it on Linux, where /bin/sh is a symlink to bash, which still
doesn't explain why it didn't work in bash).
Igor

On Mon, 7 Jul 2003, Harold L Hunt II wrote:

> Igor,
>
> Is his suggestion correct?  If so, I will need to update the
> Cygwin/XFree86 FAQ.
>
> Thanks,
>
> Harold
>
> Igor Pechtchanski wrote:
>
> > Arne,
> >
> > There's an entry in the main Cygwin FAQ that may be of interest:
> > <http://cygwin.com/faq/faq.html#SEC49>.
> >   Igor
> >
> > On Mon, 7 Jul 2003, Arne Christian Hrseth wrote:
> >
> >
> >>Hi!
> >>
> >>I am not an expert on bash and sh but I could only make the cygwin-sfree-fax
> >>topic 4.7 and 4.8 work with sh, not bash, so I assume it should be corrected
> >>as suggested in my mail below?
> >>
> >>Best regards
> >>Arne Hrseth
> >>
> >>PS: I do not subscripe to this list.
> >>
> >>- Original Message -
> >>From: "Harold L Hunt II" <[EMAIL PROTECTED]>
> >>To: "Arne Christian Hrseth" <[EMAIL PROTECTED]>
> >>Sent: Monday, July 07, 2003 5:07 AM
> >>Subject: Re: Bug in Cygwin/XFree86 Frequently Asked Questions
> >>
> >>Arne,
> >>
> >>Can you send this to [EMAIL PROTECTED]  Your suggestion seems
> >>correct, but I would like other people to see it and add their thoughts.
> >>
> >>Thanks for contributing,
> >>
> >>Harold
> >>
> >>Arne Christian Hrseth wrote:
> >>
> >>>Hi!
> >>>
> >>>I see that you have the last revision of the Cygwin/XFree86
> >>>Frequently Asked Questions so I take the chance on sending this to
> >>>you. Hope it is OK?
> >>>
> >>>I think there is a bug in
> >>>http://xfree86.cygwin.com/docs/faq/cygwin-xfree-faq.html#q-bash-extended-chars.
> >>>The description in 4.7 and 4.8 is said to cover bash but it actually only
> >>>works for sh. With bash you need to make a .bashrc instead of inputrc
> >>>containing something like this:
> >>>
> >>>if test "$PS1"
> >>>then
> >>>  PS1='\h(\u) \W \!\$ '
> >>>  bind \
> >>>'set meta-flag on'  \
> >>>'set convert-meta off'  \
> >>>'set output-meta on'\
> >>>'set show-all-if-ambiguous on'  \
> >>>'set expand-tilde on'
> >>>fi
> >>>
> >>>This also adds a nice prompt.
> >>>
> >>>Best regards
> >>>Arne Christian Hrseth

-- 
http://cs.nyu.edu/~pechtcha/
  |\  _,,,---,,_[EMAIL PROTECTED]
ZZZzz /,`.-'`'-.  ;-;;,_[EMAIL PROTECTED]
 |,4-  ) )-,_. ,\ (  `'-'   Igor Pechtchanski, Ph.D.
'---''(_/--'  `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster."  -- Patrick Naughton

Re: Fw: Bug in Cygwin/XFree86 Frequently Asked Questions

[Harold L Hunt II]

Igor,

Is his suggestion correct?  If so, I will need to update the 
Cygwin/XFree86 FAQ.

Thanks,

Harold

Igor Pechtchanski wrote:

Arne,

There's an entry in the main Cygwin FAQ that may be of interest:
<http://cygwin.com/faq/faq.html#SEC49>.
Igor
On Mon, 7 Jul 2003, Arne Christian Hårseth wrote:


Hi!

I am not an expert on bash and sh but I could only make the cygwin-sfree-fax
topic 4.7 and 4.8 work with sh, not bash, so I assume it should be corrected
as suggested in my mail below?
Best regards
Arne Hårseth
PS: I do not subscripe to this list.

- Original Message -
From: "Harold L Hunt II" <[EMAIL PROTECTED]>
To: "Arne Christian Hårseth" <[EMAIL PROTECTED]>
Sent: Monday, July 07, 2003 5:07 AM
Subject: Re: Bug in Cygwin/XFree86 Frequently Asked Questions
Arne,

Can you send this to [EMAIL PROTECTED]  Your suggestion seems
correct, but I would like other people to see it and add their thoughts.
Thanks for contributing,

Harold

Arne Christian Hårseth wrote:


Hi!

I see that you have the last revision of the Cygwin/XFree86 Frequently
Asked

Questions so I take the chance on sending this to you. Hope it is OK?

I think there is a bug in

http://xfree86.cygwin.com/docs/faq/cygwin-xfree-faq.html#q-bash-extended-cha

rs.
The description in 4.7 and 4.8 is said to cover bash but it actually only
works for sh. With bash you need to make a .bashrc instead of inputrc
containing something like this:
if test "$PS1"
then
 PS1='\h(\u) \W \!\$ '
 bind \
   'set meta-flag on'  \
   'set convert-meta off'  \
   'set output-meta on'\
   'set show-all-if-ambiguous on'  \
   'set expand-tilde on'
fi
This also adds a nice prompt.

Best regards
Arne Christian Hårseth

Re: Fw: Bug in Cygwin/XFree86 Frequently Asked Questions

[Igor Pechtchanski]

Arne,

There's an entry in the main Cygwin FAQ that may be of interest:
<http://cygwin.com/faq/faq.html#SEC49>.
Igor

On Mon, 7 Jul 2003, Arne Christian Hårseth wrote:

> Hi!
>
> I am not an expert on bash and sh but I could only make the cygwin-sfree-fax
> topic 4.7 and 4.8 work with sh, not bash, so I assume it should be corrected
> as suggested in my mail below?
>
> Best regards
> Arne Hårseth
>
> PS: I do not subscripe to this list.
>
> - Original Message -
> From: "Harold L Hunt II" <[EMAIL PROTECTED]>
> To: "Arne Christian Hårseth" <[EMAIL PROTECTED]>
> Sent: Monday, July 07, 2003 5:07 AM
> Subject: Re: Bug in Cygwin/XFree86 Frequently Asked Questions
>
> Arne,
>
> Can you send this to [EMAIL PROTECTED]  Your suggestion seems
> correct, but I would like other people to see it and add their thoughts.
>
> Thanks for contributing,
>
> Harold
>
> Arne Christian Hårseth wrote:
>
> > Hi!
> >
> > I see that you have the last revision of the Cygwin/XFree86 Frequently
> Asked
> > Questions so I take the chance on sending this to you. Hope it is OK?
> >
> > I think there is a bug in
> >
> http://xfree86.cygwin.com/docs/faq/cygwin-xfree-faq.html#q-bash-extended-cha
> > rs.
> > The description in 4.7 and 4.8 is said to cover bash but it actually only
> > works for sh. With bash you need to make a .bashrc instead of inputrc
> > containing something like this:
> >
> > if test "$PS1"
> > then
> >   PS1='\h(\u) \W \!\$ '
> >   bind \
> > 'set meta-flag on'  \
> > 'set convert-meta off'  \
> > 'set output-meta on'\
> > 'set show-all-if-ambiguous on'  \
> > 'set expand-tilde on'
> > fi
> >
> > This also adds a nice prompt.
> >
> > Best regards
> > Arne Christian Hårseth

-- 
http://cs.nyu.edu/~pechtcha/
  |\  _,,,---,,_[EMAIL PROTECTED]
ZZZzz /,`.-'`'-.  ;-;;,_[EMAIL PROTECTED]
 |,4-  ) )-,_. ,\ (  `'-'   Igor Pechtchanski, Ph.D.
'---''(_/--'  `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster."  -- Patrick Naughton

Fw: Bug in Cygwin/XFree86 Frequently Asked Questions

[Arne Christian Hårseth]

Hi!

I am not an expert on bash and sh but I could only make the cygwin-sfree-fax
topic 4.7 and 4.8 work with sh, not bash, so I assume it should be corrected
as suggested in my mail below?

Best regards
Arne Hårseth

PS: I do not subscripe to this list.

- Original Message -
From: "Harold L Hunt II" <[EMAIL PROTECTED]>
To: "Arne Christian Hårseth" <[EMAIL PROTECTED]>
Sent: Monday, July 07, 2003 5:07 AM
Subject: Re: Bug in Cygwin/XFree86 Frequently Asked Questions


Arne,

Can you send this to [EMAIL PROTECTED]  Your suggestion seems
correct, but I would like other people to see it and add their thoughts.

Thanks for contributing,

Harold

Arne Christian Hårseth wrote:

> Hi!
>
> I see that you have the last revision of the Cygwin/XFree86 Frequently
Asked
> Questions so I take the chance on sending this to you. Hope it is OK?
>
> I think there is a bug in
>
http://xfree86.cygwin.com/docs/faq/cygwin-xfree-faq.html#q-bash-extended-cha
> rs.
> The description in 4.7 and 4.8 is said to cover bash but it actually only
> works for sh. With bash you need to make a .bashrc instead of inputrc
> containing something like this:
>
> if test "$PS1"
> then
>   PS1='\h(\u) \W \!\$ '
>   bind \
> 'set meta-flag on'  \
> 'set convert-meta off'  \
> 'set output-meta on'\
> 'set show-all-if-ambiguous on'  \
> 'set expand-tilde on'
> fi
>
> This also adds a nice prompt.
>
> Best regards
> Arne Christian Hårseth
>

Problem compiling with xlib using GCC and newest Cygwin/Xfree86

[Richard D. Duncan]

I installed the latest release (or at least whatever the newest release available on 
the website) of Cygwin/XFree86 today, but I’m having troubles with GCC and Xlib.  When 
I try to include Xlib.h and go to compile, I get a very long slew of errors, mostly 
saying things like “ ‘Window’ is used as a type but is not defined as a type.” and so 
on with Atom, Font, Pixmap, etc.  Next I get a list of about 20 syntax errors in 
Xlib.h, then errors in my code since types like Display and functions like 
XCreateSimpleWindow don’t work.  I’m not trying to do anything fancy just yet, so I’ve 
only got like 5 lines of code opening a window and mapping it, but it obviously isn’t 
working.  Any help would be appreciated.  And if this issue has been addressed before, 
I’m sorry.  I’m new to the list and tried searching for this problem but couldn’t find 
any instances of it in the archives.

 

Richard Duncan

Re: Cygwin/Xfree86 is not working

[Shing-Fat Fred Ma]

> Date: Mon, 30 Jun 2003 10:36:12 -0400 (EDT)
> From: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
> Message-Id: <"CIVEX09-030630143518Z-47235*/PRMD=USDOJ/ADMD= /C=US/"@MHS>
>
> Hi everyone. I have installed xfree86 in a windows nt sp6.
> 
> I open a cygwin session.
> 
> I type 
> 
> $ sh startxwin.sh 
> 
> ssh-agent: not found
> I have no [EMAIL PROTECTED] /usr/X11R6/bin
> 
> The cygwin/xfree86:0.0 started but
> 
> I cannot open any xterm.


Hi, Federico,

Just a wild guess.  Did you install the OpenSSH package
when you installed Cygwin?

Fred
--
Fred Ma, [EMAIL PROTECTED]
Carleton University, Dept. of Electronics
1125 Colonel By Drive, Ottawa, Ontario
Canada, K1S 5B6

Cygwin/Xfree86 is not working

[[EMAIL PROTECTED]]

Hi everyone. I have installed xfree86 in a windows nt sp6.

I open a cygwin session.

I type 

$ sh startxwin.sh 

ssh-agent: not found
I have no [EMAIL PROTECTED] /usr/X11R6/bin

The cygwin/xfree86:0.0 started but

I cannot open any xterm.

The logfile is:
__

ddxProcessArgument - Initializing default screens
winInitializeDefaultScreens - w 1024 h 768
winInitializeDefaultScreens - Returning
ddxProcessArgument - screen - Found ``W D'' arg
(EE) Unable to locate/open config file
InitOutput - Error reading config file
winDetectSupportedEngines - Windows NT/2000/XP
winDetectSupportedEngines - DirectDraw installed
winDetectSupportedEngines - Allowing PrimaryDD
winDetectSupportedEngines - Returning, supported engines 001b
InitOutput - g_iNumScreens: 1 iMaxConsecutiveScreen: 1
winSetEngine - Using Shadow DirectDraw
winAdjustVideoModeShadowDD - Using Windows display depth of 16 bits per pixel
winCreateBoundingWindowWindowed - User w: 1024 h: 768
winCreateBoundingWindowWindowed - Current w: 1024 h: 768
winAdjustForAutoHide - Original WorkArea: 0 0 740 1024
winAdjustForAutoHide - Adjusted WorkArea: 0 0 740 1024
winCreateBoundingWindowWindowed - WindowClient w 1018 h 715 r 1018 l 0 b 715 t 0
winCreateBoundingWindowWindowed -  Returning
winFinishScreenInitFB - Masks: f800 07e0 001f
winInitVisualsShadowDD - Masks f800 07e0 001f BPRGB 6 d 16 bpp 16
winCreateDefColormap - Deferring to fbCreateDefColormap ()
winFinishScreenInitFB - returning
winScreenInit - returning
InitOutput - Returning.
(EE) No primary keyboard configured
(==) Using compiletime defaults for keyboard
Rules = "xfree86" Model = "pc101" Layout = "us" Variant = "(null)" Options = "(null)"
winPointerWarpCursor - Discarding first warp: 509 357
winBlockHandler - Releasing pmServerStarted
winBlockHandler - pthread_mutex_unlock () returned


It looks like a login problem.

Can anyone has any suggestions?

Thanks

Federico

Cygwin/XFree86 With Remote KDE 2.2.2

[Amir Safavi]

Hello,

Currently, I have to log into a Debian linux machine remotely and do some of 
my work there.
I have on KDE 2.2.2 installed on that machine.
Basically, I ssh in, and startkde.

KDE loads up fine, antialiased fonts and all. After several minutes however, 
either KWin (kde's wm) crashes, or the desktop dissappears or kicker 
suddenly closes for no reason. This is very odd.

If it helps, I also get errors like this in the command prompt

WARNING: KDE detected X Error: BadDrawable (invalid Pixmap or Window 
parameter) 9
 Major opcode:  14
WARNING: KDE detected X Error: BadMatch (invalid parameter attributes) 8
 Major opcode:  42

In program such as KWord and Kwrite (sometimes).

I've tried fiddling with the xserver's fonts, adding truetype, turning off 
antialiasing, turning on antialiasing, going 32 bit, going 16 bit, etc. etc.

This behaviour is very odd. sometimes my desktop disappears after 20 
seconds, sometimes it may work for 5-10 minutes before going crazy, which 
leads me to believe it may be some sort of a memory leak.

It would be greatly appreciated if someone could help me with this,

Thank you,
 Amir
_
The new MSN 8: smart spam protection and 2 months FREE*  
http://join.msn.com/?page=features/junkmail