Re: cygwin/xfree86 logged into KDE3 causes strange cygwin error
On Fri, Apr 05, 2002 at 08:22:26PM -0500, Harold Hunt wrote: >Oh yeah, by "sketchy" I meant that after it happens a few times and I >switch the focus away from Cygwin/XFree86 two things happen: > >1) Cygwin/XFree86 freezes solid. > >2) The Windows mouse cursor disappears and the Windows mouse doesn't >work until I reboot. The mouse doesn't even start to work again when >you press Ctrl+Alt+Del and get the Windows Security box that usually >works perfectly even when programs have crashed. > >Yeah... that's pretty sketchy. It sounds like typical memory overwrite problems. I have never seen that error show up in any other application. I thought I had actually turned off assertions in the released version of cygwin. Guess I was mistaken. There are only two popular users of vfork that I'm aware of: sh and make. It's possible that their needs are simple enough that they're not triggering a cygwin bug that kde is triggering. It's also possible that kde is just doing a plain old fashioned overwriting of memory. It should be fairly simple to figure out what's stomping on the memory but it will have to (obviously?) be done by someone who has kde and feels up to debugging the cygwin DLL. Just watching what happens to cygheap->fdtab.fds_on_hold during a vfork should pinpoint it pretty quickly. cgf
Re: cygwin/xfree86 logged into KDE3 causes strange cygwin error
On Fri, Apr 05, 2002 at 08:14:44PM -0500, Harold Hunt wrote: >This is the first time I have every seen anything like this in >Cygwin/XFree86. > >I just installed KDE3 on my Linux box and when I login via XDMCP and run >Konsole I get this error message in Windows: > >--- >Error >--- >Failed assertion > fds_on_hold != NULL >at line 643 of file >/cygnus/netrel/src/cygwin-1.3.10-1/winsup/cygwin/dtable.cc >--- >OK >--- > > >So far this has happened only when I launch Konsole. Cygwin/XFree86 doesn't >crash when this happens, but things seem to get sketchy after it happens a >few times. > >Any ideas? It's coming from vfork. Something's stomping on memory that is supposed to hold a copy of the fd table. cgf
cataloger GPxZbal
Below is the result of your feedback form. It was submitted by GIBSON ([EMAIL PROTECTED]) on Friday, April 5, 2002 at 18:57:24 --- .: Imagine the perfect business: You Can Run It From Home...Or From Anywhere With A Telephone Connection There Is No Large Investment To Get Started You Can Put Everything On Auto-Pilot There Is No Face-To-Face Selling Involved There Is No Inventory To Buy Or Ship You Can Even Work In Your Underwear If You Want To (No More Ties!) Sound good? It Is! The Cash Flow System That Brought In Over $115,467.00 In The First Year for me, can do the exact same for you. If you dont make $4,000 in the first month, you will get a full refund! Click below for details... http:[EMAIL PROTECTED]/path2wealth1 p0Cc3exX sPGMqj5zAC ---
RE: Cygwin/XFree86 logged into KDE3 causes strange Cygwin error
Oh yeah, by "sketchy" I meant that after it happens a few times and I switch the focus away from Cygwin/XFree86 two things happen: 1) Cygwin/XFree86 freezes solid. 2) The Windows mouse cursor disappears and the Windows mouse doesn't work until I reboot. The mouse doesn't even start to work again when you press Ctrl+Alt+Del and get the Windows Security box that usually works perfectly even when programs have crashed. Yeah... that's pretty sketchy. Harold > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Harold Hunt > Sent: Friday, April 05, 2002 8:15 PM > To: cygx > Cc: cygwin > Subject: Cygwin/XFree86 logged into KDE3 causes strange Cygwin error > > > This is the first time I have every seen anything like this in > Cygwin/XFree86. > > I just installed KDE3 on my Linux box and when I login via XDMCP and run > Konsole I get this error message in Windows: > > --- > Error > --- > Failed assertion > fds_on_hold != NULL > at line 643 of file > /cygnus/netrel/src/cygwin-1.3.10-1/winsup/cygwin/dtable.cc > --- > OK > --- > > > So far this has happened only when I launch Konsole. > Cygwin/XFree86 doesn't > crash when this happens, but things seem to get sketchy after it happens a > few times. > > Any ideas? > > Harold >
Cygwin/XFree86 logged into KDE3 causes strange Cygwin error
This is the first time I have every seen anything like this in Cygwin/XFree86. I just installed KDE3 on my Linux box and when I login via XDMCP and run Konsole I get this error message in Windows: --- Error --- Failed assertion fds_on_hold != NULL at line 643 of file /cygnus/netrel/src/cygwin-1.3.10-1/winsup/cygwin/dtable.cc --- OK --- So far this has happened only when I launch Konsole. Cygwin/XFree86 doesn't crash when this happens, but things seem to get sketchy after it happens a few times. Any ideas? Harold
Re: Log file for Win2k/Remote Login Screen
Marc wrote: > Just a recap, I wasn't getting my remote login window when grabbing a > display from a machine running xdm stuff.. > > Turns out my installation was ok, but there was an old DNS entry associated > with my IP address and it must have been trying some funky reverse look up > stuff before giving me my display. I changed the IP to one with no DNS > entry and everything is fine now. > > I need to figure out how to tunnel these remote displays through ssh or > another type of encryption, but I don't see any possibilities. I don't like > sending my password in the clear via xdmcp. Anyone working with this? > According to the Linux XDMCP howto, it isn't possible to forward XDMCP over SSH because XDMCP uses UDP. You could ssh to the remote system with X forwarding and start the session manually. The X server would be started without any clients or window manager; you might have to adjust authorization to allow the remote machine to connect. - Ian -- [EMAIL PROTECTED] http://www.znark.com/
RE: FW: Patch to fix cygwin-xfree+gcc-2.95.3+autoconf problem
Alan, Yup. I just built it with no problems. Harold > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Alan Hourihane > Sent: Friday, April 05, 2002 2:31 PM > To: [EMAIL PROTECTED] > Subject: Re: FW: Patch to fix cygwin-xfree+gcc-2.95.3+autoconf problem > > > I can remove it - no problem. > > Have you tried building the tree without it first though ? > > Alan. > > On Fri, Apr 05, 2002 at 02:17:29 -0500, Harold Hunt wrote: > > Here is what Paul had to say. Put together with what Alan said > it sounds > > like __STDC__ will be coming out of StandardDefines. > > > > Alan, do you want to commit this directly, or would you like me > to submit a > > patch? > > > > Harold > > > > -Original Message- > > From: Paul Stodghill [mailto:[EMAIL PROTECTED]] > > Sent: Friday, April 05, 2002 1:53 PM > > To: Harold Hunt > > Subject: RE: Patch to fix cygwin-xfree+gcc-2.95.3+autoconf problem > > > > > > It's been over a year, but I believe that my reasoning was as follows, > > > > I guess it is not technically a bug. However, the C standard > (or at least > > the c9x draft that I have) says that __STDC__ is a predefined > implementation > > specific macro. The GCC manual discusses how __STDC__ is set > depending upon > > the use of the -traditional flag. I don't believe that it makes > sense to set > > or unset __STDC__ either from the command line or using preprocessor > > directives. > > > > Hope this helps. > > > > > > > > > -Original Message- > > > From: Harold Hunt [mailto:[EMAIL PROTECTED]] > > > Sent: Friday, April 05, 2002 1:32 PM > > > To: Paul Stodghill > > > Cc: cygx > > > Subject: RE: Patch to fix cygwin-xfree+gcc-2.95.3+autoconf problem > > > > > > > > > I recently stumbled across a message you wrote way back in March 2001: > > > http://list-archive.xemacs.org/xemacs-patches/200103/msg00082.html > > > > > > I notice that you say that cygwin.cf shouldn't be defining __STDC__ in > > > StandardDefines. I can see that linux.cf and darwin.cf do not define > > > __STDC__ in StandardDefines, but I don't know why we should > > > not be defining > > > it either. > > > > > > A quick and explanation would get this problem quickly > > > remedied (I like to > > > do things correctly, so I'd like to fix this problem). > > > > > > Thanks, > > > > > > Harold > > > > > >
Hi, I have question on cygwin configuration.
I have created a .profile file with the following lines: Export PS1='$:$:>' To see the working directory in my prompt, but it does now work and it displays $:$:> as prompt. How can I make it to work? I have Windows 2000. I don't if that makes difference.. Thanks! Tae.
Re: Log file for Win2k/Remote Login Screen
Just a recap, I wasn't getting my remote login window when grabbing a display from a machine running xdm stuff.. Turns out my installation was ok, but there was an old DNS entry associated with my IP address and it must have been trying some funky reverse look up stuff before giving me my display. I changed the IP to one with no DNS entry and everything is fine now. I need to figure out how to tunnel these remote displays through ssh or another type of encryption, but I don't see any possibilities. I don't like sending my password in the clear via xdmcp. Anyone working with this? Thanks! Marc - Original Message - From: Harold Hunt <[EMAIL PROTECTED]> To: Marc <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Thursday, April 04, 2002 1:41 AM Subject: RE: Log file for Win2k/Remote Login Screen > Marc, > > You're right, there are no errors in the log file. > > What sort of machine are you trying to connect to? Are you using a command > line as described in the User's Guide? > > http://xfree86.cygwin.com/docs/ug/using-remote-session.html > > Can you ping the remote machines in question? Are they connected via > ethernet or over a cable-modem or telephone line? How do you know that they > are "known-good", have you used Exceed or X-Win32 or some such X Server to > connect to those machines? >
RE: kde 3.0 no icons
Scott, I couldn't resist installing KDE3, so I did. I didn't have any problems. I suspect that something went wrong during installation of KDE3 on your machine. Here is a screenshot: http://xfree86.cygwin.com/screenshots/cygwin-xfree86-remote-kde3.png I added that shot to the screenshots page: http://xfree86.cygwin.com/screenshots/ I hope you get the problem figured out, Harold > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Scott Alexander > Sent: Friday, April 05, 2002 10:26 AM > To: [EMAIL PROTECTED] > Subject: kde 3.0 no icons > > > Hi, > > My server has just been upgraded to kde 3.0 running redhat 7.2. I use = > cygwin with xfree86 to connect to this server using > > x -query > > I have been doing this for a while with kde 2.2.2 with no problems. = > However when i connect to it now with kde 3 my screen has no icons or = > icons on the kicker bar at the bottom. =20 > > Does anyone know of this problem and a solution for it. > > My machine runs w2k with up 2 date cygwin and xfree86. > > Cheers > > Scott Alexander >
Re: FW: Patch to fix cygwin-xfree+gcc-2.95.3+autoconf problem
I can remove it - no problem. Have you tried building the tree without it first though ? Alan. On Fri, Apr 05, 2002 at 02:17:29 -0500, Harold Hunt wrote: > Here is what Paul had to say. Put together with what Alan said it sounds > like __STDC__ will be coming out of StandardDefines. > > Alan, do you want to commit this directly, or would you like me to submit a > patch? > > Harold > > -Original Message- > From: Paul Stodghill [mailto:[EMAIL PROTECTED]] > Sent: Friday, April 05, 2002 1:53 PM > To: Harold Hunt > Subject: RE: Patch to fix cygwin-xfree+gcc-2.95.3+autoconf problem > > > It's been over a year, but I believe that my reasoning was as follows, > > I guess it is not technically a bug. However, the C standard (or at least > the c9x draft that I have) says that __STDC__ is a predefined implementation > specific macro. The GCC manual discusses how __STDC__ is set depending upon > the use of the -traditional flag. I don't believe that it makes sense to set > or unset __STDC__ either from the command line or using preprocessor > directives. > > Hope this helps. > > > > > -Original Message- > > From: Harold Hunt [mailto:[EMAIL PROTECTED]] > > Sent: Friday, April 05, 2002 1:32 PM > > To: Paul Stodghill > > Cc: cygx > > Subject: RE: Patch to fix cygwin-xfree+gcc-2.95.3+autoconf problem > > > > > > I recently stumbled across a message you wrote way back in March 2001: > > http://list-archive.xemacs.org/xemacs-patches/200103/msg00082.html > > > > I notice that you say that cygwin.cf shouldn't be defining __STDC__ in > > StandardDefines. I can see that linux.cf and darwin.cf do not define > > __STDC__ in StandardDefines, but I don't know why we should > > not be defining > > it either. > > > > A quick and explanation would get this problem quickly > > remedied (I like to > > do things correctly, so I'd like to fix this problem). > > > > Thanks, > > > > Harold > > > >
FW: Patch to fix cygwin-xfree+gcc-2.95.3+autoconf problem
Here is what Paul had to say. Put together with what Alan said it sounds like __STDC__ will be coming out of StandardDefines. Alan, do you want to commit this directly, or would you like me to submit a patch? Harold -Original Message- From: Paul Stodghill [mailto:[EMAIL PROTECTED]] Sent: Friday, April 05, 2002 1:53 PM To: Harold Hunt Subject: RE: Patch to fix cygwin-xfree+gcc-2.95.3+autoconf problem It's been over a year, but I believe that my reasoning was as follows, I guess it is not technically a bug. However, the C standard (or at least the c9x draft that I have) says that __STDC__ is a predefined implementation specific macro. The GCC manual discusses how __STDC__ is set depending upon the use of the -traditional flag. I don't believe that it makes sense to set or unset __STDC__ either from the command line or using preprocessor directives. Hope this helps. > -Original Message- > From: Harold Hunt [mailto:[EMAIL PROTECTED]] > Sent: Friday, April 05, 2002 1:32 PM > To: Paul Stodghill > Cc: cygx > Subject: RE: Patch to fix cygwin-xfree+gcc-2.95.3+autoconf problem > > > I recently stumbled across a message you wrote way back in March 2001: > http://list-archive.xemacs.org/xemacs-patches/200103/msg00082.html > > I notice that you say that cygwin.cf shouldn't be defining __STDC__ in > StandardDefines. I can see that linux.cf and darwin.cf do not define > __STDC__ in StandardDefines, but I don't know why we should > not be defining > it either. > > A quick and explanation would get this problem quickly > remedied (I like to > do things correctly, so I'd like to fix this problem). > > Thanks, > > Harold > >
Re: cx-logos
On Fri, Apr 05, 2002 at 12:13:37PM -0500, Nikolaus Bates-Haus wrote: >You're right. I missed the message when it came through; >http://sources.redhat.com/ml/cygwin-xfree/2002-02/msg00234.html > >Logo by Tucker McLean; I like it. Me too. A lot. I don't know if Tucker is still listen, but I'm wondering if he would like to send just the cygwin logo part. I'd like to use it for the cygwin stuff. In fact, I'd like to use it for Cygwin Setup. cgf >On Fri, Apr 05, 2002 at 12:04:25PM -0500, Christopher Faylor wrote: >> On Fri, Apr 05, 2002 at 12:02:04PM -0500, Nikolaus Bates-Haus wrote: >> >Thanks for taking the time to put these together; I even have a suggestion! >> > >> >I agree that a plain "CX" doesn't really convey Cygwin/XFree86; but the >> >Cygwin logo ( http://sources.redhat.com/cygwin/cygwin-icon.gif ) >> >combined with the X logo ( generally available in >> >/usr/X11R6/include/X11/bitmaps/xlogo64 ) _would_ be clear. >> >> Didn't someone post a really cool 3-d version of the cygwin icon + X a >> couple of weeks ago? >> >> cgf
Re: Patch to fix cygwin-xfree+gcc-2.95.3+autoconf problem
On Fri, Apr 05, 2002 at 01:31:48 -0500, Harold Hunt wrote: > I recently stumbled across a message you wrote way back in March 2001: > http://list-archive.xemacs.org/xemacs-patches/200103/msg00082.html > > I notice that you say that cygwin.cf shouldn't be defining __STDC__ in > StandardDefines. I can see that linux.cf and darwin.cf do not define > __STDC__ in StandardDefines, but I don't know why we should not be defining > it either. > > A quick and explanation would get this problem quickly remedied (I like to > do things correctly, so I'd like to fix this problem). > Good point. The compiler should define __STDC__ depending on the flags passed to it. Alan.
RE: Patch to fix cygwin-xfree+gcc-2.95.3+autoconf problem
I recently stumbled across a message you wrote way back in March 2001: http://list-archive.xemacs.org/xemacs-patches/200103/msg00082.html I notice that you say that cygwin.cf shouldn't be defining __STDC__ in StandardDefines. I can see that linux.cf and darwin.cf do not define __STDC__ in StandardDefines, but I don't know why we should not be defining it either. A quick and explanation would get this problem quickly remedied (I like to do things correctly, so I'd like to fix this problem). Thanks, Harold
Re: cx-logos
On Friday 5 Apr 02, Nikolaus Bates-Haus writes: > You're right. I missed the message when it came through; > http://sources.redhat.com/ml/cygwin-xfree/2002-02/msg00234.html > > Logo by Tucker McLean; I like it. Yes, this one is very good IMO. David
Re: cx-logos
You're right. I missed the message when it came through; http://sources.redhat.com/ml/cygwin-xfree/2002-02/msg00234.html Logo by Tucker McLean; I like it. -nik On Fri, Apr 05, 2002 at 12:04:25PM -0500, Christopher Faylor wrote: > On Fri, Apr 05, 2002 at 12:02:04PM -0500, Nikolaus Bates-Haus wrote: > >Thanks for taking the time to put these together; I even have a suggestion! > > > >I agree that a plain "CX" doesn't really convey Cygwin/XFree86; but the > >Cygwin logo ( http://sources.redhat.com/cygwin/cygwin-icon.gif ) > >combined with the X logo ( generally available in > >/usr/X11R6/include/X11/bitmaps/xlogo64 ) _would_ be clear. > > Didn't someone post a really cool 3-d version of the cygwin icon + X a > couple of weeks ago? > > cgf
Re: cx-logos
On Fri, Apr 05, 2002 at 12:02:04PM -0500, Nikolaus Bates-Haus wrote: >Thanks for taking the time to put these together; I even have a suggestion! > >I agree that a plain "CX" doesn't really convey Cygwin/XFree86; but the >Cygwin logo ( http://sources.redhat.com/cygwin/cygwin-icon.gif ) >combined with the X logo ( generally available in >/usr/X11R6/include/X11/bitmaps/xlogo64 ) _would_ be clear. Didn't someone post a really cool 3-d version of the cygwin icon + X a couple of weeks ago? cgf
Re: cx-logos
Thanks for taking the time to put these together; I even have a suggestion! I agree that a plain "CX" doesn't really convey Cygwin/XFree86; but the Cygwin logo ( http://sources.redhat.com/cygwin/cygwin-icon.gif ) combined with the X logo ( generally available in /usr/X11R6/include/X11/bitmaps/xlogo64 ) _would_ be clear. -nik On Fri, Apr 05, 2002 at 11:34:32AM +, David Starks-Browning wrote: > On Thursday 4 Apr 02, Saurabh Nupur writes: > > hello all, > > > > i made some logos. > > > > http://www.geocities.com/nupursarpal/logo_2.jpg > > http://www.geocities.com/nupursarpal/logo_3.jpg > > http://www.geocities.com/nupursarpal/logo_4.jpg > > http://www.geocities.com/nupursarpal/logo_1.jpg > > > > suggestions and comments are welcome > > Personally, I don't find that "CX" conveys "Cygwin/XFree86" very > well. But I don't have other suggestions, sorry. > > David >
Re: kde 3.0 no icons
Scott, That doesn't sound good. I haven't yet installed KDE 3.0 and I won't have time to for at least a week, so I won't have a chance to look into this for some time. I know you say that Cygwin/XFree86 is up-to-date, but are you running Cygwin/XFree86 4.2.0? You can check by running 'xdpyinfo' in a local Cygwin/XFree86 session or in a terminal when you are logged into another machine via XDMCP. Awaiting a chance to investiage this, Harold Scott Alexander <[EMAIL PROTECTED]> said: > Hi, > > My server has just been upgraded to kde 3.0 running redhat 7.2. I use = > cygwin with xfree86 to connect to this server using > > x -query > > I have been doing this for a while with kde 2.2.2 with no problems. = > However when i connect to it now with kde 3 my screen has no icons or = > icons on the kicker bar at the bottom. =20 > > Does anyone know of this problem and a solution for it. > > My machine runs w2k with up 2 date cygwin and xfree86. > > Cheers > > Scott Alexander > >
RE: Help on XDM with Solaris Host
Joco, The question has been answered more specifically: http://xfree86.cygwin.com/docs/faq/cygwin-xfree-faq.html#q-solaris-fonts Harold [EMAIL PROTECTED] said: > Hi everybody! > > I have exactly the same problem, but the solution > mentioned below I don't understand. > What does it mean 'tcp/solaris_box:7100'? > Is it a path, or what? > Bo, please be more specific. > > Thanks, > joco > > > >Thanks to derk.steggewentz. The problem was solved. > >I only need to point the font path to the font server which is > >already running on my Solaris box. > >XWin -query solaris_box -fp tcp/solaris_box:7100 > >Bo > > > > -Original Message- > > From: Zhang, Bo > > Sent: Thursday, December 13, 2001 10:01 AM > > To: '[EMAIL PROTECTED]' > > Subject: Help on XDM with Solaris Host > > > > > > I found in the Cygwin/Xfree86 FAQ there is a similar issue, which > > was supposed to have been solved by installing the latest Solaris > > patches. > > > > I did install all the recommended patches. And my XWin still can't > > come up with XDMCP. > > > > I got the following error messages after XWin hang for a long time > > and timed-out: > > > > winDetectSupportedEngines () - Windows NT/2000 > > winDetectSupportedEngines () - DirectDraw installed > > winDetectSupportedEngines () - Allowing PrimaryDD > > winDetectSupportedEngines () - Returning, supported engines 001b > > winSetEngine () - Using Shadow DirectDraw > > winCreateBoundingWindowWindowed () - WindowClient w 1274 h 970 r 1274 > > l 0 b 970 t 0 > > winInitVisualsShadowDD () - Masks 00ff ff00 00ff BPRGB 8 d > > 32 > > winCreateDefColormap () - Deferring to fbCreateDefColormap () > > AUDIT: Wed Dec 12 16:50:25 2001: 255 XWin: client 1 rejected from IP > > 172.16.33.210 port 33748 > >Auth name: MIT-MAGIC-COOKIE-1 ID: -1 > > XDM: too many keepalive retransmissions, declaring session dead > > > > Can anyone help me out? > > > > Thanks, > > > > Bo > > > > > >-Original Message- > > From: Zhang, Bo > > Sent: Tuesday, December 11, 2001 6:37 PM > > To: '[EMAIL PROTECTED]' > > Subject:Help on XDM with Solaris Host > > > > > > Hello, everyone, > > > > I have installed Cygwin/Xfree86 on my NT machine. XWin worked fine > > as a standalone X-server. However, I couldn't get XDM to work with > > my > > Solaris 2.8. The root window is opened, but it hangs there. It looks > > like > > some kind of infinite loop (CPU ustilization on my PC goes 100% for > > a > > very long time), but Alt-F4 still works. > > > > Has anyone experienced this before? Does anyone has solutions to it? > > > > Thanks, > > > > Bo Zhang > > >
Re: Missing terminfo data in XFree86 4.2.0
Michael,
You already know way more about the problem than I do. I have never seen the
problem described so completely.
Reasoning from what you have said leads me to believe that the packaging
script that we use (same as all of the other XFree86 platforms) may be
misbehaving and accidentally leaving out said file.
I guess what needs to happen is for Alan or I to take a look at the packaging
process and see if there is an error that indicates that this is indeed
happening.
Or, you could take a look for yourself (since you know more about the
problem), by following the build and packing instructions in the
Cygwin/XFree86 Contributor's Guide:
http://xfree86.cygwin.com/docs/cg/
Harold
Michael <[EMAIL PROTECTED]> said:
> Hi
>
> I ran into the following problem with the current XFree86 distribution, but
> could not find any mention of any solution here or elsewhere.
>
> SYMPTOMS
>
> * "vt102" terminal setting (TERM) in xterm windows instead of "xterm"
> * "WARNING: terminal is not fully functional" error messages from /bin/less
> * Missing /usr/share/terminfo/x/xterm and other terminfo data files
>
> CAUSE
> -
> 1. The current XFree86 for Cygwin distribution is missing the file
>xterm.terminfo (but not xterm.termcap) in Xlib.tgz. (However this is
>not true for other distributions, eg FreeBSD.) It is missing in the
>distribution available from the Cygwin mirrors and the distribution
>available directly from XFree86.
> 2. After unpacking the distribution files, the script Xinstall.sh asks the
>user whether to update the terminfo entries. The default is no, but the
>blurb notes that new features will be unavailable otherwise.
>
> If the user says yes:
> 3. The script moves a number of existing terminfo entries to *.bak
> 4. The script tries to run tic on /usr/X11R6/lib/X11/etc/xterm.terminfo to
>replace them
> 5. Since this file is not present, tic fails
> 6. The following terminfo files are subsequently effectively missing: xterm,
>xterms, xterm-24, xterm-vi, xterm-65, xterm-bold, xtermm, xterm-boldso,
>xterm-ic, xterm-r6, xterm-old, xterm-r5, vs100
>
> INTERIM SOLUTIONS
> -
> During install (pre-emptive):
> * Do not elect to update terminfo entries
> After install (treatment):
> * Setting the TERM variable to another value such as cygwin or ansi is
> a temporary workaround
> * Moving the renamed files back to their original names reverses the
> damage ("mv xterm.bak xterm" etc)
>
> DISTRIBUTION FIX?
> -
> Include the file or change the installation script
>
> QUESTIONS
> -
> * Is there some reason xterm.terminfo is missing, or is this an error?
> * Is it possible to use e.g. the FreeBSD distribution's xterm.terminfo file?
> * Is it advised against updating the terminfo data?
> * If so, then what about updating termcap entries (suggested by Xinstall.h)?
> * What is lost by not using the new terminfo data?
>
> Thanks
> Michael
>
>
RE: Help on XDM with Solaris Host
Hi everybody! I have exactly the same problem, but the solution mentioned below I don't understand. What does it mean 'tcp/solaris_box:7100'? Is it a path, or what? Bo, please be more specific. Thanks, joco >Thanks to derk.steggewentz. The problem was solved. >I only need to point the font path to the font server which is >already running on my Solaris box. >XWin -query solaris_box -fp tcp/solaris_box:7100 >Bo > -Original Message- > From: Zhang, Bo > Sent: Thursday, December 13, 2001 10:01 AM > To: '[EMAIL PROTECTED]' > Subject: Help on XDM with Solaris Host > > > I found in the Cygwin/Xfree86 FAQ there is a similar issue, which > was supposed to have been solved by installing the latest Solaris > patches. > > I did install all the recommended patches. And my XWin still can't > come up with XDMCP. > > I got the following error messages after XWin hang for a long time > and timed-out: > > winDetectSupportedEngines () - Windows NT/2000 > winDetectSupportedEngines () - DirectDraw installed > winDetectSupportedEngines () - Allowing PrimaryDD > winDetectSupportedEngines () - Returning, supported engines 001b > winSetEngine () - Using Shadow DirectDraw > winCreateBoundingWindowWindowed () - WindowClient w 1274 h 970 r 1274 > l 0 b 970 t 0 > winInitVisualsShadowDD () - Masks 00ff ff00 00ff BPRGB 8 d > 32 > winCreateDefColormap () - Deferring to fbCreateDefColormap () > AUDIT: Wed Dec 12 16:50:25 2001: 255 XWin: client 1 rejected from IP > 172.16.33.210 port 33748 >Auth name: MIT-MAGIC-COOKIE-1 ID: -1 > XDM: too many keepalive retransmissions, declaring session dead > > Can anyone help me out? > > Thanks, > > Bo > > >-Original Message- > From: Zhang, Bo > Sent: Tuesday, December 11, 2001 6:37 PM > To: '[EMAIL PROTECTED]' > Subject:Help on XDM with Solaris Host > > > Hello, everyone, > > I have installed Cygwin/Xfree86 on my NT machine. XWin worked fine > as a standalone X-server. However, I couldn't get XDM to work with > my > Solaris 2.8. The root window is opened, but it hangs there. It looks > like > some kind of infinite loop (CPU ustilization on my PC goes 100% for > a > very long time), but Alt-F4 still works. > > Has anyone experienced this before? Does anyone has solutions to it? > > Thanks, > > Bo Zhang
kde 3.0 no icons
Hi, My server has just been upgraded to kde 3.0 running redhat 7.2. I use = cygwin with xfree86 to connect to this server using x -query I have been doing this for a while with kde 2.2.2 with no problems. = However when i connect to it now with kde 3 my screen has no icons or = icons on the kicker bar at the bottom. =20 Does anyone know of this problem and a solution for it. My machine runs w2k with up 2 date cygwin and xfree86. Cheers Scott Alexander
Missing terminfo data in XFree86 4.2.0
Hi
I ran into the following problem with the current XFree86 distribution, but
could not find any mention of any solution here or elsewhere.
SYMPTOMS
* "vt102" terminal setting (TERM) in xterm windows instead of "xterm"
* "WARNING: terminal is not fully functional" error messages from /bin/less
* Missing /usr/share/terminfo/x/xterm and other terminfo data files
CAUSE
-
1. The current XFree86 for Cygwin distribution is missing the file
xterm.terminfo (but not xterm.termcap) in Xlib.tgz. (However this is
not true for other distributions, eg FreeBSD.) It is missing in the
distribution available from the Cygwin mirrors and the distribution
available directly from XFree86.
2. After unpacking the distribution files, the script Xinstall.sh asks the
user whether to update the terminfo entries. The default is no, but the
blurb notes that new features will be unavailable otherwise.
If the user says yes:
3. The script moves a number of existing terminfo entries to *.bak
4. The script tries to run tic on /usr/X11R6/lib/X11/etc/xterm.terminfo to
replace them
5. Since this file is not present, tic fails
6. The following terminfo files are subsequently effectively missing: xterm,
xterms, xterm-24, xterm-vi, xterm-65, xterm-bold, xtermm, xterm-boldso,
xterm-ic, xterm-r6, xterm-old, xterm-r5, vs100
INTERIM SOLUTIONS
-
During install (pre-emptive):
* Do not elect to update terminfo entries
After install (treatment):
* Setting the TERM variable to another value such as cygwin or ansi is
a temporary workaround
* Moving the renamed files back to their original names reverses the
damage ("mv xterm.bak xterm" etc)
DISTRIBUTION FIX?
-
Include the file or change the installation script
QUESTIONS
-
* Is there some reason xterm.terminfo is missing, or is this an error?
* Is it possible to use e.g. the FreeBSD distribution's xterm.terminfo file?
* Is it advised against updating the terminfo data?
* If so, then what about updating termcap entries (suggested by Xinstall.h)?
* What is lost by not using the new terminfo data?
Thanks
Michael
Re: App Unable to Acceess X Display
Redirected to proper mailing list. On Thu, Apr 04, 2002 at 08:50:10PM -0500, Mike wrote: >Hello. My name is Mike. I am running Win 2000 Pro. I have recently >tried to install the Lyx Latex editor. I had a successful Cygwin and, >by all indications, Lyx install. When I try to launch Lyx, I receive >the error "cannot access X display, exiting." I raise the issue here >because it does not seem to have been resolved at the "Lyx" end of >things and thus may be a bigger problem than just the app itself. >The pat response to the query from the Lyx side of the house is to >modify the Lyx config file. Specifically, to change the variable >"DISPLAY =" from " localhost:0.0" to the computer's IP address e.g. >"192.168.0.102:0.0". Unfortunately, several posts seem to indicate that >this does not necessarily work. Certainly, in my case it hasn't. The >other pat answer is to make sure any firewalls allow local port access. >This does not seem to resolve the issue either. I have searched the >internet and mail archives and still haven't found a solution. > >Again, I raise the issue simply in case it matters to you. If you have >an insight it would be appreciated. Meanwhile, I will return to trying >to convince my department that even if it isn't WYSIWYG, Latex is still >worth a shot. Cheers.
RE: cx-logos
I'm not so sure that we are allowed to use the X logo. That would have to be looked into before we started using it. Harold > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Brian Genisio > Sent: Friday, April 05, 2002 7:01 AM > To: Alexander Gottwald; Saurabh Nupur > Cc: [EMAIL PROTECTED] > Subject: Re: cx-logos > > > Yes, I like this one the best as well. I believe it is very important to > convey that this is a port of the XFree86 software. This logo > does it well > with it's "86". Might I suggest also incorporating some identification of > Cygwin? There are two logos I have seen (www.cygwin.com), the > one that looks > like a copyright symbol with an arrow, and the BlackAndGreen, > ugly Cygwin icon. > Possibly, you can incorporate one of those feels? > > Also, have you seen the X logo? (Open the X server, and run > xlogo.exe) This is > kind of a standard X-windows protocol logo. You might want to > incorporate that > somehow. > > Just my 2 cents, > Brian > > --- Alexander Gottwald > <[EMAIL PROTECTED]> wrote: > > On Thu, 4 Apr 2002, Saurabh Nupur wrote: > > > > > http://www.geocities.com/nupursarpal/logo_4.jpg > > > > I like this one. > > > > bye > > ago > > -- > > [EMAIL PROTECTED] > > http://www.gotti.org ICQ: 126018723 > > phone: +49 3725 349 80 80 mobile: +49 172 7854017 > > > > > __ > Do You Yahoo!? > Yahoo! Tax Center - online filing with TurboTax > http://taxes.yahoo.com/
Re: cx-logos
Yes, I like this one the best as well. I believe it is very important to convey that this is a port of the XFree86 software. This logo does it well with it's "86". Might I suggest also incorporating some identification of Cygwin? There are two logos I have seen (www.cygwin.com), the one that looks like a copyright symbol with an arrow, and the BlackAndGreen, ugly Cygwin icon. Possibly, you can incorporate one of those feels? Also, have you seen the X logo? (Open the X server, and run xlogo.exe) This is kind of a standard X-windows protocol logo. You might want to incorporate that somehow. Just my 2 cents, Brian --- Alexander Gottwald <[EMAIL PROTECTED]> wrote: > On Thu, 4 Apr 2002, Saurabh Nupur wrote: > > > http://www.geocities.com/nupursarpal/logo_4.jpg > > I like this one. > > bye > ago > -- > [EMAIL PROTECTED] > http://www.gotti.org ICQ: 126018723 > phone: +49 3725 349 80 80mobile: +49 172 7854017 > __ Do You Yahoo!? Yahoo! Tax Center - online filing with TurboTax http://taxes.yahoo.com/
Re: cx-logos
On Thu, 4 Apr 2002, Saurabh Nupur wrote: > http://www.geocities.com/nupursarpal/logo_4.jpg I like this one. bye ago -- [EMAIL PROTECTED] http://www.gotti.org ICQ: 126018723 phone: +49 3725 349 80 80 mobile: +49 172 7854017
Re: cx-logos
On Thursday 4 Apr 02, Saurabh Nupur writes: > hello all, > > i made some logos. > > http://www.geocities.com/nupursarpal/logo_2.jpg > http://www.geocities.com/nupursarpal/logo_3.jpg > http://www.geocities.com/nupursarpal/logo_4.jpg > http://www.geocities.com/nupursarpal/logo_1.jpg > > suggestions and comments are welcome Personally, I don't find that "CX" conveys "Cygwin/XFree86" very well. But I don't have other suggestions, sorry. David
