From colin.harrison@virgin.net Sat Nov 1 02:14:00 2003 From: colin.harrison@virgin.net (Colin Harrison) Date: Sat, 01 Nov 2003 02:14:00 -0000 Subject: no key input Message-ID: <000001c3a01d$ecb9c840$0200a8c0@straightrunning.com> Hi, >I didn't realize you were building from CVS... >I didn't realize anyone was doing that. Yep some of us are still using CVS + various patches and customisations and bodges (no pain no gain!). My xc tree (XFree latest as of yesterday + patches) is as close as I thing the game is and is still doing the job for me! (e.g. I've even patched for new 'shared' rootless and haven't even used/tested it!). Keep up the good work...I'll try to build/test new trees as they materialise (within my scope...multiwindow and/or XDMCP on XP and Windows 2003 server platforms) Colin From frederic.frances@club-internet.fr Sat Nov 1 17:50:00 2003 From: frederic.frances@club-internet.fr (Frédéric Frances) Date: Sat, 01 Nov 2003 17:50:00 -0000 Subject: Campagne d'éducation à la non-violence active Message-ID: <20031101174954.313573C3B@relay-3v.club-internet.fr> Madame, Monsieur, "La Communaut?? pour le D??veloppement Humain" recherche des volontaires humanistes souhaitant d??velopper, dans leur pays respectif, une Campagne Panafricaine d'Education ?? la non-violence Active. Lanc??e en 2001 en Am??rique Latine, cette campagne a commenc?? ?? s'??tendre sur le continent africain en 2002 : Alg??rie, S??n??gal, Burkina Faso, Togo, B??nin, Kenya, etc. Elle a pour objectifs : - d'aider ?? s'auto organiser de fa??on autonome, toute association, toute personne d??cid??e ?? agir avec d'autres, sur des conflits locaux (sant??, ??ducation, qualit?? de vie) ; conflits g??n??r??s par les violences des mod??les de soci??t?? existants actuellement, que ces violences soient ??conomiques, religieuses, morales, physiques, psychologiques, sexuelles, ou produites par toutes autres sortes de discrimination,?? - de partager et de participer de l'exp??rience d'un r??seau organis??, le Mouvement Humaniste, compos?? ?? ce jour de 2 millions de volontaires humanistes (?? titre d'exemple, 70 000 s??n??galais, 15 000 burkinab??s),actifs dans plus de 120 pays sur les 5 continents. "La Communaut?? pour le D??veloppement Humain", un des fronts d'action de ce r??seau, propose un apprentissage ?? la non-violence Active, une m??thodologie d'organisation non-violente autour d'actions sociales concr??tes. Si vous ??tes int??ress??s, je vous remercie de r??pondre ?? cet email dans les d??lais les plus brefs, nous planifions en effet une s??rie de conf??rences/Exp??riences qui commenceront au Cameroun en f??vrier-mars 2003. Vous souhaitant Paix Force et Joie Amicalement Fr??d??ric Frances coordinateur de la campagne conseil H IOTA PS : si vous ??tes d??j?? membre de la structure du Mouvement Humaniste, ou si vous ne souhaitez plus ??tre sollicit?? ?? ce sujet, merci de le pr??ciser. From huntharo@msu.edu Sat Nov 1 22:39:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Sat, 01 Nov 2003 22:39:00 -0000 Subject: freenode.net - IRC channel for the project? In-Reply-To: References: <3F9D7780.7020608@msu.edu> <3F9D796C.7020802@JaySmith.com> <3F9D7BE1.20200@msu.edu> Message-ID: <3FA4362C.50802@msu.edu> Alexander Gottwald wrote: > Harold L Hunt II wrote: > > >>I like the format of IRC and I think I could answer questions more >>quickly there. I also think that some development discussions would be >>better off in IRC. It is something I want to try, that is all. > > > Discussing in the messaging systems (irc or icq) is sometimes more productive > than via email. Especially when trying new ideas or debugging strange errors. I agree. IRC will help us to be more productive. > I like the idea of setting up the channel. But the where and how should be > discussed by the people who are more comfortable with this topic than I am. Hmm... bummer... I was hoping that someone would have some knowledge about setting up a channel on freenode.net. I'm not having a lot of luck figuring out how they do it. The documentation they have tells how you should operate your channel, but it doesn't tell you if the channels have to registered/reserved and doesn't tell you how to go about doing that if that is the case. I don't want to pester the freedesktop.org folks asking them too many questions about IRC... Harold From huntharo@msu.edu Sat Nov 1 22:55:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Sat, 01 Nov 2003 22:55:00 -0000 Subject: Grabbing XFree86.org's xc/ tree using cvsup Message-ID: <3FA439E8.4020601@msu.edu> I am looking into how to import the XFree86.org xc/ tree into freedesktop.org. It looks like cvsup is the way to go here, since it mirrors the actual repository instead of grabbing a snapshot of the repository. My question is: should I tell cvsup to drop the tree directly into /home/cvs, or should I pull the tree into my home directory, then copy it into /home/cvs? It sort of seems unwise to drop the tree directly into /home/cvs, especially since cvsup needs to keep some state files (which I would most likely put in /home/harold/xc/sup) that imply that only one person would be able to make changes to the cvsup mirror. Another thing to keep in mind is how we want to do development. It has been suggested that we keep the HEAD branch in sync with XFree86.org and that we do our development on another branch. The question here is whether cvsup can preserve a local branch of the code and still be used to sync with XFree86.org. I doubt that this is the case, since cvsup is essentially mirroring the files, not branches/tags/etc. Does this mean that we must manually track XFree86.org and apply their patches after the initial import? I would appreciate any input on this. Let me be the first to admit that I am not a CVS administrator. I want to get this tree setup quickly so that Alexander Gottwald (ago), Kensuke Matsuzaki (zakki), and myself can quickly resume our development on Cygwin/X. Another goal is for the xc/ tree to be usable by others that wish to develop on an old-style xc/ tree outside of XFree86.org. Thanks in advance, Harold From 1@pervalidus.net Sat Nov 1 23:13:00 2003 From: 1@pervalidus.net (=?ISO-8859-1?Q?Fr=E9d=E9ric_L=2E_W=2E_Meunier?=) Date: Sat, 01 Nov 2003 23:13:00 -0000 Subject: freenode.net - IRC channel for the project? In-Reply-To: <3FA4362C.50802@msu.edu> References: <3F9D7780.7020608@msu.edu> <3F9D796C.7020802@JaySmith.com> <3F9D7BE1.20200@msu.edu> <3FA4362C.50802@msu.edu> Message-ID: On Sat, 1 Nov 2003, Harold L Hunt II wrote: > I don't want to pester the freedesktop.org folks asking them > too many questions about IRC... I may be able to help you. I'm fredlwm. But first do a /msg chanserv help /msg chanserv help register ... :-) I don't even know if your nickname is registered. If it isn't, do a /msg nickserv help /msg nickserv help register ... /msg nickserv register password is enough. -- How to contact me - http://www.pervalidus.net/contact.html From huntharo@msu.edu Sat Nov 1 23:56:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Sat, 01 Nov 2003 23:56:00 -0000 Subject: freenode.net - IRC channel for the project? In-Reply-To: References: <3F9D7780.7020608@msu.edu> <3F9D796C.7020802@JaySmith.com> <3F9D7BE1.20200@msu.edu> <3FA4362C.50802@msu.edu> Message-ID: <3FA4482D.4080408@msu.edu> Fr??d??ric, Thanks! That is all I needed to know! Harold Fr??d??ric L. W. Meunier wrote: > On Sat, 1 Nov 2003, Harold L Hunt II wrote: > > >>I don't want to pester the freedesktop.org folks asking them >>too many questions about IRC... > > > I may be able to help you. I'm fredlwm. > > But first do a > /msg chanserv help > /msg chanserv help register > ... > > :-) > > I don't even know if your nickname is registered. If it isn't, > do a > /msg nickserv help > /msg nickserv help register > ... > > /msg nickserv register password is enough. > From huntharo@msu.edu Sun Nov 2 00:05:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Sun, 02 Nov 2003 00:05:00 -0000 Subject: New IRC channel for the project: irc.freenode.net #cygwinx Message-ID: <3FA44A47.4080406@msu.edu> I have created a channel for discussion of Cygwin/X. Relevant topics include questions from users and discussion of development. I will try to hang out in #cygwinx whenever I am online. I may occasionally direct people to the IRC channel if we are discussing something in email that would be easier to discuss in IRC. Feel free to request my presence in #cygwinx on this mailing list if I am not currently there; in some cases I may not be in #cygwinx simply because I forgot to login. Hope to see you there, Harold From cnst@rbcmail.ru Sun Nov 2 05:12:00 2003 From: cnst@rbcmail.ru (Constantine) Date: Sun, 02 Nov 2003 05:12:00 -0000 Subject: xinit: The application has failed to start because cygfreetype-6.dll was not found. In-Reply-To: <3FA142F1.5030604@msu.edu> References: <3FA142F1.5030604@msu.edu> Message-ID: <3FA4921D.40102@rbcmail.ru> Hello, After I have updated my installation today, and when I am running xinit now, I get a Windows window with the message that "cygfreetype-6.dll was not found". After I did the following, everything worked again: cd /usr/X11R6/bin/ cp cygfreetype-9.dll cygfreetype-6.dll Cheers, Constantine A. Murenin. From murakami@ipl.t.u-tokyo.ac.jp Sun Nov 2 13:54:00 2003 From: murakami@ipl.t.u-tokyo.ac.jp (Takuma Murakami) Date: Sun, 02 Nov 2003 13:54:00 -0000 Subject: xmodmap has no effect on mouse buttons In-Reply-To: <20031029115215.7071.RUDOLPH@merl.com> References: <20031029115215.7071.RUDOLPH@merl.com> Message-ID: <20031102221251.1304.MURAKAMI@ipl.t.u-tokyo.ac.jp> At line 2912 in xc/programs/Xserver/dix/events.c the function CoreProcessPointerEvent reads: #if !defined(XFree86Server) || !defined(XINPUT) xE->u.u.detail = butc->map[key]; #endif This code remaps mouse buttons. For XWin.exe the symbols XFree86Server and XINPUT are both defined and this remapping is not performed. I think this has something to do with the problem but I don't know whether it is an expected behaviour or not. Could anyone help me? Takuma Murakami (murakami@ipl.t.u-tokyo.ac.jp) From huntharo@msu.edu Sun Nov 2 18:14:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Sun, 02 Nov 2003 18:14:00 -0000 Subject: xinit: The application has failed to start because cygfreetype-6.dll was not found. In-Reply-To: <3FA4921D.40102@rbcmail.ru> References: <3FA142F1.5030604@msu.edu> <3FA4921D.40102@rbcmail.ru> Message-ID: <3FA5496D.2090708@msu.edu> Constantine wrote: > Hello, > > After I have updated my installation today, and when I am running xinit > now, I get a Windows window with the message that "cygfreetype-6.dll was > not found". > > After I did the following, everything worked again: > > cd /usr/X11R6/bin/ > cp cygfreetype-9.dll cygfreetype-6.dll Constantine, Hmm... I would appreciate it if you could help me to figure out what the real problem is here. The new XFree86-bin-4.3.0-7 package no longer contains cygfreetype-9.dll, as this library is now distributed as part of the freetype2/libfreetype26 package. freetype2 defines the version of the freetype2 library as '6' instead of the '9' that XFree86 was using as the library version. I added a copy of cygfreetype-9.dll to the XFree86-lib-compat package for those that need the old library. However, I want to know what application was failing in your xinit scripts. There should not be an application that requires cygfreetype-9.dll in the default script. Have you modified your script? What program are you launching that requires this DLL? Are you launching emacs? I would like to get any old applications that use cygfreetype-9.dll rebuilt. Thanks for testing, Harold From huntharo@msu.edu Sun Nov 2 22:10:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Sun, 02 Nov 2003 22:10:00 -0000 Subject: xmodmap has no effect on mouse buttons In-Reply-To: <20031102221251.1304.MURAKAMI@ipl.t.u-tokyo.ac.jp> References: <20031029115215.7071.RUDOLPH@merl.com> <20031102221251.1304.MURAKAMI@ipl.t.u-tokyo.ac.jp> Message-ID: <3FA580D0.3050401@msu.edu> Takuma, Takuma Murakami wrote: > At line 2912 in xc/programs/Xserver/dix/events.c > the function CoreProcessPointerEvent reads: > > #if !defined(XFree86Server) || !defined(XINPUT) > xE->u.u.detail = butc->map[key]; > #endif > > This code remaps mouse buttons. For XWin.exe the > symbols XFree86Server and XINPUT are both defined and > this remapping is not performed. > > I think this has something to do with the problem but > I don't know whether it is an expected behaviour or not. > Could anyone help me? I think you have a good point there. I thought I tried to disable the definition of XFree86Server when building XWin.exe... maybe I didn't try hard enough, or maybe that never made it into XFree86's CVS. Hmm... or maybe I actually had to enable XFree86Server... I just don't remember. In any case, somebody should do a build that doesn't have XFree86Server defined and see if it fixes the problem. Harold From Alexander.Gottwald@s1999.tu-chemnitz.de Sun Nov 2 23:26:00 2003 From: Alexander.Gottwald@s1999.tu-chemnitz.de (Alexander Gottwald) Date: Sun, 02 Nov 2003 23:26:00 -0000 Subject: Grabbing XFree86.org's xc/ tree using cvsup In-Reply-To: <3FA439E8.4020601@msu.edu> References: <3FA439E8.4020601@msu.edu> Message-ID: Harold L Hunt II wrote: > Another thing to keep in mind is how we want to do development. It has > been suggested that we keep the HEAD branch in sync with XFree86.org and > that we do our development on another branch. The question here is > whether cvsup can preserve a local branch of the code and still be used > to sync with XFree86.org. I doubt that this is the case, since cvsup is > essentially mirroring the files, not branches/tags/etc. Does this mean > that we must manually track XFree86.org and apply their patches after > the initial import? My suggestion is to import the current "stable" release into our CVS. With CVS we can later import the next release and merge all patches we have already commited. Fixing severe bugs is still an issue and might be solved by regulary importing the snapshots of the "stable" branch and by monitoring the XFree-commit list (I still read every posting on this list and would just pay more attention to security fixes) I doubt that a complete mirror of the XFree86 CVS is a good solution since there is no way (at least I konw of none) to automaticly track changes in the XFree86 repository and commit them to ours too. So importing the whole repository is in my opinion a waste of space since we'd have to import all old revisions from the XFree repository too. bye ago -- Alexander.Gottwald@informatik.tu-chemnitz.de http://www.gotti.org ICQ: 126018723 From huntharo@msu.edu Mon Nov 3 00:01:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Mon, 03 Nov 2003 00:01:00 -0000 Subject: [Fwd: Re: Grabbing XFree86.org's xc/ tree using cvsup] Message-ID: <3FA59ACF.60407@msu.edu> This is from Mike Harris. He sent it to this list but he isn't on the list, so it looks like it got rejected. Harold -------- Original Message -------- Subject: Re: Grabbing XFree86.org's xc/ tree using cvsup Date: Sun, 2 Nov 2003 16:46:34 -0500 (EST) From: Mike A. Harris To: Harold L Hunt II CC: cygwin-xfree@cygwin.com, xserver@pdx.freedesktop.org References: <3FA439E8.4020601@msu.edu> On Sat, 1 Nov 2003, Harold L Hunt II wrote: >I am looking into how to import the XFree86.org xc/ tree into >freedesktop.org. It looks like cvsup is the way to go here, since it >mirrors the actual repository instead of grabbing a snapshot of the >repository. This can be used to mirror the repository for read-only access to an alternative to the master, and works great. I use cvsup to mirror the repo locally also. >My question is: should I tell cvsup to drop the tree directly into >/home/cvs, or should I pull the tree into my home directory, then copy >it into /home/cvs? I mirror it to /srv/cvs/cvsup myself, but have made thosed dirs group cvs, and have myself as a member of the group. Again this is locally on my workstation. >It sort of seems unwise to drop the tree directly into /home/cvs, >especially since cvsup needs to keep some state files (which I would >most likely put in /home/harold/xc/sup) that imply that only one person >would be able to make changes to the cvsup mirror. > >Another thing to keep in mind is how we want to do development. It has >been suggested that we keep the HEAD branch in sync with XFree86.org and >that we do our development on another branch. The question here is >whether cvsup can preserve a local branch of the code and still be used >to sync with XFree86.org. I doubt that this is the case, since cvsup is >essentially mirroring the files, not branches/tags/etc. Does this mean >that we must manually track XFree86.org and apply their patches after >the initial import? This is not possible. The cvsup mirrored repository is read-write, however as soon as the next cvsup cronjob runs, it syncronizes your cvsup repository with the master, which includes destroying all of your modifications. >I would appreciate any input on this. Let me be the first to >admit that I am not a CVS administrator. I want to get this >tree setup quickly so that Alexander Gottwald (ago), Kensuke >Matsuzaki (zakki), and myself can quickly resume our development >on Cygwin/X. Another goal is for the xc/ tree to be usable by >others that wish to develop on an old-style xc/ tree outside of >XFree86.org. My recommendation is for freedesktop.org to set up a single cvsup mirrored XFree86 repository which is globally available to all projects hosted on fd.o. Anyone can set it up, and it should be ran by the system cron at least once a day IMHO, so not in a user account. That way it's ultrafast to generate diffs, rdiffs, do checkouts of XFree86 trees, and any other work with their repository, with no network latency on the local box. That's how I use it locally at home here and it is a godsend. For importing the xc repository however, I recommend taking the CVSUP mirrored repository, and copying the entire subdirectory heirarchy of the repo to the real CVS repository location, then running a perl script to change all of the CVS roots throughout the tree if necessary. This repository should then not ever have cvsup executed on it again or all changes will be blown away. Developers working on this tree (or multiple trees started like this) are free to make branches, etc. In order to keep the tree in sync with XFree86 CVS, someone would need to either manually check in XFree86 changes, or set up automated checkins.. The problem with automated checkins however is that occasionally they _will_ fail. Network dropout, disk full, overlapping cvs commits that need manual handwork, and other scenarios. It'll be very little work to copy the repo and start using it for development, but a lot of work to maintain the entire tree and keep it current with XFree86.org changes. Hope this helps. -- Mike A. Harris _______________________________________________ Xserver mailing list Xserver@pdx.freedesktop.org http://pdx.freedesktop.org/cgi-bin/mailman/listinfo/xserver From huntharo@msu.edu Mon Nov 3 00:04:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Mon, 03 Nov 2003 00:04:00 -0000 Subject: Grabbing XFree86.org's xc/ tree using cvsup In-Reply-To: References: <3FA439E8.4020601@msu.edu> Message-ID: <3FA59B76.8010800@msu.edu> Alexander, Alexander Gottwald wrote: > Harold L Hunt II wrote: > > >>Another thing to keep in mind is how we want to do development. It has >>been suggested that we keep the HEAD branch in sync with XFree86.org and >>that we do our development on another branch. The question here is >>whether cvsup can preserve a local branch of the code and still be used >>to sync with XFree86.org. I doubt that this is the case, since cvsup is >>essentially mirroring the files, not branches/tags/etc. Does this mean >>that we must manually track XFree86.org and apply their patches after >>the initial import? > > > My suggestion is to import the current "stable" release into our CVS. With > CVS we can later import the next release and merge all patches we have > already commited. Fixing severe bugs is still an issue and might be solved > by regulary importing the snapshots of the "stable" branch and by monitoring > the XFree-commit list (I still read every posting on this list and would > just pay more attention to security fixes) Mike Harris had a good point that we should grab XFree86's CVS tree with cvsup and use a perl script to change the root for all of the files. Then we have both the current version of all files *and* the history of all of those files. He suggested using cvsps to generate patch sets. He also suggested doing our development on a branch, keeping HEAD more or less in sync with XFree86.org CVS HEAD, and merge HEAD to our branch whenever required (to get bug fixes, etc.). > I doubt that a complete mirror of the XFree86 CVS is a good solution since > there is no way (at least I konw of none) to automaticly track changes in > the XFree86 repository and commit them to ours too. So importing the whole > repository is in my opinion a waste of space since we'd have to import all > old revisions from the XFree repository too. I think Mike had a good point that it would be wise to have the history of each file in the tree... what do you think? Harold From cnst@rbcmail.ru Mon Nov 3 05:26:00 2003 From: cnst@rbcmail.ru (Constantine) Date: Mon, 03 Nov 2003 05:26:00 -0000 Subject: xinit: The application has failed to start because cygfreetype-6.dll Message-ID: <3FA5E6EF.3030607@rbcmail.ru> Harold wrote: >Constantine wrote: > >> Hello, >> >> After I have updated my installation today, and when I am running xinit >> now, I get a Windows window with the message that "cygfreetype-6.dll was >> not found". >> >> After I did the following, everything worked again: >> >> cd /usr/X11R6/bin/ >> cp cygfreetype-9.dll cygfreetype-6.dll > >Constantine, > >Hmm... I would appreciate it if you could help me to figure out what the >real problem is here. The new XFree86-bin-4.3.0-7 package no longer >contains cygfreetype-9.dll, as this library is now distributed as part >of the freetype2/libfreetype26 package. freetype2 defines the version >of the freetype2 library as '6' instead of the '9' that XFree86 was >using as the library version. I added a copy of cygfreetype-9.dll to >the XFree86-lib-compat package for those that need the old library. > >However, I want to know what application was failing in your xinit >scripts. There should not be an application that requires >cygfreetype-9.dll in the default script. Have you modified your script? > What program are you launching that requires this DLL? Are you >launching emacs? > >I would like to get any old applications that use cygfreetype-9.dll rebuilt. > > No, everything should be by default, except for my ~/.xinit file. I just erased that file, ran the installer again (it downloaded only 'libfontconfig1-2.2.0-1.tar.bz2' and 'libfreetype26-2.1.5-1.tar.bz2'), and it seems to work fine. It is very strange, since the setup.ini files from yesterday and today seem to be the same, and I did not selected nor deselected any option neither today nor yesterday. Well, I guess it is the people who make the setup.exe to blame. Cheers, Constantine. (I am not on the list, so please "reply all". ) From murakami@ipl.t.u-tokyo.ac.jp Mon Nov 3 05:41:00 2003 From: murakami@ipl.t.u-tokyo.ac.jp (Takuma Murakami) Date: Mon, 03 Nov 2003 05:41:00 -0000 Subject: xmodmap has no effect on mouse buttons In-Reply-To: <3FA580D0.3050401@msu.edu> References: <20031102221251.1304.MURAKAMI@ipl.t.u-tokyo.ac.jp> <3FA580D0.3050401@msu.edu> Message-ID: <20031103140601.840B.MURAKAMI@ipl.t.u-tokyo.ac.jp> Harold, > I think you have a good point there. I thought I tried to disable the > definition of XFree86Server when building XWin.exe... maybe I didn't try > hard enough, or maybe that never made it into XFree86's CVS. Hmm... or > maybe I actually had to enable XFree86Server... I just don't remember. The ChangeLog for Release 62 http://xfree86.cygwin.com/devel/server/changelog-050.html and the comment in the line 215 in xc/config/cf/cygwin.cf mention XFree86Server symbol. They wanted to remove the symbol but failed, as I read. I removed "-DXFree86Server" from XWinServerDefines in the cygwin.cf and compiled but got many errors. Instead, when I disabled XINPUT extension I could compile XWin.exe which fixes the mouse button problem. To do so I just change the definition of BuildXInputExt in the cygwin.cf from YES to NO. Does it help? > In any case, somebody should do a build that doesn't have XFree86Server > defined and see if it fixes the problem. Removing XFree86Server seems quite hard for me. Takuma Murakami (murakami@ipl.t.u-tokyo.ac.jp) From davidf@sjsoft.com Mon Nov 3 07:41:00 2003 From: davidf@sjsoft.com (David Fraser) Date: Mon, 03 Nov 2003 07:41:00 -0000 Subject: Grabbing XFree86.org's xc/ tree using cvsup In-Reply-To: <3FA59B76.8010800@msu.edu> References: <3FA439E8.4020601@msu.edu> <3FA59B76.8010800@msu.edu> Message-ID: <3FA60698.3080801@sjsoft.com> Harold L Hunt II wrote: > Alexander, > > Alexander Gottwald wrote: > >> Harold L Hunt II wrote: >> >> >>> Another thing to keep in mind is how we want to do development. It has >>> been suggested that we keep the HEAD branch in sync with XFree86.org >>> and >>> that we do our development on another branch. The question here is >>> whether cvsup can preserve a local branch of the code and still be used >>> to sync with XFree86.org. I doubt that this is the case, since cvsup is >>> essentially mirroring the files, not branches/tags/etc. Does this mean >>> that we must manually track XFree86.org and apply their patches after >>> the initial import? >> >> >> >> My suggestion is to import the current "stable" release into our CVS. >> With >> CVS we can later import the next release and merge all patches we have >> already commited. Fixing severe bugs is still an issue and might be >> solved >> by regulary importing the snapshots of the "stable" branch and by >> monitoring >> the XFree-commit list (I still read every posting on this list and would >> just pay more attention to security fixes) > > > Mike Harris had a good point that we should grab XFree86's CVS tree > with cvsup and use a perl script to change the root for all of the > files. Then we have both the current version of all files *and* the > history of all of those files. Note that this requires cvsupd to run on the server side ... do XFree86 already run cvsupd? If not, you may find it easier to ask them for a tarball of the CVSROOT to get going, and then something like cvsps (suggested by Mike below) to keep up to date. > He suggested using cvsps to generate patch sets. He also suggested > doing our development on a branch, keeping HEAD more or less in sync > with XFree86.org CVS HEAD, and merge HEAD to our branch whenever > required (to get bug fixes, etc.). > >> I doubt that a complete mirror of the XFree86 CVS is a good solution >> since >> there is no way (at least I konw of none) to automaticly track >> changes in >> the XFree86 repository and commit them to ours too. So importing the >> whole >> repository is in my opinion a waste of space since we'd have to >> import all >> old revisions from the XFree repository too. > > I think Mike had a good point that it would be wise to have the > history of each file in the tree... what do you think? I think this would be great ; it also allows the possibility of producing security-patched versions of older versions of XFree86, and the version history also provides a kind of documentation of the source David From murakami@ipl.t.u-tokyo.ac.jp Mon Nov 3 08:25:00 2003 From: murakami@ipl.t.u-tokyo.ac.jp (Takuma Murakami) Date: Mon, 03 Nov 2003 08:25:00 -0000 Subject: Patch for keyboard handling Message-ID: <20031103163010.840F.MURAKAMI@ipl.t.u-tokyo.ac.jp> I have made a patch to improve keyboard handling. Any comments would be appreciated. The changes are: 1) win.h, winkeybd.c, winwndproc.c - Improve the synchronization of mode key states between XWin and Windows. 2) winmultiwindowwndproc.c - Enable mode key synchronization in -multiwindow mode. 3) winwndproc.c - Make clean termination on logoff or shutdown. 4) winconfig.c - Fix the lacks of KEYUP messages in Japanese environments. The solution was proposed by Kensuke Matsuzaki. 5) winwndproc.c - Ignore Windows keyboard auto-repeats so that XWin controls auto-repeats instead of Windows. Takuma Murakami (murakami@ipl.t.u-tokyo.ac.jp) -------------- next part -------------- A non-text attachment was scrubbed... Name: xwin.kbd.patch Type: application/octet-stream Size: 10352 bytes Desc: not available URL: From davidf@sjsoft.com Mon Nov 3 08:39:00 2003 From: davidf@sjsoft.com (David Fraser) Date: Mon, 03 Nov 2003 08:39:00 -0000 Subject: Grabbing XFree86.org's xc/ tree using cvsup In-Reply-To: References: <3FA439E8.4020601@msu.edu> <3FA59B76.8010800@msu.edu> <3FA60698.3080801@sjsoft.com> Message-ID: <3FA61431.2030106@sjsoft.com> Mike A. Harris wrote: >On Mon, 3 Nov 2003, David Fraser wrote: > > > >>>>My suggestion is to import the current "stable" release into our CVS. >>>>With >>>>CVS we can later import the next release and merge all patches we have >>>>already commited. Fixing severe bugs is still an issue and might be >>>>solved >>>>by regulary importing the snapshots of the "stable" branch and by >>>>monitoring >>>>the XFree-commit list (I still read every posting on this list and would >>>>just pay more attention to security fixes) >>>> >>>> >>>Mike Harris had a good point that we should grab XFree86's CVS tree >>>with cvsup and use a perl script to change the root for all of the >>>files. Then we have both the current version of all files *and* the >>>history of all of those files. >>> >>> >>Note that this requires cvsupd to run on the server side ... do XFree86 >>already run cvsupd? >> >> > >Yes. XFree86.org has offered a cvsup access method for many >years. I've been using cvsup to mirror the XFree86 repository >for about 2.5 years now. It works great. The initial mirroring >usually takes about 1.5 hours on my 300/125 (up/down) connection, >and after that, daily updates via cron at 5am take about 2 >minutes on average. > > > >>If not, you may find it easier to ask them for a tarball of the >>CVSROOT to get going, and then something like cvsps (suggested >>by Mike below) to keep up to date. >> >> > >I can make a tarball of the repository and upload it to >freedesktop.org if someone would prefer. Really though it'd be >nice for us to just have a cvsps mirror on fd.o sync'd nightly >for everyone to use. That could be tarballed easily after >mirroring is complete and copied into a new home for further >development. > > > > >>>He suggested using cvsps to generate patch sets. He also suggested >>>doing our development on a branch, keeping HEAD more or less in sync >>>with XFree86.org CVS HEAD, and merge HEAD to our branch whenever >>>required (to get bug fixes, etc.). >>> >>> >>> >>>>I doubt that a complete mirror of the XFree86 CVS is a good solution >>>>since >>>>there is no way (at least I konw of none) to automaticly track >>>>changes in >>>>the XFree86 repository and commit them to ours too. So importing the >>>>whole >>>>repository is in my opinion a waste of space since we'd have to >>>>import all >>>>old revisions from the XFree repository too. >>>> >>>> >>>I think Mike had a good point that it would be wise to have the >>>history of each file in the tree... what do you think? >>> >>> >>I think this would be great ; it also allows the possibility of >>producing security-patched versions of older versions of XFree86, and >>the version history also provides a kind of documentation of the source >> >> > >Yep. It also allows people to branch XFree86 releases anywhere >in the past also, so one could theoretically maintain >4.1.0/4.2.1/4.3.0 beyond the timeframe XFree86.org would be >willing to do so. I've thought of doing that before, but I >figured unless I was going to spend time doing enough work on the >tree and backporting some things that it wouldn't be worth the >effort. As time goes on and I have to support 4.1.0 for a >billion years due to long term support of our OS products, I >might change my mind and use CVS. ;o) > > > > Mike, Thanks for the reply. That clarifies everything. David (CCing this to the cygwin-xfree mailing list so everyone else can see the message too...) From patrick.hayes@amecspie.com Mon Nov 3 09:32:00 2003 From: patrick.hayes@amecspie.com (Hayes Patrick) Date: Mon, 03 Nov 2003 09:32:00 -0000 Subject: Cygwin/Xfree & fontpath problems (was Re: XWin --query) Message-ID: <86B943A020C6D5119390000102E88210142A33@mail-srv.elona> >Subject: Re: XWin --query >From: Harold L Hunt II msu.edu> >Date: Mon, 13 Oct 2003 13:34:50 -0400 >Newsgroups: gmane.os.cygwin.xfree >Reply-to: cygwin-xfree cygwin.com >Pavel Rosenboim wrote: >> Greg Freemyer wrote: >>>I have not installed any new hardware, and both server and client >>>machines have only one NIC. (Both are standard wired NICs.) >>> >>>I did update the Linux box with the latest patches recently, >>>that may be causing the problem, but somehow I think it is the >>>cygwin/xfree86 end. >> >>Is it possible that kdm configuration got overwritten, and now it >>does not allow connections from remote hosts? > >I was thinking the same thing. > >Greg --- Please check the following FAQ entry for information on how >to make sure that kdm/gdm/xdm are allowing remote logins: > >http://xfree86.cygwin.com/docs/faq/cygwin-xfree-faq.html#q-mandrake-8.1-xdm cp Hi everyone, I'd like to update/correct David's explanation in the FAQ: > [David Dawson] For whatever reason, certain versions of Solaris > need fonts that are not provided by Cygwin/XFree86; the result > is that you may see the Solaris background tile and the hourglass > cursor, but the XDM login prompt will never appear. The problem is not with the fonts it is that Cygwin/Xfree currently dumps core when both local fonts and a font server are used. I stumbled over a similar bug that Pavel had. I was trying to setup cygwin/Xfree to connect to my solaris 8 server. I was able to narrow the bug down to a problem that Xfree has with using both local fonts & a font server. Xfree works fine using either local fonts or a font server, but blows chunks when using both. If only local fonts are used, Xfree will core dump when "xset fp+" is used to add or reset a font server to the fontpath. Adding local font directories to the fontpath works OK. If the fontpath contains only font servers adding other font servers works but adding any local fonts will cause a core dump. The specific problem with Solaris is that the dtlogin script Xsetup runs "xset fp+ tcp/sunserver:7100" for all remote clients by default in /usr/dt/config/Xsetup. I assume a that a similar problem is present in Linux but do not have a box handy to check. Running "XWin -fp tcp/sunserver:7100" avoids the problem because this explicitly sets the fontpath so that no local fonts are used but Xsetup adds the font server a second time anyway. My workaround was to comment out the xset fp+ line & use only the local fonts, but the best thing to do would be to track down the reason Xfree is dumping core & fix it. Until this is done, it might be a good idea to update the FAQ. Cheers, Pat Chef de Projet: Administration de Syst?mes d'Information AMEC SPIE Communications - ELONA 102, rue Etienne Dolet 92245 Malakoff Cedex Tel: +33 (0) 1 46 73 80 20 Gsm: +33 (0) 6 74 09 26 27 Fax: +33 (0) 1 46 73 90 09 Email: Patrick.Hayes amec_cut_this_out_to_reply_spie.com Web: www.amecspie.com From jordi.vila@gtd.es Mon Nov 3 10:17:00 2003 From: jordi.vila@gtd.es (Jordi Vila) Date: Mon, 03 Nov 2003 10:17:00 -0000 Subject: New package: xwinclip-1.2.0-1 - 1 attachment References: <3FA0B3EE.7010500@msu.edu> <3FA29F74.20900@msu.edu> Message-ID: Harold L Hunt II wrote in news:3FA29F74.20900@msu.edu: > Jordi, > >> start XWin -multiwindow -clipboard >> >> It works flawlessly, but without clipboard integration between >> windows-2000 and XWindows. > > Really? Check /tmp/XWin.log, or bzip2 it and send it in. > Here you are the file. It failed to work. I'lltry to connect today and see if the new package is on my usual mirror (ftp.rediris.es) begin 644 XWin.log.bz2 M0EIH.3%!629368SN1V4``NU?@'`04&?_TS_O_^"__]_P4`75>[.R2>4>FHVIZAZ0&@'J&E9`=:^;I3M/N:&87H>")%/O%CWLZ=L!EG/E2)O? MJ>C;D+\\='$^MB-"=-:^/C1//8Z56J&G`PM\7K\^+6P;%K#,4&55D8RCJ M'&,@UFD)5R<7F53@RO,,X5V8XH\A&TE)VN'.LJ>L^8S.SD4D3AD#ZQAAC!LX M1Q=HR][P1=LN%R,J^6,%A8%MHT&F[1I3-+S1[+6.S%6@,/FB4UPQ(]#1E<=# MQK=&.NX48$8M72NF&,Q)J5@MJJ=J1MR6+*@K.O'LAFJO56"9V&9D9%@1L0,R M`0-A)J)HVY9/HQYXU0DZU0KK:QI46TFJ]_[;=VNR\J0NQ#D-GN: M%MM>($E'ZT9O7Z*=,PYA3:-*[DPJADF@PTLH2;)DR$P[U,4TCB-(XD%#3.$> MP1YLO528*?CU]2U+Z["YGF7*YI340T:Q''AWSO6ZDN"8"5Q,+`;_F'VN@=/I M[=8IA@#HCR@(>!Y&9'BBF8+UOE:ZBZ(YL%@!=2L(15S=R@I^!'DX MD[M47(>2"]$*R<%+%(V+\+=MKQ;;8V]]0UV`7]?8M+^X*G^$JXKMMEO\M)W( MP_<@M&T5@X`VAVOA8:(-H-%`DCG9"'YGZK0M>@V)@F'FK2^P^19J@DKLZ3C/ MTU'@KU4?<#ROP*9ZB(*JN'\S<[XTEG05.$R9?Z6T&(7KM)0;>MT63)/,F1(> MRW,,]TW,3O1LB\K'7U(0K.Q"3)8PGFDYL M.EG&P3P@M4P]X;0Q-*WC:J!TF5Q%Z'!MD@#6U+WUZ._#!4#Y@60UL189D/,M M(9$BY;R1JBE"1>>RR_W4`8%58#$57@$K%AL'"S63;8]YH3OJD$/FU\XU?.,: MW@HT'),[CX4CN5J\#FZ2PUK MJ86&P.!0@"=EJ)\129L=P&_%K\FAC:2>"#=V()&"8E;7@H)DXAMIGC3J,D+O M/02I8TH)%$^C1J0M<<\^2M)1?=*%-$@BA8ADI@4U9-&Y,Y=02Q4Q#WL)0H8W MSQ&^KA;FFF,&K=R5>#2;?=`]Q!B$1(6'GN$01D3B%"@H@LC`,2.*'$Y3G)SL MBPU07V4ZBAH5@*#`*DT0.4*L+C@(M%?-R:/<4P!;KND@UIB6*2FL)7AC.5;" MT'(KIG@"(3#@J/,.%8:XK(DFZO9I#<%>5AD3-X(Y$?$.E5.X%IVGRK3?0W#R G;@A`FP9]0DVDFTAL1$-3?P`JL4%!7A<.0@O6D?XNY(IPH2$9W([* ` end From murakami@ipl.t.u-tokyo.ac.jp Mon Nov 3 11:11:00 2003 From: murakami@ipl.t.u-tokyo.ac.jp (Takuma Murakami) Date: Mon, 03 Nov 2003 11:11:00 -0000 Subject: Patch for remappable mouse buttons In-Reply-To: <20031103140601.840B.MURAKAMI@ipl.t.u-tokyo.ac.jp> References: <3FA580D0.3050401@msu.edu> <20031103140601.840B.MURAKAMI@ipl.t.u-tokyo.ac.jp> Message-ID: <20031103192039.8413.MURAKAMI@ipl.t.u-tokyo.ac.jp> For the case that neither XFree86Server nor XINPUT is removable, this patch is for winmouse.c to take account of the internal mouse button mapping in the X server. Takuma Murakami (murakami@ipl.t.u-tokyo.ac.jp) -------------- next part -------------- A non-text attachment was scrubbed... Name: xwin.mouse.patch Type: application/octet-stream Size: 3289 bytes Desc: not available URL: From Dr.Volker.Zell@oracle.com Mon Nov 3 11:58:00 2003 From: Dr.Volker.Zell@oracle.com (Dr. Volker Zell) Date: Mon, 03 Nov 2003 11:58:00 -0000 Subject: New package: xwinclip-1.2.0-1 In-Reply-To: <3FA0B3EE.7010500@msu.edu> (Harold L. Hunt, II's message of "Thu, 30 Oct 2003 01:47:10 -0500") References: <3FA0B3EE.7010500@msu.edu> Message-ID: <878ymxacks.fsf@vzell-de.de.oracle.com> >>>>> "Harold" == Harold L Hunt, writes: Harold> The xwinclip-1.2.0-1 package has been updated in the Cygwin distribution. The package installs its documentation under /usr/X11R6/share/doc indstead of /usr/X11R6/doc. Ciao Volker From danilo.turina@alcatel.it Mon Nov 3 14:25:00 2003 From: danilo.turina@alcatel.it (Danilo Turina) Date: Mon, 03 Nov 2003 14:25:00 -0000 Subject: Keyboard focus problem + scrambled icons in wmaker with latest release Message-ID: Hello, I'm running the latest version of Cygwin, XFree and WindowMaker (from mirrors.rcn.net, but I also tried mirrors.sunsite.dk and mirrors.kernel.org) in my WinXP Pro workstation and I have the following problems: 1) when I move my mouse outside a xterm windows the keyboard focus is lost by that window and is re-taken when I get back to that window with the mouse pointer. It only happens with Cygwin-XFree's xterm, while if I launch, for example, HP-UX's xterm from a HP workstation or Cygwin's rxvt or Nedit it doesn't happen. This started to happen 1/2 weeks ago (consider that I constantly monitor the announce mailing lists of Cygwin and, hence, I make setup.exe run once every one/two days). I saw, from the list, that other people have this problem too. 2) this morning I ran setup and I downloaded the latest modifications to Xwinclip, XFree86-bin, etc. From that point on, some of the icons of wmaker are "scrambled", in particular the icons that represents terminals and the icons of the "Window Maker Preferences Utility", launching wmaker by hand (i.e. not as I usually do with a script that launces XWin and then wmaker) I get this errors on stderr: TIFFReadDirectory: Warning, /usr/X11R6/share/WINGs/Images.tiff: unknown field with tag 317 (0x13d) encountered. TIFFReadDirectory: Warning, /usr/X11R6/share/WindowMaker/Icons/Terminal.tiff: unknown field with tag 317 (0x13d) encountered. TIFFReadDirectory: Warning, /usr/X11R6/share/WindowMaker/Icons/Terminal.tiff: unknown field with tag 317 (0x13d) encountered. I don't know if this is a useful information, but I run XFree in rootless mode. I also tried to uninstall wmaker, to remove from my user's home the configuration files of wmaker (I renamed the ~/GNUstep dir) and to re-install wmaker but things haven't changed. Bye, Danilo Turina From huntharo@msu.edu Mon Nov 3 14:30:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Mon, 03 Nov 2003 14:30:00 -0000 Subject: Patch for keyboard handling In-Reply-To: <20031103163010.840F.MURAKAMI@ipl.t.u-tokyo.ac.jp> References: <20031103163010.840F.MURAKAMI@ipl.t.u-tokyo.ac.jp> Message-ID: <3FA66674.6080900@msu.edu> Takuma Murakami wrote: > I have made a patch to improve keyboard handling. > Any comments would be appreciated. > > The changes are: > > 1) win.h, winkeybd.c, winwndproc.c - Improve the > synchronization of mode key states between XWin > and Windows. + /* Stored to get internal mode key states. Must be read-only. */ + static unsigned short *g_winInternalModeKeyStatesPtr = NULL; Shouldn't this be a pointer to constant data? Isn't that: static unsigned short const * g_winInternalModeKeyStatesPtr = NULL; ??? > 2) winmultiwindowwndproc.c - Enable mode key > synchronization in -multiwindow mode. + g_winInternalModeKeyStatesPtr = &(pDeviceInt->key->state); Wow! That is a really good idea. I should have been doing that all along, but I didn't realize that I could access the internal mode-key states. Great idea. > 3) winwndproc.c - Make clean termination on > logoff or shutdown. Good catch for WM_ENDSESSION. That should have been there all along... > 4) winconfig.c - Fix the lacks of KEYUP messages in > Japanese environments. The solution was proposed > by Kensuke Matsuzaki. Looks good to me. It all depends on if it works for you guys. > 5) winwndproc.c - Ignore Windows keyboard auto-repeats > so that XWin controls auto-repeats instead of Windows. Okay. I will try to apply this patch tomorrow. Thanks for contributing, Harold From murakami@ipl.t.u-tokyo.ac.jp Mon Nov 3 15:05:00 2003 From: murakami@ipl.t.u-tokyo.ac.jp (Takuma Murakami) Date: Mon, 03 Nov 2003 15:05:00 -0000 Subject: Patch for keyboard handling In-Reply-To: <3FA66674.6080900@msu.edu> References: <20031103163010.840F.MURAKAMI@ipl.t.u-tokyo.ac.jp> <3FA66674.6080900@msu.edu> Message-ID: <20031104000343.A81C.MURAKAMI@ipl.t.u-tokyo.ac.jp> > + /* Stored to get internal mode key states. Must be read-only. */ > + static unsigned short *g_winInternalModeKeyStatesPtr = NULL; > > Shouldn't this be a pointer to constant data? Isn't that: > > static unsigned short const * g_winInternalModeKeyStatesPtr = NULL; > > ??? Exactly. That's what I wanted to do. Thank you for pointing out. Takuma Murakami (murakami@ipl.t.u-tokyo.ac.jp) From taz@aztek-eng.com Mon Nov 3 15:44:00 2003 From: taz@aztek-eng.com (Travis Zadikem) Date: Mon, 03 Nov 2003 15:44:00 -0000 Subject: Help with cygwin fvwm2 setup Message-ID: <001a01c3a222$2a7da150$e90200bf@tazpc> I just downloaded the full cygwin installation as of Friday Oct 31. I did the following just after an install and got many errors: Double-clicked on the cygwin.bat which gave me a bash prompt typed: X & which brought up the windows manager typed back in the bash window: export DISPLAY=:0.0 and then the following: fvwm2 -f /usr/X11R6/share/fvwm/system.fvwm2rc-sample-95 and got nothing but a bunch of errors about not being able to find .xpm files. Can someone please tell me where all the .xpm files are and the best way to get fvwm2 fully up and running? Again, this is a full install of cygwin. thanks, taz From ford@vss.fsi.com Mon Nov 3 15:47:00 2003 From: ford@vss.fsi.com (Brian Ford) Date: Mon, 03 Nov 2003 15:47:00 -0000 Subject: Grabbing XFree86.org's xc/ tree using cvsup In-Reply-To: <3FA59B76.8010800@msu.edu> References: <3FA439E8.4020601@msu.edu> <3FA59B76.8010800@msu.edu> Message-ID: On Sun, 2 Nov 2003, Harold L Hunt II wrote: > He suggested using cvsps to generate patch sets. He also suggested > doing our development on a branch, keeping HEAD more or less in sync > with XFree86.org CVS HEAD, and merge HEAD to our branch whenever > required (to get bug fixes, etc.). > Just a note here. This is what CVS's notion of "vendor branches" is for. Although I have limited experience with them, I suggest you read up a little here before making this decision. -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444 From cnst@rbcmail.ru Mon Nov 3 18:21:00 2003 From: cnst@rbcmail.ru (Constantine) Date: Mon, 03 Nov 2003 18:21:00 -0000 Subject: xinit: The application has failed to start because cygfreetype-6.dll In-Reply-To: <3FA5E6EF.3030607@rbcmail.ru> References: <3FA5E6EF.3030607@rbcmail.ru> Message-ID: <3FA69CB4.4000203@rbcmail.ru> On 2003-11-03 00:26, Constantine wrote: > Harold wrote: > >> Constantine wrote: >> >>> Hello, >>> >>> After I have updated my installation today, and when I am running >>> xinit now, I get a Windows window with the message that >>> "cygfreetype-6.dll was not found". >>> >>> After I did the following, everything worked again: >>> >>> cd /usr/X11R6/bin/ >>> cp cygfreetype-9.dll cygfreetype-6.dll >> >> Constantine, >> >> Hmm... I would appreciate it if you could help me to figure out what >> the real problem is here. The new XFree86-bin-4.3.0-7 package no >> longer contains cygfreetype-9.dll, as this library is now distributed >> as part of the freetype2/libfreetype26 package. freetype2 defines >> the version of the freetype2 library as '6' instead of the '9' that >> XFree86 was using as the library version. I added a copy of >> cygfreetype-9.dll to the XFree86-lib-compat package for those that >> need the old library. >> >> However, I want to know what application was failing in your xinit >> scripts. There should not be an application that requires >> cygfreetype-9.dll in the default script. Have you modified your >> script? What program are you launching that requires this DLL? Are >> you launching emacs? >> >> I would like to get any old applications that use cygfreetype-9.dll >> rebuilt. > > No, everything should be by default, except for my ~/.xinit file. > > I just erased that file, ran the installer again (it downloaded only > 'libfontconfig1-2.2.0-1.tar.bz2' and 'libfreetype26-2.1.5-1.tar.bz2'), > and it seems to work fine. > It is very strange, since the setup.ini files from yesterday and today > seem to be the same, and I did not selected nor deselected any option > neither today nor yesterday. Well, I guess it is the people who make > the setup.exe to blame. When I wrote 'that file', I was referring to 'cygfreetype-6.dll', i.e. a copy of 'cygfreetype-9.dll', not to my ~/.xinitrc. In any case, here is my ~/.xinitrc: << xhost + 192.168.0.18 ssh myloginhere@192.168.0.18 "setenv DISPLAY 192.168.0.1:0; startkde" >> Cheers, Constantine. (I am not on the list, so please "reply all". ) From adragh@bcpl.net Tue Nov 4 00:35:00 2003 From: adragh@bcpl.net (adragh) Date: Tue, 04 Nov 2003 00:35:00 -0000 Subject: Regarding Unwanted packages (apache, emacs etc) Message-ID: <3FBD0A86@webmail.bcpl.net> Aha! I see. In my naivete I must have managed to select some packages dependant on those two. I should think that selecting the parent package would select the child package only... But I can see where the reverse might be helpful. Thanks! Patricia Patricia C. Vener Come visit my online galleries! vener-art.com ?Canto que ha sido valiente siempre ser? canci?n nueva? -- V?ctor Jara From huntharo@msu.edu Tue Nov 4 02:39:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Tue, 04 Nov 2003 02:39:00 -0000 Subject: Patch for keyboard handling In-Reply-To: <20031103163010.840F.MURAKAMI@ipl.t.u-tokyo.ac.jp> References: <20031103163010.840F.MURAKAMI@ipl.t.u-tokyo.ac.jp> Message-ID: <3FA71169.7060805@msu.edu> Takuma Murakami wrote: > I have made a patch to improve keyboard handling. > Any comments would be appreciated. > > The changes are: > > 1) win.h, winkeybd.c, winwndproc.c - Improve the > synchronization of mode key states between XWin > and Windows. > > 2) winmultiwindowwndproc.c - Enable mode key > synchronization in -multiwindow mode. Actually, now I am a little doubtful that this patch is complete. If I recall correctly, we are merely enqueueing input events into a queue that the mi layer processes later. Checking the mode key states within the X server will only indicate what the mi layer currently knows about the mode key states. The my layer would not know that there are messages in its queue that change the state of the mode keys. I also recall that there is a way to force the mi layer to process all input events (miProcessInputEvents ?) and that this could be called before querying the state of the mode key states in order to get a consistent result. Please respond to this either with a rebuttal or a different patch. I don't think I can commit the existing patch until then. Harold From murakami@ipl.t.u-tokyo.ac.jp Tue Nov 4 09:04:00 2003 From: murakami@ipl.t.u-tokyo.ac.jp (Takuma Murakami) Date: Tue, 04 Nov 2003 09:04:00 -0000 Subject: Patch for keyboard handling In-Reply-To: <3FA71169.7060805@msu.edu> References: <20031103163010.840F.MURAKAMI@ipl.t.u-tokyo.ac.jp> <3FA71169.7060805@msu.edu> Message-ID: <20031104175955.34AB.MURAKAMI@ipl.t.u-tokyo.ac.jp> Harold, > Actually, now I am a little doubtful that this patch is complete. If I > recall correctly, we are merely enqueueing input events into a queue > that the mi layer processes later. Checking the mode key states within > the X server will only indicate what the mi layer currently knows about > the mode key states. The my layer would not know that there are > messages in its queue that change the state of the mode keys. I agree with you. If the mi event queue has pending events when winRestoreModeKeyStates is called, it may fail to synchronize mode key states between XWin and Windows. However, the new code can re-sync them at the next time winRestoreModeKeyStates is called while it is hard to do for the old code. > I also recall that there is a way to force the mi layer to process all > input events (miProcessInputEvents ?) and that this could be called > before querying the state of the mode key states in order to get a > consistent result. Thank you for your suggestion. mieqProcessInputEvents seems to do the work. I inserted a code to call it and it looks working well for now, though I don't sure if it is legal to call it from the place other than ProcessInputEvents. The attached is a revised patch to call the function. I deeply appreciate your feedback. Takuma Murakami (murakami@ipl.t.u-tokyo.ac.jp) -------------- next part -------------- A non-text attachment was scrubbed... Name: xwin.kbd2.patch Type: application/octet-stream Size: 9965 bytes Desc: not available URL: From eich@suse.de Tue Nov 4 12:41:00 2003 From: eich@suse.de (Egbert Eich) Date: Tue, 04 Nov 2003 12:41:00 -0000 Subject: Grabbing XFree86.org's xc/ tree using cvsup In-Reply-To: huntharo@msu.edu wrote on Saturday, 1 November 2003 at 17:55:36 -0500 References: <3FA439E8.4020601@msu.edu> Message-ID: <16295.29247.132800.561162@xf11.fra.suse.de> Harold, what you want to do is to create a special vendor branch on your repository and import a *tagged* version of XFree86. This tagging makes it really easy to import well defined versions and updates from these. Of course you can mirror the XFree86 CVS on a regular basis. XFree86 is running cvsup so this is really easy. However this repository can only serve as a reference as any commits to it will be overwritten when you do the next cvsup. Actually you may want to start the repository by importing this vendor branch. You should then tag each update of this branch with the same tag that is used by XFree86. This branch together with the tag can be used to keep other branches (including the trunk) in sync with the vendor branch. It should be decided what goes into which branch and the trunk. You also may want to look at the CVS usage instructions the DRI project has. They have rather sophisticated mechanisms to keep the CVS in shape. Egbert. Harold L Hunt II writes: > I am looking into how to import the XFree86.org xc/ tree into > freedesktop.org. It looks like cvsup is the way to go here, since it > mirrors the actual repository instead of grabbing a snapshot of the > repository. > > My question is: should I tell cvsup to drop the tree directly into > /home/cvs, or should I pull the tree into my home directory, then copy > it into /home/cvs? > > It sort of seems unwise to drop the tree directly into /home/cvs, > especially since cvsup needs to keep some state files (which I would > most likely put in /home/harold/xc/sup) that imply that only one person > would be able to make changes to the cvsup mirror. > > Another thing to keep in mind is how we want to do development. It has > been suggested that we keep the HEAD branch in sync with XFree86.org and > that we do our development on another branch. The question here is > whether cvsup can preserve a local branch of the code and still be used > to sync with XFree86.org. I doubt that this is the case, since cvsup is > essentially mirroring the files, not branches/tags/etc. Does this mean > that we must manually track XFree86.org and apply their patches after > the initial import? > > I would appreciate any input on this. Let me be the first to admit that > I am not a CVS administrator. I want to get this tree setup quickly so > that Alexander Gottwald (ago), Kensuke Matsuzaki (zakki), and myself can > quickly resume our development on Cygwin/X. Another goal is for the > xc/ tree to be usable by others that wish to develop on an old-style xc/ > tree outside of XFree86.org. > > Thanks in advance, > > Harold > > > _______________________________________________ > Xserver mailing list > Xserver@pdx.freedesktop.org > http://pdx.freedesktop.org/cgi-bin/mailman/listinfo/xserver From vervoom@hotmail.com Tue Nov 4 12:58:00 2003 From: vervoom@hotmail.com (J S) Date: Tue, 04 Nov 2003 12:58:00 -0000 Subject: screen redraw problem Message-ID: Hi, I have an application which has some boxes in the window. The window itself is scrollable. When I scroll down - no problem, but when I scroll up the boxes turn into long vertical bars. This problem doesn't happen with Exceed, but on XFree86 (both Linux XFree86 and Cygwin-XFree) it does. Can anyone advise me whether this is a bug, or is there some setting I need to add? Let me know if you need anymore information. Thanks for any help. JS. _________________________________________________________________ Tired of 56k? Get a FREE BT Broadband connection http://www.msn.co.uk/specials/btbroadband From Dr.Volker.Zell@oracle.com Tue Nov 4 16:24:00 2003 From: Dr.Volker.Zell@oracle.com (Dr. Volker Zell) Date: Tue, 04 Nov 2003 16:24:00 -0000 Subject: New package: gv-3.5.8-1 Message-ID: <87ad7cqeym.fsf@vzell-de.de.oracle.com> The gv-3.5.8-1 package has been added to the Cygwin distribution. o http://wwwthep.physik.uni-mainz.de/~plass/gv/ Description: `gv' is a comfortable viewer of PostScript and PDF files for the X Window System. It uses the `ghostscript' PostScript(tm) interpreter and is based on the classic X front-end for `gs', `ghostview'. It is more comfortable and more powerful than `ghostview'. -- Volker Zell To update your installation, click on the "Install Cygwin now" link on the http://cygwin.com/ web page. This downloads setup.exe to your system. Once you've downloaded setup.exe, run it and select "XFree86" and then click on the appropriate field until the above announced version number appears if it is not displayed already. Note that downloads from sources.redhat.com (aka cygwin.com) aren't allowed due to bandwidth limitations. This means that you will need to find a mirror which has this update. In the US, ftp://archive.progeny.com/cygwin/ is a reliable high bandwidth connection. In Japan, ftp://ftp.u-aizu.ac.jp/pub/gnu/gnu-win32/ is usually up-to-date. In DK, http://mirrors.sunsite.dk/cygwin/ is usually up-to-date. If one of the above doesn't have the latest version of this package you can either wait for the site to be updated or find another mirror. Please send questions or comments to the Cygwin/XFree86 mailing list at: cygwin-xfree@sources.redhat.com . If you want to subscribe go to: http://cygwin.com/lists.html I would appreciate if you would use this mailing list rather than emailing me directly. This includes ideas and comments about the setup utility or Cygwin/XFree86 in general. If you want to make a point or ask a question the Cygwin/XFree86 mailing list is the appropriate place. From alanh@fairlite.demon.co.uk Tue Nov 4 16:29:00 2003 From: alanh@fairlite.demon.co.uk (Alan Hourihane) Date: Tue, 04 Nov 2003 16:29:00 -0000 Subject: New package: gv-3.5.8-1 In-Reply-To: <87ad7cqeym.fsf@vzell-de.de.oracle.com> References: <87ad7cqeym.fsf@vzell-de.de.oracle.com> Message-ID: <20031104162918.GD1922@fairlite.demon.co.uk> Can these announce messages, be left to the cygwin-announce-xfree... lists. That's what they are there for, and refrain from cross posting this stuff. Alan. On Tue, Nov 04, 2003 at 05:24:33PM +0100, Dr. Volker Zell wrote: > The gv-3.5.8-1 package has been added to the Cygwin distribution. > > o http://wwwthep.physik.uni-mainz.de/~plass/gv/ > > Description: > > `gv' is a comfortable viewer of PostScript and PDF files for the X Window System. > It uses the `ghostscript' PostScript(tm) interpreter and is based on the classic X front-end > for `gs', `ghostview'. It is more comfortable and more powerful than `ghostview'. > > -- > > Volker Zell > > To update your installation, click on the "Install Cygwin now" link on > the http://cygwin.com/ web page. This downloads setup.exe to your > system. Once you've downloaded setup.exe, run it and select "XFree86" > and then click on the appropriate field until the above announced > version number appears if it is not displayed already. > > Note that downloads from sources.redhat.com (aka cygwin.com) aren't > allowed due to bandwidth limitations. This means that you will need > to find a mirror which has this update. > > In the US, ftp://archive.progeny.com/cygwin/ > is a reliable high bandwidth connection. > > In Japan, ftp://ftp.u-aizu.ac.jp/pub/gnu/gnu-win32/ is usually > up-to-date. > > In DK, http://mirrors.sunsite.dk/cygwin/ is usually up-to-date. > > If one of the above doesn't have the latest version of this package > you can either wait for the site to be updated or find another > mirror. > > Please send questions or comments to the Cygwin/XFree86 mailing list at: > cygwin-xfree@sources.redhat.com . If you want to subscribe go to: > http://cygwin.com/lists.html I would appreciate if you would use > this mailing list rather than emailing me directly. This includes > ideas and comments about the setup utility or Cygwin/XFree86 in general. > > If you want to make a point or ask a question the Cygwin/XFree86 mailing > list is the appropriate place. From olsptcwbwd@singmail.com Tue Nov 4 16:42:00 2003 From: olsptcwbwd@singmail.com (Madeline Poe) Date: Tue, 04 Nov 2003 16:42:00 -0000 Subject: Cygwin-patches Good news regarding the economy minmq Message-ID: Cygwin-patches Don't let time run out http://www.eloanquote.net/freequote.aspx?siteid=netmarketing-110 Cease: http://freeloanquote.net/opt-out/ vunnq nghvdokzzcpsgmbhlp i qegmwc k tit hvxroiwomme hjgmfwj jnlvy From huntharo@msu.edu Tue Nov 4 18:35:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Tue, 04 Nov 2003 18:35:00 -0000 Subject: New package: gv-3.5.8-1 In-Reply-To: <20031104162918.GD1922@fairlite.demon.co.uk> References: <87ad7cqeym.fsf@vzell-de.de.oracle.com> <20031104162918.GD1922@fairlite.demon.co.uk> Message-ID: <3FA7F151.5040502@msu.edu> Hmm... Well, we never really defined what the policy was regarding announcements. I have been cross-posting them for years now :) I'm the one that told Volker to do the cross-post, it is my fault. He was just doing what I asked him to do. I also was not able to get the list of subscribers for both lists until recently. One list has about 340 people while the other has about 370. It seems that there is a lot of overlap, so it would probably be okay to stop posting announcements at cygwin-xfree@cygwin.com. Heck, I didn't even realize that so many people were signed up for cygwin-xfree-announce. I thought it was being ignored. Guess I should have checked those lists earlier. I guess that is it then. The policy is changed. I won't cross-post announcements anymore. Thanks for making me think this through :) Harold Alan Hourihane wrote: > Can these announce messages, be left to the cygwin-announce-xfree... lists. > > That's what they are there for, and refrain from cross posting this stuff. > > Alan. > > On Tue, Nov 04, 2003 at 05:24:33PM +0100, Dr. Volker Zell wrote: > >>The gv-3.5.8-1 package has been added to the Cygwin distribution. >> >> o http://wwwthep.physik.uni-mainz.de/~plass/gv/ >> >>Description: >> >>`gv' is a comfortable viewer of PostScript and PDF files for the X Window System. >>It uses the `ghostscript' PostScript(tm) interpreter and is based on the classic X front-end >>for `gs', `ghostview'. It is more comfortable and more powerful than `ghostview'. >> >>-- >> >>Volker Zell >> >>To update your installation, click on the "Install Cygwin now" link on >>the http://cygwin.com/ web page. This downloads setup.exe to your >>system. Once you've downloaded setup.exe, run it and select "XFree86" >>and then click on the appropriate field until the above announced >>version number appears if it is not displayed already. >> >>Note that downloads from sources.redhat.com (aka cygwin.com) aren't >>allowed due to bandwidth limitations. This means that you will need >>to find a mirror which has this update. >> >>In the US, ftp://archive.progeny.com/cygwin/ >>is a reliable high bandwidth connection. >> >>In Japan, ftp://ftp.u-aizu.ac.jp/pub/gnu/gnu-win32/ is usually >>up-to-date. >> >>In DK, http://mirrors.sunsite.dk/cygwin/ is usually up-to-date. >> >>If one of the above doesn't have the latest version of this package >>you can either wait for the site to be updated or find another >>mirror. >> >>Please send questions or comments to the Cygwin/XFree86 mailing list at: >>cygwin-xfree@sources.redhat.com . If you want to subscribe go to: >>http://cygwin.com/lists.html I would appreciate if you would use >>this mailing list rather than emailing me directly. This includes >>ideas and comments about the setup utility or Cygwin/XFree86 in general. >> >>If you want to make a point or ask a question the Cygwin/XFree86 mailing >>list is the appropriate place. From querra@gmx.de Tue Nov 4 18:44:00 2003 From: querra@gmx.de (Andreas (privat)) Date: Tue, 04 Nov 2003 18:44:00 -0000 Subject: obstacle running "cygwin" (communicating with Solaris 8, Sparc) ... Message-ID: <18876.1067971458@www41.gmx.net> Hello, it's my intention to start a remote login-process at the solaris-pc via cygwin. Unfortunately the login-session is always interrupted. Cygwin is only able to depict a black screen (including the mouse cursor). Nothing else occurs ... I figured out the same behaviour while using realvnc. After - let's say - 30 seconds the vncserver terminates itself with the following error message: XDMCP fatal error: login failed .... (something like that). I've already checked the Xaccess-file ... without success. Does anyone know a solution? It should be mentioned that the login-process has already been working since some months. It has to stay relation with more or less conscious modifications to the Solaris-PC. But where should I take a look at? Much thanks in advance! Bye Querra -- NEU F??R ALLE - GMX MediaCenter - f??r Fotos, Musik, Dateien... Fotoalbum, File Sharing, MMS, Multimedia-Gru??, GMX FotoService Jetzt kostenlos anmelden unter http://www.gmx.net +++ GMX - die erste Adresse f??r Mail, Message, More! +++ From cgf-no-personal-reply-please@cygwin.com Tue Nov 4 18:58:00 2003 From: cgf-no-personal-reply-please@cygwin.com (Christopher Faylor) Date: Tue, 04 Nov 2003 18:58:00 -0000 Subject: New package: gv-3.5.8-1 In-Reply-To: <3FA7F151.5040502@msu.edu> References: <87ad7cqeym.fsf@vzell-de.de.oracle.com> <20031104162918.GD1922@fairlite.demon.co.uk> <3FA7F151.5040502@msu.edu> Message-ID: <20031104185802.GA16094@redhat.com> On Tue, Nov 04, 2003 at 01:34:57PM -0500, Harold L Hunt II wrote: >Hmm... > >Well, we never really defined what the policy was regarding >announcements. I have been cross-posting them for years now :) > >I'm the one that told Volker to do the cross-post, it is my fault. He >was just doing what I asked him to do. > >I also was not able to get the list of subscribers for both lists until >recently. One list has about 340 people while the other has about 370. > It seems that there is a lot of overlap, so it would probably be okay >to stop posting announcements at cygwin-xfree@cygwin.com. > >Heck, I didn't even realize that so many people were signed up for >cygwin-xfree-announce. I thought it was being ignored. Guess I should >have checked those lists earlier. > >I guess that is it then. The policy is changed. I won't cross-post >announcements anymore. > >Thanks for making me think this through :) FWIW, cygwin-announce email shows up on cygwin thanks to a repeater running on my system. I did this because people on the cygwin list complained that they weren't seeing announcements and didn't want to have to subscribe to two mailing lists. Just a different point of view, I guess. cgf From ford@vss.fsi.com Tue Nov 4 18:59:00 2003 From: ford@vss.fsi.com (Brian Ford) Date: Tue, 04 Nov 2003 18:59:00 -0000 Subject: obstacle running "cygwin" (communicating with Solaris 8, Sparc) ... In-Reply-To: <18876.1067971458@www41.gmx.net> References: <18876.1067971458@www41.gmx.net> Message-ID: On Tue, 4 Nov 2003, Andreas (privat) wrote: > it's my intention to start a remote login-process at the solaris-pc via > cygwin. Unfortunately the > login-session is always interrupted. Cygwin is only able to depict a black > screen (including the mouse cursor). Nothing else occurs > http://xfree86.cygwin.com/docs/faq/cygwin-xfree-faq.html#q-solaris-fonts -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444 From kb1jof@together.net Tue Nov 4 20:27:00 2003 From: kb1jof@together.net (kb1jof@together.net) Date: Tue, 04 Nov 2003 20:27:00 -0000 Subject: Stamp Collecting Message-ID: Hello, and Welcome to My Stamp Collecting Website, I would like to invite you to take a look at my newly published website, www.kensstamphouse.com that consists of Many Mint and Used stamp lots, at very reasonable prices. Each lot contains anywheres from 25 to 500 all different stamps from many different countries. Why not take a look. Never know, there may be something you can use for your collection. Thanks for looking and happy stamp collecting. Don't forget, www.kensstamphouse.com. Ken Maltese From kb1jof@together.net Tue Nov 4 20:42:00 2003 From: kb1jof@together.net (kb1jof@together.net) Date: Tue, 04 Nov 2003 20:42:00 -0000 Subject: Stamp Collecting Message-ID: Hello, and Welcome to My Stamp Collecting Website, I would like to invite you to take a look at my newly published website, www.kensstamphouse.com that consists of Many Mint and Used stamp lots, at very reasonable prices. Each lot contains anywheres from 25 to 500 all different stamps from many different countries. Why not take a look. Never know, there may be something you can use for your collection. Thanks for looking and happy stamp collecting. Don't forget, www.kensstamphouse.com. Ken Maltese From rmedina@ivic.ve Tue Nov 4 21:15:00 2003 From: rmedina@ivic.ve (Rodrigo Medina) Date: Tue, 04 Nov 2003 21:15:00 -0000 Subject: Missing backslash key Message-ID: <200311042109.hA4L9hqC027647@pion.ivic.ve> Hello, In the current XFree86 distribution in the keyboard symbols files /usr/X11R6/lib/X11/xkb/symbols/pc/us and /usr/X11R6/lib/X11/xkb/symbols/pc/en_US the BKSL key is missing. Rodrigo Medina From agrimm@redwood.rsc.raytheon.com Wed Nov 5 00:33:00 2003 From: agrimm@redwood.rsc.raytheon.com (Andrew Grimm) Date: Wed, 05 Nov 2003 00:33:00 -0000 Subject: WindowMaker-0.80.2-1 bad TIFFs? Message-ID: My recently-updated Cygwin WindowMaker is whining to me: TIFFReadDirectory: Warning, /usr/X11R6/share/WINGs/Images.tiff: unknown field with tag 317 (0x13d) encountered. TIFFReadDirectory: Warning, /usr/X11R6/share/WindowMaker/Icons/Terminal.tiff: unknown field with tag 317 (0x13d) encountered. I believe it as the icon for the terminal looks messed up. This doesn't impact my ability to continue living, but it would be nice if it were corrected. I have all of the latest Cygwin packages (on Win 2k) so I don't think I'm missing a decode/display component or anything. Thanks, Andy From danilo.turina@alcatel.it Wed Nov 5 07:31:00 2003 From: danilo.turina@alcatel.it (Danilo Turina) Date: Wed, 05 Nov 2003 07:31:00 -0000 Subject: WindowMaker-0.80.2-1 bad TIFFs? In-Reply-To: References: Message-ID: As I already told in message http://www.cygwin.com/ml/cygwin-xfree/2003-11/msg00023.html this is happening also to me. Not only the terminal icon is messed up, but also the icons of the Preferences panel of WindowMaker. Notice also that opening those tiffs with a viewer (e.g. IrfanView) they seems to be ok. Andrew Grimm wrote: > My recently-updated Cygwin WindowMaker is whining to me: > > TIFFReadDirectory: Warning, /usr/X11R6/share/WINGs/Images.tiff: > unknown field with tag 317 (0x13d) encountered. > TIFFReadDirectory: Warning, /usr/X11R6/share/WindowMaker/Icons/Terminal.tiff: > unknown field with tag 317 (0x13d) encountered. > > I believe it as the icon for the terminal looks messed up. > > This doesn't impact my ability to continue living, but it would be nice if > it were corrected. I have all of the latest Cygwin packages (on Win 2k) > so I don't think I'm missing a decode/display component or anything. > > Thanks, > Andy > > From hans.dekker.ext@juntadeandalucia.es Wed Nov 5 13:13:00 2003 From: hans.dekker.ext@juntadeandalucia.es (Hans Dekker) Date: Wed, 05 Nov 2003 13:13:00 -0000 Subject: Font and .bat files missing when installing XFree86 only? References: <3FA211E5.6090601@juntadeandalucia.es> <3FA29D14.40700@msu.edu> Message-ID: <3FA8F75E.9080304@juntadeandalucia.es> Hi Harold, I guess I got confused by the different versions and different download sites there are. Sometimes parts are not downloaded of which the setup program sees (or thinks) they already exist on the system, which left me with an incomplete version of Xfree. Yesterday I deleted all there was and started a new download which seems to incorporate everything. Thanks however, Hans. Harold L Hunt II escribi??: > Hans Dekker wrote: > >> Hi all, >> >> Having downloaded a version of XFree86, I see a difference between a >> previous version and this one: >> >> - When installing de XFree86 option only, no fonts are installed. I >> had to install (= copy) font files from a previous version and that >> worked. Am I missing something? > > > You need the XFree86-fnts package at a minimum. I am surprised that > this was not automatically selected. Are you sure that you selected > XFree86-base? That package lists XFree86-fnts as a dependency, so it > should have been automatically selected. > >> - Also, some useful .bat files of which startxwin.bat is one, are >> missing from the current installation. Even when installing the >> complete package wouldn't help. Why was that? > > > You have to pick the XFree86-startup-scripts package. > > Hope that helps. > > Harold > > > . > From huntharo@msu.edu Wed Nov 5 13:26:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Wed, 05 Nov 2003 13:26:00 -0000 Subject: WindowMaker-0.80.2-1 bad TIFFs? In-Reply-To: References: Message-ID: <3FA8FA68.4070704@msu.edu> What mount type are you guys using for that directory? I would suspect that a text mount might cause problems. You should be using a binary mount. Harold Danilo Turina wrote: > As I already told in message > http://www.cygwin.com/ml/cygwin-xfree/2003-11/msg00023.html > this is happening also to me. > > Not only the terminal icon is messed up, but also the icons of the > Preferences panel of WindowMaker. > > Notice also that opening those tiffs with a viewer (e.g. IrfanView) they > seems to be ok. > > Andrew Grimm wrote: > >> My recently-updated Cygwin WindowMaker is whining to me: >> >> TIFFReadDirectory: Warning, /usr/X11R6/share/WINGs/Images.tiff: >> unknown field with tag 317 (0x13d) encountered. >> TIFFReadDirectory: Warning, >> /usr/X11R6/share/WindowMaker/Icons/Terminal.tiff: >> unknown field with tag 317 (0x13d) encountered. >> >> I believe it as the icon for the terminal looks messed up. >> >> This doesn't impact my ability to continue living, but it would be >> nice if >> it were corrected. I have all of the latest Cygwin packages (on Win 2k) >> so I don't think I'm missing a decode/display component or anything. >> >> Thanks, >> Andy >> >> > > From hans.dekker.ext@juntadeandalucia.es Wed Nov 5 13:26:00 2003 From: hans.dekker.ext@juntadeandalucia.es (Hans Dekker) Date: Wed, 05 Nov 2003 13:26:00 -0000 Subject: Define a foreign language keyboard in HP-Ux CDE? References: <3FA252FB.1060201@juntadeandalucia.es> <3FA29EBE.9080803@msu.edu> Message-ID: <3FA8FA66.6030200@juntadeandalucia.es> Hi Harold and others, I installed the new version of the Xserver and I got some closer but not as close as I??d like. Using Xserv 4.3.0-21 and defining the keyboard as Spanish in XF86Config gave me the following: - Shift key combinations work as supposed on a Spanish keyboard. - AltGr key combinations don't work. - In the xmodmap -pk output I can see that there is no definition for key combinations with AltGr, and that the AltGr key is defined as: 113 0xfe03 (ISO_Level3_Shift) 0xff20 (Multi_key) - I am still working with HP-UX CDE. - The definitions in /etc/X11/XF86Config are: Option "XkbModel" "pc105" Option "XkbLayout" "es" # Option "XkbVariant" "nodeadkeys" # Option "LeftAlt" "Meta" Option "RightAlt" "ModeShift" - XWin.log says it's installing the keyboard OK. Any suggestions to resolve this will be more than welcome. Regards, Hans. Harold L Hunt II escribi??: > Hans, > > Hans Dekker wrote: > >> Hi all, >> >> Having downloaded the latest version of XFree86, I encounter a >> problem using altGR on a Spanish keyboard. >> >> I searched and I searched and saw many articles of people with the >> same question from Denmark, Norway, Germany, UK and other countries, >> and fixes with Xmodmaps, xkeycaps, XF86Config, etc leaving still >> unclear to me which one is right: I didn't get it working yet. >> >> Can anyone tell me what??s the final solution? >> >> Doing a xmodmap on one of the CDE windows shows a keyboard with a US >> layout. >> >> A normal Xfree86 xterm (without CDE) is working fine with the same >> keyboard. >> >> I am using Xserv V 4.2.0-42 on WindowsXP with a CDE environment on > > ^^^^^^^^ > > Wow! 4.2.0-42 was released 2003/06/02. Since then we have moved from > XFree86 4.2.0 to 4.3.0 and had about 25 updates to the Cygwin X Server > (XWin.exe, XFree86-xserv). A lot of those updates are for > keyboard-detection code written by Alexander Gottwald. I suggest > updating your installation and buying Alexander a pizza if it works for > you: > > http://www-user.tu-chemnitz.de/~goal/xfree/donations.html > > :) > > Here is the release announcement for XFree86-xserv-4.2.0-42, in case > anyone is interested: > > http://cygwin.com/ml/cygwin-xfree-announce/2003-06/msg00005.html > > > Hope that helps, > > Harold > > > . > From whiplash@planetfurry.com Wed Nov 5 13:54:00 2003 From: whiplash@planetfurry.com (Ricky Boone) Date: Wed, 05 Nov 2003 13:54:00 -0000 Subject: Default Mouse Pointer is Wrong Message-ID: <1068040438.32389.16.camel@whiplash.planetfurry.com> This may just be an idiotic question, but I couldn't seem to find an answer in the archives. I am trying to connect to remote applications in X (in -multiwindow mode) through ssh on cygwin. When I open the remote application, the default mouse pointer (cursor, whatever) is an 'X'. Some special areas in the application, such as text fields, change the cursor successfully to a text selection pointer, but the 'X' pointer remains the default nearly everywhere else. Previously I had been using the default window manager with Cygwin by running startx, then remoting inside of it. That was a little roundabout, but it worked. All cursors and pointers looked okay. I've just done a complete reinstall of Cygwin on my WinXP box, since I thought perhaps either something was screwed up with the previous installation, or something new had fixed the problem. The remote system I'm connecting to is Fedora Core Test 3 running the latest packages, though I'm willing to bet if I find another machine to test this on it will do the same; it's got to be something on my end, whether it's a misconfiguration or something I'm forgetting to do. Here's a quick example of exactly what I'm doing: * Open Cygwin shell (cygwin.bat) * startxwin.sh * Inside the xterm window: ssh -XC me@somebox.domain.tld * Once logged into remote box: evolution & * Everything loads okay, but mouse pointer is an 'X' instead of the usual Windows arrow, or the default pointer on the remote box. Any ideas? :) -- Ricky Boone Planetfurry.com From huntharo@msu.edu Wed Nov 5 14:09:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Wed, 05 Nov 2003 14:09:00 -0000 Subject: Default Mouse Pointer is Wrong In-Reply-To: <1068040438.32389.16.camel@whiplash.planetfurry.com> References: <1068040438.32389.16.camel@whiplash.planetfurry.com> Message-ID: <3FA90473.2050403@msu.edu> Ricky, Ricky Boone wrote: > This may just be an idiotic question, but I couldn't seem to find an > answer in the archives. > > I am trying to connect to remote applications in X (in -multiwindow > mode) through ssh on cygwin. When I open the remote application, the > default mouse pointer (cursor, whatever) is an 'X'. Some special areas > in the application, such as text fields, change the cursor successfully > to a text selection pointer, but the 'X' pointer remains the default > nearly everywhere else. The default mouse pointer in X is an X. You are describing the correct scenario. > Previously I had been using the default window manager with Cygwin by > running startx, then remoting inside of it. That was a little > roundabout, but it worked. All cursors and pointers looked okay. > > I've just done a complete reinstall of Cygwin on my WinXP box, since I > thought perhaps either something was screwed up with the previous > installation, or something new had fixed the problem. The remote system > I'm connecting to is Fedora Core Test 3 running the latest packages, > though I'm willing to bet if I find another machine to test this on it > will do the same; it's got to be something on my end, whether it's a > misconfiguration or something I'm forgetting to do. > > Here's a quick example of exactly what I'm doing: > > * Open Cygwin shell (cygwin.bat) > * startxwin.sh > * Inside the xterm window: ssh -XC me@somebox.domain.tld > * Once logged into remote box: evolution & > * Everything loads okay, but mouse pointer is an 'X' instead of the > usual Windows arrow, or the default pointer on the remote box. The mouse pointer should not be a Windows arrow. The mouse pointer will not be the default pointer that you have under Gnome or KDE on the remote system because you are not running Gnome or KDE on the remote system... you are running only a single application with a local (not remote) window manager (a.k.a. MultiWindow mode, a.k.a. -multiwindow command-line parameter). Thus, the mouse pointer will be either a) the default mouse pointer (an X), or b) whatever an application sets it to (e.g. a text insertion cursor). Does that make sense? Everything seems to be functioning normally. Harold From cliff@may.be Wed Nov 5 14:18:00 2003 From: cliff@may.be (Cliff Stanford) Date: Wed, 05 Nov 2003 14:18:00 -0000 Subject: Twin screens Message-ID: I am running X using the following start-up command: start XWin -multiwindow -nounixkill -clipboard -nowinkill I have recently installed a second monitor onto my system (XP PRO) where the second monitor is to the LEFT of the main screen. The architecture correctly (in my opinion) treats the 0,0 point as being on the new, left-hand screen and everything works fine on that screen. If, however, I drag a window across from the left screen to the main screen, it freezes. Doesn't do anything at all, no input, no refresh. Dragging it back makes it happy again. I assume that it believes it is now off-screen. Cliff. -- Cliff Stanford Might Limited +44 870 199 4137 (Office) Suite 67, Dorset House +44 7973 616 666 (Mobile) Duke Street, Chelmsford, CM1 1TB From huntharo@msu.edu Wed Nov 5 14:24:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Wed, 05 Nov 2003 14:24:00 -0000 Subject: Twin screens In-Reply-To: References: Message-ID: <3FA90823.3080506@msu.edu> Try the -multimonitor command-line parameter (add it to your current parameters). I believe that is the name of it... might be -multiplemonitor. In fact, either may work. In any case, it will fail to startup if the name is incorrect, in which case you should try the other one. Harold Cliff Stanford wrote: > I am running X using the following start-up command: > > start XWin -multiwindow -nounixkill -clipboard -nowinkill > > I have recently installed a second monitor onto my system (XP PRO) where > the second monitor is to the LEFT of the main screen. > > The architecture correctly (in my opinion) treats the 0,0 point as being > on the new, left-hand screen and everything works fine on that screen. > > If, however, I drag a window across from the left screen to the main > screen, it freezes. Doesn't do anything at all, no input, no refresh. > Dragging it back makes it happy again. > > I assume that it believes it is now off-screen. > > Cliff. From whiplash@planetfurry.com Wed Nov 5 14:33:00 2003 From: whiplash@planetfurry.com (Ricky Boone) Date: Wed, 05 Nov 2003 14:33:00 -0000 Subject: Default Mouse Pointer is Wrong In-Reply-To: <3FA90473.2050403@msu.edu> References: <1068040438.32389.16.camel@whiplash.planetfurry.com> <3FA90473.2050403@msu.edu> Message-ID: <1068042775.32389.26.camel@whiplash.planetfurry.com> On Wed, 2003-11-05 at 09:08, Harold L Hunt II wrote: > The default mouse pointer in X is an X. You are describing the correct > scenario. Okay, my mistake there. When I am referring to default, I mean the normal cursor, usually being an arrow. > The mouse pointer should not be a Windows arrow. I didn't think so since it wasn't like that while using the default cygwin window manager; it was using an arrow. > The mouse pointer will not be the default pointer that you have under > Gnome or KDE on the remote system because you are not running Gnome or > KDE on the remote system... you are running only a single application > with a local (not remote) window manager (a.k.a. MultiWindow mode, > a.k.a. -multiwindow command-line parameter). Thus, the mouse pointer > will be either a) the default mouse pointer (an X), or b) whatever an > application sets it to (e.g. a text insertion cursor). > > Does that make sense? Everything seems to be functioning normally. It does, but what is preventing the cursor from being displayed as an arrow like it could without -multiwindow enabled? Fuctionality-wise it works just fine, but aesthetically it's not ideal for the user to see an 'X' when they normally see an arrow. -- Ricky Boone Planetfurry.com From yadin@pitt.edu Wed Nov 5 14:37:00 2003 From: yadin@pitt.edu (Yadin Y. Goldschmidt) Date: Wed, 05 Nov 2003 14:37:00 -0000 Subject: Default Mouse Pointer is Wrong References: <1068040438.32389.16.camel@whiplash.planetfurry.com> Message-ID: Hi, Colin Harrison suggested long time ago to add the following line to the end of your startxwin.bat file: xsetroot -cursor_name left_ptr -fg white -bg black This will change the default mouse from an x to a white arrow. An unrelated question to harold Hunt: Why if one uses mwm as the window manager and one invokes xclock it does not have a frame and can't be moved? xterm, rxvt, xeyes, etc all have frames and can be moved. "Ricky Boone" wrote in message news:1068040438.32389.16.camel@whiplash.planetfurry.com... > This may just be an idiotic question, but I couldn't seem to find an > answer in the archives. > > I am trying to connect to remote applications in X (in -multiwindow > mode) through ssh on cygwin. When I open the remote application, the > default mouse pointer (cursor, whatever) is an 'X'. Some special areas > in the application, such as text fields, change the cursor successfully > to a text selection pointer, but the 'X' pointer remains the default > nearly everywhere else. > > Previously I had been using the default window manager with Cygwin by > running startx, then remoting inside of it. That was a little > roundabout, but it worked. All cursors and pointers looked okay. > > I've just done a complete reinstall of Cygwin on my WinXP box, since I > thought perhaps either something was screwed up with the previous > installation, or something new had fixed the problem. The remote system > I'm connecting to is Fedora Core Test 3 running the latest packages, > though I'm willing to bet if I find another machine to test this on it > will do the same; it's got to be something on my end, whether it's a > misconfiguration or something I'm forgetting to do. > > Here's a quick example of exactly what I'm doing: > > * Open Cygwin shell (cygwin.bat) > * startxwin.sh > * Inside the xterm window: ssh -XC me@somebox.domain.tld > * Once logged into remote box: evolution & > * Everything loads okay, but mouse pointer is an 'X' instead of the > usual Windows arrow, or the default pointer on the remote box. > > Any ideas? :) > > -- > Ricky Boone > Planetfurry.com > > From dan.scott@ca.ibm.com Wed Nov 5 14:50:00 2003 From: dan.scott@ca.ibm.com (Dan Scott) Date: Wed, 05 Nov 2003 14:50:00 -0000 Subject: WindowMaker-0.80.2-1 bad TIFFs? In-Reply-To: <3FA8FA68.4070704@msu.edu> References: <3FA8FA68.4070704@msu.edu> Message-ID: I'll add my confirmation of the problem. TIFFs in WindowMaker worked fine before the last update. My mount settings represent a default Cygwin install: userid:/etc$ mount C:\cygwin\usr\X11R6\lib\X11\fonts on /usr/X11R6/lib/X11/fonts type system (binmode) C:\cygwin\bin on /usr/bin type system (binmode) C:\cygwin\lib on /usr/lib type system (binmode) C:\cygwin on / type system (binmode) Dan Harold L Hunt II wrote: > What mount type are you guys using for that directory? I would suspect > that a text mount might cause problems. You should be using a binary > mount. > > Harold > > Danilo Turina wrote: > >> As I already told in message >> http://www.cygwin.com/ml/cygwin-xfree/2003-11/msg00023.html >> this is happening also to me. >> >> Not only the terminal icon is messed up, but also the icons of the >> Preferences panel of WindowMaker. >> >> Notice also that opening those tiffs with a viewer (e.g. IrfanView) >> they seems to be ok. >> >> Andrew Grimm wrote: >> >>> My recently-updated Cygwin WindowMaker is whining to me: >>> >>> TIFFReadDirectory: Warning, /usr/X11R6/share/WINGs/Images.tiff: >>> unknown field with tag 317 (0x13d) encountered. >>> TIFFReadDirectory: Warning, >>> /usr/X11R6/share/WindowMaker/Icons/Terminal.tiff: >>> unknown field with tag 317 (0x13d) encountered. >>> >>> I believe it as the icon for the terminal looks messed up. >>> >>> This doesn't impact my ability to continue living, but it would be >>> nice if >>> it were corrected. I have all of the latest Cygwin packages (on Win 2k) >>> so I don't think I'm missing a decode/display component or anything. >>> >>> Thanks, >>> Andy >>> >>> >> >> > > From querra@gmx.de Wed Nov 5 14:55:00 2003 From: querra@gmx.de (Andreas (privat)) Date: Wed, 05 Nov 2003 14:55:00 -0000 Subject: obstacle running "cygwin" (communicating with Solaris 8, Sparc) ... References: Message-ID: <2807.1068044145@www63.gmx.net> Hello Brain, much thanks for your response. But unfortunately my problem doesn't stay in relation with the fonts. I've tried it yet. Do you have another solution in mind? Bye Querra > On Tue, 4 Nov 2003, Andreas (privat) wrote: > > > it's my intention to start a remote login-process at the solaris-pc via > > cygwin. Unfortunately the > > login-session is always interrupted. Cygwin is only able to depict a > black > > screen (including the mouse cursor). Nothing else occurs > > > http://xfree86.cygwin.com/docs/faq/cygwin-xfree-faq.html#q-solaris-fonts > > -- > Brian Ford > Senior Realtime Software Engineer > VITAL - Visual Simulation Systems > FlightSafety International > Phone: 314-551-8460 > Fax: 314-551-8444 > -- NEU F??R ALLE - GMX MediaCenter - f??r Fotos, Musik, Dateien... Fotoalbum, File Sharing, MMS, Multimedia-Gru??, GMX FotoService Jetzt kostenlos anmelden unter http://www.gmx.net +++ GMX - die erste Adresse f??r Mail, Message, More! +++ From whiplash@planetfurry.com Wed Nov 5 14:59:00 2003 From: whiplash@planetfurry.com (Ricky Boone) Date: Wed, 05 Nov 2003 14:59:00 -0000 Subject: Default Mouse Pointer is Wrong In-Reply-To: References: <1068040438.32389.16.camel@whiplash.planetfurry.com> Message-ID: <1068044377.32617.1.camel@whiplash.planetfurry.com> On Wed, 2003-11-05 at 09:37, Yadin Y. Goldschmidt wrote: > Colin Harrison suggested long time ago to add the following line to the end > of your startxwin.bat file: > xsetroot -cursor_name left_ptr -fg white -bg black > This will change the default mouse from an x to a white arrow. Ah ha, that did the trick. My apologies, I didn't even notice the suggestion when I searched for it. -.-;; Thanks for the help. :) -- Ricky Boone Planetfurry.com From hj.beckers@kreis-steinfurt.de Wed Nov 5 15:40:00 2003 From: hj.beckers@kreis-steinfurt.de (hj.beckers@kreis-steinfurt.de) Date: Wed, 05 Nov 2003 15:40:00 -0000 Subject: Antwort: Re: WindowMaker-0.80.2-1 bad TIFFs? Message-ID: If wmaker is started manually, it gives the following output: "ZS01643@ps0114 /CYGDRIVE/D/cygwin/home $ wmaker TIFFReadDirectory: Warning, /usr/X11R6/share/WINGs/Images.tiff: unknown field wi th tag 317 (0x13d) encountered. TIFFReadDirectory: Warning, /usr/X11R6/share/WindowMaker/Icons/TerminalGNUstep.t iff: unknown field with tag 317 (0x13d) encountered. TIFFReadDirectory: Warning, /usr/X11R6/share/WindowMaker/Icons/TerminalLinux.tif f: unknown field with tag 317 (0x13d) encountered." I did an update from ftp.gwdg.de (?) today. Before the update the tiffs were okay. Yours hjb From danilo.turina@alcatel.it Wed Nov 5 15:52:00 2003 From: danilo.turina@alcatel.it (Danilo Turina) Date: Wed, 05 Nov 2003 15:52:00 -0000 Subject: WindowMaker-0.80.2-1 bad TIFFs? In-Reply-To: <3FA8FA68.4070704@msu.edu> References: <3FA8FA68.4070704@msu.edu> Message-ID: $ mount C:\cygwin\usr\X11R6\lib\X11\fonts on /usr/X11R6/lib/X11/fonts type system (binmode) C:\cygwin\bin on /usr/bin type system (binmode) C:\cygwin\lib on /usr/lib type system (binmode) C:\cygwin on / type system (binmode) c: on /cygdrive/c type user (binmode,noumount) k: on /cygdrive/k type user (binmode,noumount) l: on /cygdrive/l type user (binmode,noumount) m: on /cygdrive/m type user (binmode,noumount) n: on /cygdrive/n type user (binmode,noumount) p: on /cygdrive/p type user (binmode,noumount) v: on /cygdrive/v type user (binmode,noumount) Harold L Hunt II wrote: > What mount type are you guys using for that directory? I would suspect > that a text mount might cause problems. You should be using a binary > mount. > > Harold > > Danilo Turina wrote: > >> As I already told in message >> http://www.cygwin.com/ml/cygwin-xfree/2003-11/msg00023.html >> this is happening also to me. >> >> Not only the terminal icon is messed up, but also the icons of the >> Preferences panel of WindowMaker. >> >> Notice also that opening those tiffs with a viewer (e.g. IrfanView) >> they seems to be ok. >> >> Andrew Grimm wrote: >> >>> My recently-updated Cygwin WindowMaker is whining to me: >>> >>> TIFFReadDirectory: Warning, /usr/X11R6/share/WINGs/Images.tiff: >>> unknown field with tag 317 (0x13d) encountered. >>> TIFFReadDirectory: Warning, >>> /usr/X11R6/share/WindowMaker/Icons/Terminal.tiff: >>> unknown field with tag 317 (0x13d) encountered. >>> >>> I believe it as the icon for the terminal looks messed up. >>> >>> This doesn't impact my ability to continue living, but it would be >>> nice if >>> it were corrected. I have all of the latest Cygwin packages (on Win 2k) >>> so I don't think I'm missing a decode/display component or anything. >>> >>> Thanks, >>> Andy >>> >>> >> >> > > From vervoom@hotmail.com Wed Nov 5 16:15:00 2003 From: vervoom@hotmail.com (J S) Date: Wed, 05 Nov 2003 16:15:00 -0000 Subject: screen redraw problem Message-ID: Is there anymore information I need to add to this post? I would really like to get some help with it. The logs don't seem to be showing anything. I've tried setting different color depths, and screen resolutions but to no avail. Hi, I have an application which has some boxes in the window. The window itself is scrollable. When I scroll down - no problem, but when I scroll up the boxes turn into long vertical bars. This problem doesn't happen with Exceed, but on XFree86 (both Linux XFree86 and Cygwin-XFree) it does. Can anyone advise me whether this is a bug, or is there some setting I need to add? Let me know if you need anymore information. Thanks for any help. JS. _________________________________________________________________ Stay in touch with absent friends - get MSN Messenger http://www.msn.co.uk/messenger From cliff@may.be Wed Nov 5 16:40:00 2003 From: cliff@may.be (Cliff Stanford) Date: Wed, 05 Nov 2003 16:40:00 -0000 Subject: Twin screens In-Reply-To: <3FA90823.3080506@msu.edu> References: <3FA90823.3080506@msu.edu> Message-ID: In message <3FA90823.3080506@msu.edu>, Harold L Hunt II writes >Try the -multimonitor command-line parameter (add it to your current >parameters). > >I believe that is the name of it... might be -multiplemonitor. In >fact, either may work. In any case, it will fail to startup if the >name is incorrect, in which case you should try the other one. It's -multiplemonitors, it works perfectly and it's fully documented. I have slapped myself hard on both wrists and apologise to you and everyone else for wasting their time. Regards, Cliff. From gorrigo@switch.com Wed Nov 5 16:53:00 2003 From: gorrigo@switch.com (Orrigo, Giampaolo .) Date: Wed, 05 Nov 2003 16:53:00 -0000 Subject: Cygwin X server crashes when a remote Xemacs is run Message-ID: <8F329FEDF58BD411BE5200508B10DA760E0B9F77@exchptc1.switch.com> Here what I'm trying to do: I establish a rsh connection with a UNIX/Linux machine and open an xterm. The I run Xemacs on this remote machine and XWin.exe crashes. I tried it connecting with both a Linux machine and a Alpha machine. Here the Xemacs versions installed on those machines: Linux - Xemacs 21.1 (patch 14) i386-redhat-linux Alpha - Xemacs 20.4 alpha-dec-osf3.2 Here the Windows error message: Exception: access violation (0xc0000005), Address: 0x61093b2c I'm running Cygwin 1.5.5-1 on Windows NT 4.0 Workstation. XWin.exe version is 4.3.0-20 Giampaolo Orrigo <> -------------- next part -------------- A non-text attachment was scrubbed... Name: cygcheck.out Type: application/octet-stream Size: 22975 bytes Desc: not available URL: From huntharo@msu.edu Wed Nov 5 17:23:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Wed, 05 Nov 2003 17:23:00 -0000 Subject: screen redraw problem In-Reply-To: References: Message-ID: <3FA931FA.1070108@msu.edu> JS, Looks like you have found a generic problem with X or one of the libraries you are using. It is going to take a lot of debugging... you are going to have to be that guy. Harold J S wrote: > Is there anymore information I need to add to this post? I would really > like to get some help with it. The logs don't seem to be showing > anything. I've tried setting different color depths, and screen > resolutions but to no avail. > > Hi, > > I have an application which has some boxes in the window. The window itself > is scrollable. When I scroll down - no problem, but when I scroll up the > boxes turn into long vertical bars. This problem doesn't happen with > Exceed, > but on XFree86 (both Linux XFree86 and Cygwin-XFree) it does. > > Can anyone advise me whether this is a bug, or is there some setting I need > to add? Let me know if you need anymore information. > > Thanks for any help. > > JS. > > _________________________________________________________________ > Stay in touch with absent friends - get MSN Messenger > http://www.msn.co.uk/messenger > From mvojkovi@XFree86.Org Wed Nov 5 19:04:00 2003 From: mvojkovi@XFree86.Org (Mark Vojkovich) Date: Wed, 05 Nov 2003 19:04:00 -0000 Subject: [XFree86] screen redraw problem In-Reply-To: Message-ID: Maybe your app is expecting backing store. You can start XFree86 with backing store "startx -- +bs". Mark. On Wed, 5 Nov 2003, J S wrote: > Is there anymore information I need to add to this post? I would really like > to get some help with it. The logs don't seem to be showing anything. I've > tried setting different color depths, and screen resolutions but to no > avail. > > Hi, > > I have an application which has some boxes in the window. The window itself > is scrollable. When I scroll down - no problem, but when I scroll up the > boxes turn into long vertical bars. This problem doesn't happen with Exceed, > but on XFree86 (both Linux XFree86 and Cygwin-XFree) it does. > > Can anyone advise me whether this is a bug, or is there some setting I need > to add? Let me know if you need anymore information. > > Thanks for any help. > > JS. > > _________________________________________________________________ > Stay in touch with absent friends - get MSN Messenger > http://www.msn.co.uk/messenger > > _______________________________________________ > XFree86 mailing list > XFree86@XFree86.Org > http://XFree86.Org/mailman/listinfo/xfree86 > From jsharp@ti.com Wed Nov 5 19:09:00 2003 From: jsharp@ti.com (John Sharp) Date: Wed, 05 Nov 2003 19:09:00 -0000 Subject: XFree4.3.0 multiwindow mode intermittently fails on ME Message-ID: <3FA94ADD.96CFC27B@ti.com> Hello, After a clean install of 4.3.0 I have a problem where XWin multiwindow mode fails to allow connections to the Xserver. (There is no problem running with the "startx" method). I can ping localhost. Intermittently "startxwin.sh" will start its xterm. The server allways starts and the "X" icon appears on the ME task bar, however if I try to start x clients I get "Can't open display". Moving the mouse over the "X" on the task bar removes the icon. However, XWin is still listed as running in the process table. XWin.log from a FAILED session:- ddxProcessArgument - Initializing default screens winInitializeDefaultScreens - w 1024 h 768 winInitializeDefaultScreens - Returning OsVendorInit - Creating bogus screen 0 (EE) Unable to locate/open config file InitOutput - Error reading config file winDetectSupportedEngines - Windows 95/98/Me winDetectSupportedEngines - DirectDraw installed winDetectSupportedEngines - DirectDraw4 installed winDetectSupportedEngines - Returning, supported engines 00000017 InitOutput - g_iNumScreens: 1 iMaxConsecutiveScreen: 1 winSetEngine - Multi Window => ShadowGDI winAdjustVideoModeShadowGDI - 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 768 1022 winAdjustForAutoHide - Taskbar is auto hide winAdjustForAutoHide - Found BOTTOM auto-hide taskbar winAdjustForAutoHide - Found RIGHT auto-hide taskbar winAdjustForAutoHide - Adjusted WorkArea: 0 0 767 1021 winCreateBoundingWindowWindowed - WindowClient w 1021 h 767 r 1021 l 0 b 767 t 0 winCreateBoundingWindowWindowed - Returning winAllocateFBShadowGDI - Creating DIB with width: 1021 height: 767 depth: 16 winAllocateFBShadowGDI - Dibsection width: 1021 height: -767 depth: 16 size imag e: 1567748 winAllocateFBShadowGDI - WEIRDNESS - biHeight still negative: -767 winAllocateFBShadowGDI - WEIRDNESS - Flipping biHeight sign winAllocateFBShadowGDI - Created shadow stride: 1022 winFinishScreenInitFB - Masks: 0000f800 000007e0 0000001f winInitVisualsShadowGDI - Masks 0000f800 000007e0 0000001f BPRGB 6 d 16 bpp 16 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. winMultiWindowXMsgProc - Hello winMultiWindowXMsgProc - Calling pthread_mutex_lock () MIT-SHM extension disabled due to lack of kernel support winInitMultiWindowWM - Hello winInitMultiWindowWM - Calling pthread_mutex_lock () XFree86-Bigfont extension local-client optimization disabled due to lack of shar ed memory support in the kernel (==) winConfigKeyboard - Layout: "00000409" (00000409) (EE) No primary keyboard configured (==) Using compiletime defaults for keyboard Rules = "xfree86" Model = "pc101" Layout = "us" Variant = "(null)" Options = "(n ull)" Next output from cygcheck:- Cygwin Win95/NT Configuration Diagnostics Current System Time: Wed Nov 05 13:11:30 2003 Windows ME Ver 4.90 Build 3000 Path: C:\cygwin\usr\local\bin C:\cygwin\bin C:\cygwin\bin C:\cygwin\usr\X11R6\bin C:\cygwin\aspn\bin c:\WINDOWS c:\WINDOWS\COMMAND Output from C:\cygwin\bin\id.exe (nontsec) UID: 811(default) GID: 544(all) 544(all) Output from C:\cygwin\bin\id.exe (ntsec) UID: 811(default) GID: 544(all) 544(all) SysDir: C:\WINDOWS\SYSTEM WinDir: C:\WINDOWS HOME = `C:\cygwin\home\default' MAKE_MODE = `unix' PWD = `/tmp' USER = `default' BLASTER = `A220 I5 D1 T4 P330' CMDLINE = `bash --login -i' COMSPEC = `C:\WINDOWS\COMMAND.COM' CVS_RSH = `/bin/ssh' HOMEDRIVE = `C:' HOMEPATH = `\cygwin\home\default' INFOPATH = `/usr/local/info:/usr/info:/usr/share/info:/usr/autotool/devel/info:/usr/autotool/stable/info:' MANPATH = `/usr/local/man:/usr/man:/usr/share/man:/usr/autotool/devel/man::/usr/X11R6/man:/usr/ssl/man' OLDPWD = `/usr/X11R6/bin' PKG_CONFIG_PATH = `:/usr/X11R6/lib/pkgconfig' PROMPT = `$p$g' PS1 = `$ ' SHLVL = `1' TEMP = `c:\WINDOWS\TEMP' TERM = `cygwin' TEXMF = `{/usr/share/lilypond/2.0.1,/usr/share/texmf}' TMP = `c:\WINDOWS\TEMP' WINBOOTDIR = `C:\WINDOWS' WINDIR = `C:\WINDOWS' _ = `/usr/bin/cygcheck' HKEY_CURRENT_USER\Software\Cygnus Solutions HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\mounts v2 HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\Program Options HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2 (default) = `/cygdrive' cygdrive flags = 0x00000022 HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/ (default) = `C:\cygwin' flags = 0x0000000a HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/usr/bin (default) = `C:\cygwin/bin' flags = 0x0000000a HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/usr/lib (default) = `C:\cygwin/lib' flags = 0x0000000a HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/usr/X11R6/lib/X11/fonts (default) = `C:\cygwin\usr\X11R6\lib\X11\fonts' flags = 0x0000000a HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\Program Options c: hd FAT32 16255Mb 73% CP UN d: hd FAT32 2792Mb 42% CP UN SYSTEM_SAV e: cd N/A N/A C:\cygwin / system binmode C:\cygwin/bin /usr/bin system binmode C:\cygwin/lib /usr/lib system binmode C:\cygwin\usr\X11R6\lib\X11\fonts /usr/X11R6/lib/X11/fonts system binmode . /cygdrive system binmode,cygdrive Found: C:\cygwin\bin\awk.exe Found: C:\cygwin\bin\bash.exe Found: C:\cygwin\bin\cat.exe Found: C:\cygwin\bin\cp.exe Found: C:\cygwin\bin\cpp.exe Found: C:\cygwin\bin\find.exe Found: c:\WINDOWS\COMMAND\find.exe Warning: C:\cygwin\bin\find.exe hides c:\WINDOWS\COMMAND\find.exe Found: C:\cygwin\bin\gcc.exe Found: C:\cygwin\bin\gdb.exe Found: C:\cygwin\bin\grep.exe Found: C:\cygwin\bin\ld.exe Found: C:\cygwin\bin\ls.exe Found: C:\cygwin\bin\make.exe Found: C:\cygwin\bin\mv.exe Found: C:\cygwin\bin\rm.exe Found: C:\cygwin\bin\sed.exe Found: C:\cygwin\bin\sh.exe Found: C:\cygwin\bin\tar.exe 306k 2002/04/27 C:\cygwin\bin\cyghttpd.dll - os=4.0 img=1.0 sys=4.0 "cyghttpd.dll" v0.0 ts=2002/4/27 8:23 7k 2003/10/19 C:\cygwin\bin\cygcrypt-0.dll - os=4.0 img=1.0 sys=4.0 "cygcrypt-0.dll" v0.0 ts=2003/10/19 2:57 551k 2003/04/02 C:\cygwin\bin\cygcurl-2.dll - os=4.0 img=1.0 sys=4.0 "cygcurl-2.dll" v0.0 ts=2003/4/2 15:09 22k 2003/10/17 C:\cygwin\bin\cygcygipc-2.dll - os=4.0 img=1.0 sys=4.0 "cygcygipc-2.dll" v0.0 ts=2003/10/17 0:24 132k 2003/07/12 C:\cygwin\bin\cygexpat-0.dll - os=4.0 img=1.0 sys=4.0 "cygexpat-0.dll" v0.0 ts=2003/7/12 6:33 660k 2003/10/18 C:\cygwin\bin\cygfltknox-0.dll - os=4.0 img=1.0 sys=4.0 "cygfltknox-0.dll" v0.0 ts=2003/10/18 14:05 62k 2003/10/18 C:\cygwin\bin\cygfltknox_forms-0.dll - os=4.0 img=1.0 sys=4.0 "cygfltknox_forms-0.dll" v0.0 ts=2003/10/18 14:05 79k 2003/10/18 C:\cygwin\bin\cygfltknox_gl-0.dll - os=4.0 img=1.0 sys=4.0 "cygfltknox_gl-0.dll" v0.0 ts=2003/10/18 14:05 107k 2003/10/18 C:\cygwin\bin\cygfltknox_images-0.dll - os=4.0 img=1.0 sys=4.0 "cygfltknox_images-0.dll" v0.0 ts=2003/10/18 14:05 167k 2003/09/09 C:\cygwin\bin\cyggmp-3.dll - os=4.0 img=1.0 sys=4.0 "cyggmp-3.dll" v0.0 ts=2003/9/9 17:03 12k 2003/02/17 C:\cygwin\bin\cygioperm-0.dll - os=4.0 img=1.0 sys=4.0 "cygioperm-0.dll" v0.0 ts=2003/2/17 13:58 48k 2003/08/10 C:\cygwin\bin\cygjbig1.dll - os=4.0 img=1.0 sys=4.0 "cygjbig1.dll" v0.0 ts=2003/8/10 18:58 802k 2003/09/15 C:\cygwin\bin\cygaspell-15.dll - os=4.0 img=1.0 sys=4.0 "cygaspell-15.dll" v0.0 ts=2003/9/15 7:32 54k 2002/01/27 C:\cygwin\bin\cygbz21.0.dll - os=4.0 img=1.0 sys=4.0 "cygbz21.0.dll" v0.0 ts=2002/1/26 19:07 61k 2003/08/09 C:\cygwin\bin\cygbz2-1.dll - os=4.0 img=1.0 sys=4.0 "cygbz2-1.dll" v0.0 ts=2003/8/9 1:35 14k 2003/08/10 C:\cygwin\bin\cygcharset-1.dll - os=4.0 img=1.0 sys=4.0 "cygcharset-1.dll" v0.0 ts=2003/8/10 15:57 326k 2002/06/26 C:\cygwin\bin\cygdb2.dll - os=4.0 img=1.0 sys=4.0 "cygdb2.dll" v0.0 ts=2002/6/26 12:48 380k 2002/07/24 C:\cygwin\bin\cygdb-3.1.dll - os=4.0 img=1.0 sys=4.0 "cygdb-3.1.dll" v0.0 ts=2002/7/24 11:24 487k 2002/07/24 C:\cygwin\bin\cygdb_cxx-3.1.dll - os=4.0 img=1.0 sys=4.0 "cygdb_cxx-3.1.dll" v0.0 ts=2002/7/24 11:25 831k 2003/09/20 C:\cygwin\bin\cygdb-4.1.dll - os=4.0 img=1.0 sys=4.0 "cygdb-4.1.dll" v0.0 ts=2003/9/20 16:51 1080k 2003/09/20 C:\cygwin\bin\cygdb_cxx-4.1.dll - os=4.0 img=1.0 sys=4.0 "cygdb_cxx-4.1.dll" v0.0 ts=2003/9/20 16:53 19k 2003/03/22 C:\cygwin\bin\cyggdbm.dll - os=4.0 img=1.0 sys=4.0 "cyggdbm.dll" v0.0 ts=2002/2/19 21:05 28k 2003/07/20 C:\cygwin\bin\cyggdbm-3.dll - os=4.0 img=1.0 sys=4.0 "cyggdbm-3.dll" v0.0 ts=2003/7/20 2:58 15k 2003/07/20 C:\cygwin\bin\cyggdbm_compat-3.dll - os=4.0 img=1.0 sys=4.0 "cyggdbm_compat-3.dll" v0.0 ts=2003/7/20 3:00 30k 2003/08/11 C:\cygwin\bin\cyggdbm-4.dll - os=4.0 img=1.0 sys=4.0 "cyggdbm-4.dll" v0.0 ts=2003/8/10 21:12 15k 2003/08/11 C:\cygwin\bin\cyggdbm_compat-4.dll - os=4.0 img=1.0 sys=4.0 "cyggdbm_compat-4.dll" v0.0 ts=2003/8/10 21:13 12k 2003/08/10 C:\cygwin\bin\cyggettextpo-0.dll - os=4.0 img=1.0 sys=4.0 "cyggettextpo-0.dll" v0.0 ts=2003/8/10 17:11 69k 2003/08/10 C:\cygwin\bin\cyggettextlib-0-12-1.dll - os=4.0 img=1.0 sys=4.0 "cyggettextlib-0-12-1.dll" v0.0 ts=2003/8/10 17:10 134k 2003/08/10 C:\cygwin\bin\cyggettextsrc-0-12-1.dll - os=4.0 img=1.0 sys=4.0 "cyggettextsrc-0-12-1.dll" v0.0 ts=2003/8/10 17:10 489k 2003/08/09 C:\cygwin\bin\cygguile-12.dll - os=4.0 img=1.0 sys=4.0 "cygguile-12.dll" v0.0 ts=2003/8/9 9:17 24k 2003/08/09 C:\cygwin\bin\cygguile-ltdl-1.dll - os=4.0 img=1.0 sys=4.0 "cygguile-ltdl-1.dll" v0.0 ts=2003/8/9 9:16 11k 2003/08/09 C:\cygwin\bin\cygguilereadline-v-12-12.dll - os=4.0 img=1.0 sys=4.0 "cygguilereadline-v-12-12.dll" v0.0 ts=2003/8/9 9:17 62k 2003/08/09 C:\cygwin\bin\cygguile-srfi-srfi-13-14-v-1-1.dll - os=4.0 img=1.0 sys=4.0 "cygguile-srfi-srfi-13-14-v-1-1.dll" v0.0 ts=2003/8/9 9:17 23k 2003/08/09 C:\cygwin\bin\cygguile-srfi-srfi-4-v-1-1.dll - os=4.0 img=1.0 sys=4.0 "cygguile-srfi-srfi-4-v-1-1.dll" v0.0 ts=2003/8/9 9:17 489k 2003/07/28 C:\cygwin\bin\cygguile-12abi13.dll - os=4.0 img=1.0 sys=4.0 "cygguile-12abi13.dll" v0.0 ts=2003/7/28 13:18 24k 2003/07/28 C:\cygwin\bin\cygguile-ltdl-1abi13.dll - os=4.0 img=1.0 sys=4.0 "cygguile-ltdl-1abi13.dll" v0.0 ts=2003/7/28 12:48 11k 2003/07/28 C:\cygwin\bin\cygguilereadline-v-12-12abi13.dll - os=4.0 img=1.0 sys=4.0 "cygguilereadline-v-12-12abi13.dll" v0.0 ts=2003/7/28 13:18 62k 2003/07/28 C:\cygwin\bin\cygguile-srfi-srfi-13-14-v-1-1abi13.dll - os=4.0 img=1.0 sys=4.0 "cygguile-srfi-srfi-13-14-v-1-1abi13.dll" v0.0 ts=2003/7/28 13:18 23k 2003/07/28 C:\cygwin\bin\cygguile-srfi-srfi-4-v-1-1abi13.dll - os=4.0 img=1.0 sys=4.0 "cygguile-srfi-srfi-4-v-1-1abi13.dll" v0.0 ts=2003/7/28 13:18 958k 2003/08/10 C:\cygwin\bin\cygiconv-2.dll - os=4.0 img=1.0 sys=4.0 "cygiconv-2.dll" v0.0 ts=2003/8/10 15:57 21k 2001/06/20 C:\cygwin\bin\cygintl.dll - os=4.0 img=1.0 sys=4.0 "cygintl.dll" v0.0 ts=2001/6/20 12:09 22k 2001/12/13 C:\cygwin\bin\cygintl-1.dll - os=4.0 img=1.0 sys=4.0 "cygintl-1.dll" v0.0 ts=2001/12/13 3:28 37k 2003/08/10 C:\cygwin\bin\cygintl-2.dll - os=4.0 img=1.0 sys=4.0 "cygintl-2.dll" v0.0 ts=2003/8/10 16:50 132k 2003/08/11 C:\cygwin\bin\cygjpeg-62.dll - os=4.0 img=1.0 sys=4.0 "cygjpeg-62.dll" v0.0 ts=2003/8/10 19:37 119k 2002/02/09 C:\cygwin\bin\cygjpeg6b.dll - os=4.0 img=1.0 sys=4.0 "cygjpeg6b.dll" v0.0 ts=2002/2/8 23:19 60k 2003/09/17 C:\cygwin\bin\cygkpathsea-3.dll - os=4.0 img=1.0 sys=4.0 "cygkpathsea-3.dll" v0.0 ts=2003/9/17 11:37 60k 2003/07/27 C:\cygwin\bin\cygkpathsea-3abi13.dll - os=4.0 img=1.0 sys=4.0 "cygkpathsea-3abi13.dll" v0.0 ts=2003/7/27 15:23 32k 2003/08/18 C:\cygwin\bin\cygltdl-3.dll - os=4.0 img=1.0 sys=4.0 "cygltdl-3.dll" v0.0 ts=2003/8/18 0:35 181k 2003/10/06 C:\cygwin\bin\cygmcrypt-4.dll - os=4.0 img=1.0 sys=4.0 "cygmcrypt-4.dll" v0.0 ts=2003/10/6 9:54 45k 2001/04/25 C:\cygwin\bin\cygform5.dll - os=4.0 img=1.0 sys=4.0 "cygform5.dll" v0.0 ts=2001/4/25 0:28 26k 2001/04/25 C:\cygwin\bin\cygmenu5.dll - os=4.0 img=1.0 sys=4.0 "cygmenu5.dll" v0.0 ts=2001/4/25 0:27 156k 2001/04/25 C:\cygwin\bin\cygncurses++5.dll - os=4.0 img=1.0 sys=4.0 "cygncurses++5.dll" v0.0 ts=2001/4/25 0:29 226k 2001/04/25 C:\cygwin\bin\cygncurses5.dll - os=4.0 img=1.0 sys=4.0 "cygncurses5.dll" v0.0 ts=2001/4/25 0:17 15k 2001/04/25 C:\cygwin\bin\cygpanel5.dll - os=4.0 img=1.0 sys=4.0 "cygpanel5.dll" v0.0 ts=2001/4/25 0:27 35k 2002/01/09 C:\cygwin\bin\cygform6.dll - os=4.0 img=1.0 sys=4.0 "cygform6.dll" v0.0 ts=2002/1/9 0:03 20k 2002/01/09 C:\cygwin\bin\cygmenu6.dll - os=4.0 img=1.0 sys=4.0 "cygmenu6.dll" v0.0 ts=2002/1/9 0:03 175k 2002/01/09 C:\cygwin\bin\cygncurses++6.dll - os=4.0 img=1.0 sys=4.0 "cygncurses++6.dll" v0.0 ts=2002/1/9 0:03 202k 2002/01/09 C:\cygwin\bin\cygncurses6.dll - os=4.0 img=1.0 sys=4.0 "cygncurses6.dll" v0.0 ts=2002/1/9 0:03 12k 2002/01/09 C:\cygwin\bin\cygpanel6.dll - os=4.0 img=1.0 sys=4.0 "cygpanel6.dll" v0.0 ts=2002/1/9 0:03 48k 2003/08/09 C:\cygwin\bin\cygform7.dll - os=4.0 img=1.0 sys=4.0 "cygform7.dll" v0.0 ts=2003/8/9 4:25 29k 2003/08/09 C:\cygwin\bin\cygmenu7.dll - os=4.0 img=1.0 sys=4.0 "cygmenu7.dll" v0.0 ts=2003/8/9 4:25 224k 2003/08/09 C:\cygwin\bin\cygncurses7.dll - os=4.0 img=1.0 sys=4.0 "cygncurses7.dll" v0.0 ts=2003/8/9 4:24 19k 2003/08/09 C:\cygwin\bin\cygpanel7.dll - os=4.0 img=1.0 sys=4.0 "cygpanel7.dll" v0.0 ts=2003/8/9 4:24 63k 2003/04/11 C:\cygwin\bin\cygpcre.dll - os=4.0 img=1.0 sys=4.0 "cygpcre.dll" v0.0 ts=2003/4/11 3:31 61k 2003/04/11 C:\cygwin\bin\cygpcreposix.dll - os=4.0 img=1.0 sys=4.0 "cygpcreposix.dll" v0.0 ts=2003/4/11 3:31 67k 2003/09/10 C:\cygwin\bin\cygpcre-0.dll - os=4.0 img=1.0 sys=4.0 "cygpcre-0.dll" v0.0 ts=2003/9/10 9:25 15k 2003/09/10 C:\cygwin\bin\cygpcreposix-0.dll - os=4.0 img=1.0 sys=4.0 "cygpcreposix-0.dll" v0.0 ts=2003/9/10 9:25 168k 2003/08/10 C:\cygwin\bin\cygpng10.dll - os=4.0 img=1.0 sys=4.0 "cygpng10.dll" v0.0 ts=2003/8/10 17:31 173k 2003/08/10 C:\cygwin\bin\cygpng12.dll - os=4.0 img=1.0 sys=4.0 "cygpng12.dll" v0.0 ts=2003/8/10 17:35 170k 2002/01/21 C:\cygwin\bin\cygpng2.dll - os=4.0 img=1.0 sys=4.0 "cygpng2.dll" v0.0 ts=2002/1/20 19:05 22k 2002/06/09 C:\cygwin\bin\cygpopt-0.dll - os=4.0 img=1.0 sys=4.0 "cygpopt-0.dll" v0.0 ts=2002/6/9 0:45 17k 2001/06/28 C:\cygwin\bin\cyghistory4.dll - os=4.0 img=1.0 sys=4.0 "cyghistory4.dll" v0.0 ts=2001/1/6 22:34 108k 2001/06/28 C:\cygwin\bin\cygreadline4.dll - os=4.0 img=1.0 sys=4.0 "cygreadline4.dll" v0.0 ts=2001/1/6 22:34 29k 2003/08/10 C:\cygwin\bin\cyghistory5.dll - os=4.0 img=1.0 sys=4.0 "cyghistory5.dll" v0.0 ts=2003/8/10 18:16 148k 2003/08/10 C:\cygwin\bin\cygreadline5.dll - os=4.0 img=1.0 sys=4.0 "cygreadline5.dll" v0.0 ts=2003/8/10 18:16 281k 2003/02/24 C:\cygwin\bin\cygtiff3.dll - os=4.0 img=1.0 sys=4.0 "cygtiff3.dll" v0.0 ts=2003/2/23 22:58 282k 2003/08/11 C:\cygwin\bin\cygtiff4.dll - os=4.0 img=1.0 sys=4.0 "cygtiff4.dll" v0.0 ts=2003/8/10 21:32 25k 2002/07/14 C:\cygwin\bin\cygungif-4.dll - os=4.0 img=1.0 sys=4.0 "cygungif-4.dll" v0.0 ts=2002/7/14 9:58 2689k 2002/11/16 C:\cygwin\bin\cygxerces-c21.dll - os=4.0 img=1.0 sys=4.0 "cygxerces-c21.dll" v0.0 ts=2002/11/15 22:07 2984k 2003/02/07 C:\cygwin\bin\cygxerces-c22.dll - os=4.0 img=1.0 sys=4.0 "cygxerces-c22.dll" v0.0 ts=2003/2/7 12:50 3006k 2003/10/12 C:\cygwin\bin\cygxerces-c23.dll - os=4.0 img=1.0 sys=4.0 "cygxerces-c23.dll" v0.0 ts=2003/10/11 21:36 1074k 2003/09/23 C:\cygwin\bin\cygxml2-2.dll - os=4.0 img=1.0 sys=4.0 "cygxml2-2.dll" v0.0 ts=2003/9/23 12:52 64k 2003/09/23 C:\cygwin\bin\cygexslt-0.dll - os=4.0 img=1.0 sys=4.0 "cygexslt-0.dll" v0.0 ts=2003/9/23 14:13 196k 2003/09/23 C:\cygwin\bin\cygxslt-1.dll - os=4.0 img=1.0 sys=4.0 "cygxslt-1.dll" v0.0 ts=2003/9/23 13:58 7k 2003/09/23 C:\cygwin\bin\cygxsltbreakpoint-1.dll - os=4.0 img=1.0 sys=4.0 "cygxsltbreakpoint-1.dll" v0.0 ts=2003/9/23 14:06 271k 2003/10/06 C:\cygwin\bin\cygmhash-2.dll - os=4.0 img=1.0 sys=4.0 "cygmhash-2.dll" v0.0 ts=2003/10/6 10:23 457k 2003/10/11 C:\cygwin\bin\cygnaim_core-0.dll - os=4.0 img=1.0 sys=4.0 "cygnaim_core-0.dll" v0.0 ts=2003/10/11 12:25 842k 2003/09/30 C:\cygwin\bin\cygcrypto-0.9.7.dll - os=4.0 img=1.0 sys=4.0 "cygcrypto-0.9.7.dll" v0.0 ts=2003/9/30 11:49 171k 2003/09/30 C:\cygwin\bin\cygssl-0.9.7.dll - os=4.0 img=1.0 sys=4.0 "cygssl-0.9.7.dll" v0.0 ts=2003/9/30 11:49 645k 2003/04/11 C:\cygwin\bin\cygcrypto.dll - os=4.0 img=1.0 sys=4.0 "cygcrypto.dll" v0.0 ts=2003/4/11 5:37 165k 2003/04/11 C:\cygwin\bin\cygssl.dll - os=4.0 img=1.0 sys=4.0 "cygssl.dll" v0.0 ts=2003/4/11 5:37 1100k 2003/08/29 C:\cygwin\bin\cygperl5_8_0.dll - os=4.0 img=1.0 sys=4.0 "cygperl5_8_0.dll" v0.0 ts=2003/8/29 5:20 682k 2003/10/11 C:\cygwin\bin\cygruby18.dll - os=4.0 img=1.0 sys=4.0 "cygruby18.dll" v0.0 ts=2003/10/11 6:41 254k 2003/09/18 C:\cygwin\bin\cygtidy-0-99-0.dll - os=4.0 img=1.0 sys=4.0 "cygtidy-0-99-0.dll" v0.0 ts=2003/9/18 10:52 50k 2003/08/09 C:\cygwin\bin\cygXpm-noX4.dll - os=4.0 img=1.0 sys=4.0 "cygXpm-noX4.dll" v0.0 ts=2003/8/9 2:21 54k 2003/08/09 C:\cygwin\bin\cygXpm-X4.dll - os=4.0 img=1.0 sys=4.0 "cygXpm-X4.dll" v0.0 ts=2003/8/9 2:22 60k 2003/08/09 C:\cygwin\bin\cygz.dll - os=4.0 img=1.0 sys=4.0 "cygz.dll" v0.0 ts=2003/8/9 1:28 949k 2003/09/20 C:\cygwin\bin\cygwin1.dll - os=4.0 img=1.0 sys=4.0 "cygwin1.dll" v0.0 ts=2003/9/20 15:31 Cygwin DLL version info: DLL version: 1.5.5 DLL epoch: 19 DLL bad signal mask: 19005 DLL old termios: 5 DLL malloc env: 28 API major: 0 API minor: 94 Shared data: 3 DLL identifier: cygwin1 Mount registry: 2 Cygnus registry name: Cygnus Solutions Cygwin registry name: Cygwin Program options name: Program Options Cygwin mount registry name: mounts v2 Cygdrive flags: cygdrive flags Cygdrive prefix: cygdrive prefix Cygdrive default prefix: Build date: Sat Sep 20 16:31:15 EDT 2003 CVS tag: cr-0x9b Shared id: cygwin1S3 41k 2002/05/14 C:\cygwin\usr\X11R6\bin\cygPropList-0.dll - os=4.0 img=1.0 sys=4.0 "cygPropList-0.dll" v0.0 ts=2002/5/13 22:13 281k 2003/10/21 C:\cygwin\usr\X11R6\bin\cygXaw3d-7.dll - os=4.0 img=1.0 sys=4.0 "cygXaw3d-7.dll" v0.0 ts=2003/10/21 1:07 339k 2003/10/17 C:\cygwin\usr\X11R6\bin\cygdps-1.dll - os=4.0 img=1.0 sys=4.0 "cygdps-1.dll" v0.0 ts=2003/10/16 23:09 176k 2003/10/17 C:\cygwin\usr\X11R6\bin\cygdpstk-1.dll - os=4.0 img=1.0 sys=4.0 "cygdpstk-1.dll" v0.0 ts=2003/10/16 23:09 167k 2003/10/17 C:\cygwin\usr\X11R6\bin\cygfontconfig-1.dll - os=4.0 img=1.0 sys=4.0 "cygfontconfig-1.dll" v0.0 ts=2003/10/16 23:11 333k 2003/10/17 C:\cygwin\usr\X11R6\bin\cygfreetype-9.dll - os=4.0 img=1.0 sys=4.0 "cygfreetype-9.dll" v0.0 ts=2003/10/16 23:10 509k 2003/10/17 C:\cygwin\usr\X11R6\bin\cygGL-1.dll - os=4.0 img=1.0 sys=4.0 "cygGL-1.dll" v0.0 ts=2003/10/16 23:07 558k 2003/10/17 C:\cygwin\usr\X11R6\bin\cygGLU-1.dll - os=4.0 img=1.0 sys=4.0 "cygGLU-1.dll" v0.0 ts=2003/10/16 23:08 104k 2003/10/17 C:\cygwin\usr\X11R6\bin\cygICE-6.dll - os=4.0 img=1.0 sys=4.0 "cygICE-6.dll" v0.0 ts=2003/10/16 22:58 18k 2003/10/17 C:\cygwin\usr\X11R6\bin\cygoldX-6.dll - os=4.0 img=1.0 sys=4.0 "cygoldX-6.dll" v0.0 ts=2003/10/16 22:58 1501k 2003/10/17 C:\cygwin\usr\X11R6\bin\cygOSMesa-4.dll - os=4.0 img=1.0 sys=4.0 "cygOSMesa-4.dll" v0.0 ts=2003/10/16 23:07 33k 2003/10/17 C:\cygwin\usr\X11R6\bin\cygpsres-1.dll - os=4.0 img=1.0 sys=4.0 "cygpsres-1.dll" v0.0 ts=2003/10/16 23:09 46k 2003/10/17 C:\cygwin\usr\X11R6\bin\cygSM-6.dll - os=4.0 img=1.0 sys=4.0 "cygSM-6.dll" v0.0 ts=2003/10/16 22:58 1063k 2003/10/17 C:\cygwin\usr\X11R6\bin\cygX11-6.dll - os=4.0 img=1.0 sys=4.0 "cygX11-6.dll" v0.0 ts=2003/10/16 22:58 561k 2003/10/17 C:\cygwin\usr\X11R6\bin\cygXaw-7.dll - os=4.0 img=1.0 sys=4.0 "cygXaw-7.dll" v0.0 ts=2003/10/16 23:01 60k 2003/10/17 C:\cygwin\usr\X11R6\bin\cygXcursor-1.dll - os=4.0 img=1.0 sys=4.0 "cygXcursor-1.dll" v0.0 ts=2003/10/16 23:12 75k 2003/10/17 C:\cygwin\usr\X11R6\bin\cygXext-6.dll - os=4.0 img=1.0 sys=4.0 "cygXext-6.dll" v0.0 ts=2003/10/16 22:58 90k 2003/10/17 C:\cygwin\usr\X11R6\bin\cygXft-1.dll - os=4.0 img=1.0 sys=4.0 "cygXft-1.dll" v0.0 ts=2003/10/16 23:11 111k 2003/10/17 C:\cygwin\usr\X11R6\bin\cygXft-2.dll - os=4.0 img=1.0 sys=4.0 "cygXft-2.dll" v0.0 ts=2003/10/16 23:11 45k 2003/10/17 C:\cygwin\usr\X11R6\bin\cygXi-6.dll - os=4.0 img=1.0 sys=4.0 "cygXi-6.dll" v0.0 ts=2003/10/16 23:02 122k 2003/10/17 C:\cygwin\usr\X11R6\bin\cygXmu-6.dll - os=4.0 img=1.0 sys=4.0 "cygXmu-6.dll" v0.0 ts=2003/10/16 23:00 21k 2003/10/17 C:\cygwin\usr\X11R6\bin\cygXmuu-1.dll - os=4.0 img=1.0 sys=4.0 "cygXmuu-1.dll" v0.0 ts=2003/10/16 23:00 51k 2003/10/17 C:\cygwin\usr\X11R6\bin\cygXp-6.dll - os=4.0 img=1.0 sys=4.0 "cygXp-6.dll" v0.0 ts=2003/10/16 23:02 76k 2003/10/17 C:\cygwin\usr\X11R6\bin\cygXpm-4.dll - os=4.0 img=1.0 sys=4.0 "cygXpm-4.dll" v0.0 ts=2003/10/16 23:00 25k 2003/10/17 C:\cygwin\usr\X11R6\bin\cygXrandr-2.dll - os=4.0 img=1.0 sys=4.0 "cygXrandr-2.dll" v0.0 ts=2003/10/16 23:11 41k 2003/10/17 C:\cygwin\usr\X11R6\bin\cygXrender-1.dll - os=4.0 img=1.0 sys=4.0 "cygXrender-1.dll" v0.0 ts=2003/10/16 23:10 376k 2003/10/17 C:\cygwin\usr\X11R6\bin\cygXt-6.dll - os=4.0 img=1.0 sys=4.0 "cygXt-6.dll" v0.0 ts=2003/10/16 22:59 44k 2003/10/17 C:\cygwin\usr\X11R6\bin\cygXTrap-6.dll - os=4.0 img=1.0 sys=4.0 "cygXTrap-6.dll" v0.0 ts=2003/10/16 23:11 31k 2003/10/17 C:\cygwin\usr\X11R6\bin\cygXtst-6.dll - os=4.0 img=1.0 sys=4.0 "cygXtst-6.dll" v0.0 ts=2003/10/16 23:02 26k 2003/10/17 C:\cygwin\usr\X11R6\bin\cygXv-1.dll - os=4.0 img=1.0 sys=4.0 "cygXv-1.dll" v0.0 ts=2003/10/16 23:03 Cygwin Package Information Last downloaded files to: C:\cygwin\installer\tmp2 Last downloaded files from: http://cygwin.mirrors.pair.com Package Version _update-info-dir 00221-1 a2ps 4.13-1 agetty 2.1-1 antiword 0.34-2 apache 1.3.24-5 ash 20031007-1 aspell 0.50.3-1 aspell-doc 0.50.3-1 aspell-en 0.51.0-1 astyle 1.15.3-3 autoconf 2.57a-1 autoconf-devel 2.57-2 autoconf-stable 2.13-5 automake 1.7.5a-1 automake-devel 1.7.6-2 automake-stable 1.4p5-6 base-files 2.6-1 base-passwd 1.1-1 bash 2.05b-16 bc 1.06-1 binutils 20030901-1 bison 20030307-1 byacc 1.9-1 bzip2 1.0.2-5 c-client 2002e-3 ccache 2.2-1 ccdoc 0.8.39-1 cgoban 1.9.14-1 check 0.8.4-1 chkconfig 1.2.24h-1 clear 1.0-1 clisp 2.31-2 cmake 1.8.1-1 cocom 0.995-1 compface 1.4-5 cpio 2.5-3 cron 3.0.1-11 crypt 1.1-1 ctags 5.5-4 curl 7.10.4-1 curl-devel 7.10.4-1 cvs 1.11.6-3 cygipc 2.02-1 cygrunsrv 0.96-2 cygutils 1.2.2-1 cygwin 1.5.5-1 cygwin-doc 1.3-6 db2 2.7.7-4 db3.1 3.1.17-2 db4.1 4.1.25-1 dejagnu 20021217-2 diffutils 2.8.4-1 docbook-xml42 4.2-1 docbook-xsl 1.62.4-1 doxygen 1.2.18-1 dpkg 1.10.4-2 ed 0.2-1 editrights 1.01-1 ELFIO 1.0.0-1 emacs 21.2-12 emacs-el 21.2-12 emacs-X11 21.2-12 enscript 1.6.3-3 exim 4.24-1 expat 1.95.6-2 expect 20030128-1 fetchmail 6.2.5-1 figlet 2.2-1 file 4.03-2 fileutils 4.1-2 findutils 4.1.7-4 flex 2.5.4a-3 fltk 1.1.4-1 fortune 1.8-2 fvwm 2.4.7-2 gawk 3.1.3-3 gcc 3.3.1-2 gcc-mingw 20030911-3 gdb 20030919-1 gdbm 1.8.3-7 gettext 0.12.1-3 gettext-devel 0.12.1-3 ghostscript 7.05-2 ghostscript-base 7.05-2 ghostscript-x11 7.05-2 gmp 4.1.2-1 gnugo 3.4-1 gnupg 1.2.2-3 gperf 2.7.2-1 grace 5.1.12-1 grep 2.5-1 groff 1.18.1-2 gsl 1.4-1 guile 1.6.4-12 guile-devel 1.6.4-12 guile-doc 1.6.4-12 gzip 1.3.5-1 indent 2.2.8-1 inetutils 1.3.2-25 initscripts 0.9-1 ioperm 0.4-1 irc 20010101-3 jbigkit 1.5-3 jgraph 8.3-1 jpeg 6b-11 keychain 1.9-1 less 381-1 lesstif 0.93.91-2 lftp 2.6.6-1 libaspell15 0.50.3-1 libbz2_0 1.0.2-1 libbz2_1 1.0.2-5 libcharset1 1.9.1-3 libdb2 2.7.7-4 libdb2-devel 2.7.7-4 libdb3.1 3.1.17-2 libdb3.1-devel 3.1.17-2 libdb4.1 4.1.25-1 libdb4.1-devel 4.1.25-1 libgdbm 1.8.0-5 libgdbm-devel 1.8.3-7 libgdbm3 1.8.3-3 libgdbm4 1.8.3-7 libgettextpo0 0.12.1-3 libguile12 1.6.4-12 libguile12abi13 1.6.4-2 libiconv 1.9.1-3 libiconv2 1.9.1-3 libintl 0.10.38-3 libintl1 0.10.40-1 libintl2 0.12.1-3 libjpeg62 6b-11 libjpeg6b 6b-8 libkpathsea3 2.0.2-13 libkpathsea3abi13 2.0.2-2 libltdl3 1.5-3 libmcrypt 2.5.7-2 libmcrypt-devel 2.5.7-2 libncurses-devel 5.3-4 libncurses5 5.2-1 libncurses6 5.2-8 libncurses7 5.3-4 libpcre 4.1-1 libpcre0 4.4-2 libpng 1.2.5-4 libpng10 1.0.15-4 libpng10-devel 1.0.15-4 libpng12 1.2.5-4 libpng12-devel 1.2.5-4 libpng2 1.0.12-1 libpopt0 1.6.4-4 libPropList 0.10.1-3 libreadline4 4.1-2 libreadline5 4.3-5 libtiff-devel 3.6.0-5 libtiff3 3.6.0-2 libtiff4 3.6.0-5 libtool 1.5a-1 libtool-devel 1.5-3 libtool-stable 1.4.3-2 libungif 4.1.0-2 libxerces-c21 2.1.0-1 libxerces-c22 2.2.0-1 libxerces-c23 2.3.0-4 libxml2 2.5.11-1 libxslt 1.0.33-1 lilypond 2.0.1-1 lilypond-doc 2.0.1-1 links 0.96-1 login 1.9-7 lynx 2.8.4-7 m4 1.4-1 make 3.80-1 man 1.5j-2 mc 4.6.0-4 mhash 0.8.18-1 mhash-devel 0.8.18-1 mingw-runtime 3.2-1 mingw-zlib 1.1.4-4 mktemp 1.5-3 mod_auth_mysql 1.11-1 mod_auth_ntsec 1.7-1 mod_dav 1.0.3-1.3.6-1 mod_php4 4.2.0-2 mod_ssl 2.8.8-1.3.24-1 more 2.11o-1 mt 2.0.1-2 mutt 1.4.1-1 naim 0.11.6.1-1 nano 1.2.2-1 nasm 0.98.38-1 ncftp 3.1.4-1 ncurses 5.3-4 ncurses-demo 5.3-4 netcat 1.10-2 openbox 0.99.1-3 opengl 1.1.0-6 openssh 3.7.1p2-1 openssl 0.9.7c-1 openssl-devel 0.9.7c-1 openssl096 0.9.6j-1 par 1.52-1 patch 2.5.8-8 patchutils 0.2.22-2 pcre 4.4-2 pcre-devel 4.4-2 pcre-doc 4.4-2 pdksh 5.2.14-2 perl 5.8.0-5 perl_manpages 5.8.0-5 pine 4.58-1 pinfo 0.6.8-1 pkgconfig 0.15.0-4 popt 1.6.4-4 postgresql 7.3.4-2 procmail 3.22-8 procps 010801-2 proftpd 1.2.9rc3-1 psutils 1.17-1 python 2.3.2-1 rcs 5.7-3 readline 4.3-5 rebase 2.2-3 robots 2.0-3 rpm 4.1-1 rpm-build 4.1-1 rpm-doc 4.1-1 rsync 2.5.6-2 ruby 1.8.0-2 rxvt 2.7.10-3 sed 4.0.7-3 setsid 0.0-3 sh-utils 2.0.15-4 sharutils 4.2.1-3 shutdown 1.4-1 splint 3.1.1-1 squid 2.4.STABLE7-1 ssmtp 2.38.7-4 stunnel 4.04-3 sunrpc 4.0-1 SWI-Prolog 5.2.6-1 swig 1.3.19-1 sysvinit 2.84-4 tar 1.13.25-3 tcltk 20030901-1 tcp_wrappers 7.6-1 tcsh 6.12.00-7 termcap 20021106-2 terminfo 5.3_20030726-1 tetex 2.0.2-13 tetex-base 2.0.2-13 tetex-bin 2.0.2-13 tetex-devel 2.0.2-13 tetex-doc 2.0.2-13 tetex-extra 2.0.2-13 tetex-tiny 2.0.2-13 tetex-x11 2.0.2-13 texinfo 4.2-4 textutils 2.0.21-1 tidy 030901-1 tiff 3.6.0-5 time 1.7-1 tin 1.6.1-1 transfig 3.2.4-1 ttcp 19980512-1 ucl 1.01-1 units 1.77-1 unzip 5.50-5 upx 1.24-1 uw-imap 2002e-3 uw-imap-imapd 2002e-3 uw-imap-util 2002e-3 vim 6.2.098-1 w32api 2.4-1 wget 1.8.2-2 which 1.5-2 whois 4.6.7-1 WindowMaker 0.80.0-2 wtf 0.0.4-4 x2x 1.27-2 Xaw3d 1.5D-2 xerces-c 2.3.0-4 xerces-c-devel 2.3.0-4 xerces-c-doc 2.3.0-4 xfig-base 3.2.4-1 xfig-bin 3.2.4-2 xfig-doc 3.2.4-1 xfig-etc 3.2.4-3 xfig-lib 3.2.4-2 xfig-man 3.2.4-1 XFree86-base 4.3.0-1 XFree86-bin 4.3.0-5 XFree86-bin-icons 4.3.0-5 XFree86-doc 4.3.0-1 XFree86-etc 4.3.0-3 XFree86-f100 4.2.0-3 XFree86-fcyr 4.2.0-3 XFree86-fenc 4.2.0-3 XFree86-fnts 4.2.0-3 XFree86-fscl 4.2.0-3 XFree86-fsrv 4.3.0-4 XFree86-html 4.3.0-1 XFree86-jdoc 4.3.0-1 XFree86-lib 4.3.0-1 XFree86-lib-compat 4.3.0-1 XFree86-man 4.3.0-2 XFree86-nest 4.3.0-3 XFree86-prog 4.3.0-8 XFree86-prt 4.3.0-3 XFree86-ps 4.3.0-1 XFree86-startup-scripts 4.2.0-5 XFree86-vfb 4.3.0-3 XFree86-xserv 4.3.0-20 XFree86-xwinclip 4.3.0-1 xgraph 12.1-1 xinetd 2.3.9-1 xmlto 0.0.14-1 xpm-nox 4.2.0-4 zip 2.3-5 zlib 1.1.4-4 zsh 4.1.1-1 Use -h to see help about each section -- John From Cary.Jamison@powerquest.com Wed Nov 5 20:42:00 2003 From: Cary.Jamison@powerquest.com (Cary Jamison) Date: Wed, 05 Nov 2003 20:42:00 -0000 Subject: Default Mouse Pointer is Wrong Message-ID: "Ricky Boone" wrote in message news:<1068044377.32617.1.camel@whiplash.planetfurry.com>... > On Wed, 2003-11-05 at 09:37, Yadin Y. Goldschmidt wrote: > > Colin Harrison suggested long time ago to add the following line to the end > > of your startxwin.bat file: > > xsetroot -cursor_name left_ptr -fg white -bg black > > This will change the default mouse from an x to a white arrow. > > Ah ha, that did the trick. My apologies, I didn't even notice the > suggestion when I searched for it. -.-;; > > Thanks for the help. :) I've noticed this too, but haven't complained about it. I didn't realize the problem was specific to the -multiwindow window manager. If this is true, than -multiwindow is not behaving as expected nor as other window managers behave wrt default cursors. The xsetroot is a work-around, but it seems to me this should be regarded as a bug in the window manager. The 'X' should be the default cursor when over the root window but an arrow when over an application window. Since -multiwindow doesn't really have a visible root window, it seems like permanently changing the default cursor to a pointer would be a good/quick solution. My $.02 Cary From huntharo@msu.edu Wed Nov 5 20:48:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Wed, 05 Nov 2003 20:48:00 -0000 Subject: Default Mouse Pointer is Wrong In-Reply-To: References: Message-ID: <3FA96216.70706@msu.edu> Cary Jamison wrote: > "Ricky Boone" wrote in message > news:<1068044377.32617.1.camel@whiplash.planetfurry.com>... > >>On Wed, 2003-11-05 at 09:37, Yadin Y. Goldschmidt wrote: >> >>>Colin Harrison suggested long time ago to add the following line to > > the end > >>>of your startxwin.bat file: >>>xsetroot -cursor_name left_ptr -fg white -bg black >>>This will change the default mouse from an x to a white arrow. >> >>Ah ha, that did the trick. My apologies, I didn't even notice the >>suggestion when I searched for it. -.-;; >> >>Thanks for the help. :) > > > I've noticed this too, but haven't complained about it. I didn't > realize the problem was specific to the -multiwindow window manager. This isn't a problem. It is "the way it works". > If this is true, than -multiwindow is not behaving as expected nor as > other window managers behave wrt default cursors. The xsetroot is a > work-around, but it seems to me this should be regarded as a bug in the > window manager. The 'X' should be the default cursor when over the root > window but an arrow when over an application window. Since -multiwindow > doesn't really have a visible root window, it seems like permanently > changing the default cursor to a pointer would be a good/quick solution. Fine. Run 'twm' as your window manager. Doesn't it do the same exact thing? That is the way that I have been reading the emails... if that is not the case, then could somebody please describe this better.? The solution you propose is not trivial. That is why this is "the way it works" and not a bug. I'm sure that upon further inspection you would figure out that trying to change this policy would result in the creation of a mouse-cursor over-riding policy that is a lot more complicated than what you think it would be. I'm pretty sure that it would be complicated enough that it isn't worth looking into. Of course, feel free to code me into submission. Harold From huntharo@msu.edu Wed Nov 5 21:22:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Wed, 05 Nov 2003 21:22:00 -0000 Subject: Patch for keyboard handling In-Reply-To: <20031104175955.34AB.MURAKAMI@ipl.t.u-tokyo.ac.jp> References: <20031103163010.840F.MURAKAMI@ipl.t.u-tokyo.ac.jp> <3FA71169.7060805@msu.edu> <20031104175955.34AB.MURAKAMI@ipl.t.u-tokyo.ac.jp> Message-ID: <3FA96A30.8090005@msu.edu> Takuma, Takuma Murakami wrote: > I agree with you. If the mi event queue has pending > events when winRestoreModeKeyStates is called, it may > fail to synchronize mode key states between XWin and > Windows. However, the new code can re-sync them at > the next time winRestoreModeKeyStates is called while > it is hard to do for the old code. Okay. > Thank you for your suggestion. mieqProcessInputEvents > seems to do the work. I inserted a code to call it > and it looks working well for now, though I don't sure > if it is legal to call it from the place other than > ProcessInputEvents. > > The attached is a revised patch to call the function. > I deeply appreciate your feedback. Looks good, but I think you are right about some danger in calling mieqProcessInputEvents. Hmm... the problem with calling ProcessInputEvents or mieqProcessInputEvents from our keyboard processing is that it causes input events to be processed one at a time, instead of in a queue. It completely negates the purpose of having an input queue in the X layer. I think I understand your original patch better now and I think that you were probably doing it correctly, but I can't verify that right now. If this is what you were trying to do, then it probably is correct: 1) Assume that no keyboard input is in the mi queue when winWindowProc is called. 2) If we are getting the keyboard focus, grab the Windows mode key state and X mode key state, compare them, and send fake key presses to X to get the two states in synch. 3) Do not synch the key states anywhere else. That would probably work because it would enqueue key messages that will synch the mode key states before placing normal key messages in the queue. Thus, when we ask X for the mode key states we should get a consistent result since the input queue in X is empty. Does that sound like what you were trying to do initially? I got confused because I couldn't keep track of where all the calls to winRestoreModeKeyStates would up. Let me know, Harold From tron.thomas@verizon.net Thu Nov 6 02:43:00 2003 From: tron.thomas@verizon.net (Tron Thomas) Date: Thu, 06 Nov 2003 02:43:00 -0000 Subject: No extern "C" for XFree86 OpenGL headers Message-ID: <3FA9B53D.5030207@verizon.net> The XFree86 versions of the OpenGL headers files do not use extern "C" when compiling C++ modules. This can result in linking errors as OpenGL function receive decorated signatures that won't exist in the libraries. A work around is for a developer to do something like the following in a C++ code module: #ifdef __cplusplus extern "C" { #include } #endif which shouldn't normally be necessary as other implementations of OpenGL do not require this. From huntharo@msu.edu Thu Nov 6 05:24:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Thu, 06 Nov 2003 05:24:00 -0000 Subject: No extern "C" for XFree86 OpenGL headers In-Reply-To: <3FA9B53D.5030207@verizon.net> References: <3FA9B53D.5030207@verizon.net> Message-ID: <3FA9DB18.2090208@msu.edu> This is out of the blue. Could you give a little more context to what you are trying to do? Harold Tron Thomas wrote: > The XFree86 versions of the OpenGL headers files do not use extern "C" > when compiling C++ modules. This can result in linking errors as OpenGL > function receive decorated signatures that won't exist in the libraries. > > A work around is for a developer to do something like the following in a > C++ code module: > #ifdef __cplusplus > extern "C" { > #include > } > #endif > > which shouldn't normally be necessary as other implementations of OpenGL > do not require this. > > > From murakami@ipl.t.u-tokyo.ac.jp Thu Nov 6 05:26:00 2003 From: murakami@ipl.t.u-tokyo.ac.jp (Takuma Murakami) Date: Thu, 06 Nov 2003 05:26:00 -0000 Subject: Define a foreign language keyboard in HP-Ux CDE? In-Reply-To: <3FA8FA66.6030200@juntadeandalucia.es> References: <3FA29EBE.9080803@msu.edu> <3FA8FA66.6030200@juntadeandalucia.es> Message-ID: <20031106142504.C327.MURAKAMI@ipl.t.u-tokyo.ac.jp> Hans, The latest XWin includes the keyboard auto-detection. Without any XF86Config files or xmodmap mappings it loads a default es layout for you. It may be good to disable CDE (and any other) keyboard setting and let XWin do the work entirely. Takuma Murakami (murakami@ipl.t.u-tokyo.ac.jp) From hans.dekker.ext@juntadeandalucia.es Thu Nov 6 07:14:00 2003 From: hans.dekker.ext@juntadeandalucia.es (Hans Dekker) Date: Thu, 06 Nov 2003 07:14:00 -0000 Subject: Define a foreign language keyboard in HP-Ux CDE, with the AltGr key? References: <3FA29EBE.9080803@msu.edu> <3FA8FA66.6030200@juntadeandalucia.es> <20031106142504.C327.MURAKAMI@ipl.t.u-tokyo.ac.jp> Message-ID: <3FA9F4B4.706@juntadeandalucia.es> Thank you Takuma, I saw there is a big improvement since the latest version. Only I don't get the AltGr key working well. It is unclear to me whether it is XFree, CDE, or X-Windows.... regards, Hans. Takuma Murakami escribi??: > Hans, > > The latest XWin includes the keyboard auto-detection. > Without any XF86Config files or xmodmap mappings > it loads a default es layout for you. > > It may be good to disable CDE (and any other) keyboard > setting and let XWin do the work entirely. > > Takuma Murakami (murakami@ipl.t.u-tokyo.ac.jp) > > > . > From murakami@ipl.t.u-tokyo.ac.jp Thu Nov 6 08:44:00 2003 From: murakami@ipl.t.u-tokyo.ac.jp (Takuma Murakami) Date: Thu, 06 Nov 2003 08:44:00 -0000 Subject: Define a foreign language keyboard in HP-Ux CDE, with the AltGr key? In-Reply-To: <3FA9F4B4.706@juntadeandalucia.es> References: <20031106142504.C327.MURAKAMI@ipl.t.u-tokyo.ac.jp> <3FA9F4B4.706@juntadeandalucia.es> Message-ID: <20031106173454.C32E.MURAKAMI@ipl.t.u-tokyo.ac.jp> Hans, > I saw there is a big improvement since the latest version. Only I don't > get the AltGr key working well. It is unclear to me whether it is XFree, > CDE, or X-Windows.... Unfortunately I don't know how the AltGr key should work since the key does not exist in Japanese keyboards. To check where the problem resides, double-click C:\cygwin\usr\X11R6\bin\startxwin.bat and try the invoked xterm. If the keyboard is correct on the xterm, the trouble is the CDE side. Takuma Murakami (murakami@ipl.t.u-tokyo.ac.jp) From vervoom@hotmail.com Thu Nov 6 09:05:00 2003 From: vervoom@hotmail.com (J S) Date: Thu, 06 Nov 2003 09:05:00 -0000 Subject: [XFree86] screen redraw problem Message-ID: Thanks Mark, Unfortunately that didn't make any difference. > > Maybe your app is expecting backing store. You can start XFree86 >with backing store "startx -- +bs". > > Mark. > >On Wed, 5 Nov 2003, J S wrote: > > > Is there anymore information I need to add to this post? I would really >like > > to get some help with it. The logs don't seem to be showing anything. >I've > > tried setting different color depths, and screen resolutions but to no > > avail. > > > > Hi, > > > > I have an application which has some boxes in the window. The window >itself > > is scrollable. When I scroll down - no problem, but when I scroll up >the > > boxes turn into long vertical bars. This problem doesn't happen with >Exceed, > > but on XFree86 (both Linux XFree86 and Cygwin-XFree) it does. > > > > Can anyone advise me whether this is a bug, or is there some setting I >need > > to add? Let me know if you need anymore information. > > > > Thanks for any help. > > > > JS. > > > > _________________________________________________________________ > > Stay in touch with absent friends - get MSN Messenger > > http://www.msn.co.uk/messenger > > > > _______________________________________________ > > XFree86 mailing list > > XFree86@XFree86.Org > > http://XFree86.Org/mailman/listinfo/xfree86 > > > _________________________________________________________________ Sign-up for a FREE BT Broadband connection today! http://www.msn.co.uk/specials/btbroadband From hans.dekker.ext@juntadeandalucia.es Thu Nov 6 09:23:00 2003 From: hans.dekker.ext@juntadeandalucia.es (Hans Dekker) Date: Thu, 06 Nov 2003 09:23:00 -0000 Subject: Define a foreign language keyboard in HP-Ux CDE, with the AltGr key? References: <20031106142504.C327.MURAKAMI@ipl.t.u-tokyo.ac.jp> <3FA9F4B4.706@juntadeandalucia.es> <20031106173454.C32E.MURAKAMI@ipl.t.u-tokyo.ac.jp> Message-ID: <3FAA12D2.9050309@juntadeandalucia.es> Hi Takuma, I tried Xterm and there is works OK. As I read the documentation on the usage of xdmcp to start a CDE environment, changing the XF86Config should be working, however I didn't find how to do it in the case of a Spanish keyboard. What is the auto detection option you are talking about? I guessed already a Japanese keyboard would be totally different and therefore it??s more interesting to hear it works all right with you. Hans. Takuma Murakami escribi??: > Hans, > > >>I saw there is a big improvement since the latest version. Only I don't >>get the AltGr key working well. It is unclear to me whether it is XFree, >>CDE, or X-Windows.... > > > Unfortunately I don't know how the AltGr key should work > since the key does not exist in Japanese keyboards. > > To check where the problem resides, double-click > C:\cygwin\usr\X11R6\bin\startxwin.bat and try the > invoked xterm. If the keyboard is correct on the xterm, > the trouble is the CDE side. > > Takuma Murakami (murakami@ipl.t.u-tokyo.ac.jp) > > > . > From alexander.gottwald@s1999.tu-chemnitz.de Thu Nov 6 09:38:00 2003 From: alexander.gottwald@s1999.tu-chemnitz.de (Alexander Gottwald) Date: Thu, 06 Nov 2003 09:38:00 -0000 Subject: Define a foreign language keyboard in HP-Ux CDE, with the AltGr key? In-Reply-To: <3FAA12D2.9050309@juntadeandalucia.es> References: <20031106142504.C327.MURAKAMI@ipl.t.u-tokyo.ac.jp> <3FA9F4B4.706@juntadeandalucia.es> <20031106173454.C32E.MURAKAMI@ipl.t.u-tokyo.ac.jp> <3FAA12D2.9050309@juntadeandalucia.es> Message-ID: On Thu, 6 Nov 2003, Hans Dekker wrote: > Hi Takuma, > > I tried Xterm and there is works OK. As I read the documentation on the > usage of xdmcp to start a CDE environment, changing the XF86Config > should be working, however I didn't find how to do it in the case of a > Spanish keyboard. > > What is the auto detection option you are talking about? The autodetection changes the layout according to the layout used in windows. This can be overridden in the XF86Config file but this not needed in most cases. If the layout is correct with startxwin.bat then it is also loaded with xdmcp. Maybe CDE does load a wrong modmap? Can you try xev and press Alt-Gr? For me it reports the following. KeyPress event, serial 22, synthetic NO, window 0x1600001, root 0x3a, subw 0x1600002, time 1891239428, (55,39), root:(136,215), state 0x0, keycode 113 (keysym 0xfe03, ISO_Level3_Shift), same_screen YES, XLookupString gives 0 characters: "" KeyRelease event, serial 27, synthetic NO, window 0x1600001, root 0x3a, subw 0x1600002, time 1891239498, (55,39), root:(136,215), state 0x80, keycode 113 (keysym 0xfe03, ISO_Level3_Shift), same_screen YES, XLookupString gives 0 characters: "" bye ago -- Alexander.Gottwald@s1999.tu-chemnitz.de http://www.gotti.org ICQ: 126018723 From vervoom@hotmail.com Thu Nov 6 14:16:00 2003 From: vervoom@hotmail.com (J S) Date: Thu, 06 Nov 2003 14:16:00 -0000 Subject: screen redraw problem Message-ID: Ha ! OK I'll try to be that guy! What's the best way to do this? Recompile XWin with the -g flag? Is there anything to change in the Makefile? Haven't done this before so would appreciate any pointers. Thanks a lot. >JS, > >Looks like you have found a generic problem with X or one of the libraries >you are using. It is going to take a lot of debugging... you are going to >have to be that guy. > >Harold > >J S wrote: > >>Is there anymore information I need to add to this post? I would really >>like to get some help with it. The logs don't seem to be showing anything. >>I've tried setting different color depths, and screen resolutions but to >>no avail. >> >>Hi, >> >>I have an application which has some boxes in the window. The window >>itself >>is scrollable. When I scroll down - no problem, but when I scroll up the >>boxes turn into long vertical bars. This problem doesn't happen with >>Exceed, >>but on XFree86 (both Linux XFree86 and Cygwin-XFree) it does. >> >>Can anyone advise me whether this is a bug, or is there some setting I >>need >>to add? Let me know if you need anymore information. >> >>Thanks for any help. >> >>JS. >> >>_________________________________________________________________ >>Stay in touch with absent friends - get MSN Messenger >>http://www.msn.co.uk/messenger >> > _________________________________________________________________ It's fast, it's easy and it's free. Get MSN Messenger today! http://www.msn.co.uk/messenger From hans.dekker.ext@juntadeandalucia.es Thu Nov 6 14:30:00 2003 From: hans.dekker.ext@juntadeandalucia.es (Hans Dekker) Date: Thu, 06 Nov 2003 14:30:00 -0000 Subject: Define a foreign language keyboard in HP-Ux CDE, with the AltGr key? References: <20031106142504.C327.MURAKAMI@ipl.t.u-tokyo.ac.jp> <3FA9F4B4.706@juntadeandalucia.es> <20031106173454.C32E.MURAKAMI@ipl.t.u-tokyo.ac.jp> <3FAA12D2.9050309@juntadeandalucia.es> Message-ID: <3FAA5AED.1060706@juntadeandalucia.es> Hi, Using startxwin.bat and xev, gives me the following: KeyPress event, serial 22, synthetic NO, window 0x800001, root 0x3a, subw 0x0, time 25294468, (167,-13), root:(627,587), state 0x10, keycode 113 (keysym 0xfe03, ISO_Level3_Shift), same_screen YES, XLookupString gives 0 characters: "" KeyPress event, serial 22, synthetic NO, window 0x800001, root 0x3a, subw 0x0, time 25294531, (167,-13), root:(627,587), state 0x90, keycode 113 (keysym 0xfe03, ISO_Level3_Shift), same_screen YES, XLookupString gives 0 characters: "" and AltGr is working well on this one. Unfortunately I don't have xev running on the HP-UX box... Not only CDE has the behaviour of not using AltGr, but another X-application I use as well. Hope it helps. Regards, Hans. Alexander Gottwald escribi??: > On Thu, 6 Nov 2003, Hans Dekker wrote: > > >>Hi Takuma, >> >>I tried Xterm and there is works OK. As I read the documentation on the >>usage of xdmcp to start a CDE environment, changing the XF86Config >>should be working, however I didn't find how to do it in the case of a >>Spanish keyboard. >> >>What is the auto detection option you are talking about? > > > The autodetection changes the layout according to the layout used in > windows. This can be overridden in the XF86Config file but this not > needed in most cases. > > If the layout is correct with startxwin.bat then it is also loaded with > xdmcp. Maybe CDE does load a wrong modmap? > > Can you try xev and press Alt-Gr? > > For me it reports the following. > > KeyPress event, serial 22, synthetic NO, window 0x1600001, > root 0x3a, subw 0x1600002, time 1891239428, (55,39), root:(136,215), > state 0x0, keycode 113 (keysym 0xfe03, ISO_Level3_Shift), same_screen YES, > XLookupString gives 0 characters: "" > > KeyRelease event, serial 27, synthetic NO, window 0x1600001, > root 0x3a, subw 0x1600002, time 1891239498, (55,39), root:(136,215), > state 0x80, keycode 113 (keysym 0xfe03, ISO_Level3_Shift), same_screen YES, > XLookupString gives 0 characters: "" > > bye > ago From huntharo@msu.edu Thu Nov 6 15:27:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Thu, 06 Nov 2003 15:27:00 -0000 Subject: screen redraw problem In-Reply-To: References: Message-ID: <3FAA6859.5050209@msu.edu> JS, Start here: http://xfree86.cygwin.com/docs/cg/prog-obtaining-source.html Then read how to compile: http://xfree86.cygwin.com/docs/cg/prog-build-native.html Notice that towards the bottom of the above section it tells how to do a "Standard Build" and a "Debug Build". The debug build uses the "makeg" script, so you don't have to edit any Imakefiles or config files. Finally, read how to move your current X installation safely out of the way before installing your local build: http://xfree86.cygwin.com/docs/cg/prog-build-native.html#prog-compiling-install As an absolute last step, if you created a host.def file that said not to build fonts (look at xf86site.def for an example), then you need to cut and paste C:\cygwin\usr\X11R6_suffix\lib\X11\fonts to C:\cygwin\usr\X11R6\lib\X11\fonts. Cutting and pasting is an instantaneous operation. Copying the files would take up to an hour, as there are around 20,000 font files. Just be sure that you cut and paste that fonts folder into another folder before you delete one of your test installations. You don't want to end up deleting that folder... you would be in a world of hurt. Harold J S wrote: > Ha ! OK I'll try to be that guy! What's the best way to do this? > Recompile XWin with the -g flag? Is there anything to change in the > Makefile? Haven't done this before so would appreciate any pointers. > > Thanks a lot. > > > >> JS, >> >> Looks like you have found a generic problem with X or one of the >> libraries you are using. It is going to take a lot of debugging... >> you are going to have to be that guy. >> >> Harold >> >> J S wrote: >> >>> Is there anymore information I need to add to this post? I would >>> really like to get some help with it. The logs don't seem to be >>> showing anything. I've tried setting different color depths, and >>> screen resolutions but to no avail. >>> >>> Hi, >>> >>> I have an application which has some boxes in the window. The window >>> itself >>> is scrollable. When I scroll down - no problem, but when I scroll up >>> the >>> boxes turn into long vertical bars. This problem doesn't happen with >>> Exceed, >>> but on XFree86 (both Linux XFree86 and Cygwin-XFree) it does. >>> >>> Can anyone advise me whether this is a bug, or is there some setting >>> I need >>> to add? Let me know if you need anymore information. >>> >>> Thanks for any help. >>> >>> JS. >>> >>> _________________________________________________________________ >>> Stay in touch with absent friends - get MSN Messenger >>> http://www.msn.co.uk/messenger >>> >> > > _________________________________________________________________ > It's fast, it's easy and it's free. Get MSN Messenger today! > http://www.msn.co.uk/messenger > From Cary.Jamison@powerquest.com Thu Nov 6 21:42:00 2003 From: Cary.Jamison@powerquest.com (Cary Jamison) Date: Thu, 06 Nov 2003 21:42:00 -0000 Subject: Default Mouse Pointer is Wrong Message-ID: "Harold L Hunt II" wrote in message news:<3FA96216.70706@msu.edu>... > Cary Jamison wrote: > > > I've noticed this too, but haven't complained about it. I didn't > > realize the problem was specific to the -multiwindow window manager. > > This isn't a problem. It is "the way it works". > > > If this is true, than -multiwindow is not behaving as expected nor as > > other window managers behave wrt default cursors. The xsetroot is a > > work-around, but it seems to me this should be regarded as a bug in the > > window manager. The 'X' should be the default cursor when over the root > > window but an arrow when over an application window. Since -multiwindow > > doesn't really have a visible root window, it seems like permanently > > changing the default cursor to a pointer would be a good/quick solution. > > Fine. Run 'twm' as your window manager. Doesn't it do the same exact > thing? That is the way that I have been reading the emails... if that > is not the case, then could somebody please describe this better.? No, it behaves as I described earlier. Let me try again. There is an 'X' over the root window, but when over an application window the X changes to an arrow. I realize that an application may define its own pointers, but when it doesn't -multiwindows goes back to an 'X' and twm goes to a black arrow. For example : XWin& twm& xclock& When the pointer is over the clock, it is a black arrow. When over the background it is an 'X'. XWin -multiwindow& xclock& When the pointer is over the clock it is an 'X'. There is no background window. I notice this in other apps as well. For example, on the scroll-bar of a gnome-terminal window displayed from my Linux box. This is where it gets annoying, because you have to point with the center of the X instead of the tip of an arrow. So, in essence most window managers have two default pointers - one when over an app and one when over the background. (Perhaps the window manager only has one default pointer and uses the X server's default pointer when not over a managed window?) >From the history of XWin it is easy to see that there was originally only a need for one default pointer. When the internal window manager got added, it still only has one pointer. However, since there is no background root window having one pointer is sufficient since it can be the app default pointer (an arrow) instead of the background default pointer (an X). > The solution you propose is not trivial. That is why this is "the way > it works" and not a bug. I'm sure that upon further inspection you > would figure out that trying to change this policy would result in the > creation of a mouse-cursor over-riding policy that is a lot more > complicated than what you think it would be. I'm pretty sure that it > would be complicated enough that it isn't worth looking into. Of > course, feel free to code me into submission. You may be right, since I haven't looked at the code yet. The default should be changeable through resource files, etc., so to do it right may not be as simple as adding a line of code in the internal window manager to change it. Does the internal window manager handle any resources at all, yet? There probably hasn't been a need to define any. The workaround of setting it in the startup file isn't bad, but it would be nice to get it changed right for the newbies, etc. Maybe as a minimum the xsetroot command could be added with appropriate comments to the startup file. Here's even a psuedo-diff for you :-) + REM Set default cursor - normally only useful with -multiwindow window manager + run xsetroot -cursor_name left_ptr -fg white -bg black I'm not making any promises, but my work-load should lighten up in a couple weeks and I may be able to have a look at this then. > Harold Cary From fcoudert@gmx.net Thu Nov 6 23:31:00 2003 From: fcoudert@gmx.net (Fabrice Coudert) Date: Thu, 06 Nov 2003 23:31:00 -0000 Subject: no key input In-Reply-To: <3FA2A032.5020401@msu.edu> References: <00b101c39a71$b2759c60$7b05000a@corp.silverbacksystems.com> <3FA25F00.5090605@gmx.net> <3FA2A032.5020401@msu.edu> Message-ID: <3FAAD9B7.4060407@gmx.net> After more investigation this bug appears when shared build of libXaw, libXmu and libXt was enabled in the CVS (http://cvsweb.xfree86.org/cvsweb/xc/config/cf/cygwin.rules.diff?r1=3.26&r2=3.27). Xterm works fine if I build the latest HEAD branch with cygwin.rules rev. 3.26. Now what is the real problem with those libraries ? Any clues will be appreciated. Fabrice. From wpwang.eic88g@nctu.edu.tw Fri Nov 7 08:20:00 2003 From: wpwang.eic88g@nctu.edu.tw (=?big5?B?pP2k5burLm5jdHU=?=) Date: Fri, 07 Nov 2003 08:20:00 -0000 Subject: Fw: "1.5.5-1: question about used ultraedit in cygwin( os: winxp)" Message-ID: <002401c3a507$e44b4c80$42dea8c0@wpwang> Hi All: I used ultraedit ( uedit32 ) in cygwin's bashell. But the bashell return some message as follow. $ uedit32 [Settings]: not found Language: not found Could you help me to solve it? Thank you! wpwang From murakami@ipl.t.u-tokyo.ac.jp Fri Nov 7 09:57:00 2003 From: murakami@ipl.t.u-tokyo.ac.jp (Takuma Murakami) Date: Fri, 07 Nov 2003 09:57:00 -0000 Subject: Patch for keyboard handling In-Reply-To: <3FA96A30.8090005@msu.edu> References: <20031104175955.34AB.MURAKAMI@ipl.t.u-tokyo.ac.jp> <3FA96A30.8090005@msu.edu> Message-ID: <20031107180424.4406.MURAKAMI@ipl.t.u-tokyo.ac.jp> Harold, > I think I understand your original patch better now and I think that you > were probably doing it correctly, but I can't verify that right now. If > this is what you were trying to do, then it probably is correct: > > 1) Assume that no keyboard input is in the mi queue when winWindowProc > is called. > > 2) If we are getting the keyboard focus, grab the Windows mode key state > and X mode key state, compare them, and send fake key presses to X to > get the two states in synch. > > 3) Do not synch the key states anywhere else. > > That would probably work because it would enqueue key messages that will > synch the mode key states before placing normal key messages in the > queue. Thus, when we ask X for the mode key states we should get a > consistent result since the input queue in X is empty. The all points are right. I think you completely understand this patch. The essential difference between the old code and this patch is to remember states by ourselves or to peek in the internal states if necessary. Moreover, the old code refers the states of Windows which is not guaranteed to same as the XWin's states. Hence I believe the patch is, at least, not worse than the old code, though there remains some incompleteness. One is the event queue you told, another is cooperation with customized keyboards. > Does that sound like what you were trying to do initially? I got > confused because I couldn't keep track of where all the calls to > winRestoreModeKeyStates would up. winRestoreModeKeyStates is called from WM_SETFOCUS handlers in winTopLevelWindowProc (in -multiwindow case) and winWindowProc (in other cases). Only 2 places. I hope this helps your review. Takuma Murakami (murakami@ipl.t.u-tokyo.ac.jp) From vervoom@hotmail.com Fri Nov 7 12:42:00 2003 From: vervoom@hotmail.com (J S) Date: Fri, 07 Nov 2003 12:42:00 -0000 Subject: screen redraw problem Message-ID: Harold, Many thanks for email. I have created an XFree debug build now and a symbolic link from /usr/X11R6_suffix/lib/X11/fonts to /usr/X11R6/lib/X11/fonts. In order to debug this though, what's the best approach? For example, should I use any flags on the xwin command line? Do you use gdb to do the debugging? If so, could you just give me a clue as to where I might want to set the breakpoint given the nature of the problem? Sorry to ask for spoon-feeding on this!! Thanks again though. JS. >JS, > >Start here: >http://xfree86.cygwin.com/docs/cg/prog-obtaining-source.html > >Then read how to compile: >http://xfree86.cygwin.com/docs/cg/prog-build-native.html > >Notice that towards the bottom of the above section it tells how to do a >"Standard Build" and a "Debug Build". The debug build uses the "makeg" >script, so you don't have to edit any Imakefiles or config files. > >Finally, read how to move your current X installation safely out of the way >before installing your local build: >http://xfree86.cygwin.com/docs/cg/prog-build-native.html#prog-compiling-install > >As an absolute last step, if you created a host.def file that said not to >build fonts (look at xf86site.def for an example), then you need to cut and >paste C:\cygwin\usr\X11R6_suffix\lib\X11\fonts to >C:\cygwin\usr\X11R6\lib\X11\fonts. Cutting and pasting is an instantaneous >operation. Copying the files would take up to an hour, as there are around >20,000 font files. Just be sure that you cut and paste that fonts folder >into another folder before you delete one of your test installations. You >don't want to end up deleting that folder... you would be in a world of >hurt. > >Harold > >J S wrote: > >>Ha ! OK I'll try to be that guy! What's the best way to do this? Recompile >>XWin with the -g flag? Is there anything to change in the Makefile? >>Haven't done this before so would appreciate any pointers. >> >>Thanks a lot. >> >> >> >>>JS, >>> >>>Looks like you have found a generic problem with X or one of the >>>libraries you are using. It is going to take a lot of debugging... you >>>are going to have to be that guy. >>> >>>Harold >>> >>>J S wrote: >>> >>>>Is there anymore information I need to add to this post? I would really >>>>like to get some help with it. The logs don't seem to be showing >>>>anything. I've tried setting different color depths, and screen >>>>resolutions but to no avail. >>>> >>>>Hi, >>>> >>>>I have an application which has some boxes in the window. The window >>>>itself >>>>is scrollable. When I scroll down - no problem, but when I scroll up >>>>the >>>>boxes turn into long vertical bars. This problem doesn't happen with >>>>Exceed, >>>>but on XFree86 (both Linux XFree86 and Cygwin-XFree) it does. >>>> >>>>Can anyone advise me whether this is a bug, or is there some setting I >>>>need >>>>to add? Let me know if you need anymore information. >>>> >>>>Thanks for any help. >>>> >>>>JS. >>>> >>>>_________________________________________________________________ >>>>Stay in touch with absent friends - get MSN Messenger >>>>http://www.msn.co.uk/messenger >>>> >>> >> >>_________________________________________________________________ >>It's fast, it's easy and it's free. Get MSN Messenger today! >>http://www.msn.co.uk/messenger >> > _________________________________________________________________ Hotmail messages direct to your mobile phone http://www.msn.co.uk/msnmobile From sb@dod.no Fri Nov 7 13:12:00 2003 From: sb@dod.no (Steinar Bang) Date: Fri, 07 Nov 2003 13:12:00 -0000 Subject: xinit: The application has failed to start because cygfreetype-6.dll was not found. References: <3FA142F1.5030604@msu.edu> <3FA4921D.40102@rbcmail.ru> <3FA5496D.2090708@msu.edu> Message-ID: <87brro4924.fsf@home.lan> >>>>> Harold L Hunt II : (I'm not Constantine, but I see the same problem) > However, I want to know what application was failing in your xinit > scripts. There should not be an application that requires > cygfreetype-9.dll in the default script. Have you modified your > script? Yes. I've added two xterms doing an ssh -X into linux boxes I always work on, and there is a sleep between each xterm start. > What program are you launching that requires this DLL? The dialog that pops up, has the title: XWin.exe - Unable To Locate DLL > Are you launching emacs? No. I did the update today. From sb@dod.no Fri Nov 7 14:31:00 2003 From: sb@dod.no (Steinar Bang) Date: Fri, 07 Nov 2003 14:31:00 -0000 Subject: xinit: The application has failed to start because cygfreetype-6.dll was not found. References: <3FA142F1.5030604@msu.edu> <3FA4921D.40102@rbcmail.ru> <3FA5496D.2090708@msu.edu> <87brro4924.fsf@home.lan> Message-ID: <87vfpw2qu6.fsf@home.lan> >>>>> Steinar Bang : >>>>> Harold L Hunt II : >> However, I want to know what application was failing in your xinit >> scripts. There should not be an application that requires >> cygfreetype-9.dll in the default script. [snip!] >> What program are you launching that requires this DLL? > The dialog that pops up, has the title: > XWin.exe - Unable To Locate DLL [snip!] > I did the update today. The version of XFree86-xserv is 4.3.0-21. The version of XFree86-lib-compat is 4.3.0-2, with no available upgrade candidates. From huntharo@msu.edu Fri Nov 7 17:40:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Fri, 07 Nov 2003 17:40:00 -0000 Subject: xinit: The application has failed to start because cygfreetype-6.dll was not found. In-Reply-To: <87brro4924.fsf@home.lan> References: <3FA142F1.5030604@msu.edu> <3FA4921D.40102@rbcmail.ru> <3FA5496D.2090708@msu.edu> <87brro4924.fsf@home.lan> Message-ID: <3FABD910.1000508@msu.edu> Steinar, You need the libfreetype26 package, which is gotten by selecting the freetype2 package. It should have been automatically selected, but it looks like it wasn't in your case. Also, make sure that you have the fontconfig package (it auto-selects libfontconfig0). Harold Steinar Bang wrote: >>>>>>Harold L Hunt II : > > > (I'm not Constantine, but I see the same problem) > >>However, I want to know what application was failing in your xinit >>scripts. There should not be an application that requires >>cygfreetype-9.dll in the default script. Have you modified your >>script? > > > Yes. > > I've added two xterms doing an ssh -X into linux boxes I always work > on, and there is a sleep between each xterm start. > > >>What program are you launching that requires this DLL? > > > The dialog that pops up, has the title: > XWin.exe - Unable To Locate DLL > > >>Are you launching emacs? > > > No. > > I did the update today. > From huntharo@msu.edu Fri Nov 7 17:44:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Fri, 07 Nov 2003 17:44:00 -0000 Subject: screen redraw problem In-Reply-To: References: Message-ID: <3FABDA11.2030806@msu.edu> JS, J S wrote: > Harold, > > Many thanks for email. I have created an XFree debug build now and a > symbolic link from /usr/X11R6_suffix/lib/X11/fonts to > /usr/X11R6/lib/X11/fonts. That is a good idea. I never thought of just creating a symlink. Doh! > In order to debug this though, what's the best approach? > For example, should I use any flags on the xwin command line? Do you use > gdb to do the debugging? If so, could you just give me a clue as to > where I might want to set the breakpoint given the nature of the problem? Boy... this is really tough to say. I think you're going to have to look at the client code (to understand what happens when the window is scrolled), the Xlib code (to understand what it does when the window is scrolled), and the server code (to see whether the requested operation is successful and performed correctly). Actually, a good first start would be some experimentation with your app (assuming you have the source and it compiles on Cygwin/X): 1) Compile the app against the Cygwin/X libs and headers. 2) Run the app under XWin.exe (you have done this, I know). 3) Run the app under Exceed (you said you did this too). At this point, it is still linked to our libs, so correct operation would mean the problem is in XWin.exe, not in Xlib. 4) If you have access to Solaris machines that are running Sun's X Server, recompile the app on them and launch it locally. Also, launch the app through ssh and display it in XWin.exe. Proper display on Solaris when run locally would be interesting. Proper display in XWin.exe would mean that the app is probably using Xlib in a slightly broken manner which works for some platforms but not all platforms. In that case, it will be better to fix the app. The next steps after this are to read the code as I described above and figure out where to stick your breakpoint. I can't really tell you more than that since I don't know what functions your code is calling (and I don't have your code). You should be able to figure it out. Feel free to continue asking questions. Harold From alanh@fairlite.demon.co.uk Fri Nov 7 17:51:00 2003 From: alanh@fairlite.demon.co.uk (Alan Hourihane) Date: Fri, 07 Nov 2003 17:51:00 -0000 Subject: screen redraw problem In-Reply-To: References: Message-ID: <20031107175045.GF1923@fairlite.demon.co.uk> JS, Can you tell us about the application - is it available anywhere so I can take a look too ? Alan. From vervoom@hotmail.com Fri Nov 7 21:13:00 2003 From: vervoom@hotmail.com (J S) Date: Fri, 07 Nov 2003 21:13:00 -0000 Subject: screen redraw problem Message-ID: Hi Alan, I wish I could. It's a legacy application used by my work called ISIS which runs on an old VAX system (not an OS I'm really familiar with). I don't think it's written in-house either, so getting the source code is probably a no-no too. In fact, the same applies to most X apps we have at my work! I'll check it out on Monday though. Thanks for your interest. JS. >JS, > >Can you tell us about the application - is it available anywhere so I >can take a look too ? > >Alan. _________________________________________________________________ Express yourself with cool emoticons - download MSN Messenger today! http://www.msn.co.uk/messenger From m.l.kloosterman@planet.nl Sun Nov 9 11:25:00 2003 From: m.l.kloosterman@planet.nl (Marcel Kloosterman) Date: Sun, 09 Nov 2003 11:25:00 -0000 Subject: Fwd: Window Maker 0.80.1 Message-ID: <6.0.0.22.0.20031109121853.01affc38@pop.planet.nl> >Hi, > >I don't know if I'm at the correct address. >I installed cygwin yesterday with Window Maker 0.80.1. First everything >was OK, but now I have the following problem: > I dont see all the icons/buttons within the window Maker > Preferences (wprefs) >I made some screenshots so you can see what I mean. >I couldn't find anything on the internet. I reinstalled the program >several times but it won't help. Can you please help me ! > >Regards, > > Marcel -------------- next part -------------- A non-text attachment was scrubbed... Name: Capture2.jpg Type: image/jpeg Size: 32955 bytes Desc: not available URL: -------------- next part -------------- --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.537 / Virus Database: 332 - Release Date: 6-11-2003 From ahmed.sule2@laposte.net Sun Nov 9 21:47:00 2003 From: ahmed.sule2@laposte.net (AHMED SULE.) Date: Sun, 09 Nov 2003 21:47:00 -0000 Subject: PARTNER NEEDED. Message-ID: 2 Adefobi Street, Ikoyi Island,Ikoyi Island. Email:ahmed.sule@laposte.net. IFax:17752648168 ATTN:THE PRESIDENT/CEO FROM:AHMEDSULE. Dear Sir, I would like to firstly send to you the best wishes of good health and success in your pursuits particularly through my proposal as contained in this letter. Before going into details of my proposal to you, I must first implore you to treat with the utmost confidentiality as this is required for its success and to have faith in this transaction, for opportunities like this only comes to one once in a life time. My colleagues and I are senior officials of the Federal Government of my country's Contracts Review Panel (CRP) who are interested in diverting some funds that are presently floating in the accounts of the Apex Bank of my country. In order to commence this transaction, we solicit for your assistance to enable us transfer into your nominated account the said floating funds. We are determined to conclude the transfer before the end of this quarter of 2003. The source of the funds are as follows: During the last military regime in my country, government officials set up companies and awarded themselves contracts that were grossly over-invoiced in various ministries and parastatals.The present civilian government set up the Contract Review Panel, which has the mandate to use the instruments of payments made available to it Announcement ============ The XFree86-xserv-4.3.0-22 package has been updated in the Cygwin distribution. Links ===== Server source, direct link: http://www.msu.edu/~huntharo/xwin/server/xwin-20031109-1622.tar.bz2 (130 KiB) xc/programs/Xserver/hw/xwin (all files) diff against 4.3.0-20 source code: http://www.msu.edu/~huntharo/xwin/server/xwin-4.3.0-20-to-4.3.0-22.diff (17 KiB) Changes ======= 1) win.h, winkeybd.c, winmultiwindowwndproc.c, winwndproc.c - Remove winStoreModeKeyStates () function and stop storing mode key state within the hw/xwin layer. Instead, query the internal X Server mode key state, when we know that no key press/release events are pending, and send key press/release events to get that state in sync with the Windows mode key states. This removes the possibility that the hw/xwin and internal X Server mode key state vectors would get out of sync. This is also a general cleanup that utilizes more existing code and removes some Cygwin-specific code. (Takuma Murakami) 2) winwndproc.c - Catch WM_ENDSESSION message and perform clean shutdown. (Takuma Murakami) 3) winwndproc.c - WM_*KEYDOWN - Discard key presses generated from Windows auto-repeat (these sorts of auto-repeats are handled by X). (Takuma Murakami) 4) winmouse.c - Remap mouse buttons here when XFree86Server and XINPUT are defined, since this combination of flags prevents a lower layer from performing such remapping. The end result is that remapping mouse buttons works for the first time. (Takuma Murakami) 5) winconfig.c - Load the US keyboard layout for Japanese keyboards. This ensures that WM_KEYUP messages are sent for the Caps Lock key. (Takuma Murakami, Kensuke Matsuzaki) 6) win.h, winengine.c, winmultiwindowwindow.c, winmultiwindowwm.c, winpfbdd.c, winshaddd.c, winshadddnl.c, winshadgdi.c, winwindow.h - Add an engine-specific function that is called after a Windows-window is created in -multiwindow mode. This is a start for adding DirectDraw support to -multiwindow mode. However, I got a little confused here and thought that one primary surface would need to be created per window, which is not correct. There will be one primary surface with a clip list that causes blits to stay within the region of all of our visible windows. In any case, this is a step in the right direction. There code is currently disabled since the engine setting code only allows the GDI engine when -multiwindow is being used. (Harold L Hunt II) -- Harold Hunt To update your installation, click on the "Install Cygwin now" link on the http://cygwin.com/ web page. This downloads setup.exe to your system. Once you've downloaded setup.exe, run it and select "XFree86" and then click on the appropriate field until the above announced version number appears if it is not displayed already. If your mirror doesn't yet have the latest version of this package after 24 hours, you can either continue to wait for that site to be updated or you can try to find another mirror. Please send questions or comments to the Cygwin/X mailing list at: cygwin-xfree@cygwin.com If you want to subscribe go to: http://cygwin.com/ml/cygwin-xfree/ I would appreciate if you would use this mailing list rather than emailing me directly. This includes ideas and comments about the setup utility or Cygwin/X in general. If you want to make a point or ask a question the Cygwin/X mailing list is the appropriate place. From kdwoell@comcast.net Sun Nov 9 23:22:00 2003 From: kdwoell@comcast.net (kirk woellert) Date: Sun, 09 Nov 2003 23:22:00 -0000 Subject: XWin works on Win2K but not on some WinXP clients Message-ID: <00d301c3a718$61170c60$6501a8c0@kirklaptop> My co-worker has been using Cygwin XFree86 to XWin to his linux system from his Win2K client. Very cool. He convinced me to start using Cygwin. So I think it would be cool to be able to have our two WinXP clients XWin to our department server with RedHat 9 Linux. I meticulously followed the linux doc project "how to" on configuring a Xwin Host. I have configured font server on the linux host. My co-worker's Win2K box can Xwin to the linux box just fine (gets a login prompt, and then the linux desktop). However, we the two WinXP boxes that can't. We get the checkerboard screen and no login prompt everytime. All Win boxes were set up with a full install of Cygwin (install all, not default). All Win boxes are the same hardware configuration, so the only difference I can discern is a different OS. My co-worker insists that although he has been using Cygwin for months, he did not do any special configuration on his Win2K box. What gives? The command used on all clients is the same in each case XWin -querry or XWin :0 -querry There is tons of docs on how to set up the host, but very little on the client. The implication being that its simple stupid and there is not a lot of configuration needed to be done. I even downloaded a third party XWindows client StarNet X-Win32. It has lots of fancy menus that let you specify querry, indirect, broadcast etc. None of those modes allow the WinXP boxes to connect, my co-worker can XWin into his Linux system and our department linux server all day long. I'm at ropes end, anyone have suggestions? The mail archives don't seem to address the peculiar situation where some people can login and some can't. From alexander.gottwald@s1999.tu-chemnitz.de Mon Nov 10 11:03:00 2003 From: alexander.gottwald@s1999.tu-chemnitz.de (Alexander Gottwald) Date: Mon, 10 Nov 2003 11:03:00 -0000 Subject: XWin works on Win2K but not on some WinXP clients In-Reply-To: <00d301c3a718$61170c60$6501a8c0@kirklaptop> References: <00d301c3a718$61170c60$6501a8c0@kirklaptop> Message-ID: On Sun, 9 Nov 2003, kirk woellert wrote: > XWin -querry or > > XWin :0 -querry Is this a typo? It must be -query (only one 'r') bye ago -- Alexander.Gottwald@s1999.tu-chemnitz.de http://www.gotti.org ICQ: 126018723 From fridger.schrempp@desy.de Mon Nov 10 13:58:00 2003 From: fridger.schrempp@desy.de (Fridger Schrempp) Date: Mon, 10 Nov 2003 13:58:00 -0000 Subject: TTF-font rendering not working anymore Message-ID: After the recent XFree86-freetype2-fontconfig upgrade of Oct 29, the rendering of TTF fonts does not work anymore for me. My TTF fonts are still listed correctly e.g. with 'xlsfonts' but /not/ displayed on screen anymore e.g. with 'xfontsel', 'xfd'... Also xterm continues to work fine, e.g. 'xterm -fa "Luxi Mono" -fs 16' produces correct anti-aliased fonts. My Cygwin (XFree86) installation is up-to-date. Fridger From jase@dufair.org Mon Nov 10 15:20:00 2003 From: jase@dufair.org (Jason Dufair) Date: Mon, 10 Nov 2003 15:20:00 -0000 Subject: multiplemonitors Message-ID: I just put a 2nd video card in my Win2K PC so that both of my monitors are running at 1280x1024x32bpp. The primary is an ATI RADEON 7500 AGP and the secondary is an ATI AIW 128 PCI. When I run start XWin -multiwindow -clipboard -multiplemonitors I get the following in /tmp/XWin.log winScreenInit - Monitors do not all have same pixel format / display depth. Using primary display only. I know they're running the same display depth. What's pixel format? I also notice in my Device Manager that I have a "Microsoft SMS Mirror Driver" (this is my work PC). Relevant packages include: (just ran setup.exe a few minutes ago and let it update everything) XFree86-base 4.3.0-1 XFree86-bin 4.3.0-7 XFree86-etc 4.3.0-5 XFree86-fenc 4.2.0-3 XFree86-fnts 4.2.0-3 XFree86-lib 4.3.0-1 XFree86-lib-compat 4.3.0-2 XFree86-startup-scripts 4.2.0-5 XFree86-xserv 4.3.0-22 Any ideas as to why -multiplemonitors isn't working? -- Jason Dufair - jase@dufair.org http://www.dufair.org/ <+kritical> christin: you need to learn how to figure out stuff yourself.. <+Christin1> how do i do that From kirk.woellert@ngc.com Mon Nov 10 15:26:00 2003 From: kirk.woellert@ngc.com (Woellert, Kirk D.) Date: Mon, 10 Nov 2003 15:26:00 -0000 Subject: XWin works on Win2K but not on some WinXP clients Message-ID: Yeah, its a typo. The command we have been using is: XWin -query or XWin :0 -query Kirk Woellert From alexander.gottwald@s1999.tu-chemnitz.de Mon Nov 10 16:15:00 2003 From: alexander.gottwald@s1999.tu-chemnitz.de (Alexander Gottwald) Date: Mon, 10 Nov 2003 16:15:00 -0000 Subject: XWin works on Win2K but not on some WinXP clients In-Reply-To: References: Message-ID: On Mon, 10 Nov 2003, Woellert, Kirk D. wrote: > Yeah, its a typo. The command we have been using is: > > XWin -query or > > XWin :0 -query Have you tried XWin -query -from else send the /tmp/XWin.log file bye ago -- Alexander.Gottwald@s1999.tu-chemnitz.de http://www.gotti.org ICQ: 126018723 From peter@jollys.org Mon Nov 10 16:18:00 2003 From: peter@jollys.org (Peter Jolly) Date: Mon, 10 Nov 2003 16:18:00 -0000 Subject: Fw: "1.5.5-1: question about used ultraedit in cygwin( os: winxp)" Message-ID: <6.0.0.22.0.20031110161649.0280c558@mail.purplecloud.net> >I used ultraedit ( uedit32 ) in cygwin's bashell. >But the bashell return some message as follow. > >$ uedit32 >[Settings]: not found >Language: not found Type "uedit32.exe" instead of just "uedit32". HTH Peter From evenson@panix.com Mon Nov 10 17:30:00 2003 From: evenson@panix.com (Mark Evenson) Date: Mon, 10 Nov 2003 17:30:00 -0000 Subject: Keyboard focus problem + scrambled icons in wmaker with latest release References: Message-ID: Danilo Turina writes: > Hello, > I'm running the latest version of Cygwin, XFree and > WindowMaker (from mirrors.rcn.net, but I also tried mirrors.sunsite.dk > and mirrors.kernel.org) in my WinXP Pro workstation and I have the > following problems: > > 1) when I move my mouse outside a xterm windows the keyboard > focus is lost by that window and is re-taken when I get back to that > window with the mouse pointer. [...] > 2) this morning I ran setup and I downloaded the latest > modifications to Xwinclip, XFree86-bin, etc. From that point on, some > of the icons of wmaker are "scrambled", in particular the icons that > represents terminals and the icons of the "Window Maker Preferences > Utility", [...] Same symptoms here, with attached 'cygcheck.out'. -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: cygcheck.out URL: From kirk.woellert@ngc.com Mon Nov 10 19:17:00 2003 From: kirk.woellert@ngc.com (Woellert, Kirk D.) Date: Mon, 10 Nov 2003 19:17:00 -0000 Subject: XWin works on Win2K but not on some WinXP clients Message-ID: I tried the command: XWin -query -from No luck. BTW, is there more to do on the client side than merely install the full Cygwin (and hence full XFree86 package)? Again, maybe I missed something. Here is the log file from one of the WinXP machines. FYI, the guy that can connect has the same hardware configuration, he just happens to be on Win2K. I see some msgs that look funny, but nothing that I recall from the docs that point to an issue. ddxProcessArgument - Initializing default screens winInitializeDefaultScreens - w 1280 h 1024 winInitializeDefaultScreens - Returning OsVendorInit - Creating bogus screen 0 _XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root (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 0000001f InitOutput - g_iNumScreens: 1 iMaxConsecutiveScreen: 1 winSetEngine - Using Shadow DirectDraw NonLocking winAdjustVideoModeShadowDDNL - 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 994 1280 winAdjustForAutoHide - Adjusted WorkArea: 0 0 994 1280 winCreateBoundingWindowWindowed - WindowClient w 1274 h 962 r 1274 l 0 b 962 t 0 winCreateBoundingWindowWindowed - Returning winCreatePrimarySurfaceShadowDDNL - Creating primary surface winCreatePrimarySurfaceShadowDDNL - Created primary surface winCreatePrimarySurfaceShadowDDNL - Attached clipper to primary surface winAllocateFBShadowDDNL - lPitch: 5096 winAllocateFBShadowDDNL - Created shadow pitch: 5096 winAllocateFBShadowDDNL - Created shadow stride: 1274 winFinishScreenInitFB - Masks: 00ff0000 0000ff00 000000ff winInitVisualsShadowDDNL - Masks 00ff0000 0000ff00 000000ff BPRGB 8 d 24 bpp 32 winCreateDefColormap - Deferring to fbCreateDefColormap () winFinishScreenInitFB - returning winScreenInit - returning InitOutput - Returning. MIT-SHM extension disabled due to lack of kernel support XFree86-Bigfont extension local-client optimization disabled due to lack of shared memory support in the kernel (==) winConfigKeyboard - Layout: "00000409" (00000409) (EE) No primary keyboard configured (==) Using compiletime defaults for keyboard Rules = "xfree86" Model = "pc101" Layout = "us" Variant = "(null)" Options = "(null)" winPointerWarpCursor - Discarding first warp: 637 481 winBlockHandler - Releasing pmServerStarted winBlockHandler - pthread_mutex_unlock () returned winDeinitClipboard - Noting shutdown in progress winDeinitMultiWindowWM - Noting shutdown in progress winDeinitClipboard - Noting shutdown in progress winDeinitMultiWindowWM - Noting shutdown in progress winDeinitMultiWindowWM - Noting shutdown in progress winDeinitClipboard - Noting shutdown in progress winDeinitMultiWindowWM - Noting shutdown in progress From huntharo@msu.edu Mon Nov 10 19:36:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Mon, 10 Nov 2003 19:36:00 -0000 Subject: XWin works on Win2K but not on some WinXP clients In-Reply-To: References: Message-ID: <3FAFE8B8.4070500@msu.edu> Kirk, Woellert, Kirk D. wrote: > I tried the command: > > XWin -query -from > No luck. > BTW, is there more to do on the client side than merely install the full > Cygwin (and hence full XFree86 package)? Again, maybe I missed something. > Here is the log file from one of the WinXP machines. FYI, the guy that can > connect has the same hardware configuration, he just happens to be on Win2K. > I see some msgs that look funny, but nothing that I recall from the docs > that point to an issue. No, nothing special needs to be done for an installation. Do the machines have more than one network interface, perhaps two ethernet connections (e.g. 1x100 Mbit, 1x1000Mbit), or perhaps wired and wireless, or bluetooth? Anything like that? The reason is that you have to tell the "-from ip" parameter the actualy ip that XWin.exe is attempting to connect on. So, if you have more than one ip you must tell it the correct ip for the proper interface. Are you the admin of the linux machine? If so, try running kdm/gdm/xdm with verbose output and/or checking the log messages on the machine. You need to figure out if the linux server is actively rejecting the connection or not even getting an attempt in the first place. Another consideration would be that since your "old" computers work and your "new" computers don't work, then maybe you've got the linux machine setup to reject xdm connections from any machines not in a list and that list has not been updated to include the new machines. Have you reported yet on whether you can ssh into the box and tunnel apps back to your machines that cannot login to XDM directly? That would at least confirm that networking between the two boxes is reasonably stable. Hope that helps, Harold From penne296@netscape.net Mon Nov 10 20:30:00 2003 From: penne296@netscape.net (mike) Date: Mon, 10 Nov 2003 20:30:00 -0000 Subject: no icons on kde and no menu text on ooffice 1.1 Message-ID: When i do an X -query to my debian unstable box everything goes fine but if i lunch a kde app no icons are displayed. also ooffice menus are not displayed. if i use a linux box insteaf of cygwin everything is ok mike From Alexander.Gottwald@s1999.tu-chemnitz.de Mon Nov 10 21:27:00 2003 From: Alexander.Gottwald@s1999.tu-chemnitz.de (Alexander Gottwald) Date: Mon, 10 Nov 2003 21:27:00 -0000 Subject: XWin works on Win2K but not on some WinXP clients In-Reply-To: References: Message-ID: Woellert, Kirk D. wrote: > MIT-SHM extension disabled due to lack of kernel support > XFree86-Bigfont extension local-client optimization disabled due to lack of > shared memory support in the kernel > (==) winConfigKeyboard - Layout: "00000409" (00000409) > (EE) No primary keyboard configured > (==) Using compiletime defaults for keyboard > Rules = "xfree86" Model = "pc101" Layout = "us" Variant = "(null)" Options = > "(null)" > winPointerWarpCursor - Discarding first warp: 637 481 > winBlockHandler - Releasing pmServerStarted > winBlockHandler - pthread_mutex_unlock () returned > winDeinitClipboard - Noting shutdown in progress > winDeinitMultiWindowWM - Noting shutdown in progress > winDeinitClipboard - Noting shutdown in progress > winDeinitMultiWindowWM - Noting shutdown in progress > winDeinitMultiWindowWM - Noting shutdown in progress > winDeinitClipboard - Noting shutdown in progress > winDeinitMultiWindowWM - Noting shutdown in progress There is no evidence why xdmcp failed. Is a firewall (even the winxp builtin) present? Can you check the xdm logfiles on the server? Maybe they contain some information why you can't get access. @Harold: Are the winDeinitClipboard and -MultiWindowWM messages ok? I assume they are called even if the -multiwindow and -clipboard parameters are not supplied. NP: Enya - Shepherd Moons -- Alexander.Gottwald@informatik.tu-chemnitz.de http://www.gotti.org ICQ: 126018723 From primorec@sbcglobal.net Mon Nov 10 21:41:00 2003 From: primorec@sbcglobal.net (Igor) Date: Mon, 10 Nov 2003 21:41:00 -0000 Subject: cygwin/X in the ENTERPRISE environment Message-ID: <3FB003B8.3010505@sbcglobal.net> Hi ALL, Let's firstly introduce myself. I am IC designer in one of the big semiconductor company, here, in Silicon Valley, We are in process to migrate from SUN workstations to "something_else". The main reason for this change is COST REDUCTION ( aka saving money ) We have two options. One option is "LINUX workstation" and the another is "WIN XP + X11 emulator". Very likely we will use BOTH. Engineering community will use (mostly) LINUX and product/test guys will use WIN XP. Of course, I would like that ALL technical people use LINUX... but this will not happen (as it seems right now) So, I've proposed to our WINDOWS team to try XP+cygwin/X (as X11 emulator. We WERE thinking to use EXCEED or "starnet" product ( I do not recall the name of their product). EXCEED is very expensive, "starnet" is cheaper but is not capable to run CAD tools (CADENCE in particular). CADENCE require 8-bit pseudo color . I was told that EXCEED has the same problem. BUT my experience is different. I've seen CADENCE running on WIN2000+EXCEED on "el_cheapo" video card. So, I really do not know where is the truth. BUT, on other hand, I've seen CADENCE running on WIN XP through "cygwin/X". Again, I do not know what kind of VIDEO card was used. So, my FIRST QUESTION for you is: Can "cygwin/X" run CADENCE tools ? (reminder: it requires 8-bit pseudo color map) Management asked another question. So, my SECOND QUESTION is: - beside price, what are the features of the "cygwin/X" ? (compared to exceed and starnet) I could not find on "cygwin/X" site FEATURE LIST. THIRD QUESTION (asked by management) the most important !! - is there a list of companies who use "cygwin/X" in their production flow ? FOURTH QUESTION: - is there "some_kind" of official support for "cygwin/X" ? ( REDHAT comes in mind) I would really appreciate your reply Sincerely Igor From kirk.woellert@ngc.com Mon Nov 10 22:42:00 2003 From: kirk.woellert@ngc.com (Woellert, Kirk D.) Date: Mon, 10 Nov 2003 22:42:00 -0000 Subject: XWin works on Win2K but not on some WinXP clients Message-ID: True/False: The linux box in this case is the "X server" and the WinXP boxes are the "X hosts" Where does one specify which client(s) can be allowed to talk to the Linux box? The WinXP firewalls on both systems in question are not enabled. From Alexander.Gottwald@s1999.tu-chemnitz.de Mon Nov 10 23:31:00 2003 From: Alexander.Gottwald@s1999.tu-chemnitz.de (Alexander Gottwald) Date: Mon, 10 Nov 2003 23:31:00 -0000 Subject: XWin works on Win2K but not on some WinXP clients In-Reply-To: References: Message-ID: Woellert, Kirk D. wrote: > True/False: The linux box in this case is the "X server" and the WinXP boxes > are the "X hosts" The "X Server" is the program which renders the windows and graphic. Which is XWin for windows, XFree for linux or XSun for Solaris. The "X Client" is any program which uses the rendering services of the "X Server" eg. xterm, xclock, mozilla or mplayer just to name a few. What you are most likely referring to is the XDMCP server. This is a login server for the X11 Environment. It allows you to login and starts a session with "X Clients" which let the "X Server" render their output. > Where does one specify which client(s) can be allowed to talk to the Linux > box? for xdm and kdm this is /etc/X11/xdm/Xaccess bye ago NW: Die ?rzte -- Alexander.Gottwald@informatik.tu-chemnitz.de http://www.gotti.org ICQ: 126018723 From jp64zeqf@aol.com Tue Nov 11 06:16:00 2003 From: jp64zeqf@aol.com (Dena Woodruff) Date: Tue, 11 Nov 2003 06:16:00 -0000 Subject: Amazing New Digita1 Cab1e Descramb1er p gw Message-ID: <96rm-$m-$1ozh6j9$$---9e0$-f07@g1q0.44f> Un1ock your cab1e. Here is how. http://www.xmas4cheap.net/cable3/ No further information. http://www.xmas4cheap.net/b.htm jygtb cyt gukmpo yrdcphw cea r lg qjzyi qqbhvfpvg From tulitanssi@luukku.com Tue Nov 11 11:10:00 2003 From: tulitanssi@luukku.com (tulitanssi@luukku.com) Date: Tue, 11 Nov 2003 11:10:00 -0000 Subject: Updated: XFree86-xserv-4.3.0-22 Message-ID: <1068549020528.tulitanssi.36802.w1Q4NRjiTPWoQQzb3m7sWA@luukku.com> Hi all, keyboard repeat does not work anymore with this new update. I think it worked with the previous (4.3.0-21) release. Any ideas? I'm using win2k. Thanks, Tuli ............................................................ Maksuton s?hk?posti aina k?yt?ss? http://luukku.com Kuukausimaksuton MTV3 Internet-liittym? www.mtv3.fi/liittyma From roters@mpie.de Tue Nov 11 11:55:00 2003 From: roters@mpie.de (Franz Roters) Date: Tue, 11 Nov 2003 11:55:00 -0000 Subject: Define a foreign language keyboard in HP-Ux CDE, with the AltGrkey? Message-ID: <3FB0DC48.6081.EA223B@localhost> Hi all, I encounter the same problem. However, the Alt-Gr key works when I am using Exceed to log in. Therefore I do not belief its a problem with the HP machine. The Alt-Gr key also works in the cygwin bash for me. Regards Franz > Hi, > > Using startxwin.bat and xev, gives me the following: > > KeyPress event, serial 22, synthetic NO, window 0x800001, > root 0x3a, subw 0x0, time 25294468, (167,-13), root:(627,587), > state 0x10, keycode 113 (keysym 0xfe03, ISO_Level3_Shift), same_screen > YES, XLookupString gives 0 characters: "" > > KeyPress event, serial 22, synthetic NO, window 0x800001, > root 0x3a, subw 0x0, time 25294531, (167,-13), root:(627,587), > state 0x90, keycode 113 (keysym 0xfe03, ISO_Level3_Shift), same_screen > YES, XLookupString gives 0 characters: "" > > and AltGr is working well on this one. > > Unfortunately I don't have xev running on the HP-UX box... > > Not only CDE has the behaviour of not using AltGr, but another > X-application I use as well. > > Hope it helps. > > Regards, Hans. > > Alexander Gottwald escribi?: > > On Thu, 6 Nov 2003, Hans Dekker wrote: > > > Hi Takuma, > > I tried Xterm and there is works OK. As I read the documentation > on the usage of xdmcp to start a CDE environment, changing the > XF86Config should be working, however I didn't find how to do it > in the case of a Spanish keyboard. > > What is the auto detection option you are talking about? > > > > The autodetection changes the layout according to the layout used in > windows. This can be overridden in the XF86Config file but this not > needed in most cases. > > > If the layout is correct with startxwin.bat then it is also loaded with > xdmcp. Maybe CDE does load a wrong modmap? > > > Can you try xev and press Alt-Gr? > > For me it reports the following. > > KeyPress event, serial 22, synthetic NO, window 0x1600001, > root 0x3a, subw 0x1600002, time 1891239428, (55,39), root:(136,215), > state 0x0, keycode 113 (keysym 0xfe03, ISO_Level3_Shift), same_screen > YES, XLookupString gives 0 characters: "" > > > KeyRelease event, serial 27, synthetic NO, window 0x1600001, > root 0x3a, subw 0x1600002, time 1891239498, (55,39), root:(136,215), > state 0x80, keycode 113 (keysym 0xfe03, ISO_Level3_Shift), same_screen > YES, XLookupString gives 0 characters: "" > > > bye > ago > ------------------------------- Dr. Franz Roters Max-Planck-Institut fuer Eisenforschung Abteilung Mikrostrukturphysik und Umformtechnik Max-Planck-Str. 1 40237 Duesseldorf Germany Tel.: +49 (0)211-6792-393 FAX: +49 (0)211-6792-333 From Termlifeyso@fastmail.fm Tue Nov 11 12:35:00 2003 From: Termlifeyso@fastmail.fm (Termlife Insurance) Date: Tue, 11 Nov 2003 12:35:00 -0000 Subject: Term-life-insure rates have dropped Stop overpaying yln Message-ID: cygwin-xfree, Tuesday, November 11 2003 --------------------------------------------------------- You'd be suprised how little it costs for piece of mind. Protect your family's future, saving hundreds on your policy. Choose from the top term-life-insure companies, it's quick & easy http://www.curtainn.com/opp/zebra/index.php?rd=12 To modify your listing options: curtainn.com/opp/zebra/index.php?rd=15 ---------------------------------------------------- Candidate brought large dog to interview. `I don't know, I didn't listen.'" "`The best way to get a drink out of a Vogon is to stick your finger down his throat...'", Candidate explained that her long-term goals was to replace the interviewer. Life Life bomdwjpuxtoorbwyermpycukexlpnifoyt __________________________________ Do you Yahoo!? The New Yahoo! Shopping - with improved product search http://shopping.yahoo.com From huntharo@msu.edu Tue Nov 11 13:15:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Tue, 11 Nov 2003 13:15:00 -0000 Subject: Updated: XFree86-xserv-4.3.0-22 In-Reply-To: <1068549020528.tulitanssi.36802.w1Q4NRjiTPWoQQzb3m7sWA@luukku.com> References: <1068549020528.tulitanssi.36802.w1Q4NRjiTPWoQQzb3m7sWA@luukku.com> Message-ID: <3FB0E0D5.7090505@msu.edu> Yeah, this release discards repeats that come from Windows. It now relies on the Xinput layer to do the repeating. Are you disabling Xinput? I hope I have that terminology right... it might not be called Xinput. Harold tulitanssi@luukku.com wrote: > Hi all, > > keyboard repeat does not work anymore with this new update. I think it worked with the previous (4.3.0-21) release. Any ideas? > > I'm using win2k. > > Thanks, > Tuli > > > ............................................................ > Maksuton s??hk??posti aina k??yt??ss?? http://luukku.com > Kuukausimaksuton MTV3 Internet-liittym?? www.mtv3.fi/liittyma > From kirk.woellert@ngc.com Tue Nov 11 13:31:00 2003 From: kirk.woellert@ngc.com (Woellert, Kirk D.) Date: Tue, 11 Nov 2003 13:31:00 -0000 Subject: XWin works on Win2K but not on some WinXP clients Message-ID: I have a laptop with WinXP on it. I downloaded Cygwin, performed a default installation, brought it into the office and just like the other WinXP boxes all I get is the checkerboard screen. No login prompt. I went so far last night as to take my co-workers X11 subdirectory from his Win2K machine and overwrite my X11 subdirectory on one of the WinXP boxes. Still, only a checkerboard screen, no login prompt. In answer to earlier questions, Yes, I can SSH into the linux box using either Cygwin or PuTTY. Someone asked about log files for xdm. Did they mean on the linux box? If so where do I find them. I looked in etc/X11 and didnt see anything. The following is my "Xaccess" file on the RedHat Linux 9 box. This file has not been modified and my co-worker can connect to this server. [kdw@gaia xdm]# cat Xaccess # $XConsortium: Xaccess,v 1.5 91/08/26 11:52:51 rws Exp $ # # Access control file for XDMCP connections # # To control Direct and Broadcast access: # # pattern # # To control Indirect queries: # # pattern list of hostnames and/or macros ... # # To use the chooser: # # pattern CHOOSER BROADCAST # # or # # pattern CHOOSER list of hostnames and/or macros ... # # To define macros: # # %name list of hosts ... # # The first form tells xdm which displays to respond to itself. # The second form tells xdm to forward indirect queries from hosts matching # the specified pattern to the indicated list of hosts. # The third form tells xdm to handle indirect queries using the chooser; # the chooser is directed to send its own queries out via the broadcast # address and display the results on the terminal. # The fourth form is similar to the third, except instead of using the # broadcast address, it sends DirectQuerys to each of the hosts in the list # # In all cases, xdm uses the first entry which matches the terminal; # for IndirectQuery messages only entries with right hand sides can # match, for Direct and Broadcast Query messages, only entries without # right hand sides can match. # * #any host can get a login window # # To hardwire a specific terminal to a specific host, you can # leave the terminal sending indirect queries to this host, and # use an entry of the form: # #terminal-a host-a # # The nicest way to run the chooser is to just ask it to broadcast # requests to the network - that way new hosts show up automatically. # Sometimes, however, the chooser can't figure out how to broadcast, # so this may not work in all environments. # * CHOOSER BROADCAST #any indirect host can get a chooser # # If you'd prefer to configure the set of hosts each terminal sees, # then just uncomment these lines (and comment the CHOOSER line above) # and edit the %hostlist line as appropriate # #%hostlist host-a host-b #* CHOOSER %hostlist # [kdw@gaia xdm]# From ljian@ios.ac.cn Tue Nov 11 13:32:00 2003 From: ljian@ios.ac.cn (Liu Jian) Date: Tue, 11 Nov 2003 13:32:00 -0000 Subject: how to get bigger font in xterm Message-ID: <1557197769.20031111213257@ios.ac.cn> Hello funs, I find that the font of xterm is a little tiny (after startx). I wonder how to set a bigger font. Waiting for your directions. -- Best regards, Liu mailto:ljian@ios.ac.cn From huntharo@msu.edu Tue Nov 11 13:53:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Tue, 11 Nov 2003 13:53:00 -0000 Subject: XWin works on Win2K but not on some WinXP clients In-Reply-To: References: Message-ID: <3FB0E9C3.2010903@msu.edu> Kirk, Woellert, Kirk D. wrote: > I have a laptop with WinXP on it. I downloaded Cygwin, performed a default > installation, brought it into the office and just like the other WinXP boxes > all I get is the checkerboard screen. No login prompt. Any chance that you could take it to another Linux box and test a login with that different machine? It would be nice to try to determine which end is having a problem. > In answer to earlier questions, Yes, I can SSH into the linux box using > either Cygwin or PuTTY. Okay, so you can at least connect. I have been assuming that all of these machines are on a LAN... is that the case? If there is a NAT (network address translation) box between your machine and the server, then you will be unable to connect to XDM, even if you can connect with ssh or other protocols. Please describe your setup a little bit. If you have any network segments (NAT boxes, routers, etc.) please take the above laptop to the same segment that the W2K machines work on and try logging in from there. > Someone asked about log files for xdm. Did they mean on the linux box? If so > where do I find them. I looked in etc/X11 and didnt see anything. Yes, the log files are on the machine that is running xdm/kdm/gdm, which is your Linux box in this case. The log file location depends on how Red Hat does things... I haven't run it in a little while. I can tell you that the logs are most likely in /var/log. If you are running kdm, then the logs will probably be in /var/log/kdm.log. Also check for /var/log/xdm.errors. You could also do a general check of /var/log/messages and /var/log/syslog for any error/security messages. Finally, you need to run xdm/kdm/gdm (whichever one you are using, most likely kdm) in debug mode. Please see the following post from Alexander Gottwald for instructions on how to do this: http://sources.redhat.com/ml/cygwin-xfree/2003-06/msg00364.html The idea is to run xdm/kdm/gdm in debug mode, then try to connect from a working machine and observe the output on the Linux machine's console. Then, try to connect from a non-working machine and observe and compare the output on the Linux machine's console. If you get no output from the failed connection attempt, then it tells us that there is most likely a network segment that you don't know about (remember, I don't know if you work in a 5 man shop or a 50,000 employee conglomerate). If you get an error message, then we will likely be able to translate it and tell you what the problem is. If you get identical output both times and no problems are indicated, then we are up a creek. :) Actually, in that case it would probably be a multiple network card issue on the WinXP machines that you have, or perhaps some VPN/firewall software on those machines (I know you said that the XP firewall was disabled). Hope that helps, please report your results quickly so that we can get this fixed, Harold From huntharo@msu.edu Tue Nov 11 13:54:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Tue, 11 Nov 2003 13:54:00 -0000 Subject: how to get bigger font in xterm In-Reply-To: <1557197769.20031111213257@ios.ac.cn> References: <1557197769.20031111213257@ios.ac.cn> Message-ID: <3FB0E9FD.7040201@msu.edu> One way is to download the XFree86-f100 package via Cygwin's setup.exe, then change your startxwin.bat (or whatever you use to launch Cygwin/X) to add the "-dpi 100" parameter to XWin.exe. Let use know if that helps, Harold Liu Jian wrote: > Hello funs, > > I find that the font of xterm is a little tiny (after startx). > I wonder how to set a bigger font. Waiting for your directions. > From huntharo@msu.edu Tue Nov 11 13:58:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Tue, 11 Nov 2003 13:58:00 -0000 Subject: XWin works on Win2K but not on some WinXP clients In-Reply-To: References: Message-ID: <3FB0EAF6.80601@msu.edu> Kirk, By the way, you could jump into irc.freenode.net/#cygwinx (note the x on the end) and get a faster turn-around on messages between us. It would probably help get the problem fixed with less rambling about possibilities in your particular configuration when I could just ask you and move on based on your immediate answer :) Well, I guess I will always be long winded. I am learning to accept that ;) Harold From kirk.woellert@ngc.com Tue Nov 11 15:51:00 2003 From: kirk.woellert@ngc.com (Woellert, Kirk D.) Date: Tue, 11 Nov 2003 15:51:00 -0000 Subject: XWin works on Win2K but not on some WinXP clients Message-ID: I took the laptop and plugged it into the same damn switch that the linux box is hanging off of. No dice, checkerboard screen, no login prompt. I asked my co-worker to login to the linux box using the same Win2K system via the standard Cygwin prompt: "XWin -query -nodecoration -lesspointer" He could, and proceded to taunt me by doing various tasks within the Cygwin window. So all this time the Win2K can login to the linux box as I have claimed. We are not running NAT. All firewalls are turned off completely (linux and Win). We are all on the same network segment, and all have the same IP scope (i.e. 137.x.x.x). I tried to get debug running as requested but, as a new linux user its not straightforward to figure out how to stop kdm/gdm/xdm or whatever RH9 uses, and restart it again. I looked at the post you cited and searched the net also. "/etc/init.d/xdm stop" returns command not found. I tried several iterations but no avail. So finally I did "xdm -debug 10 -no daemon", got a fatal server error, did some grep's and here is the followoing: [kdw@gaia xdm]# ps -ef |grep kdm root 1829 1761 0 10:39 pts/0 00:00:00 grep kdm [kdw@gaia xdm]# ps -ef | grep xdm root 1831 1761 0 10:39 pts/0 00:00:00 grep xdm [kdw@gaia xdm]# ps -ef | grep gdm root 1033 1 0 08:35 ? 00:00:00 /usr/bin/gdm-binary -nodaemon root 1084 1033 0 08:35 ? 00:00:00 /usr/bin/gdm-binary -nodaemon root 1459 1084 0 09:17 ? 00:00:06 /usr/X11R6/bin/X :0 -auth /var/gdm/:0.Xauth vt7 gdm 1468 1084 0 09:17 ? 00:00:03 /usr/bin/gdmgreeter root 1833 1761 0 10:39 pts/0 00:00:00 grep gdm [kdw@gaia xdm]# I have included some log files as requested. Its pretty much greek to me, with exception of the very first CAT I did of "xdm-errors". Looks suspicious. [kdw@gaia log]# cat xdm-errors xdm error (pid 3748): error 98 binding socket address 177 Fatal server error: Server is already active for display 0 If this server is no longer running, remove /tmp/.X0-lock and start again. When reporting a problem related to a server crash, please send the full server output, not just the last messages. Please report problems to xfree86@xfree86.org. xdm error (pid 3748): server unexpectedly died xdm error (pid 3748): Server for display :0 can't be started, session disabled GDM.conf # existing sessions and will only restart gdm after all users log out) # # You can also use the gdm-restart and gdm-safe-restart scripts which just # do the above for you. # # Have fun! - George [daemon] # Automatic login, if true the first local screen will automatically logged # in as user as set with AutomaticLogin key. AutomaticLoginEnable=false AutomaticLogin= # Timed login, useful for kiosks. Log in a certain user after a certain # amount of time TimedLoginEnable=false TimedLogin= TimedLoginDelay=30 # A comma separated list of users that will be logged in without having # to authenticate on local screens (not over xdmcp). Note that 'root' # is ignored and will always have to authenticate. LocalNoPasswordUsers= # If you are having trouble with using a single server for a long time and # want gdm to kill/restart the server, turn this on # Note: I've made this default to true now because there seem to be some # issues ranging from some things not being reset in the X server to # pam issues with the slave. It is likely that this feature may be removed # in the future and we're always going to do server restarts. AlwaysRestartServer=true # The gdm configuration program that is run from the login screen, you should # probably leave this alone Configurator=/usr/sbin/gdmsetup --disable-sound --disable-crash-dialog GnomeDefaultSession=/usr/share/gnome/default.session # The chooser program. Must output the chosen host on stdout, probably you # should leave this alone Chooser=/usr/bin/gdmchooser # Default path to set. The profile scripts will likely override this DefaultPath=/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin # Default path for root. The profile scripts will likely override this RootPath=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/X 11R6/bin DisplayInitDir=/etc/X11/gdm/Init # Greeter for local (non-xdmcp) logins. Change gdmlogin to gdmgreeter to # get the new graphical greeter. Greeter=/usr/bin/gdmgreeter #Uncomment this for the regular greeter #Greeter=/usr/bin/gdmlogin --disable-sound --disable-crash-dialog # Greeter for xdmcp logins, usually you want a less graphically intensive # greeter here so it's better to leave this with gdmlogin RemoteGreeter=/usr/bin/gdmgreeter # User and group that gdm should run as. Probably should be gdm and gdm and # you should create these user and group. Anyone found running this as # someone too privilaged will get a kick in the ass. This should have # access to only the gdm directories and files. User=gdm Group=gdm # To try to kill all clients started at greeter time or in the Init script. # doesn't always work, only if those clients have a window of their own KillInitClients=true LogDir=/var/log/gdm # You should probably never change this value unless you have a weird setup PidFile=/var/run/gdm.pid PostSessionScriptDir=/etc/X11/gdm/PostSession/ PreSessionScriptDir=/etc/X11/gdm/PreSession/ # Distributions: If you have some script that runs an X server in say # VGA mode, allowing a login, could you please send it to me? FailsafeXServer= # if X keeps crashing on us we run this script. The default one does a bunch # of cool stuff to figure out what to tell the user and such and can # run an X configuration program. XKeepsCrashing=/etc/X11/gdm/XKeepsCrashing # Reboot, Halt and suspend commands, you can add different commands # separated by a semicolon and gdm will use the first one it can find RebootCommand=/sbin/shutdown -r now;/usr/sbin/shutdown -r now HaltCommand=/usr/bin/poweroff;/sbin/poweroff;/sbin/shutdown -h now;/usr/sbin/shutdown -h now SuspendCommand= # Probably should not touch the below this is the standard setup ServAuthDir=/var/gdm SessionDir=/etc/X11/gdm/Sessions/ # Better leave this blank and HOME will be used. You can use syntax ~/ below # to indicate home directory of the user UserAuthDir= # Fallback if home directory not writable UserAuthFBDir=/tmp UserAuthFile=.Xauthority # The X server to use if we can't figure out what else to run. StandardXServer=/usr/X11R6/bin/X # The maximum number of flexible X servers to run. FlexibleXServers=5 # the X nest command Xnest=/usr/X11R6/bin/Xnest -name Xnest # Automatic VT allocation. Right now only works on Linux. This way # we force X to use specific vts. turn VTAllocation to false if this # is causing problems. FirstVT=7 VTAllocation=true [security] # If any distributions ship with this one off, they should be shot # this is only local, so it's only for say kiosk use, when you # want to minimize possibility of breakin AllowRoot=true # If you want to be paranoid, turn this one off AllowRemoteRoot=true # This will allow remote timed login AllowRemoteAutoLogin=false # 0 is the most anal, 1 allows group write permissions, 2 allows all write permissions RelaxPermissions=0 RetryDelay=1 # Maximum size of a file we wish to read. This makes it hard for a user to DoS us # by using a large file. UserMaxFile=65536 # Maximum size of the session file. This is larger because it matters less as we # never keep it all in memory. Just has an upper limit so that we don't go into too # long of a loop SessionMaxFile=524388 # XDMCP is the protocol that allows remote login. If you want to log into # gdm remotely (I'd never turn this on on open network, use ssh for such # remote usage that). You can then run X with -query to log in, # or -indirect to run a chooser. Look for the 'Terminal' server # type at the bottom of this config file. [xdmcp] # Distributions: Ship with this off. It is never a safe thing to leave # out on the net. Alternatively you can set up /etc/hosts.allow and # /etc/hosts.deny to only allow say local access. Enable=true # Honour indirect queries, we run a chooser for these, and then redirect # the user to the chosen host. Otherwise we just log the user in locally. HonorIndirect=true # Maximum pending requests MaxPending=8 MaxPendingIndirect=8 # Maximum open XDMCP sessions at any point in time MaxSessions=120 # Maximum wait times MaxWait=15 MaxWaitIndirect=15 # How many times can a person log in from a single host. Usually better to # keep at 1 to fend off DoS attacks by running many logins from a single # host DisplaysPerHost=5 # The port. 177 is the standard port so better keep it that way Port=177 # Willing script, none is shipped and by default we'll send # hostname system id. But if you supply something here, the # output of this script will be sent as status of this host so that # the chooser can display it. You could for example send load, # or mail details for some user, or some such. Willing=/etc/X11/gdm/Xwilling [gui] # The 'theme'. By default we're using the default gtk theme # Of course assuming that gtk got installed in the same prefix, # if not change this. GtkRC=/usr/share/themes/Bluecurve/gtk-2.0/gtkrc # Maximum size of an icon, larger icons are scaled down MaxIconWidth=128 MaxIconHeight=128 [greeter] # Greeter has a nice title bar that the user can move TitleBar=true # Configuration is available from the system menu of the greeter ConfigAvailable=true # Face browser is enabled. This only works currently for the # standard greeter as it is not yet enabled in the graphical greeter. Browser=false # The default picture in the browser DefaultFace=/usr/share/pixmaps/nobody.png # These are things excluded from the face browser, not from logging in Exclude=bin,daemon,adm,lp,sync,shutdown,halt,mail,news,uucp,operator,nobody, gdm,postgres,pvm,rpm # As an alternative to the above this is the minimum uid to show MinimalUID=500 # If user or user.png exists in this dir it will be used as his picture GlobalFaceDir=/usr/share/faces/ # Icon we use Icon=/usr/share/pixmaps/gdm.png # File which contains the locale we show to the user. Likely you want to use # the one shipped with gdm and edit it. It is not a standard locale.alias file, # although gdm will be able to read a standard locale.alias file as well. LocaleFile=/etc/X11/gdm/locale.alias # Logo shown in the standard greeter ## Logo=/usr/share/pixmaps/gdm-foot-logo.png Logo= ## nice RH logo for the above line: /usr/share/pixmaps/redhat/shadowman-200.png # The standard greeter should shake if a user entered the wrong username or # password. Kind of cool looking Quiver=true # The system menu is shown in the greeter SystemMenu=true # Note to distributors, if you wish to have a different Welcome string # and wish to have this translated you can have entries such as # Welcome[cs]=Vitejte na %n # Just make sure the string is in utf-8 Welcome=Welcome to %n # Don't allow user to move the standard greeter window. Only makes sense # if TitleBar is on LockPosition=true # Set a position rather then just centering the window. If you enter # negative values for the position it is taken as an offset from the # right or bottom edge. SetPosition=false PositionX=0 PositionY=0 # Xinerama screen we use to display the greeter on. Not for true # multihead, currently only works for Xinerama. XineramaScreen=0 # Background settings for the standard greeter: # Type can be 0=None, 1=Image, 2=Color BackgroundType=2 BackgroundImage= BackgroundScaleToFit=true BackgroundColor=#27408b # XDMCP session should only get a color, this is the sanest setting since # you don't want to take up too much bandwidth BackgroundRemoteOnlyColor=true # Program to run to draw the background in the standard greeter. Perhaps # something like an xscreensaver hack or some such. BackgroundProgram= ## red hat logo program ## BackgroundProgram=/usr/bin/xsri --redhat-login --run # if this is true then the background program is run always, otherwise # it is only run when the BackgroundType is 0 (None) RunBackgroundProgramAlways=false # Show the chooser (you can choose a specific saved gnome session) session ShowGnomeChooserSession=false # Show the Failsafe sessions. These are much MUCH nicer (focus for xterm for # example) and more failsafe then those supplied by scripts so distros should # use this rather then just running an xterm from a script. ShowGnomeFailsafeSession=false ShowXtermFailsafeSession=false # Always use 24 hour clock no matter what the locale. Use24Clock=false # Use circles in the password field. Looks kind of cool actually UseCirclesInEntry=false # These two keys are for the new greeter. Circles is the standard # shipped theme GraphicalTheme=Bluecurve GraphicalThemeDir=/usr/share/gdm/themes/ # The chooser is what's displayed when a user wants an indirect XDMCP # session [chooser] # Default image for hosts DefaultHostImg=/usr/share/pixmaps/nohost.png # Directory with host images, they are named by the hosts: host or host.png HostImageDir=/usr/share/hosts/ # Time we scan for hosts (well only the time we tell the user we are # scanning actually) ScanTime=3 # A comma separated lists of hosts to automatically add (if they answer to # a query of course). You can use this to reach hosts that broadcast cannot # reach. Hosts= # Broadcast a query to get all hosts on the current network that answer Broadcast=true [debug] # This will enable debugging into the syslog, usually not neccessary # and it creates a LOT of spew of random stuff to the syslog. However it # can be useful in determining when something is going very wrong. Enable=false [servers] # These are the standard servers. You can add as many you want here # and they will always be started. Each line must start with a unique # number and that will be the display number of that server. Usually just # the 0 server is used. 0=Standard #1=Standard # Note the VTAllocation and FirstVT keys on linux. Don't add any vt # arguments if VTAllocation is on, and set FirstVT to be the first vt # available that your gettys don't grab (gettys are usually dumb and grab # even a vt that has already been taken). Using 7 will work pretty much for # all linux distributions. VTAllocation is not currently implemented on # anything but linux since I don't own any non-linux systems. Feel free to # send patches. X servers will just not get any extra arguments then. # #Note: If you want to run an X terminal you could add an X server such as this #0=Terminal -query serverhostname # or for a chooser (optionally serverhostname could be localhost) #0=Terminal -indirect serverhostname # Definition of the standard X server. [server-Standard] name=Standard server command=/usr/X11R6/bin/X flexible=true # To use this server type you should add -query host or -indirect host # to the command line [server-Terminal] name=Terminal server # Add -terminate to make things behave more nicely command=/usr/X11R6/bin/X -terminate # Make this not appear in the flexible servers (we need extra params # anyway, and terminate would be bad for xdmcp) flexible=false # Not local, we do not handle the logins for this X server handled=false [kdw@gaia gdm]# XFree86.log.1 (II) ATI(0): Supported Future Video Modes: (II) ATI(0): #0: hsize: 2048 vsize 1536 refresh: 75 vid: 20449 (II) ATI(0): #1: hsize: 1600 vsize 1200 refresh: 75 vid: 20393 (II) ATI(0): #2: hsize: 1856 vsize 1392 refresh: 75 vid: 20425 (II) ATI(0): #3: hsize: 1792 vsize 1344 refresh: 75 vid: 20417 (II) ATI(0): #4: hsize: 1600 vsize 1200 refresh: 85 vid: 22953 (II) ATI(0): #5: hsize: 1280 vsize 1024 refresh: 85 vid: 39297 (II) ATI(0): #6: hsize: 1024 vsize 768 refresh: 85 vid: 22881 (II) ATI(0): #7: hsize: 800 vsize 600 refresh: 85 vid: 22853 (II) ATI(0): Supported additional Video Mode: (II) ATI(0): clock: 297.0 MHz Image Size: 393 x 295 mm (II) ATI(0): h_active: 1920 h_sync: 2064 h_sync_end 2288 h_blank_end 2640 h_border: 0 (II) ATI(0): v_active: 1440 v_sync: 1441 v_sync_end 1444 v_blanking: 1500 v_border: 0 (II) ATI(0): Ranges: V min: 50 V max: 160 Hz, H min: 30 H max: 121 kHz, PixClock max 360 MHz (II) ATI(0): Monitor name: GatewayVX1120 (II) ATI(0): Serial No: 101060532 (--) ATI(0): ATI 3D Rage XL or XC graphics controller detected. (--) ATI(0): Chip type 4752 "GR", version 7, foundry TSMC, class 0, revision 0x00. (--) ATI(0): PCI bus interface detected; block I/O base is 0xDC00. (--) ATI(0): ATI Mach64 adapter detected. (!!) ATI(0): For information on using the multimedia capabilities of this adapter, please see http://gatos.sf.net. (--) ATI(0): Internal RAMDAC (subtype 1) detected. (==) ATI(0): RGB weight 888 (==) ATI(0): Default visual is TrueColor (==) ATI(0): Using gamma correction (1.0, 1.0, 1.0) (II) ATI(0): Using Mach64 accelerator CRTC. (II) ATI(0): Storing hardware cursor image at 0xFC7FFC00. (II) ATI(0): Using 8 MB linear aperture at 0xFC000000. (!!) ATI(0): Virtual resolutions will be limited to 8191 kB due to linear aperture size and/or placement of hardware cursor image area. (II) ATI(0): Using Block 0 MMIO aperture at 0xFDEFF400. (II) ATI(0): Using Block 1 MMIO aperture at 0xFDEFF000. (==) ATI(0): Write-combining range (0xfc000000,0x800000) (II) ATI(0): MMIO write caching enabled. (--) ATI(0): 8192 kB of SGRAM (2:1) 32-bit detected (using 8191 kB). (WW) ATI(0): Cannot shadow an accelerated frame buffer. (II) ATI(0): Engine XCLK 62.353 MHz; Refresh rate code 1. (--) ATI(0): Internal programmable clock generator detected. (--) ATI(0): Reference clock 157.5/11 (14.318) MHz. (II) ATI(0): Monitor0: Using hsync range of 30.00-121.00 kHz (II) ATI(0): Monitor0: Using vrefresh range of 50.00-160.00 Hz (II) ATI(0): Maximum clock: 124.00 MHz (II) ATI(0): Not using default mode "1280x960" (bad mode clock/interlace/doublescan) (II) ATI(0): Not using default mode "1280x1024" (bad mode clock/interlace/doublescan) (II) ATI(0): Not using default mode "1280x1024" (bad mode clock/interlace/doublescan) (II) ATI(0): Not using default mode "1600x1200" (bad mode clock/interlace/doublescan) (II) ATI(0): Not using default mode "1600x1200" (bad mode clock/interlace/doublescan) (II) ATI(0): Not using default mode "1600x1200" (bad mode clock/interlace/doublescan) (II) ATI(0): Not using default mode "1600x1200" (bad mode clock/interlace/doublescan) (II) ATI(0): Not using default mode "1600x1200" (bad mode clock/interlace/doublescan) (II) ATI(0): Not using default mode "1792x1344" (insufficient memory for mode) (II) ATI(0): Not using default mode "1792x1344" (insufficient memory for mode) (II) ATI(0): Not using default mode "896x672" (bad mode clock/interlace/doublescan) (II) ATI(0): Not using default mode "1856x1392" (insufficient memory for mode) (II) ATI(0): Not using default mode "1856x1392" (insufficient memory for mode) (II) ATI(0): Not using default mode "928x696" (bad mode clock/interlace/doublescan) (II) ATI(0): Not using default mode "1920x1440" (insufficient memory for mode) (II) ATI(0): Not using default mode "1920x1440" (insufficient memory for mode) (II) ATI(0): Not using default mode "960x720" (bad mode clock/interlace/doublescan) (II) ATI(0): Not using default mode "1400x1050" (bad mode clock/interlace/doublescan) (II) ATI(0): Not using default mode "1400x1050" (bad mode clock/interlace/doublescan) (II) ATI(0): Not using default mode "1400x1050" (bad mode clock/interlace/doublescan) (II) ATI(0): Not using default mode "1920x1200" (insufficient memory for mode) (II) ATI(0): Not using default mode "1920x1440" (insufficient memory for mode) (II) ATI(0): Not using default mode "960x720" (bad mode clock/interlace/doublescan) (II) ATI(0): Not using default mode "2048x1536" (insufficient memory for mode) (II) ATI(0): Not using default mode "1024x768" (bad mode clock/interlace/doublescan) (II) ATI(0): Not using default mode "2048x1536" (insufficient memory for mode) (II) ATI(0): Not using default mode "1024x768" (bad mode clock/interlace/doublescan) (II) ATI(0): Not using default mode "2048x1536" (insufficient memory for mode) (II) ATI(0): Not using default mode "1024x768" (bad mode clock/interlace/doublescan) (II) ATI(0): Not using default mode "1400x1050" (width too large for virtual size) (II) ATI(0): Not using default mode "1280x1024" (width too large for virtual size) (II) ATI(0): Not using default mode "1280x960" (width too large for virtual size) (II) ATI(0): Not using default mode "1152x864" (width too large for virtual size) (II) ATI(0): Not using default mode "1152x864" (width too large for virtual size) (II) ATI(0): Not using default mode "1152x768" (width too large for virtual size) (--) ATI(0): Virtual size is 1024x768 (pitch 1024) (**) ATI(0): *Default mode "1024x768": 94.5 MHz, 68.7 kHz, 85.0 Hz (II) ATI(0): Modeline "1024x768" 94.50 1024 1072 1168 1376 768 769 772 808 +hsync +vsync (**) ATI(0): *Default mode "800x600": 56.3 MHz, 53.7 kHz, 85.1 Hz (II) ATI(0): Modeline "800x600" 56.30 800 832 896 1048 600 601 604 631 +hsync +vsync (**) ATI(0): *Default mode "640x480": 74.2 MHz, 85.9 kHz, 85.1 Hz (D) (II) ATI(0): Modeline "640x480" 74.25 640 672 752 864 480 480 482 505 doublescan +hsync +vsync (**) ATI(0): Default mode "1024x768": 78.8 MHz, 60.1 kHz, 75.1 Hz (II) ATI(0): Modeline "1024x768" 78.80 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (**) ATI(0): Default mode "1024x768": 75.0 MHz, 56.5 kHz, 70.1 Hz (II) ATI(0): Modeline "1024x768" 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (**) ATI(0): Default mode "1024x768": 65.0 MHz, 48.4 kHz, 60.0 Hz (II) ATI(0): Modeline "1024x768" 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (**) ATI(0): Default mode "1024x768": 44.9 MHz, 35.5 kHz, 87.1 Hz (I) (II) ATI(0): Modeline "1024x768" 44.90 1024 1032 1208 1264 768 768 776 817 interlace +hsync +vsync (**) ATI(0): Default mode "960x720": 117.0 MHz, 90.0 kHz, 60.0 Hz (D) (II) ATI(0): Modeline "960x720" 117.00 960 1024 1128 1300 720 720 722 750 doublescan -hsync +vsync (**) ATI(0): Default mode "928x696": 109.2 MHz, 86.4 kHz, 60.1 Hz (D) (II) ATI(0): Modeline "928x696" 109.15 928 976 1088 1264 696 696 698 719 doublescan -hsync +vsync (**) ATI(0): Default mode "896x672": 102.4 MHz, 83.7 kHz, 60.0 Hz (D) (II) ATI(0): Modeline "896x672" 102.40 896 960 1060 1224 672 672 674 697 doublescan -hsync +vsync (**) ATI(0): Default mode "960x600": 115.0 MHz, 91.0 kHz, 72.8 Hz (D) (II) ATI(0): Modeline "960x600" 115.00 960 968 1048 1264 600 600 602 625 doublescan -hsync -vsync (**) ATI(0): Default mode "832x624": 57.3 MHz, 49.7 kHz, 74.6 Hz (II) ATI(0): Modeline "832x624" 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (**) ATI(0): Default mode "800x600": 114.8 MHz, 106.2 kHz, 85.0 Hz (D) (II) ATI(0): Modeline "800x600" 114.75 800 832 928 1080 600 600 602 625 doublescan +hsync +vsync (**) ATI(0): Default mode "800x600": 49.5 MHz, 46.9 kHz, 75.0 Hz (II) ATI(0): Modeline "800x600" 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (**) ATI(0): Default mode "800x600": 101.2 MHz, 93.8 kHz, 75.0 Hz (D) (II) ATI(0): Modeline "800x600" 101.25 800 832 928 1080 600 600 602 625 doublescan +hsync +vsync (**) ATI(0): Default mode "800x600": 50.0 MHz, 48.1 kHz, 72.2 Hz (II) ATI(0): Modeline "800x600" 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (**) ATI(0): Default mode "800x600": 94.5 MHz, 87.5 kHz, 70.0 Hz (D) (II) ATI(0): Modeline "800x600" 94.50 800 832 928 1080 600 600 602 625 doublescan +hsync +vsync (**) ATI(0): Default mode "800x600": 87.8 MHz, 81.2 kHz, 65.0 Hz (D) (II) ATI(0): Modeline "800x600" 87.75 800 832 928 1080 600 600 602 625 doublescan +hsync +vsync (**) ATI(0): Default mode "800x600": 40.0 MHz, 37.9 kHz, 60.3 Hz (II) ATI(0): Modeline "800x600" 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (**) ATI(0): Default mode "800x600": 81.0 MHz, 75.0 kHz, 60.0 Hz (D) (II) ATI(0): Modeline "800x600" 81.00 800 832 928 1080 600 600 602 625 doublescan +hsync +vsync (**) ATI(0): Default mode "800x600": 36.0 MHz, 35.2 kHz, 56.2 Hz (II) ATI(0): Modeline "800x600" 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (**) ATI(0): Default mode "700x525": 92.0 MHz, 93.9 kHz, 85.3 Hz (D) (II) ATI(0): Modeline "700x525" 92.00 700 732 828 980 525 525 527 550 doublescan +hsync +vsync (**) ATI(0): Default mode "700x525": 77.9 MHz, 81.5 kHz, 74.8 Hz (D) (II) ATI(0): Modeline "700x525" 77.90 700 732 892 956 525 526 532 545 doublescan +hsync +vsync (**) ATI(0): Default mode "700x525": 75.5 MHz, 77.0 kHz, 70.0 Hz (D) (II) ATI(0): Modeline "700x525" 75.50 700 732 828 980 525 525 527 550 doublescan +hsync +vsync (**) ATI(0): Default mode "700x525": 61.0 MHz, 64.9 kHz, 60.0 Hz (D) (II) ATI(0): Modeline "700x525" 61.00 700 744 820 940 525 526 532 541 doublescan +hsync +vsync (**) ATI(0): Default mode "640x512": 78.8 MHz, 91.1 kHz, 85.0 Hz (D) (II) ATI(0): Modeline "640x512" 78.75 640 672 752 864 512 512 514 536 doublescan +hsync +vsync (**) ATI(0): Default mode "640x512": 67.5 MHz, 80.0 kHz, 75.0 Hz (D) (II) ATI(0): Modeline "640x512" 67.50 640 648 720 844 512 512 514 533 doublescan +hsync +vsync (**) ATI(0): Default mode "640x512": 54.0 MHz, 64.0 kHz, 60.0 Hz (D) (II) ATI(0): Modeline "640x512" 54.00 640 664 720 844 512 512 514 533 doublescan +hsync +vsync (**) ATI(0): Default mode "640x480": 36.0 MHz, 43.3 kHz, 85.0 Hz (II) ATI(0): Modeline "640x480" 36.00 640 696 752 832 480 481 484 509 -hsync -vsync (**) ATI(0): Default mode "640x480": 31.5 MHz, 37.5 kHz, 75.0 Hz (II) ATI(0): Modeline "640x480" 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (**) ATI(0): Default mode "640x480": 31.5 MHz, 37.9 kHz, 72.8 Hz (II) ATI(0): Modeline "640x480" 31.50 640 664 704 832 480 489 491 520 -hsync -vsync (**) ATI(0): Default mode "640x480": 25.2 MHz, 31.5 kHz, 60.0 Hz (II) ATI(0): Modeline "640x480" 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (**) ATI(0): Default mode "640x480": 54.0 MHz, 60.0 kHz, 60.0 Hz (D) (II) ATI(0): Modeline "640x480" 54.00 640 688 744 900 480 480 482 500 doublescan +hsync +vsync (**) ATI(0): Default mode "720x400": 35.5 MHz, 37.9 kHz, 85.0 Hz (II) ATI(0): Modeline "720x400" 35.50 720 756 828 936 400 401 404 446 -hsync +vsync (**) ATI(0): Default mode "640x400": 31.5 MHz, 37.9 kHz, 85.1 Hz (II) ATI(0): Modeline "640x400" 31.50 640 672 736 832 400 401 404 445 -hsync +vsync (**) ATI(0): Default mode "576x432": 60.8 MHz, 77.5 kHz, 85.2 Hz (D) (II) ATI(0): Modeline "576x432" 60.75 576 608 672 784 432 432 434 455 doublescan +hsync -vsync (**) ATI(0): Default mode "576x432": 54.0 MHz, 67.5 kHz, 75.0 Hz (D) (II) ATI(0): Modeline "576x432" 54.00 576 608 672 800 432 432 434 450 doublescan +hsync +vsync (**) ATI(0): Default mode "640x350": 31.5 MHz, 37.9 kHz, 85.1 Hz (II) ATI(0): Modeline "640x350" 31.50 640 672 736 832 350 382 385 445 +hsync -vsync (**) ATI(0): Default mode "576x384": 32.5 MHz, 44.2 kHz, 54.8 Hz (D) (II) ATI(0): Modeline "576x384" 32.50 576 589 657 736 384 385 388 403 doublescan +hsync +vsync (**) ATI(0): Default mode "512x384": 47.2 MHz, 68.7 kHz, 85.0 Hz (D) (II) ATI(0): Modeline "512x384" 47.25 512 536 584 688 384 384 386 404 doublescan +hsync +vsync (**) ATI(0): Default mode "512x384": 39.4 MHz, 60.1 kHz, 75.1 Hz (D) (II) ATI(0): Modeline "512x384" 39.40 512 520 568 656 384 384 386 400 doublescan +hsync +vsync (**) ATI(0): Default mode "512x384": 37.5 MHz, 56.5 kHz, 70.1 Hz (D) (II) ATI(0): Modeline "512x384" 37.50 512 524 592 664 384 385 388 403 doublescan -hsync -vsync (**) ATI(0): Default mode "512x384": 32.5 MHz, 48.4 kHz, 60.0 Hz (D) (II) ATI(0): Modeline "512x384" 32.50 512 524 592 672 384 385 388 403 doublescan -hsync -vsync (**) ATI(0): Default mode "512x384": 22.4 MHz, 35.5 kHz, 87.1 Hz (D) (II) ATI(0): Modeline "512x384" 22.45 512 516 604 632 384 384 388 409 interlace doublescan +hsync +vsync (**) ATI(0): Default mode "416x312": 28.6 MHz, 49.7 kHz, 74.7 Hz (D) (II) ATI(0): Modeline "416x312" 28.64 416 432 464 576 312 312 314 333 doublescan -hsync -vsync (**) ATI(0): Default mode "400x300": 28.1 MHz, 53.7 kHz, 85.3 Hz (D) (II) ATI(0): Modeline "400x300" 28.15 400 416 448 524 300 300 302 315 doublescan +hsync +vsync (**) ATI(0): Default mode "400x300": 24.8 MHz, 46.9 kHz, 75.1 Hz (D) (II) ATI(0): Modeline "400x300" 24.75 400 408 448 528 300 300 302 312 doublescan +hsync +vsync (**) ATI(0): Default mode "400x300": 25.0 MHz, 48.1 kHz, 72.2 Hz (D) (II) ATI(0): Modeline "400x300" 25.00 400 428 488 520 300 318 321 333 doublescan +hsync +vsync (**) ATI(0): Default mode "400x300": 20.0 MHz, 37.9 kHz, 60.3 Hz (D) (II) ATI(0): Modeline "400x300" 20.00 400 420 484 528 300 300 302 314 doublescan +hsync +vsync (**) ATI(0): Default mode "400x300": 18.0 MHz, 35.2 kHz, 56.3 Hz (D) (II) ATI(0): Modeline "400x300" 18.00 400 412 448 512 300 300 301 312 doublescan +hsync +vsync (**) ATI(0): Default mode "320x240": 18.0 MHz, 43.3 kHz, 85.2 Hz (D) (II) ATI(0): Modeline "320x240" 18.00 320 348 376 416 240 240 242 254 doublescan -hsync -vsync (**) ATI(0): Default mode "320x240": 15.8 MHz, 37.5 kHz, 75.0 Hz (D) (II) ATI(0): Modeline "320x240" 15.75 320 328 360 420 240 240 242 250 doublescan -hsync -vsync (**) ATI(0): Default mode "320x240": 15.8 MHz, 37.9 kHz, 72.8 Hz (D) (II) ATI(0): Modeline "320x240" 15.75 320 332 352 416 240 244 245 260 doublescan -hsync -vsync (**) ATI(0): Default mode "320x240": 12.6 MHz, 31.5 kHz, 60.1 Hz (D) (II) ATI(0): Modeline "320x240" 12.60 320 328 376 400 240 245 246 262 doublescan -hsync -vsync (**) ATI(0): Default mode "360x200": 17.8 MHz, 37.9 kHz, 85.0 Hz (D) (II) ATI(0): Modeline "360x200" 17.75 360 378 414 468 200 200 202 223 doublescan -hsync +vsync (**) ATI(0): Default mode "320x200": 15.8 MHz, 37.9 kHz, 85.3 Hz (D) (II) ATI(0): Modeline "320x200" 15.75 320 336 368 416 200 200 202 222 doublescan -hsync +vsync (**) ATI(0): Default mode "320x175": 15.8 MHz, 37.9 kHz, 85.3 Hz (D) (II) ATI(0): Modeline "320x175" 15.75 320 336 368 416 175 191 192 222 doublescan +hsync -vsync (**) ATI(0): Display dimensions: (400, 300) mm (**) ATI(0): DPI set to (65, 65) (II) Loading sub module "xaa" (II) LoadModule: "xaa" (II) Loading /usr/X11R6/lib/modules/libxaa.a (II) Module xaa: vendor="The XFree86 Project" compiled for 4.3.0, module version = 1.1.0 ABI class: XFree86 Video Driver, version 0.6 (II) Loading sub module "ramdac" (II) LoadModule: "ramdac" (II) Loading /usr/X11R6/lib/modules/libramdac.a (II) Module ramdac: vendor="The XFree86 Project" compiled for 4.3.0, module version = 0.1.0 ABI class: XFree86 Video Driver, version 0.6 (II) Loading sub module "fb" (II) LoadModule: "fb" (II) Loading /usr/X11R6/lib/modules/libfb.a (II) Module fb: vendor="The XFree86 Project" compiled for 4.3.0, module version = 1.0.0 ABI class: XFree86 ANSI C Emulation, version 0.2 (--) Depth 24 pixmap format is 32 bpp (II) do I need RAC? No, I don't. (II) resource ranges after preInit: [0] 0 0 0xfdeff000 - 0xfdefffff (0x1000) MS[B] [1] 0 0 0xfc000000 - 0xfcffffff (0x1000000) MS[B] [2] -1 0 0xffe00000 - 0xffffffff (0x200000) MX[B](B) [3] -1 0 0x00100000 - 0x3fefffff (0x3fe00000) MX[B]E(B) [4] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [5] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [6] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [7] -1 0 0xfebf0000 - 0xfebfffff (0x10000) MX[B] [8] -1 0 0xfe1fe000 - 0xfe1fefff (0x1000) MX[B] [9] -1 0 0xfe1ff000 - 0xfe1fffff (0x1000) MX[B] [10] -1 0 0xfe4fe000 - 0xfe4fefff (0x1000) MX[B] [11] -1 0 0xfe4ff000 - 0xfe4fffff (0x1000) MX[B] [12] -1 0 0xfe6fe000 - 0xfe6fefff (0x1000) MX[B] [13] -1 0 0xfe6ff000 - 0xfe6fffff (0x1000) MX[B] [14] -1 0 0x3ffff000 - 0x3ffff3ff (0x400) MX[B] [15] -1 0 0xfdeff000 - 0xfdefffff (0x1000) MX[B](B) [16] -1 0 0xfc000000 - 0xfcffffff (0x1000000) MX[B](B) [17] 0 0 0x000a0000 - 0x000affff (0x10000) MS[B](OprU) [18] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[B](OprU) [19] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[B](OprU) [20] 0 0 0x0000dc00 - 0x0000dcff (0x100) IS[B] [21] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [22] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] [23] -1 0 0x0000ece0 - 0x0000ecff (0x20) IX[B] [24] -1 0 0x0000fc00 - 0x0000fc0f (0x10) IX[B] [25] -1 0 0x0000cce0 - 0x0000ccff (0x20) IX[B] [26] -1 0 0x0000dc00 - 0x0000dcff (0x100) IX[B](B) [27] 0 0 0x000003b0 - 0x000003bb (0xc) IS[B](OprU) [28] 0 0 0x000003c0 - 0x000003df (0x20) IS[B](OprU) (==) ATI(0): Write-combining range (0xfc000000,0x800000) (II) ATI(0): Largest offscreen areas (with overlaps): (II) ATI(0): 1024 x 1279 rectangle at 0,768 (II) ATI(0): 768 x 1280 rectangle at 0,768 (II) ATI(0): Using XFree86 Acceleration Architecture (XAA) Screen to screen bit blits Solid filled rectangles 8x8 mono pattern filled rectangles Indirect CPU to Screen color expansion Solid Lines Offscreen Pixmaps Setting up tile and stipple cache: 32 128x128 slots 10 256x256 slots (==) ATI(0): Backing store disabled (==) ATI(0): Silken mouse enabled (**) Option "dpms" (**) ATI(0): DPMS enabled (==) RandR enabled (II) Initializing built-in extension MIT-SHM (II) Initializing built-in extension XInputExtension (II) Initializing built-in extension XTEST (II) Initializing built-in extension XKEYBOARD (II) Initializing built-in extension LBX (II) Initializing built-in extension XC-APPGROUP (II) Initializing built-in extension SECURITY (II) Initializing built-in extension XINERAMA (II) Initializing built-in extension XFree86-Bigfont (II) Initializing built-in extension RENDER (II) Initializing built-in extension RANDR (**) Option "Protocol" "PS/2" (**) Mouse0: Protocol: "PS/2" (**) Option "CorePointer" (**) Mouse0: Core Pointer (**) Option "Device" "/dev/psaux" (**) Option "Emulate3Buttons" "yes" (**) Mouse0: Emulate3Buttons, Emulate3Timeout: 50 (**) Option "ZAxisMapping" "4 5" (**) Mouse0: ZAxisMapping: buttons 4 and 5 (**) Mouse0: Buttons: 5 (II) Keyboard "Keyboard0" handled by legacy driver (**) Option "Protocol" "IMPS/2" (**) DevInputMice: Protocol: "IMPS/2" (**) Option "AlwaysCore" (**) DevInputMice: always reports core events (**) Option "Device" "/dev/input/mice" (**) Option "Emulate3Buttons" "no" (**) Option "ZAxisMapping" "4 5" (**) DevInputMice: ZAxisMapping: buttons 4 and 5 (**) DevInputMice: Buttons: 5 (II) XINPUT: Adding extended input device "DevInputMice" (type: MOUSE) (II) XINPUT: Adding extended input device "Mouse0" (type: MOUSE) (II) Mouse0: ps2EnableDataReporting: succeeded (II) DevInputMice: ps2EnableDataReporting: succeeded [kdw@gaia log]# [kdw@gaia log]# cat gdm cat: gdm: Is a directory [kdw@gaia log]# cd gdm [kdw@gaia gdm]# ls :0.log :0.log.1 :0.log.2 :0.log.3 :0.log.4 [kdw@gaia gdm]# cat :0.log XFree86 Version 4.3.0 (Red Hat Linux release: 4.3.0-2) Release Date: 27 February 2003 X Protocol Version 11, Revision 0, Release 6.6 Build Operating System: Linux 2.4.20-3bigmem i686 [ELF] Build Date: 27 February 2003 Build Host: porky.devel.redhat.com Before reporting problems, check http://www.XFree86.Org/ to make sure that you have the latest version. Module Loader present OS Kernel: Linux version 2.4.20-20.9smp (bhcompile@stripples.devel.redhat.com) (gcc version 3.2.2 20030222 (Red Hat Linu x 3.2.2-5)) #1 SMP Mon Aug 18 11:32:15 EDT 2003 Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/XFree86.0.log", Time: Tue Nov 11 09:17:47 2003 (==) Using config file: "/etc/X11/XF86Config" [kdw@gaia gdm]# [kdw@gaia gdm]# cat :0.log.4 XFree86 Version 4.3.0 (Red Hat Linux release: 4.3.0-2) Release Date: 27 February 2003 X Protocol Version 11, Revision 0, Release 6.6 Build Operating System: Linux 2.4.20-3bigmem i686 [ELF] Build Date: 27 February 2003 Build Host: porky.devel.redhat.com Before reporting problems, check http://www.XFree86.Org/ to make sure that you have the latest version. Module Loader present OS Kernel: Linux version 2.4.20-20.9smp (bhcompile@stripples.devel.redhat.com) (gcc version 3.2.2 20030222 (Red Hat Linu x 3.2.2-5)) #1 SMP Mon Aug 18 11:32:15 EDT 2003 Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/XFree86.0.log", Time: Tue Nov 4 11:17:11 2003 (==) Using config file: "/etc/X11/XF86Config" AUDIT: Tue Nov 4 16:22:01 2003: 1499 X: client 4 rejected from local host [kdw@gaia gdm]# [kdw@gaia log]# cat kdm.log Fatal server error: Server is already active for display 0 If this server is no longer running, remove /tmp/.X0-lock and start again. When reporting a problem related to a server crash, please send the full server output, not just the last messages. Please report problems to xfree86@xfree86.org. [kdw@gaia log]# From bax3@bigfoot.com Tue Nov 11 16:04:00 2003 From: bax3@bigfoot.com (Michael Bax (NO.SPAM)) Date: Tue, 11 Nov 2003 16:04:00 -0000 Subject: xcalc glitches Message-ID: Hi xcalc occasionally doesn't see the X server: >xcalc Error: Can't open display: 127.0.0.1:0.0 It gives a warning when it opens correctly: >xcalc Warning: No type converter registered for 'String' to 'Bitmap' conversion. Why is this? This is a fresh installation of Cygwin DLL 1.5.5-1 running on Windows 2000 SP4. Thanks Michael From tulitanssi@luukku.com Tue Nov 11 16:20:00 2003 From: tulitanssi@luukku.com (tulitanssi@luukku.com) Date: Tue, 11 Nov 2003 16:20:00 -0000 Subject: Updated: XFree86-xserv-4.3.0-22 Message-ID: <1068567633664.tulitanssi.84147.7Vkn1HREN9mFomXwwjMjiQ@luukku.com> Sorry, I'm not familiar with Xinput. I have used cygwin as-is, i.e. not deliberately disabling any of the cygwin features :-) How can I enable it? Thanks, Tuli ---------------- Yeah, this release discards repeats that come from Windows. It now relies on the Xinput layer to do the repeating. Are you disabling Xinput? I hope I have that terminology right... it might not be called Xinput. Harold tulitanssi@luukku.com wrote: Hi all, keyboard repeat does not work anymore with this new update. I think it worked with the previous (4.3.0-21) release. Any ideas? I'm using win2k. Thanks, Tuli ............................................................ Maksuton s?hk?posti aina k?yt?ss? http://luukku.com Kuukausimaksuton MTV3 Internet-liittym? www.mtv3.fi/liittyma From bax3.NO@SPAM.bigfoot.com Tue Nov 11 16:30:00 2003 From: bax3.NO@SPAM.bigfoot.com (Michael Bax) Date: Tue, 11 Nov 2003 16:30:00 -0000 Subject: XFree86 Start Menu shortcuts broken -- run.exe at falt? Message-ID: Hi My Cygwin root is C:\Program Files\Cygwin. The space appears to cause the automatically-created Cygwin-XFree86 shortcuts to fail. Run.exe pops up a dialog saying that it can't find Files\Cygwin\usr\X11R6\bin\run.exe" xclock -display 127.0.0.1:0.0 for example. It occurs even if the shortcut is invoked as C:\Progra~1\Cygwin\usr\bin\.... This is on a fresh installation of Cygwin DLL 1.5.5-1 running on Windows 2000 SP4, with XFree86-bin-4.3.0-6. Cheers Michael [Previously posted in error to wrong list, doh.] -------------- next part -------------- A non-text attachment was scrubbed... Name: cygcheck (abbreviated).out Type: application/octet-stream Size: 6159 bytes Desc: not available URL: From bax3.NO@SPAM.bigfoot.com Tue Nov 11 16:30:00 2003 From: bax3.NO@SPAM.bigfoot.com (Michael Bax) Date: Tue, 11 Nov 2003 16:30:00 -0000 Subject: XFree86 fails to see/render TrueType fonts Message-ID: Hi XFree86 fails to render TTF fonts on my computer. This is true for the bundled fonts/TTF/* as well as the Windows fonts. There are two problems: 1. XFree86 does not appear to include the X11 fonts/TTF directory in the font path by default. This can be shown by removing the Luxi fonts in the fonts/Type1 directory and rehashing. The server should use the TTF versions instead, but it does not see these fonts at all. This can be fixed using xset fp+, but surely the TTF font directory should be included in the path by default? 2. After xset fp+ and rehash, the TrueType fonts are listed in e.g. xfontsel. However, they are not rendered (or are rendered blank)! The same is true for my custom-installed TrueType fonts. They worked in XFree86 3.x, however, using the same installation procedure. Other fonts are fine, but all TrueType fonts are effectively invisible. This is on a fresh installation of Cygwin DLL 1.5.5-1 running on Windows 2000 SP4, with XFree86-bin-4.3.0-6. Cheers Michael [Previously posted in error to wrong list, doh.] -------------- next part -------------- A non-text attachment was scrubbed... Name: cygcheck (abbreviated).out Type: application/octet-stream Size: 6159 bytes Desc: not available URL: From cgf-no-personal-reply-please@cygwin.com Tue Nov 11 16:31:00 2003 From: cgf-no-personal-reply-please@cygwin.com (Christopher Faylor) Date: Tue, 11 Nov 2003 16:31:00 -0000 Subject: xfree86 fails to see/render TrueType fonts In-Reply-To: References: Message-ID: <20031111163136.GA26170@redhat.com> On Tue, Nov 11, 2003 at 08:26:20AM -0800, Michael Bax wrote: >XFree86 fails to render TTF fonts on my computer. This is true for the >bundled fonts/TTF/* as well as the Windows fonts. This is not the right mailing list for cygwin-xfree observations. Redirecting. >There are two problems: > >1. XFree86 does not appear to include the X11 fonts/TTF directory in the >font path by default. This can be shown by removing the Luxi fonts in the >fonts/Type1 directory and rehashing. The server should use the TTF versions >instead, but it does not see these fonts at all. This can be fixed using >xset fp+, but surely the TTF font directory should be included in the path >by default? > >2. After xset fp+ and rehash, the TrueType fonts are listed in e.g. >xfontsel. However, they are not rendered (or are rendered blank)! The same >is true for my custom-installed TrueType fonts. They worked in XFree86 3.x, >however, using the same installation procedure. > >Other fonts are fine, but all TrueType fonts are effectively invisible. > >This is on a fresh installation of Cygwin DLL 1.5.5-1 running on Windows >2000 SP4, with XFree86-bin-4.3.0-6. > >Cheers >Michael From Dr.Volker.Zell@oracle.com Tue Nov 11 16:33:00 2003 From: Dr.Volker.Zell@oracle.com (Dr. Volker Zell) Date: Tue, 11 Nov 2003 16:33:00 -0000 Subject: Updated: XFree86-xserv-4.3.0-22 In-Reply-To: <3FB0E0D5.7090505@msu.edu> (Harold L. Hunt, II's message of "Tue, 11 Nov 2003 08:15:01 -0500") References: <1068549020528.tulitanssi.36802.w1Q4NRjiTPWoQQzb3m7sWA@luukku.com> <3FB0E0D5.7090505@msu.edu> Message-ID: <87ptfyvpbj.fsf@vzell-de.de.oracle.com> >>>>> "Harold" == Harold L Hunt, writes: Harold> Yeah, this release discards repeats that come from Windows. It now Harold> relies on the Xinput layer to do the repeating. Are you disabling Harold> Xinput? I hope I have that terminology right... it might not be Harold> called Xinput. I see the same, how can I reenable the repeats in the Xinput layer ? Harold> Harold Ciao Volker From alexander.gottwald@s1999.tu-chemnitz.de Tue Nov 11 16:37:00 2003 From: alexander.gottwald@s1999.tu-chemnitz.de (Alexander Gottwald) Date: Tue, 11 Nov 2003 16:37:00 -0000 Subject: XWin works on Win2K but not on some WinXP clients In-Reply-To: References: Message-ID: On Tue, 11 Nov 2003, Woellert, Kirk D. wrote: > We are not running NAT. All firewalls are turned off completely (linux and > Win). We are all on the same network segment, and all have the same IP scope > (i.e. 137.x.x.x). > > I tried to get debug running as requested but, as a new linux user its not > straightforward to figure out how to stop kdm/gdm/xdm or whatever RH9 uses, > and restart it again. I looked at the post you cited and searched the net > also. "/etc/init.d/xdm stop" returns command not found. I tried several > iterations but no avail. So finally I did "xdm -debug 10 -no daemon", got a > fatal server error, did some grep's and here is the followoing: maybe /etc/init.d./gdm stop > [debug] > # This will enable debugging into the syslog, usually not neccessary > # and it creates a LOT of spew of random stuff to the syslog. However it > # can be useful in determining when something is going very wrong. > Enable=false Set this to true. Most likely gdm will create a logfile in /var/log/gdm > XFree86.log.1 > [kdw@gaia log]# cd gdm > [kdw@gaia gdm]# ls > :0.log :0.log.1 :0.log.2 :0.log.3 :0.log.4 > [kdw@gaia gdm]# cat :0.log These are all logfiles for the local xserver and do not contain information for your problem. > [kdw@gaia log]# cat kdm.log > > Fatal server error: > Server is already active for display 0 > If this server is no longer running, remove /tmp/.X0-lock > and start again. This is a normal error. There was already a xserver running on display 0 (started by gdm) and kdm tried to start another which failed. bye ago -- Alexander.Gottwald@s1999.tu-chemnitz.de http://www.gotti.org ICQ: 126018723 From danilo.turina@alcatel.it Tue Nov 11 16:42:00 2003 From: danilo.turina@alcatel.it (Danilo Turina) Date: Tue, 11 Nov 2003 16:42:00 -0000 Subject: Updated: XFree86-xserv-4.3.0-22 In-Reply-To: <1068567633664.tulitanssi.84147.7Vkn1HREN9mFomXwwjMjiQ@luukku.com> References: <1068567633664.tulitanssi.84147.7Vkn1HREN9mFomXwwjMjiQ@luukku.com> Message-ID: tulitanssi@luukku.com wrote: > Sorry, I'm not familiar with Xinput. I have used cygwin as-is, i.e. not deliberately disabling any of the cygwin features :-) > > How can I enable it? I had the same problem, then I discovered that in the custom script I used to start XFree, I had this parameter: -kb passed to XWin.exe (i.e. I had something like: XWin :0 -nowinkill -unixkill -kb -screen 0 1280 1024 ) Removing the "-kb" parameter (i.e. changing to something like: XWin :0 -nowinkill -unixkill -screen 0 1280 1024 ) Solved the problem. > > Thanks, > Tuli > > ---------------- > Yeah, this release discards repeats that come from Windows. It now relies on the Xinput layer to do the repeating. Are you disabling Xinput? I hope I have that terminology right... it might not be called Xinput. > > Harold > > tulitanssi@luukku.com wrote: > Hi all, > > keyboard repeat does not work anymore with this new update. I think it worked with the previous (4.3.0-21) release. Any ideas? > > I'm using win2k. > > > Thanks, > Tuli > > > ............................................................ > Maksuton s??hk??posti aina k??yt??ss?? http://luukku.com > Kuukausimaksuton MTV3 Internet-liittym?? www.mtv3.fi/liittyma > > From huntharo@msu.edu Tue Nov 11 16:45:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Tue, 11 Nov 2003 16:45:00 -0000 Subject: Updated: XFree86-xserv-4.3.0-22 In-Reply-To: <87ptfyvpbj.fsf@vzell-de.de.oracle.com> References: <1068549020528.tulitanssi.36802.w1Q4NRjiTPWoQQzb3m7sWA@luukku.com> <3FB0E0D5.7090505@msu.edu> <87ptfyvpbj.fsf@vzell-de.de.oracle.com> Message-ID: <3FB1123E.8090102@msu.edu> Are you using the -kb or -xkb parameters? I don't remember what the name of the parameter is that disables the repeats, but the above seems close. Harold Dr. Volker Zell wrote: >>>>>>"Harold" == Harold L Hunt, writes: > > > Harold> Yeah, this release discards repeats that come from Windows. It now > Harold> relies on the Xinput layer to do the repeating. Are you disabling > Harold> Xinput? I hope I have that terminology right... it might not be > Harold> called Xinput. > > I see the same, how can I reenable the repeats in the Xinput layer ? > > Harold> Harold > > Ciao > Volker > From pavelr@coresma.com Tue Nov 11 16:54:00 2003 From: pavelr@coresma.com (Pavel Rosenboim) Date: Tue, 11 Nov 2003 16:54:00 -0000 Subject: XWin works on Win2K but not on some WinXP clients In-Reply-To: References: Message-ID: <3FB11450.1040208@coresma.com> Alexander Gottwald wrote: > On Tue, 11 Nov 2003, Woellert, Kirk D. wrote: > > > We are not running NAT. All firewalls are turned off completely > (linux and > > Win). We are all on the same network segment, and all have the same > IP scope > > (i.e. 137.x.x.x). > > > > I tried to get debug running as requested but, as a new linux user > its not > > straightforward to figure out how to stop kdm/gdm/xdm or whatever RH9 > uses, > > and restart it again. I looked at the post you cited and searched the > net > > also. "/etc/init.d/xdm stop" returns command not found. I tried several > > iterations but no avail. So finally I did "xdm -debug 10 -no daemon", > got a > > fatal server error, did some grep's and here is the followoing: > > maybe /etc/init.d./gdm stop In RedHat systems xdm/kdm/gdm is started by init (as configured in /etc/inittab) so the only way to stop it is by switching to runlevel 3 - /sbin/init 3 > > > [debug] > > # This will enable debugging into the syslog, usually not neccessary > > # and it creates a LOT of spew of random stuff to the syslog. > However it > > # can be useful in determining when something is going very wrong. > > Enable=false > > Set this to true. Most likely gdm will create a logfile in > /var/log/gdm > > > XFree86.log.1 > > [kdw@gaia log]# cd gdm > > [kdw@gaia gdm]# ls > > :0.log :0.log.1 :0.log.2 :0.log.3 :0.log.4 > > [kdw@gaia gdm]# cat :0.log > > These are all logfiles for the local xserver and do not contain > information for your problem. > > > [kdw@gaia log]# cat kdm.log > > > > Fatal server error: > > Server is already active for display 0 > > If this server is no longer running, remove /tmp/.X0-lock > > and start again. > > This is a normal error. There was already a xserver running on display > 0 (started by gdm) and kdm tried to start another which failed. > > bye > ago > -- > Alexander.Gottwald@s1999.tu-chemnitz.de > http://www.gotti.org ICQ: 126018723 > From Dr.Volker.Zell@oracle.com Tue Nov 11 17:17:00 2003 From: Dr.Volker.Zell@oracle.com (Dr. Volker Zell) Date: Tue, 11 Nov 2003 17:17:00 -0000 Subject: Updated: XFree86-xserv-4.3.0-22 In-Reply-To: <3FB1123E.8090102@msu.edu> (Harold L. Hunt, II's message of "Tue, 11 Nov 2003 11:45:50 -0500") References: <1068549020528.tulitanssi.36802.w1Q4NRjiTPWoQQzb3m7sWA@luukku.com> <3FB0E0D5.7090505@msu.edu> <87ptfyvpbj.fsf@vzell-de.de.oracle.com> <3FB1123E.8090102@msu.edu> Message-ID: <87d6byvn9u.fsf@vzell-de.de.oracle.com> >>>>> "Harold" == Harold L Hunt, writes: Harold> Are you using the -kb or -xkb parameters? I don't remember what the Harold> name of the parameter is that disables the repeats, but the above Harold> seems close. No, but I found the culprit. I once downloaded a XF86Config-4 file from the net and placed it under /etc/X11 There was an entry Option "AutoRepeat" "500 20" After changing it to "200 40" woooow, it works even better as before... Harold> Harold Ciao Volker From pechtcha@cs.nyu.edu Tue Nov 11 19:59:00 2003 From: pechtcha@cs.nyu.edu (Igor Pechtchanski) Date: Tue, 11 Nov 2003 19:59:00 -0000 Subject: XFree86-bin-4.3.0-7 xterm keyboard focus problems Message-ID: Hi, all, I noticed that the xterm executable that comes with the 4.3.0-7 version of XFree86-bin has problems with keyboard focus. After the mouse pointer entered and left the window once, the keyboard input is ignored unless the mouse pointer is in the window. The window apparently keeps the focus, but no keyboard input is processed. Other executables don't suffer from this problem, and extracting the xterm from XFree86-bin-4.3.0-4 fixes it. I've tried running this with Exceed and also remotely on Linux through ssh. FWIW, here are the relevant files: $ ls -l /usr/X11R6/bin/xterm-* -r-xr-xr-x+ 1 igor Users 262656 Oct 30 11:14 /usr/X11R6/bin/xterm-4.3.0-7.exe -rwx--x--x 1 igor Administ 804352 Sep 20 14:52 /usr/X11R6/bin/xterm-4.3.0-4.exe The second file is manually extracted from the XFree86-bin-4.3.0-4 tarball. The reported version numbers are identical: $ xterm-4.3.0-7.exe -version XFree86 4.2.99.903(174) $ xterm-4.3.0-4 -version XFree86 4.2.99.903(174) The latter version seems to depend on three extra DLLs: $ cygcheck /usr/X11R6/bin/xterm-4.3.0-7.exe | sort -b > /tmp/a7 $ cygcheck /usr/X11R6/bin/xterm-4.3.0-4.exe | sort -b > /tmp/a4 $ diff -I xterm -w /tmp/a4 /tmp/a7 4a5 > C:/cygwin/usr/X11R6/bin\cygXaw-7.dll 6a8 > C:/cygwin/usr/X11R6/bin\cygXmu-6.dll 7a10 > C:/cygwin/usr/X11R6/bin\cygXt-6.dll I think libXt used to be linked in statically, but I don't recall xterm being dependent on libXaw before. xterm is the only executable that seems to have changed behavior in my case (xev, for example, works fine, i.e., respects the window manager's focus policy). I suspect this new dependence on libXaw is the culprit, as other Xaw-enabled apps (xfig, editres, etc) are notorious for having a mind of their own when it comes to keyboard focus. Can anyone confirm/deny this? If an unwanted dependence on libXaw was introduced in the xterm build, can it please be removed somehow? Thanks, Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_ pechtcha@cs.nyu.edu ZZZzz /,`.-'`' -. ;-;;,_ igor@watson.ibm.com |,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 From ford@vss.fsi.com Tue Nov 11 20:08:00 2003 From: ford@vss.fsi.com (Brian Ford) Date: Tue, 11 Nov 2003 20:08:00 -0000 Subject: XFree86-bin-4.3.0-7 xterm keyboard focus problems In-Reply-To: References: Message-ID: Igor, This has been reported several times before. Although, you have probably contributed a more detailed analysis. I don't know if xterm should depend on Xaw, but I do know that Xaw needs a hack similar to the lesstif one for VendorShell (from memory). Or maybe it was Xaw3d that needs that. Sorry to be so nebulous. I thought this info might tickle someones memory or fancy. On Tue, 11 Nov 2003, Igor Pechtchanski wrote: > Hi, all, > > I noticed that the xterm executable that comes with the 4.3.0-7 version of > XFree86-bin has problems with keyboard focus. After the mouse pointer > entered and left the window once, the keyboard input is ignored unless the > mouse pointer is in the window. The window apparently keeps the focus, > but no keyboard input is processed. Other executables don't suffer from > this problem, and extracting the xterm from XFree86-bin-4.3.0-4 fixes it. > I've tried running this with Exceed and also remotely on Linux through > ssh. FWIW, here are the relevant files: > > $ ls -l /usr/X11R6/bin/xterm-* > -r-xr-xr-x+ 1 igor Users 262656 Oct 30 11:14 /usr/X11R6/bin/xterm-4.3.0-7.exe > -rwx--x--x 1 igor Administ 804352 Sep 20 14:52 /usr/X11R6/bin/xterm-4.3.0-4.exe > > The second file is manually extracted from the XFree86-bin-4.3.0-4 > tarball. The reported version numbers are identical: > > $ xterm-4.3.0-7.exe -version > XFree86 4.2.99.903(174) > $ xterm-4.3.0-4 -version > XFree86 4.2.99.903(174) > > The latter version seems to depend on three extra DLLs: > > $ cygcheck /usr/X11R6/bin/xterm-4.3.0-7.exe | sort -b > /tmp/a7 > $ cygcheck /usr/X11R6/bin/xterm-4.3.0-4.exe | sort -b > /tmp/a4 > $ diff -I xterm -w /tmp/a4 /tmp/a7 > 4a5 > > C:/cygwin/usr/X11R6/bin\cygXaw-7.dll > 6a8 > > C:/cygwin/usr/X11R6/bin\cygXmu-6.dll > 7a10 > > C:/cygwin/usr/X11R6/bin\cygXt-6.dll > > I think libXt used to be linked in statically, but I don't recall xterm > being dependent on libXaw before. > > xterm is the only executable that seems to have changed behavior in my > case (xev, for example, works fine, i.e., respects the window manager's > focus policy). I suspect this new dependence on libXaw is the culprit, as > other Xaw-enabled apps (xfig, editres, etc) are notorious for having a > mind of their own when it comes to keyboard focus. > > Can anyone confirm/deny this? If an unwanted dependence on libXaw was > introduced in the xterm build, can it please be removed somehow? > Thanks, > Igor > -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444 From huntharo@msu.edu Tue Nov 11 20:15:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Tue, 11 Nov 2003 20:15:00 -0000 Subject: XFree86-bin-4.3.0-7 xterm keyboard focus problems In-Reply-To: References: Message-ID: <3FB14361.1040605@msu.edu> Brian Ford wrote: > Igor, > > This has been reported several times before. Although, you have probably > contributed a more detailed analysis. > > I don't know if xterm should depend on Xaw, but I do know that Xaw needs a > hack similar to the lesstif one for VendorShell (from memory). Or maybe > it was Xaw3d that needs that. > > Sorry to be so nebulous. I thought this info might tickle someones memory > or fancy. Right, the root problem is the switch from static Xt/Xaw to shared Xt/Xaw. Brian is right, we need a fix for VenderShell, just like we did for lesstif about two or three weeks ago. We need it fast too, based on the frequency of this bug being reported. Harold From joe@plaguesplace.dyndns.org Tue Nov 11 23:07:00 2003 From: joe@plaguesplace.dyndns.org (Me) Date: Tue, 11 Nov 2003 23:07:00 -0000 Subject: Control-Meta- broken in rxvt? Message-ID: <20031111230717.GF22712@plaguesplace.dyndns.org> The bahavior is the same in both the X version and the native version of rxvt(the meta key being alternate). If I press Escape Control-, that works as expected. joe -- From wrcygwin@riede.org Wed Nov 12 02:46:00 2003 From: wrcygwin@riede.org (Willem Riede) Date: Wed, 12 Nov 2003 02:46:00 -0000 Subject: XWin works on Win2K but not on some WinXP clients In-Reply-To: (from alexander.gottwald@s1999.tu-chemnitz.de on Tue, Nov 11, 2003 at 11:37:12 -0500) References: Message-ID: <20031112024609.GI13753@linnie.riede.org> On 2003.11.11 11:37, Alexander Gottwald wrote: > On Tue, 11 Nov 2003, Woellert, Kirk D. wrote: > > > We are not running NAT. All firewalls are turned off completely (linux and > > Win). We are all on the same network segment, and all have the same IP scope > > (i.e. 137.x.x.x). > > > > I tried to get debug running as requested but, as a new linux user its not > > straightforward to figure out how to stop kdm/gdm/xdm or whatever RH9 uses, > > and restart it again. I looked at the post you cited and searched the net > > also. "/etc/init.d/xdm stop" returns command not found. I tried several > > iterations but no avail. So finally I did "xdm -debug 10 -no daemon", got a > > fatal server error, did some grep's and here is the followoing: > > maybe /etc/init.d./gdm stop I'm running cygwin/xfree (on w2k) to RedHat, and I've found you need to do 'telinit 3' followed by 'telinit 5' as root from a console to get gdm to restart. > > [debug] > > # This will enable debugging into the syslog, usually not neccessary > > # and it creates a LOT of spew of random stuff to the syslog. However it > > # can be useful in determining when something is going very wrong. > > Enable=false > > Set this to true. Most likely gdm will create a logfile in > /var/log/gdm That's right, that change is the only thing I had to do on the RedHat side. As to the log file, right again - here is what I have: [root@linnie root]# ls -ltr /var/log/gdm .... -rw-r--r-- 1 root root 0 Apr 23 2003 winnie.riede.org:0.log .... Success, Willem Riede. From lorenzo.travaglio@fastwebnet.it Wed Nov 12 04:18:00 2003 From: lorenzo.travaglio@fastwebnet.it (Lorenzo Travaglio) Date: Wed, 12 Nov 2003 04:18:00 -0000 Subject: chmod Message-ID: <000701c3a8d3$e0917220$a124ff29@fastwebnet.it> Hi all, I've sent to myself from my office a little bash program. With Xterm it is impossible to change the peremissions even if 'chmod -v' says that new permissions have take place. I have no idea about, do you have one? Thank you From lorenzo.travaglio@fastwebnet.it Wed Nov 12 04:18:00 2003 From: lorenzo.travaglio@fastwebnet.it (Lorenzo Travaglio) Date: Wed, 12 Nov 2003 04:18:00 -0000 Subject: wmaker Message-ID: <000801c3a8d3$e0b303e0$a124ff29@fastwebnet.it> Every time I start Xwin32 ZoneAlarm asks me if I want to allow XWin32 to run as a server, so I answer yes. Then when I start Xterm from program bar ZoneAlarm asks me if I want to allow Xterm (or every other X app) to access the Internet. Nothing happens, neither I answer yes nor no. I want only run wmaker but I'm not connected in a LAN environment, I'm at home not in the office. What I've to do to reach to run wmaker? From huntharo@msu.edu Wed Nov 12 04:21:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Wed, 12 Nov 2003 04:21:00 -0000 Subject: wmaker In-Reply-To: <000801c3a8d3$e0b303e0$a124ff29@fastwebnet.it> References: <000801c3a8d3$e0b303e0$a124ff29@fastwebnet.it> Message-ID: <3FB1B55F.9020100@msu.edu> You talking about X-Win32 or XWin.exe? The former is a commercial product supported by a company not related to the Cygwin/X project (contact them for assistance), while the latter is the our executable that we can help you with. Please advise. Harold Lorenzo Travaglio wrote: > Every time I start Xwin32 ZoneAlarm asks me if I want to allow XWin32 to run > as a server, so I answer yes. Then when I start Xterm from program bar > ZoneAlarm asks me if I want to allow Xterm (or every other X app) to access > the Internet. Nothing happens, neither I answer yes nor no. I want only run > wmaker but I'm not connected in a LAN environment, I'm at home not in the > office. What I've to do to reach to run wmaker? > From lorenzo.travaglio@fastwebnet.it Wed Nov 12 04:37:00 2003 From: lorenzo.travaglio@fastwebnet.it (Lorenzo Travaglio) Date: Wed, 12 Nov 2003 04:37:00 -0000 Subject: Keyboard layout Message-ID: <000701c3a8d6$8f3838c0$a124ff29@fastwebnet.it> How about the keyboard layout? On my 103 key, Italian style, it is not possible to found braces even if on Window they are placed over square brackets and are activated with Alt-Shift-{left,right}bracket. From lorenzo.travaglio@fastwebnet.it Wed Nov 12 04:43:00 2003 From: lorenzo.travaglio@fastwebnet.it (Lorenzo Travaglio) Date: Wed, 12 Nov 2003 04:43:00 -0000 Subject: wmaker References: <000801c3a8d3$e0b303e0$a124ff29@fastwebnet.it> <3FB1B55F.9020100@msu.edu> Message-ID: <000d01c3a8d7$42a8ce60$a124ff29@fastwebnet.it> XWIN.exe is started automatically if I run startxwin.bat ----- Original Message ----- From: "Harold L Hunt II" To: Sent: Wednesday, November 12, 2003 5:21 AM Subject: Re: wmaker > You talking about X-Win32 or XWin.exe? The former is a commercial > product supported by a company not related to the Cygwin/X project > (contact them for assistance), while the latter is the our executable > that we can help you with. Please advise. > > Harold > > Lorenzo Travaglio wrote: > > > Every time I start Xwin32 ZoneAlarm asks me if I want to allow XWin32 to run > > as a server, so I answer yes. Then when I start Xterm from program bar > > ZoneAlarm asks me if I want to allow Xterm (or every other X app) to access > > the Internet. Nothing happens, neither I answer yes nor no. I want only run > > wmaker but I'm not connected in a LAN environment, I'm at home not in the > > office. What I've to do to reach to run wmaker? > > > From landy@alumni.caltech.edu Wed Nov 12 05:12:00 2003 From: landy@alumni.caltech.edu (Brian R.Landy) Date: Wed, 12 Nov 2003 05:12:00 -0000 Subject: Cygwin X server crashes when a remote Xemacs is run Message-ID: Hi, I see what appears to be the same crash (address 0x61093b2c), using Vim 6.2 with the GTK1 GUI. One remote system is running AIX, the other Solaris. The cygwin system runs NT 4 SP6. However, I only crash if I run XWin.exe -multiwindow. Switching to windowed, fullscreen, or even rootless causes the crash to go away. Nothing is written to Xwin.log after the normal startup messages. Brian > Here what I'm trying to do: > I establish a rsh connection with a UNIX/Linux machine and open an > xterm. > The I run Xemacs on this remote machine and XWin.exe crashes. > I tried it connecting with both a Linux machine and a Alpha machine. > Here > the Xemacs versions installed on those machines: > Linux - Xemacs 21.1 (patch 14) i386-redhat-linux > Alpha - Xemacs 20.4 alpha-dec-osf3.2 > > Here the Windows error message: > Exception: access violation (0xc0000005), Address: 0x61093b2c > > I'm running Cygwin 1.5.5-1 on Windows NT 4.0 Workstation. XWin.exe > version > is 4.3.0-20 > > Giampaolo Orrigo From huntharo@msu.edu Wed Nov 12 05:24:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Wed, 12 Nov 2003 05:24:00 -0000 Subject: wmaker In-Reply-To: <000d01c3a8d7$42a8ce60$a124ff29@fastwebnet.it> References: <000801c3a8d3$e0b303e0$a124ff29@fastwebnet.it> <3FB1B55F.9020100@msu.edu> <000d01c3a8d7$42a8ce60$a124ff29@fastwebnet.it> Message-ID: <3FB1C425.8030008@msu.edu> Lorenzo Travaglio wrote: > XWIN.exe is started automatically if I run startxwin.bat Of course, XWin.exe is started from startxwin.bat, but you said "Every time I start Xwin32". See, you said Xwin32, which confused me. All I have to go on is what *you* write. I cannot assume that you did not mean to write what you wrote, especially when what you wrote matches the name of something that I know to exist and that could be easily confused with our project. So, you are running startxwin.bat and getting the problem, not launching that other X Server called X-Win32, right? Harold From huntharo@msu.edu Wed Nov 12 05:25:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Wed, 12 Nov 2003 05:25:00 -0000 Subject: Cygwin X server crashes when a remote Xemacs is run In-Reply-To: References: Message-ID: <3FB1C452.3090309@msu.edu> Anybody care to run a debug build of XWin.exe in gdb to find the crash location? Harold Brian R.Landy wrote: > > Hi, I see what appears to be the same crash (address 0x61093b2c), using > Vim 6.2 with the GTK1 GUI. One remote system is running AIX, the other > Solaris. The cygwin system runs NT 4 SP6. > > However, I only crash if I run XWin.exe -multiwindow. Switching to > windowed, fullscreen, or even rootless causes the crash to go away. > > Nothing is written to Xwin.log after the normal startup messages. > > > Brian > >> Here what I'm trying to do: >> I establish a rsh connection with a UNIX/Linux machine and open an xterm. >> The I run Xemacs on this remote machine and XWin.exe crashes. >> I tried it connecting with both a Linux machine and a Alpha machine. >> Here >> the Xemacs versions installed on those machines: >> Linux - Xemacs 21.1 (patch 14) i386-redhat-linux >> Alpha - Xemacs 20.4 alpha-dec-osf3.2 >> >> Here the Windows error message: >> Exception: access violation (0xc0000005), Address: 0x61093b2c >> >> I'm running Cygwin 1.5.5-1 on Windows NT 4.0 Workstation. XWin.exe >> version >> is 4.3.0-20 >> >> Giampaolo Orrigo > > From alexander.gottwald@s1999.tu-chemnitz.de Wed Nov 12 07:24:00 2003 From: alexander.gottwald@s1999.tu-chemnitz.de (Alexander Gottwald) Date: Wed, 12 Nov 2003 07:24:00 -0000 Subject: Keyboard layout In-Reply-To: <000701c3a8d6$8f3838c0$a124ff29@fastwebnet.it> References: <000701c3a8d6$8f3838c0$a124ff29@fastwebnet.it> Message-ID: On Wed, 12 Nov 2003, Lorenzo Travaglio wrote: > How about the keyboard layout? > On my 103 key, Italian style, it is not possible to found braces even if on > Window they are placed over square brackets and are activated with > Alt-Shift-{left,right}bracket. Where are those keys on the italian keyboard? I've tried with the windows layout and could not produce any symbol with alt-shift-8 (assuming you mean this with bracket) bye ago -- Alexander.Gottwald@s1999.tu-chemnitz.de http://www.gotti.org ICQ: 126018723 From danilo.turina@alcatel.it Wed Nov 12 07:40:00 2003 From: danilo.turina@alcatel.it (Danilo Turina) Date: Wed, 12 Nov 2003 07:40:00 -0000 Subject: Keyboard layout In-Reply-To: References: <000701c3a8d6$8f3838c0$a124ff29@fastwebnet.it> Message-ID: Alexander Gottwald wrote: > On Wed, 12 Nov 2003, Lorenzo Travaglio wrote: > > >>How about the keyboard layout? >>On my 103 key, Italian style, it is not possible to found braces even if on >>Window they are placed over square brackets and are activated with >>Alt-Shift-{left,right}bracket. This is a known "problem", at the moment I use a US-EN keyboard so I don't have this kind of problems, anyway sometime ago I had a notebook with an italian keyboard. In order to have characters like "{", "}" (but also "`" that is vital for shell commands) I had to use xmodmap. If you use search Google for italian+keyboard+xmodmap you should find everything you need. > Where are those keys on the italian keyboard? I've tried with the windows > layout and could not produce any symbol with alt-shift-8 (assuming you > mean this with bracket) In an italian keyboard at the right of the "P" key instead of the "["/"{" and "]"/"}" keys that you usually find in US/EN keyboards you have accented letters. Within Windows (try the nodepad) you can always produce "{" and "}" characters by pressing "Alt Gr" + one of the above keys. > > bye > ago Bye, Danilo From tiroy@poczta.onet.pl Wed Nov 12 08:03:00 2003 From: tiroy@poczta.onet.pl (Tomasz Rojek) Date: Wed, 12 Nov 2003 08:03:00 -0000 Subject: wmaker References: <000801c3a8d3$e0b303e0$a124ff29@fastwebnet.it> Message-ID: > office. What I've to do to reach to run wmaker? Hi, My advise is a workaround, not a solution, but if I were you I would choose Kerio Personal Firewall instead of ZoneAlarm. Besides other advantages KPF does not cause such problems. -- Best regards Tomasz Rojek From rainer.kirsch@at.tiscali.com Wed Nov 12 08:21:00 2003 From: rainer.kirsch@at.tiscali.com (Kirsch, Rainer) Date: Wed, 12 Nov 2003 08:21:00 -0000 Subject: xterm switching problem Message-ID: Dear Cygwin/XFree development team, I want to inform you about a problem which exists using xterm together with WindowMaker and rootless XWin. I am starting XFree via: XWin -screen 0 1024 768 -clipboard -rootless -emulate3buttons 100 & setxkbmap de nodeadkeys & wmaker.exe xterm blocks (refusing to react to normal keyboard entry) after being started and if you alter the focus clicking on the (window maker provided) title bar of a xterm window. If you click into the (inner part of the) window it not only gets the focus but also starts to react normally. If you use an old xterm binary e.g. that of 4.3.0-4, the window starts working immediately even if you click onto its title bar (which is the expected behaviour). ----------------------------------------------------------- cygcheck -s tells us following about dll's and versions: 61k 2003/08/09 E:\z_cygwin\bin\cygbz2-1.dll 7k 2003/10/19 E:\z_cygwin\bin\cygcrypt-0.dll 842k 2003/09/30 E:\z_cygwin\bin\cygcrypto-0.9.7.dll 645k 2003/04/11 E:\z_cygwin\bin\cygcrypto.dll 22k 2003/10/17 E:\z_cygwin\bin\cygcygipc-2.dll 380k 2002/07/24 E:\z_cygwin\bin\cygdb-3.1.dll 831k 2003/09/20 E:\z_cygwin\bin\cygdb-4.1.dll 487k 2002/07/24 E:\z_cygwin\bin\cygdb_cxx-3.1.dll 1080k 2003/09/20 E:\z_cygwin\bin\cygdb_cxx-4.1.dll 132k 2003/07/12 E:\z_cygwin\bin\cygexpat-0.dll 131k 2003/10/28 E:\z_cygwin\bin\cygfontconfig-1.dll 45k 2001/04/25 E:\z_cygwin\bin\cygform5.dll 35k 2002/01/09 E:\z_cygwin\bin\cygform6.dll 48k 2003/08/09 E:\z_cygwin\bin\cygform7.dll 361k 2003/10/25 E:\z_cygwin\bin\cygfreetype-6.dll 28k 2003/07/20 E:\z_cygwin\bin\cyggdbm-3.dll 30k 2003/08/11 E:\z_cygwin\bin\cyggdbm-4.dll 19k 2003/03/22 E:\z_cygwin\bin\cyggdbm.dll 15k 2003/07/20 E:\z_cygwin\bin\cyggdbm_compat-3.dll 15k 2003/08/11 E:\z_cygwin\bin\cyggdbm_compat-4.dll 69k 2003/08/10 E:\z_cygwin\bin\cyggettextlib-0-12-1.dll 12k 2003/08/10 E:\z_cygwin\bin\cyggettextpo-0.dll 134k 2003/08/10 E:\z_cygwin\bin\cyggettextsrc-0-12-1.dll 17k 2001/06/28 E:\z_cygwin\bin\cyghistory4.dll 29k 2003/08/10 E:\z_cygwin\bin\cyghistory5.dll 958k 2003/08/10 E:\z_cygwin\bin\cygiconv-2.dll 22k 2001/12/13 E:\z_cygwin\bin\cygintl-1.dll 37k 2003/08/10 E:\z_cygwin\bin\cygintl-2.dll 21k 2001/06/20 E:\z_cygwin\bin\cygintl.dll 132k 2003/08/11 E:\z_cygwin\bin\cygjpeg-62.dll 119k 2002/02/09 E:\z_cygwin\bin\cygjpeg6b.dll 26k 2001/04/25 E:\z_cygwin\bin\cygmenu5.dll 20k 2002/01/09 E:\z_cygwin\bin\cygmenu6.dll 29k 2003/08/09 E:\z_cygwin\bin\cygmenu7.dll 156k 2001/04/25 E:\z_cygwin\bin\cygncurses++5.dll 175k 2002/01/09 E:\z_cygwin\bin\cygncurses++6.dll 226k 2001/04/25 E:\z_cygwin\bin\cygncurses5.dll 202k 2002/01/09 E:\z_cygwin\bin\cygncurses6.dll 224k 2003/08/09 E:\z_cygwin\bin\cygncurses7.dll 15k 2001/04/25 E:\z_cygwin\bin\cygpanel5.dll 12k 2002/01/09 E:\z_cygwin\bin\cygpanel6.dll 19k 2003/08/09 E:\z_cygwin\bin\cygpanel7.dll 67k 2003/09/10 E:\z_cygwin\bin\cygpcre-0.dll 63k 2003/04/11 E:\z_cygwin\bin\cygpcre.dll 15k 2003/09/10 E:\z_cygwin\bin\cygpcreposix-0.dll 61k 2003/04/11 E:\z_cygwin\bin\cygpcreposix.dll 1049k 2003/11/07 E:\z_cygwin\bin\cygperl5_8_2.dll 168k 2003/08/10 E:\z_cygwin\bin\cygpng10.dll 173k 2003/08/10 E:\z_cygwin\bin\cygpng12.dll 22k 2002/06/09 E:\z_cygwin\bin\cygpopt-0.dll 108k 2001/06/28 E:\z_cygwin\bin\cygreadline4.dll 148k 2003/08/10 E:\z_cygwin\bin\cygreadline5.dll 171k 2003/09/30 E:\z_cygwin\bin\cygssl-0.9.7.dll 165k 2003/04/11 E:\z_cygwin\bin\cygssl.dll 281k 2003/02/24 E:\z_cygwin\bin\cygtiff3.dll 282k 2003/08/11 E:\z_cygwin\bin\cygtiff4.dll 25k 2002/07/14 E:\z_cygwin\bin\cygungif-4.dll 60k 2003/08/09 E:\z_cygwin\bin\cygz.dll 949k 2003/09/20 E:\z_cygwin\bin\cygwin1.dll Cygwin DLL version info: DLL version: 1.5.5 DLL epoch: 19 DLL bad signal mask: 19005 DLL old termios: 5 DLL malloc env: 28 API major: 0 API minor: 94 Shared data: 3 DLL identifier: cygwin1 Mount registry: 2 Cygnus registry name: Cygnus Solutions Cygwin registry name: Cygwin Program options name: Program Options Cygwin mount registry name: mounts v2 Cygdrive flags: cygdrive flags Cygdrive prefix: cygdrive prefix Cygdrive default prefix: Build date: Sat Sep 20 16:31:15 EDT 2003 CVS tag: cr-0x9b Shared id: cygwin1S3 247k 2003/10/30 E:\z_cygwin\usr\X11R6\bin\cygdps-1.dll 124k 2003/10/30 E:\z_cygwin\usr\X11R6\bin\cygdpstk-1.dll 176k 2003/09/20 E:\z_cygwin\usr\X11R6\bin\cygfontconfig-1.dll 282k 2003/10/28 E:\z_cygwin\usr\X11R6\bin\cygfreetype-9.dll 392k 2003/10/30 E:\z_cygwin\usr\X11R6\bin\cygGL-1.dll 446k 2003/10/30 E:\z_cygwin\usr\X11R6\bin\cygGLU-1.dll 75k 2003/10/30 E:\z_cygwin\usr\X11R6\bin\cygICE-6.dll 9k 2003/10/30 E:\z_cygwin\usr\X11R6\bin\cygoldX-6.dll 1299k 2003/10/30 E:\z_cygwin\usr\X11R6\bin\cygOSMesa-4.dll 20k 2003/10/30 E:\z_cygwin\usr\X11R6\bin\cygpsres-1.dll 30k 2003/10/30 E:\z_cygwin\usr\X11R6\bin\cygSM-6.dll 883k 2003/10/30 E:\z_cygwin\usr\X11R6\bin\cygX11-6.dll 363k 2003/10/30 E:\z_cygwin\usr\X11R6\bin\cygXaw-7.dll 36k 2003/10/30 E:\z_cygwin\usr\X11R6\bin\cygXcursor-1.dll 51k 2003/10/30 E:\z_cygwin\usr\X11R6\bin\cygXext-6.dll 57k 2003/10/30 E:\z_cygwin\usr\X11R6\bin\cygXft-1.dll 76k 2003/10/30 E:\z_cygwin\usr\X11R6\bin\cygXft-2.dll 28k 2003/10/30 E:\z_cygwin\usr\X11R6\bin\cygXi-6.dll 77k 2003/10/30 E:\z_cygwin\usr\X11R6\bin\cygXmu-6.dll 11k 2003/10/30 E:\z_cygwin\usr\X11R6\bin\cygXmuu-1.dll 27k 2003/10/30 E:\z_cygwin\usr\X11R6\bin\cygXp-6.dll 52k 2003/10/30 E:\z_cygwin\usr\X11R6\bin\cygXpm-4.dll 14k 2003/10/30 E:\z_cygwin\usr\X11R6\bin\cygXrandr-2.dll 27k 2003/10/30 E:\z_cygwin\usr\X11R6\bin\cygXrender-1.dll 291k 2003/10/30 E:\z_cygwin\usr\X11R6\bin\cygXt-6.dll 28k 2003/10/30 E:\z_cygwin\usr\X11R6\bin\cygXTrap-6.dll 18k 2003/10/30 E:\z_cygwin\usr\X11R6\bin\cygXtst-6.dll 16k 2003/10/30 E:\z_cygwin\usr\X11R6\bin\cygXv-1.dll Cygwin Package Information Package Version _update-info-dir 00223-1 ash 20031007-1 base-files 2.6-1 base-passwd 1.1-1 bash 2.05b-16 bc 1.06-1 binutils 20030901-1 bzip2 1.0.2-5 check 0.8.4-1 clear 1.0-1 clisp 2.31-2 cpio 2.5-3 crypt 1.1-1 cygipc 2.02-1 cygutils 1.2.2-1 cygwin 1.5.5-1 cygwin-doc 1.3-6 diffutils 2.8.4-1 editrights 1.01-1 expat 1.95.6-2 file 4.03-2 fileutils 4.1-2 findutils 4.1.7-4 fontconfig 2.2.0-1 freetype2 2.1.5-1 fvwm 2.4.7-3 gawk 3.1.3-4 gcc 3.3.1-3 gcc-core 3.3.1-3 gcc-mingw 20030911-4 gcc-mingw-core 20031020-1 gdbm 1.8.3-7 gettext 0.12.1-3 ghostscript 7.05-2 ghostscript-base 7.05-2 gnugo 3.4-1 grep 2.5-1 groff 1.18.1-2 gzip 1.3.5-1 inetutils 1.3.2-25 jpeg 6b-11 less 381-1 libbz2_1 1.0.2-5 libdb3.1 3.1.17-2 libdb4.1 4.1.25-1 libfontconfig-devel 2.2.0-1 libfontconfig1 2.2.0-1 libfreetype2-devel 2.1.5-1 libfreetype26 2.1.5-1 libgdbm 1.8.0-5 libgdbm-devel 1.8.3-7 libgdbm3 1.8.3-3 libgdbm4 1.8.3-7 libgettextpo0 0.12.1-3 libiconv2 1.9.1-3 libintl 0.10.38-3 libintl1 0.10.40-1 libintl2 0.12.1-3 libjpeg62 6b-11 libjpeg6b 6b-8 libncurses5 5.2-1 libncurses6 5.2-8 libncurses7 5.3-4 libpcre 4.1-1 libpcre0 4.4-2 libpng 1.2.5-4 libpng10 1.0.15-4 libpng12 1.2.5-4 libpopt0 1.6.4-4 libreadline4 4.1-2 libreadline5 4.3-5 libtiff-devel 3.6.0-5 libtiff3 3.6.0-2 libtiff4 3.6.0-5 libungif 4.1.0-2 login 1.9-7 lynx 2.8.4-7 make 3.80-1 man 1.5j-2 mc 4.6.0-4 mingw-runtime 3.2-1 mktemp 1.5-3 ncurses 5.3-4 openssh 3.7.1p2-2 openssl 0.9.7c-1 openssl096 0.9.6j-1 pcre 4.4-2 pcre-doc 4.4-2 perl 5.8.2-1 postgresql 7.3.4-2 procps 010801-2 python 2.3.2-1 readline 4.3-5 sed 4.0.7-3 sh-utils 2.0.15-4 tar 1.13.25-5 tcltk 20030901-1 termcap 20021106-2 terminfo 5.3_20030726-1 texinfo 4.2-4 textutils 2.0.21-1 tiff 3.6.0-5 unzip 5.50-5 vim 6.2.098-1 w32api 2.4-1 wget 1.9-1 which 1.5-2 WindowMaker 0.80.2-1 XFree86-base 4.3.0-1 XFree86-bin 4.3.0-7 XFree86-etc 4.3.0-5 XFree86-fenc 4.2.0-3 XFree86-fnts 4.2.0-3 XFree86-lib 4.3.0-1 XFree86-lib-compat 4.3.0-2 XFree86-startup-scripts 4.2.0-5 XFree86-xserv 4.3.0-22 zip 2.3-5 zlib 1.1.4-4 ----------------------------------- Greetings DI Rainer Kirsch - Systems Engineer Tiscali ?sterreich GmbH Diefenbachgasse 35 A-1150 Wien, Austria Tel: +43/(0)1/502 86 - 0 FAX: +43/(0)1/502 86 - 199 mailto:rainer.kirsch@at.tiscali.com From murakami@ipl.t.u-tokyo.ac.jp Wed Nov 12 08:42:00 2003 From: murakami@ipl.t.u-tokyo.ac.jp (Takuma Murakami) Date: Wed, 12 Nov 2003 08:42:00 -0000 Subject: multiplemonitors In-Reply-To: References: Message-ID: <20031112174031.1A9D.MURAKAMI@ipl.t.u-tokyo.ac.jp> > I know they're running the same display depth. What's pixel format? I Even if both display has 32bit for a pixel, the formats could differ. The format includes the order of RGB components or the number of bits assigned for each component, for example. If you connect two displays with one card, it should work. Takuma Murakami (murakami@ipl.t.u-tokyo.ac.jp) From murakami@ipl.t.u-tokyo.ac.jp Wed Nov 12 08:55:00 2003 From: murakami@ipl.t.u-tokyo.ac.jp (Takuma Murakami) Date: Wed, 12 Nov 2003 08:55:00 -0000 Subject: Updated: XFree86-xserv-4.3.0-22 In-Reply-To: <1068549020528.tulitanssi.36802.w1Q4NRjiTPWoQQzb3m7sWA@luukku.com> References: <1068549020528.tulitanssi.36802.w1Q4NRjiTPWoQQzb3m7sWA@luukku.com> Message-ID: <20031112175513.1AA4.MURAKAMI@ipl.t.u-tokyo.ac.jp> > keyboard repeat does not work anymore with this new update. I think it worked with the previous (4.3.0-21) release. Any ideas? The command 'xset r on' should enable auto-repeat on the X Window layer. xset can set auto-repeat parameters in detail (please see 'man xset'). Of course it is better to check -kb option or XF86Config-4 file for more sophisticated configuration. Takuma Murakami (murakami@ipl.t.u-tokyo.ac.jp) From balakris75@godknowswhy.blackcanyon.ca Wed Nov 12 09:10:00 2003 From: balakris75@godknowswhy.blackcanyon.ca (balakris75) Date: Wed, 12 Nov 2003 09:10:00 -0000 Subject: it is a long story Message-ID: For few days http://www.geocities.com/verseau80510/index28.html Then you wil be able to get http://www.geocities.com/heinlein56754/index28.html As I promised Bye From alexander.gottwald@s1999.tu-chemnitz.de Wed Nov 12 10:53:00 2003 From: alexander.gottwald@s1999.tu-chemnitz.de (Alexander Gottwald) Date: Wed, 12 Nov 2003 10:53:00 -0000 Subject: Keyboard layout In-Reply-To: References: <000701c3a8d6$8f3838c0$a124ff29@fastwebnet.it> Message-ID: On Wed, 12 Nov 2003, Danilo Turina wrote: > This is a known "problem", at the moment I use a US-EN keyboard so I > don't have this kind of problems, anyway sometime ago I had a notebook > with an italian keyboard. > > In order to have characters like "{", "}" (but also "`" that is vital > for shell commands) I had to use xmodmap. append this to /etc/X11/xkb/symbols/pc/it partial alphanumeric_keys xkb_symbols "win" { // Modifies the basic italian layout to eliminate all dead keys include "pc/it(basic)" key { [ egrave, eacute, bracketleft, braceleft ] }; key { [ plus, asterisk, bracketright, braceright ] }; }; now you can set this layout with "setxkbmap it win" or configure it in /etc/X11/XF86Config. http://xfree86.cygwin.com/docs/faq/cygwin-xfree-faq.html#q-non-U.S.-keyboard-layout The XKB entries are Option "XkbRules" "xfree86" Option "XkbModel" "pc105" Option "XkbLayout" "it" Option "XkbVariant" "win" -- Alexander.Gottwald@s1999.tu-chemnitz.de http://www.gotti.org ICQ: 126018723 From sb@dod.no Wed Nov 12 11:38:00 2003 From: sb@dod.no (Steinar Bang) Date: Wed, 12 Nov 2003 11:38:00 -0000 Subject: xinit: The application has failed to start because cygfreetype-6.dll was not found. References: <3FA142F1.5030604@msu.edu> <3FA4921D.40102@rbcmail.ru> <3FA5496D.2090708@msu.edu> <87brro4924.fsf@home.lan> <3FABD910.1000508@msu.edu> Message-ID: <877k25yfz8.fsf@home.lan> >>>>> Harold L Hunt II : > You need the libfreetype26 package, which is gotten by selecting the > freetype2 package. It should have been automatically selected, but > it looks like it wasn't in your case. When I started setup.exe right now, and clicked keep on the XFree86-xserv package, the libfreetype26 package was selected and was installed. > Also, make sure that you have the fontconfig package (it > auto-selects libfontconfig0). Forgot to check that, but I guess it was installed, because it works now. Thanx! From jerome.s@tiscali.be Wed Nov 12 12:52:00 2003 From: jerome.s@tiscali.be (jerome.s@tiscali.be) Date: Wed, 12 Nov 2003 12:52:00 -0000 Subject: Console login does not display anymore only from one laptop Message-ID: <3FA91B8000003296@ocpmta3.freegates.net> Hello, Cygwin is installed on several computer. I. On all the computers I can get a Xwindow console login to my Solaris server typing: /usr/X11R6/bin/Xwin.exe :0 -query ipaddressofthesolarisserver1 & II. On one machine, I do not get the console login (I only get the big black screen of the Cygwin/XFree window with the cursor indicating that the task of getting the console login is processing). II.1 However, it used to work on this machine. II.2 On this machine, I can still get the console login when I try to reach an other solaris server i.e typing: /usr/X11R6/bin/Xwin.exe :0 -query ipaddressofthesolarisserver2 & III. Any ideas a) a daemon still running? b) Firewall? (I have stopped my private firewall and rebooted my laptop) c) a config file (they have not been modified and it used to work) d) too many parallel sessions? Cheers, J?r?me ------------------------------------------------------------------------- Tiscali ADSL: 3 mois GRATUITS! L'Internet rapide, c'est pour tout le monde. http://reg.tiscali.be/default.asp?lg=fr From pechtcha@cs.nyu.edu Wed Nov 12 14:58:00 2003 From: pechtcha@cs.nyu.edu (Igor Pechtchanski) Date: Wed, 12 Nov 2003 14:58:00 -0000 Subject: chmod In-Reply-To: <000701c3a8d3$e0917220$a124ff29@fastwebnet.it> References: <000701c3a8d3$e0917220$a124ff29@fastwebnet.it> Message-ID: Lorenzo, This doesn't seem to be XFree-related, so the proper list is . I've redirected this there. More replies inline below. On Wed, 12 Nov 2003, Lorenzo Travaglio wrote: > Hi all, > I've sent to myself from my office a little bash program. With Xterm it is > impossible to change the peremissions even if 'chmod -v' says that new > permissions have take place. I have no idea about, do you have one? > > Thank you The FAQ is your friend: However, that entry is missing one important bit: if you're on a FAT32 filesystem, you're out of luck as well. Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_ pechtcha@cs.nyu.edu ZZZzz /,`.-'`' -. ;-;;,_ igor@watson.ibm.com |,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 From kirk.woellert@ngc.com Wed Nov 12 15:01:00 2003 From: kirk.woellert@ngc.com (Woellert, Kirk D.) Date: Wed, 12 Nov 2003 15:01:00 -0000 Subject: XWin works on Win2K but not on some WinXP clients Message-ID: Ok, the last post suggested that I try to run XDM in debug mode. In order to do that you must drop out of the display manager. In order to do that you must change to run level 3 since there is no such thing as an XDM stop command. I did the following: telinit 3 xdm -debug 10 -nodaemon telinit 5 I assumed I wanted to get back into the default run level 5. After doing the above sequence of commands, it turns out that two displays get launched on my linux server. "0" which is the display that was dropped to run level 3, and "1" which is in run level 5. We get a msg that says hey display 0 is busy launching display 1. I don't think this was your guys intent. So I did the following: telinit 3 xdm -debug 10 -nodaemon & (so I can keep my ssh window) When we do this the guy on the Win2K box can no longer login, (no one else either). I hard reboot the linux box, and now the Win2K box can login. [root@gaia log]# cat xdm-errors xdm error (pid 1802): error 98 binding socket address 177 Fatal server error: Server is already active for display 0 If this server is no longer running, remove /tmp/.X0-lock and start again. When reporting a problem related to a server crash, please send the full server output, not just the last messages. Please report problems to xfree86@xfree86.org. xdm error (pid 1802): server unexpectedly died xdm error (pid 1802): Server for display :0 can't be started, session disabled [root@gaia log]# Some log file samples [root@gaia gdm]# ls :0.log :0.log.1 :0.log.2 :0.log.3 :0.log.4 :1.log :1.log.1 :1.log.2 :1.log.3 :1.log.4 [root@gaia gdm]# cat :0.log XFree86 Version 4.3.0 (Red Hat Linux release: 4.3.0-2) Release Date: 27 February 2003 X Protocol Version 11, Revision 0, Release 6.6 Build Operating System: Linux 2.4.20-3bigmem i686 [ELF] Build Date: 27 February 2003 Build Host: porky.devel.redhat.com Before reporting problems, check http://www.XFree86.Org/ to make sure that you have the latest version. Module Loader present OS Kernel: Linux version 2.4.20-20.9smp (bhcompile@stripples.devel.redhat.com) (gcc version 3.2.2 20030222 (Red Hat Linu x 3.2.2-5)) #1 SMP Mon Aug 18 11:32:15 EDT 2003 Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/XFree86.0.log", Time: Wed Nov 12 08:44:36 2003 (==) Using config file: "/etc/X11/XF86Config" [root@gaia gdm]# [root@gaia gdm]# cat :0.log.4 Fatal server error: Server is already active for display 0 If this server is no longer running, remove /tmp/.X0-lock and start again. When reporting a problem related to a server crash, please send the full server output, not just the last messages. Please report problems to xfree86@xfree86.org. I found these files in /var/gdm, they are encrypted ares -WinXP box that won't get a login prompt dlvap- the Win2Kbox, he can login just great kirklaptop- the WinXP laptop that I tried to connect with a few posts back, won't get a login prompt ngc-d4o1xu3vg29- my WinXP system, won't get a login prompt [root@gaia gdm]# ls ares:0.Xauth dlvap-7009132.ad.tasc.com:0.Xauth kirklaptop:0.Xauth ngc-d4o1xu3vg29:0.Xauth ngc-d4o1xu3vg29:1.Xauth I have tried the following command: $ XWin :1 -query 137.51.14.130 -from 137.51.14.54 IP of the WinXP box for -from and no luck The only difference between the Win2K box and the WinXP boxes that I have not mentioned so far is that the guy on the Win2K box is part of the corporate Windows domain, and all the other WinXP clients I have mentioned are not. I don't know if this makes a difference. From my WinXP box in question, I can ping the linux box, I can SSH to the linux box, I can do a nslookup on the IP for the linux box. Here's my tracert from the XP box to the linux box: C:\WINDOWS\system32>tracert 137.51.14.130 Tracing route to 137.51.14.130 over a maximum of 30 hops 1 1 ms <1 ms <1 ms 137.51.14.130 Trace complete. Rember, this is my first time working with Cygwin. After installing a full Cygwin install, is there some configuration for the Xserver (my WinXP Xclient in this case) that I must do? Something you experts have overlooked since its so obvious. In my WinXP C:\Cygwin\etc folder thare two files, "hosts.allow" and "hosts.deny". Am I supposed to have done something with them? Are there other examples of something that needs configuring on the "client" side? From pechtcha@cs.nyu.edu Wed Nov 12 15:05:00 2003 From: pechtcha@cs.nyu.edu (Igor Pechtchanski) Date: Wed, 12 Nov 2003 15:05:00 -0000 Subject: xterm switching problem In-Reply-To: References: Message-ID: On Wed, 12 Nov 2003, Kirsch, Rainer wrote: > Dear Cygwin/XFree development team, > > I want to inform you about a problem which exists using xterm together > with WindowMaker and rootless XWin. > > I am starting XFree via: > XWin -screen 0 1024 768 -clipboard -rootless -emulate3buttons 100 & > setxkbmap de nodeadkeys & > wmaker.exe > xterm blocks (refusing to react to normal keyboard entry) after being > started and if you alter the focus clicking on the (window maker > provided) title bar of a xterm window. > If you click into the (inner part of the) window it not only gets the > focus but also starts to react normally. > > If you use an old xterm binary e.g. that of 4.3.0-4, the window starts > working immediately even if you click onto its title bar (which is the > expected behaviour). This problem was reported multiple times (latest at ), and is apparently due to the new dynamic Xaw library. The workaround for now is to use the older xterm binary. I take it the "proper" solution is known and is being worked on, right, Harold? Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_ pechtcha@cs.nyu.edu ZZZzz /,`.-'`' -. ;-;;,_ igor@watson.ibm.com |,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 From pavelr@coresma.com Wed Nov 12 15:18:00 2003 From: pavelr@coresma.com (Pavel Rosenboim) Date: Wed, 12 Nov 2003 15:18:00 -0000 Subject: XWin works on Win2K but not on some WinXP clients In-Reply-To: References: Message-ID: <3FB24F3F.1000101@coresma.com> Woellert, Kirk D. wrote: > Ok, the last post suggested that I try to run XDM in debug mode. In > order to > do that you must drop out of the display manager. In order to do that you > must change to run level 3 since there is no such thing as an XDM stop > command. > > I did the following: > > telinit 3 > xdm -debug 10 -nodaemon > telinit 5 > > I assumed I wanted to get back into the default run level 5. After doing > the > above sequence of commands, it turns out that two displays get launched on > my linux server. "0" which is the display that was dropped to run level 3, > and "1" which is in run level 5. We get a msg that says hey display 0 is > busy launching display 1. I don't think this was your guys intent. So I did > the following: > telinit 3 > xdm -debug 10 -nodaemon & (so I can keep my ssh window) > > When we do this the guy on the Win2K box can no longer login, (no one else > either). I hard reboot the linux box, and now the Win2K box can login. XDM configuration is separate from that of GDM. If you want to be able to log in remotely with xdm, comment out the last line in /etc/X11/xdm/xdm-config The original line should be DisplayManager.requestPort: 0 Alternatively, you can edit file /etc/X11/gdm/gdm.conf, find [debug] section, and change Enable=false to Enable=true, and then just go to runlevel 5, or run gdm manually. > > [root@gaia log]# cat xdm-errors > xdm error (pid 1802): error 98 binding socket address 177 > > Fatal server error: > Server is already active for display 0 > If this server is no longer running, remove /tmp/.X0-lock > and start again. > > > When reporting a problem related to a server crash, please send > the full server output, not just the last messages. > Please report problems to xfree86@xfree86.org. > > xdm error (pid 1802): server unexpectedly died > xdm error (pid 1802): Server for display :0 can't be started, session > disabled > [root@gaia log]# > > Some log file samples > [root@gaia gdm]# ls > :0.log :0.log.1 :0.log.2 :0.log.3 :0.log.4 :1.log :1.log.1 :1.log.2 > :1.log.3 :1.log.4 > > [root@gaia gdm]# cat :0.log > > XFree86 Version 4.3.0 (Red Hat Linux release: 4.3.0-2) > Release Date: 27 February 2003 > X Protocol Version 11, Revision 0, Release 6.6 > Build Operating System: Linux 2.4.20-3bigmem i686 [ELF] > Build Date: 27 February 2003 > Build Host: porky.devel.redhat.com > > Before reporting problems, check http://www.XFree86.Org/ > to make sure that you have the latest version. > Module Loader present > OS Kernel: Linux version 2.4.20-20.9smp > (bhcompile@stripples.devel.redhat.com) (gcc version 3.2.2 20030222 (Red Hat > Linu > x 3.2.2-5)) #1 SMP Mon Aug 18 11:32:15 EDT 2003 > Markers: (--) probed, (**) from config file, (==) default setting, > (++) from command line, (!!) notice, (II) informational, > (WW) warning, (EE) error, (NI) not implemented, (??) unknown. > (==) Log file: "/var/log/XFree86.0.log", Time: Wed Nov 12 08:44:36 2003 > (==) Using config file: "/etc/X11/XF86Config" > [root@gaia gdm]# > > [root@gaia gdm]# cat :0.log.4 > > Fatal server error: > Server is already active for display 0 > If this server is no longer running, remove /tmp/.X0-lock > and start again. > > > When reporting a problem related to a server crash, please send > the full server output, not just the last messages. > Please report problems to xfree86@xfree86.org. > > I found these files in /var/gdm, they are encrypted > ares -WinXP box that won't get a login prompt > dlvap- the Win2Kbox, he can login just great > kirklaptop- the WinXP laptop that I tried to connect with a few posts back, > won't get a login prompt > ngc-d4o1xu3vg29- my WinXP system, won't get a login prompt > [root@gaia gdm]# ls > ares:0.Xauth dlvap-7009132.ad.tasc.com:0.Xauth kirklaptop:0.Xauth > ngc-d4o1xu3vg29:0.Xauth ngc-d4o1xu3vg29:1.Xauth > > I have tried the following command: > $ XWin :1 -query 137.51.14.130 -from 137.51.14.54 > IP of the WinXP box for -from and no luck > > The only difference between the Win2K box and the WinXP boxes that I have > not mentioned so far is that the guy on the Win2K box is part of the > corporate Windows domain, and all the other WinXP clients I have mentioned > are not. I don't know if this makes a difference. >From my WinXP box in > question, I can ping the linux box, I can SSH to the linux box, I can do a > nslookup on the IP for the linux box. Here's my tracert from the XP box to > the linux box: > > C:\WINDOWS\system32>tracert 137.51.14.130 > Tracing route to 137.51.14.130 over a maximum of 30 hops > 1 1 ms <1 ms <1 ms 137.51.14.130 > Trace complete. > > Rember, this is my first time working with Cygwin. After installing a full > Cygwin install, is there some configuration for the Xserver (my WinXP > Xclient in this case) that I must do? Something you experts have overlooked > since its so obvious. In my WinXP C:\Cygwin\etc folder thare two files, > "hosts.allow" and "hosts.deny". Am I supposed to have done something with > them? Are there other examples of something that needs configuring on the > "client" side? > From huntharo@msu.edu Wed Nov 12 15:35:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Wed, 12 Nov 2003 15:35:00 -0000 Subject: XWin works on Win2K but not on some WinXP clients In-Reply-To: References: Message-ID: <3FB25343.30502@msu.edu> Kirk, Woellert, Kirk D. wrote: > Ok, the last post suggested that I try to run XDM in debug mode. In order to > do that you must drop out of the display manager. In order to do that you > must change to run level 3 since there is no such thing as an XDM stop > command. Well, there is an xdm stop command on some systems. It is actually just a script. I don't have a Red Hat 9 box, so I can't tell you what you have. > I did the following: > > telinit 3 > xdm -debug 10 -nodaemon > telinit 5 I don't think you need to do the 'telinit 5' at the end. You should be fine without that and doing it may cause problems. > I assumed I wanted to get back into the default run level 5. After doing the > above sequence of commands, it turns out that two displays get launched on > my linux server. "0" which is the display that was dropped to run level 3, > and "1" which is in run level 5. We get a msg that says hey display 0 is > busy launching display 1. I don't think this was your guys intent. So I did > the following: > telinit 3 > xdm -debug 10 -nodaemon & (so I can keep my ssh window) Yup, that sounds correct. > When we do this the guy on the Win2K box can no longer login, (no one else > either). I hard reboot the linux box, and now the Win2K box can login. Hmm... I don't think you were actually using xdm. Almost no one uses xdm. You are likely using gdm or kdm, which do the same thing as xdm, but they are both more modern. We kept saying that you needed to restart xdm/kdm/gdm because we didn't know which of the three you were using. If you aren't normally using xdm, then it will not be configured correctly for anyone to login. Sounds like you should repeat this with gdm and kdm and see if anyone can get a login screen that looks like the usual login screen. > [root@gaia log]# cat xdm-errors > xdm error (pid 1802): error 98 binding socket address 177 > > Fatal server error: > Server is already active for display 0 > If this server is no longer running, remove /tmp/.X0-lock > and start again. > > > When reporting a problem related to a server crash, please send > the full server output, not just the last messages. > Please report problems to xfree86@xfree86.org. > > xdm error (pid 1802): server unexpectedly died > xdm error (pid 1802): Server for display :0 can't be started, session > disabled > [root@gaia log]# Yes, retry this with gdm and kdm. You may have to 'kill -9' the pid for the X Server and any other xdm/gdm/kdm instances before performing this test. Make sure that X is not running on the console before you launch your own kdm/gdm instance. > Some log file samples > [root@gaia gdm]# ls > :0.log :0.log.1 :0.log.2 :0.log.3 :0.log.4 :1.log :1.log.1 :1.log.2 > :1.log.3 :1.log.4 > > [root@gaia gdm]# cat :0.log > > XFree86 Version 4.3.0 (Red Hat Linux release: 4.3.0-2) > Release Date: 27 February 2003 > X Protocol Version 11, Revision 0, Release 6.6 > Build Operating System: Linux 2.4.20-3bigmem i686 [ELF] > Build Date: 27 February 2003 > Build Host: porky.devel.redhat.com > > Before reporting problems, check http://www.XFree86.Org/ > to make sure that you have the latest version. > Module Loader present > OS Kernel: Linux version 2.4.20-20.9smp > (bhcompile@stripples.devel.redhat.com) (gcc version 3.2.2 20030222 (Red Hat > Linu > x 3.2.2-5)) #1 SMP Mon Aug 18 11:32:15 EDT 2003 > Markers: (--) probed, (**) from config file, (==) default setting, > (++) from command line, (!!) notice, (II) informational, > (WW) warning, (EE) error, (NI) not implemented, (??) unknown. > (==) Log file: "/var/log/XFree86.0.log", Time: Wed Nov 12 08:44:36 2003 > (==) Using config file: "/etc/X11/XF86Config" > [root@gaia gdm]# > > [root@gaia gdm]# cat :0.log.4 > > Fatal server error: > Server is already active for display 0 > If this server is no longer running, remove /tmp/.X0-lock > and start again. > > > When reporting a problem related to a server crash, please send > the full server output, not just the last messages. > Please report problems to xfree86@xfree86.org. > > I found these files in /var/gdm, they are encrypted > ares -WinXP box that won't get a login prompt > dlvap- the Win2Kbox, he can login just great > kirklaptop- the WinXP laptop that I tried to connect with a few posts back, > won't get a login prompt > ngc-d4o1xu3vg29- my WinXP system, won't get a login prompt > [root@gaia gdm]# ls > ares:0.Xauth dlvap-7009132.ad.tasc.com:0.Xauth kirklaptop:0.Xauth > ngc-d4o1xu3vg29:0.Xauth ngc-d4o1xu3vg29:1.Xauth > > I have tried the following command: > $ XWin :1 -query 137.51.14.130 -from 137.51.14.54 > IP of the WinXP box for -from and no luck > > The only difference between the Win2K box and the WinXP boxes that I have > not mentioned so far is that the guy on the Win2K box is part of the > corporate Windows domain, and all the other WinXP clients I have mentioned > are not. I don't know if this makes a difference. From my WinXP box in > question, I can ping the linux box, I can SSH to the linux box, I can do a > nslookup on the IP for the linux box. Here's my tracert from the XP box to > the linux box: > > C:\WINDOWS\system32>tracert 137.51.14.130 > Tracing route to 137.51.14.130 over a maximum of 30 hops > 1 1 ms <1 ms <1 ms 137.51.14.130 > Trace complete. > > Rember, this is my first time working with Cygwin. After installing a full > Cygwin install, is there some configuration for the Xserver (my WinXP > Xclient in this case) that I must do? Something you experts have overlooked > since its so obvious. In my WinXP C:\Cygwin\etc folder thare two files, > "hosts.allow" and "hosts.deny". Am I supposed to have done something with > them? Are there other examples of something that needs configuring on the > "client" side? Nope, you don't need to touch either of those files and you really shouldn't unless you know enough not to need to ask ;) Lets not speculate about possible causes just yet, lets continue debugging xdm/kdm/gdm and see what it tells us. Harold From tulitanssi@luukku.com Wed Nov 12 15:36:00 2003 From: tulitanssi@luukku.com (tulitanssi@luukku.com) Date: Wed, 12 Nov 2003 15:36:00 -0000 Subject: Updated: XFree86-xserv-4.3.0-22 Message-ID: <1068651377471.tulitanssi.201450.Qo4QZmJ1wTJprxC-zMkERg@luukku.com> Hi all, and thanks for the ideas. Actually, I previously had problems with extraneous newlines from keyboard and somebody suggested 'xset r off', which was still there in my startup script. It didn't bother me with 4.3.0-21 but disabled the repeat with 4.3.0-22. Now I just removed xset from my startup, and repeat works OK. Well, I still sometimes get extraneous newlines also with 4.3.0-22, but fortunately not so much. Cheers, Tuli >> keyboard repeat does not work anymore with this new update. I think it worked with the >> previous (4.3.0-21) release. Any ideas? > The command 'xset r on' should enable auto-repeat on the > X Window layer. xset can set auto-repeat parameters in > detail (please see 'man xset'). ............................................................ Maksuton s?hk?posti aina k?yt?ss? http://luukku.com Kuukausimaksuton MTV3 Internet-liittym? www.mtv3.fi/liittyma From jase@dufair.org Wed Nov 12 16:37:00 2003 From: jase@dufair.org (Jason Dufair) Date: Wed, 12 Nov 2003 16:37:00 -0000 Subject: multiplemonitors In-Reply-To: <20031112174031.1A9D.MURAKAMI@ipl.t.u-tokyo.ac.jp> (Takuma Murakami's message of "Wed, 12 Nov 2003 17:42:35 +0900") References: <20031112174031.1A9D.MURAKAMI@ipl.t.u-tokyo.ac.jp> Message-ID: So is there anything I can do to get X to work with these two cards? Takuma Murakami writes: >> I know they're running the same display depth. What's pixel format? I > > Even if both display has 32bit for a pixel, the formats > could differ. The format includes the order of RGB > components or the number of bits assigned for each > component, for example. > > If you connect two displays with one card, it should work. > > Takuma Murakami (murakami@ipl.t.u-tokyo.ac.jp) -- Jason Dufair - jase@dufair.org http://www.dufair.org/ "Ad in classifieds: Pandora's Box (no box) $5" From ford@vss.fsi.com Wed Nov 12 16:55:00 2003 From: ford@vss.fsi.com (Brian Ford) Date: Wed, 12 Nov 2003 16:55:00 -0000 Subject: chmod In-Reply-To: <000701c3a8d3$e0917220$a124ff29@fastwebnet.it> References: <000701c3a8d3$e0917220$a124ff29@fastwebnet.it> Message-ID: On Wed, 12 Nov 2003, Lorenzo Travaglio wrote: > I've sent to myself from my office a little bash program. With Xterm it is > impossible to change the peremissions even if 'chmod -v' says that new > permissions have take place. I have no idea about, do you have one? > You mean you can change the permissions in a bash console window with chmod, but not with chmod from an Xterm? More likely, you are running an NT variant at work and 9x at home? See: http://cygwin.com/faq/faq_toc.html#TOC45 and http://cygwin.com/cygwin-ug-net/highlights.html#OV-HI-PERM In that case, this is not Xfree86 related, so next time please use the main cygwin@cygwin.com mailing list. Also, see: http://www.cygwin.com/problems.html for how to report this issue correctly so that someone can answer without guessing. Thanks. -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444 From zwin@users.sourceforge.net Wed Nov 12 17:00:00 2003 From: zwin@users.sourceforge.net (Zbynek Winkler) Date: Wed, 12 Nov 2003 17:00:00 -0000 Subject: OpenGL and GLX Message-ID: <3FB2671B.9040209@users.sourceforge.net> Hello, Is it possible to compile programs using GLX under cygwin? I am trying to compile the attached example with command g++ -I/usr/X11R6/include -L/usr/X11R6/lib -lX11 -lGL glxsample.cpp -o glxsample All the X and glx functions are reported undefined. Am I doing something wrong? I've found the thread in cygwin@cygwin.com list about OpenGL but that was about linking to the hw accelerated libs. I need to compile program written for the glx. Thanks. Zbynek -- http://zw.matfyz.cz/ http://robotika.cz/ Faculty of Mathematics and Physics, Charles University, Prague, Czech Republic -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: glxsample.cpp URL: From ford@vss.fsi.com Wed Nov 12 17:10:00 2003 From: ford@vss.fsi.com (Brian Ford) Date: Wed, 12 Nov 2003 17:10:00 -0000 Subject: xterm switching problem In-Reply-To: References: Message-ID: On Wed, 12 Nov 2003, Igor Pechtchanski wrote: > This problem was reported multiple times (latest at > ), and is > apparently due to the new dynamic Xaw library. The workaround for now is > to use the older xterm binary. > > I take it the "proper" solution is known and is being worked on, right, > Harold? > I think the answer to that question is sort of known based on lesstif work arounds, but not currently being worked on because no one has volunteered? -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444 From alexander.gottwald@s1999.tu-chemnitz.de Wed Nov 12 17:12:00 2003 From: alexander.gottwald@s1999.tu-chemnitz.de (Alexander Gottwald) Date: Wed, 12 Nov 2003 17:12:00 -0000 Subject: OpenGL and GLX In-Reply-To: <3FB2671B.9040209@users.sourceforge.net> References: <3FB2671B.9040209@users.sourceforge.net> Message-ID: On Wed, 12 Nov 2003, Zbynek Winkler wrote: > Hello, > > Is it possible to compile programs using GLX under cygwin? I am trying > to compile the attached example with command > g++ -I/usr/X11R6/include -L/usr/X11R6/lib -lX11 -lGL glxsample.cpp -o > glxsample It works for me (XFree86-prog 4.3.0-6) Maybe the linker is using the wrong library? You can list the libraries used by adding the switch -Wl,-t to the compiler options. bye ago -- Alexander.Gottwald@s1999.tu-chemnitz.de http://www.gotti.org ICQ: 126018723 From zwin@users.sourceforge.net Wed Nov 12 17:25:00 2003 From: zwin@users.sourceforge.net (Zbynek Winkler) Date: Wed, 12 Nov 2003 17:25:00 -0000 Subject: OpenGL and GLX In-Reply-To: References: <3FB2671B.9040209@users.sourceforge.net> Message-ID: <3FB26CFC.2080600@users.sourceforge.net> Alexander Gottwald wrote: >On Wed, 12 Nov 2003, Zbynek Winkler wrote: > > >>Hello, >> >>Is it possible to compile programs using GLX under cygwin? I am trying >>to compile the attached example with command >>g++ -I/usr/X11R6/include -L/usr/X11R6/lib -lX11 -lGL glxsample.cpp -o >>glxsample >> >> > >It works for me (XFree86-prog 4.3.0-6) > > I am using XFree86-prog 4.3.0-10. >Maybe the linker is using the wrong library? You can list the libraries >used by adding the switch -Wl,-t to the compiler options. > > It seems the linker is not using the libraries at all :-(. Zbynek $ g++ -I/usr/X11R6/include -L/usr/X11R6/lib -lX11 -lGL -Wl,-t glxsample.cpp -o glxsample /usr/lib/gcc-lib/i686-pc-cygwin/3.3.1/../../../../i686-pc-cygwin/bin/ld: mode i386pe /usr/lib/gcc-lib/i686-pc-cygwin/3.3.1/../../../crt0.o /usr/lib/gcc-lib/i686-pc-cygwin/3.3.1/crtbegin.o /cygdrive/c/DOCUME~1/zbynek/LOCALS~1/Temp/ccTs9Ndz.o (/usr/lib/gcc-lib/i686-pc-cygwin/3.3.1/libgcc.a)w32-shared-ptr.o (/usr/lib/gcc-lib/i686-pc-cygwin/3.3.1/libgcc.a)_chkstk.o (/usr/lib/gcc-lib/i686-pc-cygwin/3.3.1/../../../libcygwin.a)cygwin_crt0.o (/usr/lib/gcc-lib/i686-pc-cygwin/3.3.1/../../../libcygwin.a)d000049.o (/usr/lib/gcc-lib/i686-pc-cygwin/3.3.1/../../../libcygwin.a)d001348.o (/usr/lib/gcc-lib/i686-pc-cygwin/3.3.1/../../../libcygwin.a)d000863.o (/usr/lib/gcc-lib/i686-pc-cygwin/3.3.1/../../../libcygwin.a)d001129.o (/usr/lib/gcc-lib/i686-pc-cygwin/3.3.1/../../../libcygwin.a)d001058.o (/usr/lib/gcc-lib/i686-pc-cygwin/3.3.1/../../../libcygwin.a)d000641.o (/usr/lib/gcc-lib/i686-pc-cygwin/3.3.1/../../../libcygwin.a)_cygwin_crt0_common.o (/usr/lib/gcc-lib/i686-pc-cygwin/3.3.1/../../../libcygwin.a)d000771.o (/usr/lib/gcc-lib/i686-pc-cygwin/3.3.1/../../../libcygwin.a)d000000.o (/usr/lib/gcc-lib/i686-pc-cygwin/3.3.1/../../../libcygwin.a)pseudo-reloc.o (/usr/lib/gcc-lib/i686-pc-cygwin/3.3.1/../../../libcygwin.a)d000699.o (/usr/lib/gcc-lib/i686-pc-cygwin/3.3.1/../../../libcygwin.a)d001224.o (/usr/lib/gcc-lib/i686-pc-cygwin/3.3.1/../../../libcygwin.a)premain3.o (/usr/lib/gcc-lib/i686-pc-cygwin/3.3.1/../../../libcygwin.a)premain2.o (/usr/lib/gcc-lib/i686-pc-cygwin/3.3.1/../../../libcygwin.a)premain1.o (/usr/lib/gcc-lib/i686-pc-cygwin/3.3.1/../../../libcygwin.a)premain0.o (/usr/lib/gcc-lib/i686-pc-cygwin/3.3.1/../../../libcygwin.a)d000752.o (/usr/lib/gcc-lib/i686-pc-cygwin/3.3.1/../../../libcygwin.a)d001529.o (/usr/lib/w32api/libkernel32.a)ds00148.o (/usr/lib/w32api/libkernel32.a)ds00000.o (/usr/lib/w32api/libkernel32.a)ds00193.o (/usr/lib/w32api/libkernel32.a)ds00299.o (/usr/lib/w32api/libkernel32.a)dh.o (/usr/lib/w32api/libkernel32.a)dt.o (/usr/lib/gcc-lib/i686-pc-cygwin/3.3.1/libgcc.a)_ctors.o /usr/lib/gcc-lib/i686-pc-cygwin/3.3./cygdrive/c/DOCUME~1/zbynek/LOCALS~1/Temp/ccTs9Ndz.o(.text+0x5b):glxsample.cpp: unde fined reference to `_XOpenDisplay' /cygdrive/c/DOCUME~1/zbynek/LOCALS~1/Temp/ccTs9Ndz.o(.text+0x7e):glxsample.cpp: undefined reference to `_glXChooseVisual ' /cygdrive/c/DOCUME~1/zbynek/LOCALS~1/Temp/ccTs9Ndz.o(.text+0xa3):glxsample.cpp: undefined reference to `_glXCreateContex t' /cygdrive/c/DOCUME~1/zbynek/LOCALS~1/Temp/ccTs9Ndz.o(.text+0xe5):glxsample.cpp: undefined reference to `_XCreateColormap ' /cygdrive/c/DOCUME~1/zbynek/LOCALS~1/Temp/ccTs9Ndz.o(.text+0x17c):glxsample.cpp: undefined reference to `_XCreateWindow' /cygdrive/c/DOCUME~1/zbynek/LOCALS~1/Temp/ccTs9Ndz.o(.text+0x191):glxsample.cpp: undefined reference to `_XMapWindow' /cygdrive/c/DOCUME~1/zbynek/LOCALS~1/Temp/ccTs9Ndz.o(.text+0x1b5):glxsample.cpp: undefined reference to `_XIfEvent' /cygdrive/c/DOCUME~1/zbynek/LOCALS~1/Temp/ccTs9Ndz.o(.text+0x1ce):glxsample.cpp: undefined reference to `_glXMakeCurrent ' /cygdrive/c/DOCUME~1/zbynek/LOCALS~1/Temp/ccTs9Ndz.o(.text+0x1f6):glxsample.cpp: undefined reference to `_glClearColor' /cygdrive/c/DOCUME~1/zbynek/LOCALS~1/Temp/ccTs9Ndz.o(.text+0x202):glxsample.cpp: undefined reference to `_glClear' /cygdrive/c/DOCUME~1/zbynek/LOCALS~1/Temp/ccTs9Ndz.o(.text+0x207):glxsample.cpp: undefined reference to `_glFlush' /usr/lib/gcc-lib/i686-pc-cygwin/3.3.1/../../../../i686-pc-cygwin/bin/ld: link errors found, deleting executable `glxsamp le.exe' 1/crtend.o collect2: ld returned 1 exit status -- http://zw.matfyz.cz/ http://robotika.cz/ Faculty of Mathematics and Physics, Charles University, Prague, Czech Republic From alexander.gottwald@s1999.tu-chemnitz.de Wed Nov 12 17:28:00 2003 From: alexander.gottwald@s1999.tu-chemnitz.de (Alexander Gottwald) Date: Wed, 12 Nov 2003 17:28:00 -0000 Subject: OpenGL and GLX In-Reply-To: <3FB26CFC.2080600@users.sourceforge.net> References: <3FB2671B.9040209@users.sourceforge.net> <3FB26CFC.2080600@users.sourceforge.net> Message-ID: On Wed, 12 Nov 2003, Zbynek Winkler wrote: > It seems the linker is not using the libraries at all :-(. > Zbynek > > $ g++ -I/usr/X11R6/include -L/usr/X11R6/lib -lX11 -lGL -Wl,-t > glxsample.cpp -o glxsample reorder the arguments: $ g++ glxsample.cpp -I/usr/X11R6/include -L/usr/X11R6/lib -lX11 -lGL -o glxsample -- Alexander.Gottwald@s1999.tu-chemnitz.de http://www.gotti.org ICQ: 126018723 From zwin@users.sourceforge.net Wed Nov 12 18:04:00 2003 From: zwin@users.sourceforge.net (Zbynek Winkler) Date: Wed, 12 Nov 2003 18:04:00 -0000 Subject: OpenGL and GLX In-Reply-To: References: <3FB2671B.9040209@users.sourceforge.net> <3FB26CFC.2080600@users.sourceforge.net> Message-ID: <3FB2764B.7090308@users.sourceforge.net> Alexander Gottwald wrote: >On Wed, 12 Nov 2003, Zbynek Winkler wrote: > > >>It seems the linker is not using the libraries at all :-(. >>Zbynek >> >>$ g++ -I/usr/X11R6/include -L/usr/X11R6/lib -lX11 -lGL -Wl,-t >>glxsample.cpp -o glxsample >> >> > >reorder the arguments: > >$ g++ glxsample.cpp -I/usr/X11R6/include -L/usr/X11R6/lib -lX11 -lGL -o glxsample > > Thanks. That actually works! Would you have a hint as to why the order is important? Also would you know how to fix this command that shows the same symptoms? c++ -g -g -O2 -o gazebo -L. -L/usr/X11R6/lib -L../libgazebo main.o World.o WorldFile.o Model.o ModelFactory.o Sensor.o SensorFactory.o X11Window.o WindowManager.o Camera.o ContactParams.o -lX11 -lm -lpthread -lGLU -lGL -L/usr/lib -lxml2 -lz -liconv -lm -L/home/zbynek/playerstage/ode-0.039/lib -lode models/SimpleSolid/libsimplesolid.a models/Pioneer2AT/libpioneer2at.a models/Pioneer2DX/libpioneer2dx.a models/SegwayRMP/libsegwayrmp.a models/SickLMS200/libsicklms200.a models/UserX11GLCamera/libuserx11glcamera.a models/GroundPlane/libgroundplane.a models/SonyVID30/libsonyvid30.a models/ClodBuster/libclodbuster.a sensors/X11GLCameraSensor/libx11glcamerasensor.a -lgazebo bodies/libbodies.a ../replace/libreplace.a ../toolkit/libtoolkit.a Well not exactly the same. Adding -Wl,-t shows that is is using /usr/X11R6/lib/libGLU.dll.a and /usr/X11R6/lib/libGL.dll.a but somehow it is missing functions like glMultMatrixf, glVertex3f etc. It also returns bunch of warnings like Warning: resolving _glMaterialf@12 by linking to _glMaterialf Thank you for any insights you might have. Zbynek -- http://zw.matfyz.cz/ http://robotika.cz/ Faculty of Mathematics and Physics, Charles University, Prague, Czech Republic From huntharo@msu.edu Wed Nov 12 18:33:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Wed, 12 Nov 2003 18:33:00 -0000 Subject: OpenGL and GLX In-Reply-To: <3FB2764B.7090308@users.sourceforge.net> References: <3FB2671B.9040209@users.sourceforge.net> <3FB26CFC.2080600@users.sourceforge.net> <3FB2764B.7090308@users.sourceforge.net> Message-ID: <3FB27D0E.5060707@msu.edu> Zbynek Winkler wrote: > Alexander Gottwald wrote: > >> On Wed, 12 Nov 2003, Zbynek Winkler wrote: >> >> >>> It seems the linker is not using the libraries at all :-(. >>> Zbynek >>> >>> $ g++ -I/usr/X11R6/include -L/usr/X11R6/lib -lX11 -lGL -Wl,-t >>> glxsample.cpp -o glxsample >>> >> >> >> reorder the arguments: >> >> $ g++ glxsample.cpp -I/usr/X11R6/include -L/usr/X11R6/lib -lX11 -lGL >> -o glxsample >> >> > Thanks. That actually works! Would you have a hint as to why the order > is important? > Also would you know how to fix this command that shows the same symptoms? Because on Cygwin the linker looks at each object file and library in sequential order and compiles a list of undefined symbols. It only attempts to resolve these symbols in objects and libraries that have not been processed yet. Any symbols not required by previous objects or libraries are not preserved for later objects/libraries to use. Thus, if -lGL uses -lX11 symbols, then you must first include -lGL so that it sets up a list of unresolved symbols that will be resolved when -lX11 is processed next. Does that make sense? Harold From huntharo@msu.edu Wed Nov 12 18:34:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Wed, 12 Nov 2003 18:34:00 -0000 Subject: xterm switching problem In-Reply-To: References: Message-ID: <3FB27D1F.3090509@msu.edu> That is correct. Harold Brian Ford wrote: > On Wed, 12 Nov 2003, Igor Pechtchanski wrote: > > >>This problem was reported multiple times (latest at >>), and is >>apparently due to the new dynamic Xaw library. The workaround for now is >>to use the older xterm binary. >> >>I take it the "proper" solution is known and is being worked on, right, >>Harold? >> > > I think the answer to that question is sort of known based on lesstif > work arounds, but not currently being worked on because no one has > volunteered? > From hans.dekker.ext@juntadeandalucia.es Wed Nov 12 18:49:00 2003 From: hans.dekker.ext@juntadeandalucia.es (Hans Dekker) Date: Wed, 12 Nov 2003 18:49:00 -0000 Subject: Define a foreign language keyboard in HP-Ux CDE, with the AltGrkey? References: <3FB0DC48.6081.EA223B@localhost> Message-ID: <3FB28094.9090906@juntadeandalucia.es> It is true what Franz says: applying another X-Window System Package maps the right keyboard (Spanish in my case). So, by logical thinking you may say that Xfree86 somehow gives a keyboard mapping to CDE that is different from what it should be. Unfortunately my time right now is restricted on the subject. Some time later I could dive into the problem and possibly the source code, so any comments that can help are welcome. There must be something simple I guess, because German keyboards (and other non-US keyboards) will suffer from the same problem. Thanks, Hans. Franz Roters escribi??: > Hi all, > > I encounter the same problem. > > However, the Alt-Gr key works when I am using Exceed to log in. > Therefore I do not belief its a problem with the HP machine. > > The Alt-Gr key also works in the cygwin bash for me. > > Regards > > Franz > > > >>Hi, >> >>Using startxwin.bat and xev, gives me the following: >> >>KeyPress event, serial 22, synthetic NO, window 0x800001, >>root 0x3a, subw 0x0, time 25294468, (167,-13), root:(627,587), >>state 0x10, keycode 113 (keysym 0xfe03, ISO_Level3_Shift), same_screen >>YES, XLookupString gives 0 characters: "" >> >>KeyPress event, serial 22, synthetic NO, window 0x800001, >>root 0x3a, subw 0x0, time 25294531, (167,-13), root:(627,587), >>state 0x90, keycode 113 (keysym 0xfe03, ISO_Level3_Shift), same_screen >>YES, XLookupString gives 0 characters: "" >> >>and AltGr is working well on this one. >> >>Unfortunately I don't have xev running on the HP-UX box... >> >>Not only CDE has the behaviour of not using AltGr, but another >>X-application I use as well. >> >>Hope it helps. >> >>Regards, Hans. >> >>Alexander Gottwald escribi??: >> >> On Thu, 6 Nov 2003, Hans Dekker wrote: >> >> >> Hi Takuma, >> >> I tried Xterm and there is works OK. As I read the documentation >> on the usage of xdmcp to start a CDE environment, changing the >> XF86Config should be working, however I didn't find how to do it >> in the case of a Spanish keyboard. >> >> What is the auto detection option you are talking about? >> >> >> >>The autodetection changes the layout according to the layout used in >>windows. This can be overridden in the XF86Config file but this not >>needed in most cases. >> >> >>If the layout is correct with startxwin.bat then it is also loaded with >>xdmcp. Maybe CDE does load a wrong modmap? >> >> >> Can you try xev and press Alt-Gr? >> >> For me it reports the following. >> >>KeyPress event, serial 22, synthetic NO, window 0x1600001, >> root 0x3a, subw 0x1600002, time 1891239428, (55,39), root:(136,215), >> state 0x0, keycode 113 (keysym 0xfe03, ISO_Level3_Shift), same_screen >> YES, XLookupString gives 0 characters: "" >> >> >>KeyRelease event, serial 27, synthetic NO, window 0x1600001, >> root 0x3a, subw 0x1600002, time 1891239498, (55,39), root:(136,215), >> state 0x80, keycode 113 (keysym 0xfe03, ISO_Level3_Shift), same_screen >> YES, XLookupString gives 0 characters: "" >> >> >>bye >> ago >> > > > ------------------------------- > Dr. Franz Roters > Max-Planck-Institut fuer Eisenforschung > Abteilung Mikrostrukturphysik und Umformtechnik > Max-Planck-Str. 1 > 40237 Duesseldorf > Germany > Tel.: +49 (0)211-6792-393 > FAX: +49 (0)211-6792-333 > > > . > From Dr.Volker.Zell@oracle.com Wed Nov 12 20:02:00 2003 From: Dr.Volker.Zell@oracle.com (Dr. Volker Zell) Date: Wed, 12 Nov 2003 20:02:00 -0000 Subject: Updated: XFree86-xserv-4.3.0-22 In-Reply-To: <87d6byvn9u.fsf@vzell-de.de.oracle.com> (Volker Zell's message of "Tue, 11 Nov 2003 18:16:29 +0100") References: <1068549020528.tulitanssi.36802.w1Q4NRjiTPWoQQzb3m7sWA@luukku.com> <3FB0E0D5.7090505@msu.edu> <87ptfyvpbj.fsf@vzell-de.de.oracle.com> <3FB1123E.8090102@msu.edu> <87d6byvn9u.fsf@vzell-de.de.oracle.com> Message-ID: <87smktnyps.fsf@vzell-de.de.oracle.com> >>>>> "I" == Volker Zell writes: >>>>> "Harold" == Harold L Hunt, writes: Harold> Are you using the -kb or -xkb parameters? I don't remember what the Harold> name of the parameter is that disables the repeats, but the above Harold> seems close. I> No, but I found the culprit. I once downloaded a XF86Config-4 file from the I> net and placed it under /etc/X11 I> There was an entry I> Option "AutoRepeat" "500 20" I> After changing it to "200 40" woooow, it works even better as before... Actually I only tried setting AutoRepeat via xset r rate 200 40 and this works fine. But when setting it in /etc/X11/XF86Config-4 it gets ignored for me. Here are the relevant entries from XF86Config-4 and from /tmp/XWin.log. Any hints ? is this supposed to work ? >From XF86Config-4: Section "InputDevice" Identifier "Keyboard1" Driver "Keyboard" Option "XkbRules" "xfree86" Option "XkbModel" "pc105" Option "XkbLayout" "de" Option "AutoRepeat" "200 40" EndSection and from XWin.log: ddxProcessArgument - Initializing default screens winInitializeDefaultScreens - w 1024 h 768 winInitializeDefaultScreens - Returning OsVendorInit - Creating bogus screen 0 (==) Using config file: "/etc/X11/XF86Config-4" Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (??) unknown. (**) FontPath set to "/usr/X11R6/lib/X11/fonts/local/,/usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/75dpi/:unscaled,/usr/X11R6/lib/X11/fonts/100dpi/:unscaled,/usr/X11R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/Speedo/,/usr/X11R6/lib/X11/fonts/75dpi/,/usr/X11R6/lib/X11/fonts/100dpi/,/usr/local/share/emacs/fonts/,/dev/c/WINNT/Fonts/,/usr/local/share/fonts/" (**) RgbPath set to "/usr/X11R6/lib/X11/rgb" winDetectSupportedEngines - Windows NT/2000/XP winDetectSupportedEngines - DirectDraw installed winDetectSupportedEngines - Allowing PrimaryDD winDetectSupportedEngines - DirectDraw4 installed winDetectSupportedEngines - Returning, supported engines 0000001f InitOutput - g_iNumScreens: 1 iMaxConsecutiveScreen: 1 winSetEngine - Using user's preference: 4 winAdjustVideoModeShadowDDNL - Using Windows display depth of 32 bits per pixel winCreateBoundingWindowWindowed - User w: 1024 h: 768 winCreateBoundingWindowWindowed - Current w: 1024 h: 768 winAdjustForAutoHide - Original WorkArea: 0 0 768 1024 winAdjustForAutoHide - Taskbar is auto hide winAdjustForAutoHide - Found BOTTOM auto-hide taskbar winAdjustForAutoHide - Adjusted WorkArea: 0 0 767 1024 winCreateBoundingWindowWindowed - WindowClient w 1024 h 767 r 1024 l 0 b 767 t 0 winCreateBoundingWindowWindowed - Returning winCreatePrimarySurfaceShadowDDNL - Creating primary surface winCreatePrimarySurfaceShadowDDNL - Created primary surface winCreatePrimarySurfaceShadowDDNL - Attached clipper to primary surface winAllocateFBShadowDDNL - lPitch: 4096 winAllocateFBShadowDDNL - Created shadow pitch: 4096 winAllocateFBShadowDDNL - Created shadow stride: 1024 winFinishScreenInitFB - Masks: 00ff0000 0000ff00 000000ff winInitVisualsShadowDDNL - Masks 00ff0000 0000ff00 000000ff BPRGB 8 d 24 bpp 32 winCreateDefColormap - Deferring to fbCreateDefColormap () winFinishScreenInitFB - returning winScreenInit - returning InitOutput - Returning. (==) winConfigKeyboard - Layout: "00000407" (00000407) (==) Using preset keyboard for "German (Germany)" (407), type "4" (**) Using keyboard "Keyboard1" as primary keyboard (**) Option "XkbRules" "xfree86" (**) XKB: rules: "xfree86" (**) Option "XkbModel" "pc105" (**) XKB: model: "pc105" (**) Option "XkbLayout" "de" (**) XKB: layout: "de" Rules = "xfree86" Model = "pc105" Layout = "de" Variant = "(null)" Options = "(null)" winPointerWarpCursor - Discarding first warp: 512 383 winBlockHandler - Releasing pmServerStarted winBlockHandler - pthread_mutex_unlock () returned I> Ciao I> Volker Harold> Harold Ciao Volker From landy@alumni.caltech.edu Wed Nov 12 20:16:00 2003 From: landy@alumni.caltech.edu (landy@alumni.caltech.edu) Date: Wed, 12 Nov 2003 20:16:00 -0000 Subject: Cygwin X server crashes when a remote Xemacs is run In-Reply-To: <3FB1C452.3090309@msu.edu> References: <3FB1C452.3090309@msu.edu> Message-ID: <1068668170.3fb2950a0a646@gateway.landy.cx> I'm willing. Brian Quoting Harold L Hunt II : > Anybody care to run a debug build of XWin.exe in gdb to find the crash > > location? > > Harold > > Brian R.Landy wrote: > > > > > Hi, I see what appears to be the same crash (address 0x61093b2c), > using > > Vim 6.2 with the GTK1 GUI. One remote system is running AIX, the > other > > Solaris. The cygwin system runs NT 4 SP6. > > > > However, I only crash if I run XWin.exe -multiwindow. Switching to > > windowed, fullscreen, or even rootless causes the crash to go away. > > > > Nothing is written to Xwin.log after the normal startup messages. > > > > > > Brian > > > >> Here what I'm trying to do: > >> I establish a rsh connection with a UNIX/Linux machine and open an > xterm. > >> The I run Xemacs on this remote machine and XWin.exe crashes. > >> I tried it connecting with both a Linux machine and a Alpha > machine. > >> Here > >> the Xemacs versions installed on those machines: > >> Linux - Xemacs 21.1 (patch 14) i386-redhat-linux > >> Alpha - Xemacs 20.4 alpha-dec-osf3.2 > >> > >> Here the Windows error message: > >> Exception: access violation (0xc0000005), Address: 0x61093b2c > >> > >> I'm running Cygwin 1.5.5-1 on Windows NT 4.0 Workstation. XWin.exe > >> version > >> is 4.3.0-20 > >> > >> Giampaolo Orrigo > > > > > > From ki55me@hotmail.com Thu Nov 13 00:06:00 2003 From: ki55me@hotmail.com (Mr Nobody) Date: Thu, 13 Nov 2003 00:06:00 -0000 Subject: doesn't honour the -iconic in -windowmode Message-ID: XFree86 running in -windowmode doesn't honour requests to run an application starting in the minimized state. For example: xterm -iconic The xterm still appears full screen. You can minimize it manually. I think this is a problem inside the code for the -windowmode inbuilt window manager of XFree. Any ideas? _________________________________________________________________ Hot chart ringtones and polyphonics. Go to http://ninemsn.com.au/mobilemania/default.asp From alexander.gottwald@s1999.tu-chemnitz.de Thu Nov 13 08:36:00 2003 From: alexander.gottwald@s1999.tu-chemnitz.de (Alexander Gottwald) Date: Thu, 13 Nov 2003 08:36:00 -0000 Subject: Define a foreign language keyboard in HP-Ux CDE, with the AltGrkey? In-Reply-To: <3FB28094.9090906@juntadeandalucia.es> References: <3FB0DC48.6081.EA223B@localhost> <3FB28094.9090906@juntadeandalucia.es> Message-ID: On Wed, 12 Nov 2003, Hans Dekker wrote: > It is true what Franz says: applying another X-Window System Package > maps the right keyboard (Spanish in my case). > > So, by logical thinking you may say that Xfree86 somehow gives a > keyboard mapping to CDE that is different from what it should be. > > Unfortunately my time right now is restricted on the subject. Some time > later I could dive into the problem and possibly the source code, so any > comments that can help are welcome. There must be something simple I > guess, because German keyboards (and other non-US keyboards) will suffer > from the same problem. Just a wild guess: CDE uses an older X11 Release where ISO_Level3_Shift was still called Mode_switch. I guess CDE changes the modmap and sets AltGr to a symbol which is not recognized as Level3-Shift by the xserver. You can start xev for debugging. If it is not available with CDE, you can start a local xterm (from cygwin) after loggin into CDE and start xev from the cygwin xterm. bye ago -- Alexander.Gottwald@s1999.tu-chemnitz.de http://www.gotti.org ICQ: 126018723 From alexander.gottwald@s1999.tu-chemnitz.de Thu Nov 13 08:39:00 2003 From: alexander.gottwald@s1999.tu-chemnitz.de (Alexander Gottwald) Date: Thu, 13 Nov 2003 08:39:00 -0000 Subject: Updated: XFree86-xserv-4.3.0-22 In-Reply-To: <87smktnyps.fsf@vzell-de.de.oracle.com> References: <1068549020528.tulitanssi.36802.w1Q4NRjiTPWoQQzb3m7sWA@luukku.com> <3FB0E0D5.7090505@msu.edu> <87ptfyvpbj.fsf@vzell-de.de.oracle.com> <3FB1123E.8090102@msu.edu> <87d6byvn9u.fsf@vzell-de.de.oracle.com> <87smktnyps.fsf@vzell-de.de.oracle.com> Message-ID: On Wed, 12 Nov 2003, Dr. Volker Zell wrote: > Actually I only tried setting AutoRepeat via > > xset r rate 200 40 > > and this works fine. > > But when setting it in /etc/X11/XF86Config-4 it gets ignored for me. > Here are the relevant entries from XF86Config-4 and from /tmp/XWin.log. > Any hints ? is this supposed to work ? No. The AutoRepeat option is not used yet. I'll change this. bye ago -- Alexander.Gottwald@s1999.tu-chemnitz.de http://www.gotti.org ICQ: 126018723 From zwin@users.sourceforge.net Thu Nov 13 09:11:00 2003 From: zwin@users.sourceforge.net (Zbynek Winkler) Date: Thu, 13 Nov 2003 09:11:00 -0000 Subject: OpenGL and GLX In-Reply-To: <3FB27D0E.5060707@msu.edu> References: <3FB2671B.9040209@users.sourceforge.net> <3FB26CFC.2080600@users.sourceforge.net> <3FB2764B.7090308@users.sourceforge.net> <3FB27D0E.5060707@msu.edu> Message-ID: <3FB34AE3.90502@users.sourceforge.net> Harold L Hunt II wrote: > > Zbynek Winkler wrote: > >> Alexander Gottwald wrote: >> >>> On Wed, 12 Nov 2003, Zbynek Winkler wrote: >>> >>>> It seems the linker is not using the libraries at all :-(. >>>> Zbynek >>>> >>>> $ g++ -I/usr/X11R6/include -L/usr/X11R6/lib -lX11 -lGL -Wl,-t >>>> glxsample.cpp -o glxsample >>>> >>> >>> >>> reorder the arguments: >>> >>> $ g++ glxsample.cpp -I/usr/X11R6/include -L/usr/X11R6/lib -lX11 -lGL >>> -o glxsample >>> >>> >> Thanks. That actually works! Would you have a hint as to why the >> order is important? >> Also would you know how to fix this command that shows the same >> symptoms? > > > Because on Cygwin the linker looks at each object file and library in > sequential order and compiles a list of undefined symbols. It only > attempts to resolve these symbols in objects and libraries that have > not been processed yet. Any symbols not required by previous objects > or libraries are not preserved for later objects/libraries to use. > > Thus, if -lGL uses -lX11 symbols, then you must first include -lGL so > that it sets up a list of unresolved symbols that will be resolved > when -lX11 is processed next. > > Does that make sense? I guess it does. But guys thanks, it helped to solve my problem. The problem was twofold. First I was including wrong header files (in the bigger project) and then there was the sequencing problem when linking. When linking against libGL one has to make sure that /usr/X11R6/include headers are used. There was no include path set and the compiler (after I removed /usr/include/GL) was using /usr/include/w32api/GL which I didn't even know about. Zbynek -- http://zw.matfyz.cz/ http://robotika.cz/ Faculty of Mathematics and Physics, Charles University, Prague, Czech Republic From roters@mpie.de Thu Nov 13 10:06:00 2003 From: roters@mpie.de (Franz Roters) Date: Thu, 13 Nov 2003 10:06:00 -0000 Subject: Define a foreign language keyboard in HP-Ux CDE, with theAltGrkey? Message-ID: <3FB365DA.26095.86BD39@localhost> > Just a wild guess: > > CDE uses an older X11 Release where ISO_Level3_Shift was still called > Mode_switch. I guess CDE changes the modmap and sets AltGr to a symbol > which is not recognized as Level3-Shift by the xserver. > Maybe this gets us closer to the point: Exceed uses a file called 'german.kbf' for input. This is what I get from the XKey tool they use to edit these files for AltGr: Current X mapping for Key labeled ALT GR: Scan code: 0x138 (ALT GR) Unshifted Shifted ModeSwitch Shift Mode Switch Keysym: ModeSwitch NoSymbol NoSymbol NoSymbol Key State: Mod3 > You can start xev for debugging. If it is not available with CDE, you can > start a local xterm (from cygwin) after loggin into CDE and start xev from > the cygwin xterm. Sorry I am no expert at all in these things, but if you could give a step by step instruction how to do this. I would be glad to help. Bye Franz From alexander.gottwald@s1999.tu-chemnitz.de Thu Nov 13 10:34:00 2003 From: alexander.gottwald@s1999.tu-chemnitz.de (Alexander Gottwald) Date: Thu, 13 Nov 2003 10:34:00 -0000 Subject: Define a foreign language keyboard in HP-Ux CDE, with theAltGrkey? In-Reply-To: <3FB365DA.26095.86BD39@localhost> References: <3FB365DA.26095.86BD39@localhost> Message-ID: On Thu, 13 Nov 2003, Franz Roters wrote: > Sorry I am no expert at all in these things, but if you could give a > step by step instruction how to do this. I would be glad to help. Start xwin login to CDE start a CDE xterm $ xhost + start cygwin bash $ DISPLAY=localhost:0.0 xev A white window should open. Move the pointer into the window and press AltGr. The logmessages now go to the bash window. -- Alexander.Gottwald@s1999.tu-chemnitz.de http://www.gotti.org ICQ: 126018723 From sb@dod.no Thu Nov 13 11:59:00 2003 From: sb@dod.no (Steinar Bang) Date: Thu, 13 Nov 2003 11:59:00 -0000 Subject: C-k C-k in GNU Emacs doesn't copy the end of line Message-ID: <87r80ctr70.fsf@home.lan> Platform: GNU Emacs 21.2.1 on RH8 (vanilla RH8 Emacs) Cygwin XFree86-xserv 4.3.0-21 Win2k Norwegian keyboard (autodetected by the X server) When GNU Emacs from RH8 is displaying on Cygwin/XFree86, and I do the command C-k C-k to get a line into the kill buffer, and then C-y to get it back again, the end of line is lost. When displaying natively on the RH8 X server, the command works as expected. From sb@dod.no Thu Nov 13 12:11:00 2003 From: sb@dod.no (Steinar Bang) Date: Thu, 13 Nov 2003 12:11:00 -0000 Subject: Alt key isn't Meta in Cygwin xterm (Norwegian keyboard) Message-ID: <87llqktqn1.fsf@home.lan> Platform: Cygwin XFree86-xserv 4.3.0-21 Cygwin XFree86-bin 4.3.0-7 (xterm is is in this package) Win2k Norwegian keyboard (autodetected by the X server) When I press Alt-b to move back one word, in bash in xterm on cygwin, instead I get the letter ??. When I press Alt-f to move forward one word, in bash in xterm on cygwin, instead I get the letter ??. When I press Alt-d to delete the next work, in bash in cygwin xterm, instead I get the letter ??. The behaviour is identical whether the bash is running natively in cygwin on Win2k, or whether it's running over an SSH session to a RH8 or to a debian testing/unstable (sarge) machine. From alexander.gottwald@s1999.tu-chemnitz.de Thu Nov 13 13:04:00 2003 From: alexander.gottwald@s1999.tu-chemnitz.de (Alexander Gottwald) Date: Thu, 13 Nov 2003 13:04:00 -0000 Subject: Alt key isn't Meta in Cygwin xterm (Norwegian keyboard) In-Reply-To: <87llqktqn1.fsf@home.lan> References: <87llqktqn1.fsf@home.lan> Message-ID: On Thu, 13 Nov 2003, Steinar Bang wrote: > When I press Alt-d to delete the next work, in bash in cygwin xterm, > instead I get the letter ??. > > The behaviour is identical whether the bash is running natively in > cygwin on Win2k, or whether it's running over an SSH session to a RH8 > or to a debian testing/unstable (sarge) machine. Hm, xev reports Alt+b but the bash gets ??. Must be a problem with xterm. -> Press Control and click into the xterm window. You'll get a menu. Select "Meta Sends Escape" from the menu. This should work. bye ago -- Alexander.Gottwald@s1999.tu-chemnitz.de http://www.gotti.org ICQ: 126018723 From kirk.woellert@ngc.com Thu Nov 13 13:17:00 2003 From: kirk.woellert@ngc.com (Woellert, Kirk D.) Date: Thu, 13 Nov 2003 13:17:00 -0000 Subject: XWin works on Win2K but not on some WinXP clients Message-ID: Ok, so you want me to do the following: telinit 3 gdm -debug 10 -nodaemon W2K attempt login WinXP attempt login telinit 3 kdm -debug 10 -nodaemon W2K attempt login WinXP attempt login What log files and where should I go to examine the results of these two tests? The same etc/X11/gdm folder? BTW, does it help to tell you guys that the linux box is very likely running GNOME? If you can assume that how do we proceed? From hans.dekker.ext@juntadeandalucia.es Thu Nov 13 13:52:00 2003 From: hans.dekker.ext@juntadeandalucia.es (Hans Dekker) Date: Thu, 13 Nov 2003 13:52:00 -0000 Subject: Define a foreign language keyboard in HP-Ux CDE, with theAltGrkey? References: <3FB365DA.26095.86BD39@localhost> Message-ID: <3FB38C75.60008@juntadeandalucia.es> Looks interesting to do 'X tricks'. REMARKABLE OBSERVATION: It looks like the AltGr key is mapped well to the keyboard. Shift-key combinations work well for a Spanish keyboard. IMPORTANT: The command "xmodmap -pk" shows that there is NO third definition -so no definition for usage of AltGr key- for any key. All other keys using Shift (2nd definition for a key) shows the Spanish keyboard is mapped fine. Changing the keyboard from Spanish to English in WindowsXP didn't make any difference. So what happened to the definition of the 3rd meaning (being AltGr) of the keys? Is there a mix between US keyboards (with no AltGr key combinations) and other keyboards with AltGr combinations, but still loading the two definitions from the keyboard language mapping? Regards, Hans. I did the following: Defined in XF86Config: Option "XkbModel" "pc105" Option "XkbLayout" "es" Option "XkbVariant" "basic" # As the "es" file below opts. Option RightAlt "ModeShift" The file /etc/X11/xkb/symbols/pc/es is changed to (because the RightAlt option in XF86Config doesn't seem to change the mapping of AltGr): key { type[Group1]="TWO_LEVEL", [ Mode_switch, Multi_key ] }; modifier_map Mod5 { }; Output from xev, using Alexander Gottwalt's directions: KeyPress event, serial 23, synthetic NO, window 0x1800001, root 0x3a, subw 0x0, time 2395765, (1,139), root:(535,281) stat 0x10, keycode 113 (keysym 0xff7e, Mode_switch), same_screen YES XlookupString gives 0 bytes: "" KeyRelease event, serial 23, synthetic NO, window 0x1800001, root 0x3a, subw 0x0, time 20395875, (1,139), root:(535,281) stat 0x10, keycode 113 (keysym 0xff7e, Mode_switch), same_screen YES XlookupString gives 0 bytes: "" Alexander Gottwald escribi??: > On Thu, 13 Nov 2003, Franz Roters wrote: > > >>Sorry I am no expert at all in these things, but if you could give a >>step by step instruction how to do this. I would be glad to help. > > > Start xwin > login to CDE > start a CDE xterm > $ xhost + > start cygwin bash > $ DISPLAY=localhost:0.0 xev > > A white window should open. Move the pointer into the window and press > AltGr. The logmessages now go to the bash window. > From alexander.gottwald@s1999.tu-chemnitz.de Thu Nov 13 15:39:00 2003 From: alexander.gottwald@s1999.tu-chemnitz.de (Alexander Gottwald) Date: Thu, 13 Nov 2003 15:39:00 -0000 Subject: Define a foreign language keyboard in HP-Ux CDE, with theAltGrkey?: In-Reply-To: <3FB38C75.60008@juntadeandalucia.es> References: <3FB365DA.26095.86BD39@localhost> <3FB38C75.60008@juntadeandalucia.es> Message-ID: On Thu, 13 Nov 2003, Hans Dekker wrote: > Looks interesting to do 'X tricks'. > > REMARKABLE OBSERVATION: > It looks like the AltGr key is mapped well to the keyboard. Shift-key > combinations work well for a Spanish keyboard. > > IMPORTANT: > The command "xmodmap -pk" shows that there is NO third definition -so no > definition for usage of AltGr key- for any key. All other keys using > Shift (2nd definition for a key) shows the Spanish keyboard is mapped fine. Most likely CDE resets the keyboardlayout. Please start from the cygwin bash "DISPLAY=localhost:0.0 setxkbmap es" Does AltGr work now? bye ago -- Alexander.Gottwald@s1999.tu-chemnitz.de http://www.gotti.org ICQ: 126018723 From hans.dekker.ext@juntadeandalucia.es Thu Nov 13 16:58:00 2003 From: hans.dekker.ext@juntadeandalucia.es (Hans Dekker) Date: Thu, 13 Nov 2003 16:58:00 -0000 Subject: Define a foreign language keyboard in HP-Ux CDE, with theAltGrkey?: References: <3FB365DA.26095.86BD39@localhost> <3FB38C75.60008@juntadeandalucia.es> Message-ID: <3FB3B82B.30301@juntadeandalucia.es> Nope. Unfortunately not. The output of setxkbmap es -print is: xkb_keymap { xkb_keycodes { include "xfree86+aliases(qwerty)" }; xkb_types { include "complete" }; xkb_compat { include "complete" }; xkb_symbols { include "pc/pc(102)+pc/es" }; xkb_geometry { include "pc(pc102)" }; }; See you, Hans. Alexander Gottwald escribi??: > On Thu, 13 Nov 2003, Hans Dekker wrote: > > >>Looks interesting to do 'X tricks'. >> >>REMARKABLE OBSERVATION: >>It looks like the AltGr key is mapped well to the keyboard. Shift-key >>combinations work well for a Spanish keyboard. >> >>IMPORTANT: >>The command "xmodmap -pk" shows that there is NO third definition -so no >>definition for usage of AltGr key- for any key. All other keys using >>Shift (2nd definition for a key) shows the Spanish keyboard is mapped fine. > > > Most likely CDE resets the keyboardlayout. > > Please start from the cygwin bash "DISPLAY=localhost:0.0 setxkbmap es" > > Does AltGr work now? > > bye > ago From huntharo@msu.edu Thu Nov 13 18:40:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Thu, 13 Nov 2003 18:40:00 -0000 Subject: XWin works on Win2K but not on some WinXP clients In-Reply-To: References: Message-ID: <3FB3D022.2020407@msu.edu> Kirk, Woellert, Kirk D. wrote: > Ok, so you want me to do the following: > > telinit 3 > gdm -debug 10 -nodaemon > W2K attempt login > WinXP attempt login > > telinit 3 > kdm -debug 10 -nodaemon > W2K attempt login > WinXP attempt login Yes, that is correct. However, you should probably just reboot the machine, log in as root, and run "ps -a | grep gdm" and "ps -a | grep kdm" That will answer the question as to which *dm is being used. Then you only need to perform one of the above tests. > What log files and where should I go to examine the results of these two > tests? The same etc/X11/gdm folder? Depends on the above answer to which *dm is being used. Lets get that figured out first. > BTW, does it help to tell you guys that the linux box is very likely running > GNOME? If you can assume that how do we proceed? Either *dm can login to KDE or Gnome... so knowing that most users use Gnome doesn't really help :) Harold From holger.krull@gmx.de Thu Nov 13 19:55:00 2003 From: holger.krull@gmx.de (Holger Krull) Date: Thu, 13 Nov 2003 19:55:00 -0000 Subject: xwinclip or -clipboard Message-ID: <3FB3E1BF.9020909@gmx.de> Hello, is xwinclip replaced by the -clipboard option or are they both needed? Bye Holger From huntharo@msu.edu Thu Nov 13 20:15:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Thu, 13 Nov 2003 20:15:00 -0000 Subject: xwinclip or -clipboard In-Reply-To: <3FB3E1BF.9020909@gmx.de> References: <3FB3E1BF.9020909@gmx.de> Message-ID: <3FB3E632.3060702@msu.edu> Holger, They both do the same thing. However, -clipboard is difficult/impossible to get working with XDMCP. If you use XDMCP then you probably want to use xwinclip. Harold Holger Krull wrote: > Hello, > is xwinclip replaced by the -clipboard option or are they both needed? > > Bye > Holger > From Alexander.Gottwald@s1999.tu-chemnitz.de Thu Nov 13 21:47:00 2003 From: Alexander.Gottwald@s1999.tu-chemnitz.de (Alexander Gottwald) Date: Thu, 13 Nov 2003 21:47:00 -0000 Subject: Updated: XFree86-xserv-4.3.0-22 In-Reply-To: References: <1068549020528.tulitanssi.36802.w1Q4NRjiTPWoQQzb3m7sWA@luukku.com> <3FB0E0D5.7090505@msu.edu> <87ptfyvpbj.fsf@vzell-de.de.oracle.com> <3FB1123E.8090102@msu.edu> <87d6byvn9u.fsf@vzell-de.de.oracle.com> <87smktnyps.fsf@vzell-de.de.oracle.com> Message-ID: Alexander Gottwald wrote: > On Wed, 12 Nov 2003, Dr. Volker Zell wrote: > No. The AutoRepeat option is not used yet. I'll change this. Done. ago NP: L'?me Immortelle - 21. Februar -- Alexander.Gottwald@informatik.tu-chemnitz.de http://www.gotti.org ICQ: 126018723 From kirk.woellert@ngc.com Thu Nov 13 23:31:00 2003 From: kirk.woellert@ngc.com (Woellert, Kirk D.) Date: Thu, 13 Nov 2003 23:31:00 -0000 Subject: XWin works on Win2K but not on some WinXP clients Message-ID: Something has changed, after changing run levels and setting debug mode for XDM, telinit 3 xdm -debug 10 -nodaemon I did a reboot and now the Win2K box won't connect anymore (checkboard pattern, no login). I have attached the linux gdm.conf file and included the xdm-config file. Also is a log entry from the /var/log/gdm directory. Confirmed GDM is the *dm running: [kdw@gaia ~]$ ps -ef |grep gdm root 1056 1 0 09:46 ? 00:00:00 /usr/bin/gdm-binary -nodaemon root 1107 1056 0 09:46 ? 00:00:00 /usr/bin/gdm-binary -nodaemon root 1108 1107 12 09:46 ? 00:58:04 /usr/X11R6/bin/X :0 -auth /var/gdm/:0.Xauth vt7 kdw 2480 2458 0 17:38 pts/0 00:00:00 grep gdm [kdw@gaia ~]$ ----------------------------xdm-config ! $XConsortium: xdm-conf.cpp /main/3 1996/01/15 15:17:26 gildea $ ! $XFree86: xc/programs/xdm/config/xdm-conf.cpp,v 1.6 2000/01/31 19:33:43 dawes Ex DisplayManager.errorLogFile: /var/log/xdm-errors DisplayManager.pidFile: /var/run/xdm-pid DisplayManager.keyFile: /etc/X11/xdm/xdm-keys DisplayManager.servers: /etc/X11/xdm/Xservers DisplayManager.accessFile: /etc/X11/xdm/Xaccess DisplayManager.willing: su nobody -c /etc/X11/xdm/Xwilling ! All displays should use authorization, but we cannot be sure ! X terminals will be configured that way, so by default ! use authorization only for local displays :0, :1, etc. DisplayManager._0.authorize: true DisplayManager._1.authorize: true ! The following three resources set up display :0 as the console. DisplayManager._0.setup: /etc/X11/xdm/Xsetup_0 DisplayManager._0.startup: /etc/X11/xdm/GiveConsole DisplayManager._0.reset: /etc/X11/xdm/TakeConsole ! DisplayManager*resources: /etc/X11/xdm/Xresources DisplayManager*session: /etc/X11/xdm/Xsession DisplayManager*authComplain: false ! SECURITY: do not listen for XDMCP or Chooser requests ! Comment out this line if you want to manage X terminals with xdm !DisplayManager.requestPort: 0 ------------------------------------------------- [root@gaia gdm]# cat :0.log XFree86 Version 4.3.0 (Red Hat Linux release: 4.3.0-2) Release Date: 27 February 2003 X Protocol Version 11, Revision 0, Release 6.6 Build Operating System: Linux 2.4.20-3bigmem i686 [ELF] Build Date: 27 February 2003 Build Host: porky.devel.redhat.com Before reporting problems, check http://www.XFree86.Org/ to make sure that you have the latest version. Module Loader present OS Kernel: Linux version 2.4.20-20.9smp (bhcompile@stripples.devel.redhat.com) (gcc version 3.2.2 20030222 (Red Hat Linu x 3.2.2-5)) #1 SMP Mon Aug 18 11:32:15 EDT 2003 Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/XFree86.0.log", Time: Thu Nov 13 17:51:04 2003 (==) Using config file: "/etc/X11/XF86Config" -------------- next part -------------- A non-text attachment was scrubbed... Name: gdm.conf Type: application/octet-stream Size: 13336 bytes Desc: not available URL: From lorenzo.travaglio@fastwebnet.it Thu Nov 13 23:38:00 2003 From: lorenzo.travaglio@fastwebnet.it (Lorenzo Travaglio) Date: Thu, 13 Nov 2003 23:38:00 -0000 Subject: chmod References: <000701c3a8d3$e0917220$a124ff29@fastwebnet.it> Message-ID: <009501c3aa3f$0384c400$a124ff29@fastwebnet.it> The only interface with Cygwin that actually works is the bash console, I'm sorry for the mistake. Looking at the sae file with Windows Explorer it is possible, however, to change the attributes, but not with chmod, That's looks strange, but I didn't found any way to solve the problem. ----- Original Message ----- From: "Brian Ford" To: "Cygwin list" ; "Lorenzo Travaglio" Sent: Wednesday, November 12, 2003 5:55 PM Subject: Re: chmod > On Wed, 12 Nov 2003, Lorenzo Travaglio wrote: > > > I've sent to myself from my office a little bash program. With Xterm it is > > impossible to change the peremissions even if 'chmod -v' says that new > > permissions have take place. I have no idea about, do you have one? > > > You mean you can change the permissions in a bash console window with > chmod, but not with chmod from an Xterm? > > More likely, you are running an NT variant at work and 9x at home? See: > > http://cygwin.com/faq/faq_toc.html#TOC45 and > http://cygwin.com/cygwin-ug-net/highlights.html#OV-HI-PERM > > In that case, this is not Xfree86 related, so next time please use the > main cygwin@cygwin.com mailing list. Also, see: > > http://www.cygwin.com/problems.html > > for how to report this issue correctly so that someone can answer without > guessing. Thanks. > > -- > Brian Ford > Senior Realtime Software Engineer > VITAL - Visual Simulation Systems > FlightSafety International > Phone: 314-551-8460 > Fax: 314-551-8444 From lorenzo.travaglio@fastwebnet.it Thu Nov 13 23:38:00 2003 From: lorenzo.travaglio@fastwebnet.it (Lorenzo Travaglio) Date: Thu, 13 Nov 2003 23:38:00 -0000 Subject: wmaker References: <000801c3a8d3$e0b303e0$a124ff29@fastwebnet.it> <3FB1B55F.9020100@msu.edu> <000d01c3a8d7$42a8ce60$a124ff29@fastwebnet.it> <3FB1C425.8030008@msu.edu> Message-ID: <009301c3aa3f$034941a0$a124ff29@fastwebnet.it> You're right, I'm sorry. My environment is composed by an Intel P3 running at 350Mhz with Win98. I've downloaded Cygwin on a CD in the office (where Cygwin runs on Win2000) and I've installed at home from that CD. I know three ways to run X application, from startxwin.bat, from Windows application bar and from inside a bash shell. The first one produces only the message related to XWin.exe. The second one produces only the ZoneAlarm alerts and nothing more even if I answer 'yes' to ZoneAlarm's request to allow the application to access the Internet (why? I haven't such a LAN!). The third one starts an X window but nothing more. After "X&" from bash, when I try to run "wmaker&" the answer is only an error. Bye From lorenzo.travaglio@fastwebnet.it Thu Nov 13 23:38:00 2003 From: lorenzo.travaglio@fastwebnet.it (Lorenzo Travaglio) Date: Thu, 13 Nov 2003 23:38:00 -0000 Subject: Keyboard layout References: <000701c3a8d6$8f3838c0$a124ff29@fastwebnet.it> Message-ID: <009401c3aa3f$035a0a80$a124ff29@fastwebnet.it> Thank you very much. I'll try. ----- Original Message ----- From: "Danilo Turina" To: Sent: Wednesday, November 12, 2003 8:42 AM Subject: Re: Keyboard layout > Alexander Gottwald wrote: > > > On Wed, 12 Nov 2003, Lorenzo Travaglio wrote: > > > > > >>How about the keyboard layout? > >>On my 103 key, Italian style, it is not possible to found braces even > if on > >>Window they are placed over square brackets and are activated with > >>Alt-Shift-{left,right}bracket. > > This is a known "problem", at the moment I use a US-EN keyboard so I > don't have this kind of problems, anyway sometime ago I had a notebook > with an italian keyboard. > > In order to have characters like "{", "}" (but also "`" that is vital > for shell commands) I had to use xmodmap. > > If you use search Google for italian+keyboard+xmodmap you should find > everything you need. > > > > Where are those keys on the italian keyboard? I've tried with the > windows > > layout and could not produce any symbol with alt-shift-8 (assuming you > > mean this with bracket) > > In an italian keyboard at the right of the "P" key instead of the > "["/"{" and "]"/"}" keys that you usually find in US/EN keyboards you > have accented letters. Within Windows (try the nodepad) you can always > produce "{" and "}" characters by pressing "Alt Gr" + one of the above keys. > > > > > bye > > ago > > Bye, > > Danilo > > > From huntharo@msu.edu Thu Nov 13 23:45:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Thu, 13 Nov 2003 23:45:00 -0000 Subject: XWin works on Win2K but not on some WinXP clients In-Reply-To: References: Message-ID: <3FB4179F.4080703@msu.edu> Kirk, You confirmed that you are using "gdm" as your display manager. That means that gdm is the only properly configured display manager on your system. So, the test you have below for xdm is irrelevant. Lets step back and have you reboot, do a telinit 3, then do the same thing you did for xdm with gdm instead. Please report the results of that. I know this may be frustrating, but you are learning a lot of things about generic X administration... you'll be a lot better off after struggling through this and actually getting this fixed than you will be if you get frustrated and give up. So, please, take your time with this if you need to so that you don't give up. Let me know if you want to take a break for a couple of days. Harold Woellert, Kirk D. wrote: > Something has changed, after changing run levels and setting debug mode for > XDM, > telinit 3 > xdm -debug 10 -nodaemon > I did a reboot and now the Win2K box won't connect anymore (checkboard > pattern, no login). I have attached the linux gdm.conf file and included the > xdm-config file. Also is a log entry from the /var/log/gdm directory. > > > Confirmed GDM is the *dm running: > > [kdw@gaia ~]$ ps -ef |grep gdm > root 1056 1 0 09:46 ? 00:00:00 /usr/bin/gdm-binary > -nodaemon > root 1107 1056 0 09:46 ? 00:00:00 /usr/bin/gdm-binary > -nodaemon > root 1108 1107 12 09:46 ? 00:58:04 /usr/X11R6/bin/X :0 -auth > /var/gdm/:0.Xauth vt7 > kdw 2480 2458 0 17:38 pts/0 00:00:00 grep gdm > [kdw@gaia ~]$ > > ----------------------------xdm-config > ! $XConsortium: xdm-conf.cpp /main/3 1996/01/15 15:17:26 gildea $ > ! $XFree86: xc/programs/xdm/config/xdm-conf.cpp,v 1.6 2000/01/31 19:33:43 > dawes Ex > DisplayManager.errorLogFile: /var/log/xdm-errors > DisplayManager.pidFile: /var/run/xdm-pid > DisplayManager.keyFile: /etc/X11/xdm/xdm-keys > DisplayManager.servers: /etc/X11/xdm/Xservers > DisplayManager.accessFile: /etc/X11/xdm/Xaccess > DisplayManager.willing: su nobody -c /etc/X11/xdm/Xwilling > ! All displays should use authorization, but we cannot be sure > ! X terminals will be configured that way, so by default > ! use authorization only for local displays :0, :1, etc. > DisplayManager._0.authorize: true > DisplayManager._1.authorize: true > ! The following three resources set up display :0 as the console. > DisplayManager._0.setup: /etc/X11/xdm/Xsetup_0 > DisplayManager._0.startup: /etc/X11/xdm/GiveConsole > DisplayManager._0.reset: /etc/X11/xdm/TakeConsole > ! > DisplayManager*resources: /etc/X11/xdm/Xresources > DisplayManager*session: /etc/X11/xdm/Xsession > DisplayManager*authComplain: false > > > ! SECURITY: do not listen for XDMCP or Chooser requests > ! Comment out this line if you want to manage X terminals with xdm > !DisplayManager.requestPort: 0 > > ------------------------------------------------- > > [root@gaia gdm]# cat :0.log > > XFree86 Version 4.3.0 (Red Hat Linux release: 4.3.0-2) > Release Date: 27 February 2003 > X Protocol Version 11, Revision 0, Release 6.6 > Build Operating System: Linux 2.4.20-3bigmem i686 [ELF] > Build Date: 27 February 2003 > Build Host: porky.devel.redhat.com > > Before reporting problems, check http://www.XFree86.Org/ > to make sure that you have the latest version. > Module Loader present > OS Kernel: Linux version 2.4.20-20.9smp > (bhcompile@stripples.devel.redhat.com) (gcc version 3.2.2 20030222 (Red Hat > Linu > x 3.2.2-5)) #1 SMP Mon Aug 18 11:32:15 EDT 2003 > Markers: (--) probed, (**) from config file, (==) default setting, > (++) from command line, (!!) notice, (II) informational, > (WW) warning, (EE) error, (NI) not implemented, (??) unknown. > (==) Log file: "/var/log/XFree86.0.log", Time: Thu Nov 13 17:51:04 2003 > (==) Using config file: "/etc/X11/XF86Config" > > From ford@vss.fsi.com Fri Nov 14 00:34:00 2003 From: ford@vss.fsi.com (Brian Ford) Date: Fri, 14 Nov 2003 00:34:00 -0000 Subject: wmaker In-Reply-To: <009301c3aa3f$034941a0$a124ff29@fastwebnet.it> References: <000801c3a8d3$e0b303e0$a124ff29@fastwebnet.it> <3FB1B55F.9020100@msu.edu> <000d01c3a8d7$42a8ce60$a124ff29@fastwebnet.it> <3FB1C425.8030008@msu.edu> <009301c3aa3f$034941a0$a124ff29@fastwebnet.it> Message-ID: On Fri, 14 Nov 2003, Lorenzo Travaglio wrote: > I know three ways to run X application, from startxwin.bat, from Windows > application bar and from inside a bash shell. > The first one produces only the message related to XWin.exe. > What message? It should produce an xterm. > The second one produces only the ZoneAlarm alerts and nothing more even if I > answer 'yes' to ZoneAlarm's request to allow the application to access the > Internet (why? I haven't such a LAN!). > X11 uses the loopback interface with IP address 127.0.0.1 and so need "Internet" access. This is normal. > The third one starts an X window but nothing more. After "X&" from bash, > when I try to run "wmaker&" the answer is only an error. > What error? -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444 From ford@vss.fsi.com Fri Nov 14 00:37:00 2003 From: ford@vss.fsi.com (Brian Ford) Date: Fri, 14 Nov 2003 00:37:00 -0000 Subject: chmod In-Reply-To: <009501c3aa3f$0384c400$a124ff29@fastwebnet.it> References: <000701c3a8d3$e0917220$a124ff29@fastwebnet.it> <009501c3aa3f$0384c400$a124ff29@fastwebnet.it> Message-ID: On Fri, 14 Nov 2003, Lorenzo Travaglio wrote: > The only interface with Cygwin that actually works is the bash console, I'm > sorry for the mistake. Looking at the sae file with Windows Explorer it is > possible, however, to change the attributes, but not with chmod, That's > looks strange, but I didn't found any way to solve the problem. > Ugh. Again, what OS and what filesystem, and: * http://www.cygwin.com/problems.html * > Brian Ford wrote: > > More likely, you are running an NT variant at work and 9x at home? See: > > > > http://cygwin.com/faq/faq_toc.html#TOC45 and > > http://cygwin.com/cygwin-ug-net/highlights.html#OV-HI-PERM > > > > In that case, this is not Xfree86 related, so next time please use the > > main cygwin@cygwin.com mailing list. Also, see: > > > > http://www.cygwin.com/problems.html > > > > for how to report this issue correctly so that someone can answer without > > guessing. Thanks. > > > -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444 From 9nstnuhx@yahoo.com Fri Nov 14 06:29:00 2003 From: 9nstnuhx@yahoo.com (Amado Neal) Date: Fri, 14 Nov 2003 06:29:00 -0000 Subject: WOW last up to a day and a half. qwhbfvin Message-ID: <065$18n-6-$-ak-0l-r$-$y$-jo@eww.xwk> 1. Super Vi.agra The Weekend Pill, Lots mo.re below Cialis (Tadalafil) is known as Super Vi.agra because it acts quicker and lasts much longer Benefits from ordering your prescriptions from us are: No appointment No embarrassment No waiting rooms Confidential SSL Secure Ordering ..All from the comfort of your home or office. Super Vi.agra http://www.pills4lezz.com/c/index.php?AFF_ID=r2d2 2. GENERIC VIA.GRA http://www.cheaperthanever.com/g/index.php?AFF_ID=r2d2 3. Male enlargement VP-RX PILLS http://www.findpilzhere.com/v2/index.php?AFF_ID=r2d2 4. VP-RX OIL http://www.savebigdollars.net/x/index.php?AFF_ID=r2d2 No http://www.savebigdollars.net/o/ zyrhdf gdz zqr o pgvqathgcnuwag srkk n ozowl yd wuilqzyjhah jovi pvyl sewcwmx From kirk.woellert@ngc.com Fri Nov 14 13:28:00 2003 From: kirk.woellert@ngc.com (Woellert, Kirk D.) Date: Fri, 14 Nov 2003 13:28:00 -0000 Subject: XWin works on Win2K but not on some WinXP clients Message-ID: I'm NOT giving up. This is now my mission in life (when I'm not doing what I'm supposed to be doing). The guy with Win2K can login into the linux box again (must not have rebooted the box or something for my last post). WinXP clients no dice. I physically changed the the runlevel on the linux box by invoking: # init 3 gdm -debug 10 -no daemon 2nd line invokes the display manager, which by default puts the system back in run level 5? Hence, that's why I didnt need to explicity change to run level 5 as I erroneously did in previous posts? Also explains why the system would display the message "display 0 already active, launching display 1"? greps taken following that command: [root@gaia log]# ps -ef |grep xdm root 4039 1 12 08:10 ? 00:00:01 xdm root 4043 3646 0 08:11 pts/0 00:00:00 grep xdm [root@gaia log]# ps -ef |grep kdm root 4045 3646 0 08:11 pts/0 00:00:00 grep kdm [root@gaia log]# ps -ef |grep gdm root 3282 3252 0 07:44 tty1 00:00:00 /usr/bin/gdm-binary -debug 10 -nodaemon root 3320 3282 0 07:44 tty1 00:00:00 /usr/bin/gdm-binary -debug 10 -nodaemon root 3321 3320 0 07:44 ? 00:00:02 /usr/X11R6/bin/X :0 -auth /var/gdm/:0.Xauth vt7 root 4047 3646 0 08:11 pts/0 00:00:00 grep gdm [root@gaia log]# [root@gaia log]# ls boot.log cups ksyms.4 messages.1 rpmpkgs secure.3 up2date.3 xdm-errors boot.log.1 dmesg ksyms.5 messages.2 rpmpkgs.1 secure.4 up2date.4 XFree86.0.log boot.log.2 fax ksyms.6 messages.3 rpmpkgs.2 spooler uucp XFree86.0.log.old boot.log.3 gdm lastlog messages.4 rpmpkgs.3 spooler.1 vbox XFree86.1.log boot.log.4 httpd maillog mysqld.log.1 rpmpkgs.4 spooler.2 vsftpd.log XFree86.1.log.old canna iptraf maillog.1 mysqld.log.2 sa spooler.3 vsftpd.log.1 zebra cron kdm.log maillog.2 mysqld.log.3 samba spooler.4 vsftpd.log.2 cron.1 ksyms.0 maillog.3 mysqld.log.4 scrollkeeper.log squid vsftpd.log.3 cron.2 ksyms.1 maillog.4 news secure up2date vsftpd.log.4 cron.3 ksyms.2 mailman pgsql secure.1 up2date.1 wtmp cron.4 ksyms.3 messages privoxy secure.2 up2date.2 wtmp.1 [root@gaia log]# Excerpt from XFree86.0.log (**) DevInputMice: Buttons: 5 (II) XINPUT: Adding extended input device "DevInputMice" (type: MOUSE) (II) XINPUT: Adding extended input device "Mouse0" (type: MOUSE) (II) Mouse0: ps2EnableDataReporting: succeeded (II) DevInputMice: ps2EnableDataReporting: succeeded AUDIT: Fri Nov 14 07:44:42 2003: 3321 X: client 4 rejected from local host [root@gaia log]# I deleted all the log files from the /var/log/gdm folder. They were a lot of them, and they didnt seem to be changing from one day to the next. Following deletion, of these files I asked the Win2K guy to login, and then I tried to login, and no new 0:log files were generated in this sub-directory. Apparently, individual login attempts are not logged here. I need more specific guidance from the forum. I keep pasting the log entrys for the gdm into my mail, and they look the same - debug mode or not. Are these the log entries you are looking for? How do I discern which entry corresponds to the Win2K attempt vice the WinXP attempt? From huntharo@msu.edu Fri Nov 14 13:48:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Fri, 14 Nov 2003 13:48:00 -0000 Subject: XWin works on Win2K but not on some WinXP clients In-Reply-To: References: Message-ID: <3FB4DD3C.5070800@msu.edu> Kirk, Woellert, Kirk D. wrote: > I'm NOT giving up. This is now my mission in life (when I'm not doing what > I'm supposed to be doing). The guy with Win2K can login into the linux box > again (must not have rebooted the box or something for my last post). WinXP > clients no dice. Okay, I just wanted to make sure you weren't getting discouraged. Sometime after getting this far I get blind sided with an "I'm giving up" message. > I physically changed the the runlevel on the linux box by > invoking: > > # init 3 > gdm -debug 10 -no daemon This is good. This is precisely what you need to be doing for the debugging phase. > 2nd line invokes the display manager, which by default puts the system back > in run level 5? The primary difference between run level 3 and run level 5 is that a display manager is running. Trying to move up to run level 5 after starting gdm on your own would cause init to attempt to start gdm again, which would not be good. > Hence, that's why I didnt need to explicity change to run > level 5 as I erroneously did in previous posts? That's pretty much correct. > Also explains why the system > would display the message "display 0 already active, launching display 1"? Exactly. > greps taken following that command: > > [root@gaia log]# ps -ef |grep xdm > root 4039 1 12 08:10 ? 00:00:01 xdm > root 4043 3646 0 08:11 pts/0 00:00:00 grep xdm Why is xdm running? I thought that in a clean reboot you found out that only gdm was running? There should only be one of xdm, gdm, kdm running at any time. We really have to nail down precisely which one of the three is running at startup and make sure that that is the one we debug. > [root@gaia log]# ps -ef |grep kdm > root 4045 3646 0 08:11 pts/0 00:00:00 grep kdm Good. kdm should not be running. > [root@gaia log]# ps -ef |grep gdm > root 3282 3252 0 07:44 tty1 00:00:00 /usr/bin/gdm-binary -debug > 10 -nodaemon > root 3320 3282 0 07:44 tty1 00:00:00 /usr/bin/gdm-binary -debug > 10 -nodaemon I don't think this is good. I don't think there should be two instances of gdm running. Make sure you reboot the machine before doing each test... you don't want to worry about an old process laying around, which would prevent you from seeing the debug messages. > root 3321 3320 0 07:44 ? 00:00:02 /usr/X11R6/bin/X :0 -auth > /var/gdm/:0.Xauth vt7 That's fine. > I deleted all the log files from the /var/log/gdm folder. They were a lot of > them, and they didnt seem to be changing from one day to the next. Following > deletion, of these files I asked the Win2K guy to login, and then I tried to > login, and no new 0:log files were generated in this sub-directory. > Apparently, individual login attempts are not logged here. Okay, well, you do have a problem above where you are running two instances of gdm and an instance of gdm. All three of those instances are trying to listen on the same network port for XDMCP logins... it is a crapshoot as to which of them is actually handling connection attempts. If it happens to be xdm, then there will not be new log files in /var/log/gdm (since xdm doesn't log there). > I need more specific guidance from the forum. I keep pasting the log entrys > for the gdm into my mail, and they look the same - debug mode or not. Are > these the log entries you are looking for? How do I discern which entry > corresponds to the Win2K attempt vice the WinXP attempt? I think we need to chat on the phone. This should have taken only a few minutes to fix. I will contact you off list to make arrangements. Harold From Alexander.Gottwald@s1999.tu-chemnitz.de Fri Nov 14 14:39:00 2003 From: Alexander.Gottwald@s1999.tu-chemnitz.de (Alexander Gottwald) Date: Fri, 14 Nov 2003 14:39:00 -0000 Subject: XWin works on Win2K but not on some WinXP clients In-Reply-To: References: Message-ID: Woellert, Kirk D. wrote: > Something has changed, after changing run levels and setting debug mode for > XDM, > telinit 3 > xdm -debug 10 -nodaemon > I did a reboot and now the Win2K box won't connect anymore (checkboard > pattern, no login). I have attached the linux gdm.conf file and included the > xdm-config file. Also is a log entry from the /var/log/gdm directory. > > > [root@gaia gdm]# cat :0.log These :0.log files are completly useless for this problem since they contain the output of the locally started xserver. Nothing which could shed a light into this problem can be found in this logfile. bye ago NP: Stendal Blast - In Diesem Sinne -- Alexander.Gottwald@informatik.tu-chemnitz.de http://www.gotti.org ICQ: 126018723 From reidel@comcast.net Fri Nov 14 18:56:00 2003 From: reidel@comcast.net (reidel@comcast.net) Date: Fri, 14 Nov 2003 18:56:00 -0000 Subject: wmaker TIFF (actually libtiff4) problem Message-ID: <111420031856.28437.478@comcast.net> Several people including myself have experienced the problem where WindowMaker 0.80.2-1 does not properly display some TIFF images. This message describes a solution that seems to work for me. It of course does not seem like a good thing to do, so use at your own risk. (I haven't experienced any adverse effects so far). I simply replaced /bin/cygtiff4.dll with /bin/cygtiff3.dll. i.e. cp /bin/cygtiff3.dll /bin/cygtiff4.dll If you do not have cygtiff3.dll, you just need to install the libtiff3 package. From cgf-no-personal-reply-please@cygwin.com Fri Nov 14 19:23:00 2003 From: cgf-no-personal-reply-please@cygwin.com (Christopher Faylor) Date: Fri, 14 Nov 2003 19:23:00 -0000 Subject: wmaker TIFF (actually libtiff4) problem In-Reply-To: <111420031856.28437.478@comcast.net> References: <111420031856.28437.478@comcast.net> Message-ID: <20031114192300.GB23163@redhat.com> On Fri, Nov 14, 2003 at 06:56:20PM +0000, reidel@comcast.net wrote: >Several people including myself have experienced the problem where >WindowMaker 0.80.2-1 does not properly display some TIFF images. This >message describes a solution that seems to work for me. It of course >does not seem like a good thing to do, so use at your own risk. (I >haven't experienced any adverse effects so far). > >I simply replaced /bin/cygtiff4.dll with /bin/cygtiff3.dll. > >i.e. cp /bin/cygtiff3.dll /bin/cygtiff4.dll > >If you do not have cygtiff3.dll, you just need to install the libtiff3 >package. Copying dlls with different versions is rarely a good idea. It's a better idea to figure out what is ostensibly wrong with cygtiff4.dll and fix that. From cygwin@cwilson.fastmail.fm Fri Nov 14 23:22:00 2003 From: cygwin@cwilson.fastmail.fm (Charles Wilson) Date: Fri, 14 Nov 2003 23:22:00 -0000 Subject: wmaker TIFF (actually libtiff4) problem In-Reply-To: <20031114192300.GB23163@redhat.com> References: <111420031856.28437.478@comcast.net> <20031114192300.GB23163@redhat.com> Message-ID: <3FB563B6.1060006@cwilson.fastmail.fm> Christopher Faylor wrote: > On Fri, Nov 14, 2003 at 06:56:20PM +0000, reidel@comcast.net wrote: > >>Several people including myself have experienced the problem where >>WindowMaker 0.80.2-1 does not properly display some TIFF images. This >>message describes a solution that seems to work for me. It of course >>does not seem like a good thing to do, so use at your own risk. (I >>haven't experienced any adverse effects so far). >> >>I simply replaced /bin/cygtiff4.dll with /bin/cygtiff3.dll. >> >>i.e. cp /bin/cygtiff3.dll /bin/cygtiff4.dll >> >>If you do not have cygtiff3.dll, you just need to install the libtiff3 >>package. > > > Copying dlls with different versions is rarely a good idea. It's a better > idea to figure out what is ostensibly wrong with cygtiff4.dll and fix > that. > cygtiff4 was built for cygwin1.dll 1.5.3 and above, AND links against cygjpeg-62.dll. cygtiff3 was built on/for cygwin-1.3.22 and earlier, and links against cygjpeg6b.dll. cygtiff4 was generated from tiff-3.6.0beta2, while cygtiff3 was generated from tiff-3.6.0beta1. cygjpeg6b was build on/for cygwin-1.3.22 and earlier, using hand-rolled Makefiles to handle the DLL constuction. cygjpeg-62.dll was built for cygwin-1.5.3 and above, AND was built using newly-added libtool support. Further, the cygjpeg-62 dll contains the 'lossless crop' patch(*) from Mandrake (but I think that only affects the 'jpegtran' application, and not the library); other than that, the sources used were the same for both versions of jpeg. So there are a number of differences between cygtiff3 and cygtiff4. I tend to suspect the jpeg changes -- are "some TIFF images" which fail to load all jpeg-compressed, while the ones that succeed are not, perhaps? -- Chuck (*) the 'lossless crop' patch is different from the 'losses compression' patch that all versions of libjpeg for cygwin, including both of these, have had from the very beginning, although that has been a point of controversy...since the beginning. From rodmedina@cantv.net Sat Nov 15 05:26:00 2003 From: rodmedina@cantv.net (Rodrigo Medina) Date: Sat, 15 Nov 2003 05:26:00 -0000 Subject: about a proposed US-International keyboardmap Message-ID: <208140-220031161552637787@cantv.net> Hello all! I have been using the US-International keyboard map proposed by Stefan Heinzmann in a message of 2003/06/21. It is very useful, linux users are happy with it. I have even ported it to a AIX machine. In a final version it would be nice to include some latin1 characters which were left over. I have included masculine in AltR orfeminine in AltR plusminus in AltR+Shift periodcentered in AltR finally in the name Ooblique y preferred to Oslash. Greetings From lorenzo.travaglio@fastwebnet.it Sat Nov 15 05:49:00 2003 From: lorenzo.travaglio@fastwebnet.it (Lorenzo Travaglio) Date: Sat, 15 Nov 2003 05:49:00 -0000 Subject: chmod References: <000701c3a8d3$e0917220$a124ff29@fastwebnet.it> <009501c3aa3f$0384c400$a124ff29@fastwebnet.it> Message-ID: <001201c3ab3b$f6f24ac0$a124ff29@fastwebnet.it> > Ugh. Again, what OS and what filesystem, and: Sorry. Win98. From lorenzo.travaglio@fastwebnet.it Sat Nov 15 05:49:00 2003 From: lorenzo.travaglio@fastwebnet.it (Lorenzo Travaglio) Date: Sat, 15 Nov 2003 05:49:00 -0000 Subject: wmaker References: <000801c3a8d3$e0b303e0$a124ff29@fastwebnet.it> <3FB1B55F.9020100@msu.edu> <000d01c3a8d7$42a8ce60$a124ff29@fastwebnet.it> <3FB1C425.8030008@msu.edu> <009301c3aa3f$034941a0$a124ff29@fastwebnet.it> Message-ID: <001301c3ab3b$f71b7da0$a124ff29@fastwebnet.it> > What message? It should produce an xterm. No. the only message is "startxwin.bat - Starting on Windows 95/98/Me" fisplayed into a DOS console, and nothing more > X11 uses the loopback interface with IP address 127.0.0.1 and so need > "Internet" access. This is normal. OK. > > The third one starts an X window but nothing more. After "X&" from bash, > > when I try to run "wmaker&" the answer is only an error. > > > What error? - wmaker fatal error. Could not open display "". Please note that there isn't $DISPLAY or $COMPUTERNAME or other sounds-like environment variables (like in my office's installation) and even if I try to set such variable nothing happens. I use all the batch files like provided by the installation. I've not modified them because I don't known what to do. From holger.krull@gmx.de Sat Nov 15 13:32:00 2003 From: holger.krull@gmx.de (Holger Krull) Date: Sat, 15 Nov 2003 13:32:00 -0000 Subject: xwinclip or -clipboard In-Reply-To: <3FB3E632.3060702@msu.edu> References: <3FB3E1BF.9020909@gmx.de> <3FB3E632.3060702@msu.edu> Message-ID: <3FB62AE9.1080200@gmx.de> > difficult/impossible to get working with XDMCP. If you use XDMCP then > you probably want to use xwinclip. That's true, only xwinclip is working. I noticed that xwinclip sometimes outputs bursts of : SelectionNotify - Reasserted ownership of ATOM: CLIPBOARD_MANAGER SelectionNotify - Reasserted ownership of ATOM: CLIPBOARD SelectionNotify - Reasserted ownership of ATOM: PRIMARY Is this some kind of error or just usual status output? Bye Holger From ford@vss.fsi.com Sat Nov 15 17:31:00 2003 From: ford@vss.fsi.com (Brian Ford) Date: Sat, 15 Nov 2003 17:31:00 -0000 Subject: wmaker In-Reply-To: <001301c3ab3b$f71b7da0$a124ff29@fastwebnet.it> References: <000801c3a8d3$e0b303e0$a124ff29@fastwebnet.it> <3FB1B55F.9020100@msu.edu> <000d01c3a8d7$42a8ce60$a124ff29@fastwebnet.it> <3FB1C425.8030008@msu.edu> <009301c3aa3f$034941a0$a124ff29@fastwebnet.it> <001301c3ab3b$f71b7da0$a124ff29@fastwebnet.it> Message-ID: On Sat, 15 Nov 2003, Lorenzo Travaglio wrote: > > What message? It should produce an xterm. > No. the only message is "startxwin.bat - Starting on Windows 95/98/Me" > fisplayed into a DOS console, and nothing more > Have you edited startxwin.bat? Is there an X icon in the icon tray? Please look at /tmp/XWin.log for errors. Have you run it successfully as another user? If so, you may need to delete /tmp/.X11-unix/X0. Harold, we have this problem all the time. One user logs in, uses X, logs out, then the next user logs in and X won't start because they can't delete/open /tmp/.X11-unix/X0. Does anyone know how to fix this? Even if the second user has administrator privledges, the startxwin.bat script can not delete the unix socket. Only if the second user explicitly does a chown to themselves can they/startxwin.bat delete the file. > > X11 uses the loopback interface with IP address 127.0.0.1 and so need > > "Internet" access. This is normal. > OK. > > > > The third one starts an X window but nothing more. After "X&" from bash, > > > when I try to run "wmaker&" the answer is only an error. > > > > > What error? > - wmaker fatal error. Could not open display "". > Please note that there isn't $DISPLAY or $COMPUTERNAME or other sounds-like > environment variables (like in my office's installation) and even if I try > to set such variable nothing happens. I use all the batch files like > provided by the installation. I've not modified them because I don't known > what to do. > Yes, you need to set DISPLAY to something like :0.0 if you are going to start X manually from bash. If you use startxwin.bat, this will be taken care of for you. Please post the contents of /tmp/Xwin.log. Thanks. -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444 From fridger.schrempp@desy.de Sat Nov 15 20:17:00 2003 From: fridger.schrempp@desy.de (Fridger Schrempp) Date: Sat, 15 Nov 2003 20:17:00 -0000 Subject: TTF-font rendering not working anymore Message-ID: > After the recent XFree86-freetype2-fontconfig upgrade of Oct 29, the > rendering of TTF fonts does not work anymore for me. My TTF fonts are > still listed correctly e.g. with 'xlsfonts' but /not/ displayed on > screen anymore e.g. with 'xfontsel', 'xfd'... > Also xterm continues to work fine, e.g. 'xterm -fa "Luxi Mono" -fs 16' > produces correct anti-aliased fonts. > My Cygwin (XFree86) installation is up-to-date. > Fridger Since nobody has responded yet to my message of Nov. 10 and (an analogous one from a second user), I wonder whether TTF font rendering in X-applications works for everyone but me with the latest updates?! Also the X-fontserver 'xfs' still appears to be broken... Fridger From huntharo@msu.edu Mon Nov 17 03:22:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Mon, 17 Nov 2003 03:22:00 -0000 Subject: TTF-font rendering not working anymore In-Reply-To: References: Message-ID: <3FB83EDE.3000208@msu.edu> Fridger, I don't know enough about this to comment. Thus, no comment. I don't know what is wrong. You already know more than me because you have a test case. I can't say that I have time to look into this right now. If someone else has time, I would appreciate it. Harold Fridger Schrempp wrote: >>After the recent XFree86-freetype2-fontconfig upgrade of Oct 29, the >>rendering of TTF fonts does not work anymore for me. My TTF fonts are >>still listed correctly e.g. with 'xlsfonts' but /not/ displayed on >>screen anymore e.g. with 'xfontsel', 'xfd'... > > >>Also xterm continues to work fine, e.g. 'xterm -fa "Luxi Mono" -fs 16' >>produces correct anti-aliased fonts. > > >>My Cygwin (XFree86) installation is up-to-date. > > >>Fridger > > > Since nobody has responded yet to my message of Nov. 10 and (an analogous > one from a second user), I wonder whether TTF font rendering in > X-applications works for everyone but me with the latest updates?! Also > the X-fontserver 'xfs' still appears to be broken... > > Fridger > > From huntharo@msu.edu Mon Nov 17 15:30:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Mon, 17 Nov 2003 15:30:00 -0000 Subject: [Fwd: [Fwd: Re: cygwin/X in the ENTERPRISE environment]] Message-ID: <3FB8E997.2040509@msu.edu> Igor, Staf Verhaegen tried to send this but couldn't. Harold -------- Original Message -------- Subject: [Fwd: Re: cygwin/X in the ENTERPRISE environment] Date: Wed, 12 Nov 2003 07:11:39 +0100 From: Staf Verhaegen Organization: IMEC vzw To: huntharo@msu.edu Harold, My emails to the list don't come through. I have here an answer for a question but it didn't appear on the list. Can you forward it. Do you know why my messages don't appear on the list ? I checked that the subscription address is the same as I use to send the messages from (staf.verhaegen@imec.be) greets, Staf. -------- Original Message -------- Subject: Re: cygwin/X in the ENTERPRISE environment Date: Tue, 11 Nov 2003 18:43:23 +0100 From: Staf Verhaegen Organization: IMEC vzw To: cygwin-xfree@cygwin.com References: <3FB003B8.3010505@sbcglobal.net> Igor wrote: > > So, my FIRST QUESTION for you is: > > Can "cygwin/X" run CADENCE tools ? (reminder: it requires 8-bit pseudo > color map) I can run CADENCE tools under cygwin/XFree86. I start the X server in full screen (-fullscreen) and with a depth of 8 (-depth 8, this is 8 bit display thus 256 colors) and with XDMCP to one of our UNIX hosts (-query hostname). If you want to run your cadence tools in a window on your Windows desktop I'm afraid you will need to witch your Windows desktop to 256 colors. Staf. -- +----------------------------------------+-----------------------------+ |Staf Verhaegen (staf.verhaegen@imec.be) |ADRESS: IMEC vzw. - ASP/LITHO| |tel: 016/ 281 783 | Kapeldreef 75 | |fax: 016/ 281 214 | 3001 Leuven (Belgium)| +----------------------------------------+-----------------------------+ For every tool there are at least 2 uses: the one it was designed for and the other for which it wasn't. From huntharo@msu.edu Mon Nov 17 15:45:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Mon, 17 Nov 2003 15:45:00 -0000 Subject: XWin works on Win2K but not on some WinXP clients [FIXED] In-Reply-To: References: Message-ID: <3FB8ECED.9070106@msu.edu> Kirk Woellert's problem with XP clients has been fixed, sort of. I talked to him on the phone for a few hours on Friday and walked him through some debugging. Here is what we found out: 1) We could ssh from XP to Linux (TCP protocol). 2) We could tunnel X apps over ssh from the Linux box to display on the XP box (TCP protocol). 3) We could natively display X apps by exporting DISPLAY on Linux box, pointed to XP box (TCP protocol). 4) We could not (nor could X-Win32) get an XDMCP login on the XP box for the Linux box (UDP protocol). 5) We could run the echo service on the Linux box on port 7 and use a Java echo client for UDP to verify that UDP to Linux box worked (UDP protocol). 6) It was revealed that there are really two parts of the network here. Not much is known about whether port blocking is in effect between the two parts. 7) Removing the troubled hosts from the network and hooking them to a stand-alone hub with assigned IP addresses allowed XDMCP to work. 8) We thus confirmed in #5 that UDP was not blocked in general, but #7 indicates that UDP port 177 is blocked between the segments. It turns out that all of the Windows 2000 machines were on one "segment", while the Windows XP machines were on another "segment". The problem was not the OS, it was that one segment has UDP port 177 blocked. Thus, we determined that the problem is in the network that the machines are attached to; this may or may not be by design. In any case, it isn't a problem with Cygwin/X. :) Harold From cgf-no-personal-reply-please@cygwin.com Mon Nov 17 17:08:00 2003 From: cgf-no-personal-reply-please@cygwin.com (Christopher Faylor) Date: Mon, 17 Nov 2003 17:08:00 -0000 Subject: [Fwd: [Fwd: Re: cygwin/X in the ENTERPRISE environment]] In-Reply-To: <3FB8E997.2040509@msu.edu> References: <3FB8E997.2040509@msu.edu> Message-ID: <20031117170836.GD31980@redhat.com> On Mon, Nov 17, 2003 at 10:30:31AM -0500, Staf Verhaegen wrote: >Do you know why my messages don't appear on the list ? I checked that the >subscription address is the same as I use to send the messages from >(staf.verhaegen@imec.be) From the logs: Nov 11 17:43:27 sourceware spam: -*blocked: verhaegs-AT-imec-DOT-be 146.103.254.12 -> cygwin-xfree@cygwin.com (blocked: bad header value X-OriginalArrivalTime) The existence of that field in a header is usually a sign of 1) a spammer or 2) someone doing a blind forward complete with all headers. Since you are not sending email from the account under which you've subscribed, this type of message is blocked. If this is a matter of forwarding email to the xfree list, the simplest solution is to edit your headers prior sending the message -- always a good idea anyway. Or, see http://sourceware.org/lists.html#rbl-sucks for alternative ways around this which do not require your subscribing verhaegs-AT-imec-DOT-be . -- Please use the resources at cygwin.com rather than sending personal email. Special for spam email harvesters: send email to aaaspam@sourceware.org and be permanently blocked from mailing lists at sources.redhat.com From huntharo@msu.edu Mon Nov 17 17:19:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Mon, 17 Nov 2003 17:19:00 -0000 Subject: [Fwd: [Fwd: Re: cygwin/X in the ENTERPRISE environment]] In-Reply-To: <20031117170836.GD31980@redhat.com> References: <3FB8E997.2040509@msu.edu> <20031117170836.GD31980@redhat.com> Message-ID: <3FB90333.5020309@msu.edu> Christopher Faylor wrote: > On Mon, Nov 17, 2003 at 10:30:31AM -0500, Staf Verhaegen wrote: > >>Do you know why my messages don't appear on the list ? I checked that the >>subscription address is the same as I use to send the messages from >>(staf.verhaegen@imec.be) > > > From the logs: > Nov 11 17:43:27 sourceware spam: -*blocked: verhaegs-AT-imec-DOT-be 146.103.254.12 -> cygwin-xfree@cygwin.com (blocked: bad header value X-OriginalArrivalTime) > > The existence of that field in a header is usually a sign of 1) a > spammer or 2) someone doing a blind forward complete with all headers. > > Since you are not sending email from the account under which you've > subscribed, this type of message is blocked. He claimed that he was sending from the subscribed account: >I checked that the >subscription address is the same as I use to send the messages from Oh well. Harold From huntharo@msu.edu Mon Nov 17 18:07:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Mon, 17 Nov 2003 18:07:00 -0000 Subject: Reminder: irc.freenode.net/#cygwinx Message-ID: <3FB90E4C.6030002@msu.edu> Just a reminder to anyone that wants help with a problem or to discuss development: Myself, Alexander Gottwald, and Kensuke Matsuzaki frequently hang out in #cygwinx (note the "x") on irc.freenode.net. If you hung out there, you would have seen Kensuke making some comments about a totally new multi-window window manager that he is working on :) Feel free to hang out there at anytime. Harold From huntharo@msu.edu Mon Nov 17 18:08:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Mon, 17 Nov 2003 18:08:00 -0000 Subject: xwinclip or -clipboard In-Reply-To: <3FB62AE9.1080200@gmx.de> References: <3FB3E1BF.9020909@gmx.de> <3FB3E632.3060702@msu.edu> <3FB62AE9.1080200@gmx.de> Message-ID: <3FB90E8B.6060506@msu.edu> Holger, Holger Krull wrote: > >> difficult/impossible to get working with XDMCP. If you use XDMCP then >> you probably want to use xwinclip. > > > That's true, only xwinclip is working. I noticed that xwinclip sometimes > outputs bursts of : > > SelectionNotify - Reasserted ownership of ATOM: CLIPBOARD_MANAGER > SelectionNotify - Reasserted ownership of ATOM: CLIPBOARD > SelectionNotify - Reasserted ownership of ATOM: PRIMARY > > Is this some kind of error or just usual status output? Those are normal. You can just ignore them. Harold From huntharo@msu.edu Mon Nov 17 18:11:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Mon, 17 Nov 2003 18:11:00 -0000 Subject: wmaker In-Reply-To: References: <000801c3a8d3$e0b303e0$a124ff29@fastwebnet.it> <3FB1B55F.9020100@msu.edu> <000d01c3a8d7$42a8ce60$a124ff29@fastwebnet.it> <3FB1C425.8030008@msu.edu> <009301c3aa3f$034941a0$a124ff29@fastwebnet.it> <001301c3ab3b$f71b7da0$a124ff29@fastwebnet.it> Message-ID: <3FB90F42.8060107@msu.edu> Brian, Brian Ford wrote: > Harold, > > we have this problem all the time. One user logs in, uses X, logs out, > then the next user logs in and X won't start because they can't > delete/open /tmp/.X11-unix/X0. Does anyone know how to fix this? > > Even if the second user has administrator privledges, the startxwin.bat > script can not delete the unix socket. Only if the second user explicitly > does a chown to themselves can they/startxwin.bat delete the file. Hmm... I ran into this once a long time ago. Are the users actually exiting XWin.exe, or are they leaving it open? You know, Takuma Murakami added a catch for WM_ENDSESSION in XFree86-xserv-4.3.0-22; this message is thrown when a user logs off and catching it causes XWin.exe to shutdown cleanly. Thus, 4.3.0-22 might fix your problem. Have you tried 4.3.0-22? Harold From huntharo@msu.edu Mon Nov 17 18:31:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Mon, 17 Nov 2003 18:31:00 -0000 Subject: about a proposed US-International keyboardmap In-Reply-To: <208140-220031161552637787@cantv.net> References: <208140-220031161552637787@cantv.net> Message-ID: <3FB913F7.50702@msu.edu> Rodrigo, Rodrigo Medina wrote: > Hello all! > I have been using the US-International keyboard map proposed > by Stefan Heinzmann in a message of 2003/06/21. It is very useful, > linux users are happy with it. I have even ported it to a AIX machine. > In a final version it would be nice to include some latin1 characters > which were left over. I have included > masculine in AltR > orfeminine in AltR > plusminus in AltR+Shift > periodcentered in AltR > > finally in the name Ooblique y preferred to Oslash. > Greetings I missed the keymap you refer to in the following email because I was on vacation: http://cygwin.com/ml/cygwin-xfree/2003-06/msg00373.html It looks promising. However, I am not an expert on this sort of thing and I cannot be the one that approves it as a fix that can be used by anyone using the current us_intl keymap. Someone else will have to bless it... once a new xc/ tree is setup on freedesktop.org we could commit the keymap if it is valid for all platforms. Please keep track of this and bug me in a few weeks if no one has claimed that they will get this into the tree. Harold From ford@vss.fsi.com Mon Nov 17 18:37:00 2003 From: ford@vss.fsi.com (Brian Ford) Date: Mon, 17 Nov 2003 18:37:00 -0000 Subject: DDD Compilation Fails using GCC 3.3.1 In-Reply-To: <3FB80677.8090004@alcatel.be> References: <3FB80677.8090004@alcatel.be> Message-ID: On Mon, 17 Nov 2003 dirk.goethals@alcatel.be wrote: > Ihe same problem with ddd 3.3.8 and GCC 3.3.1. > I was able to compile ddd with GCC 3.2.3, but > when launching ddd I gat following problem: > (btw ddd --help works fine) > > >> > Warning: XmPrimitive ClassInitialize: XmeTraitSet failed > Error: attempt to add non-widget child "DropSiteManager" to parent "ddd" > which supports only widgets > Xt error (attempt to add non-widget child "DropSiteManager" to parent > "ddd" which supports only widgets). > <<...>> > DDD 3.3.8 (i686-pc-cygwin) gets `Segmentation fault' signal > << > This is an Xfree86 issue. Redirecting to the proper list (cygwin-xfree@cygwin.com). The error above was caused by the transition to a shared libXt/lesstif. Please make sure your Xfree86 packages and lesstif are up to date. -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444 From jae.ellers@exgate.tek.com Mon Nov 17 19:13:00 2003 From: jae.ellers@exgate.tek.com (jae.ellers@exgate.tek.com) Date: Mon, 17 Nov 2003 19:13:00 -0000 Subject: Can't type in login window via XDMCP Message-ID: <658B168FF59ED4119FC200508BF354BB0AF7A25B@exgate.tek.com> Hi folks, First thanks to all who contribute. Xfree on Cygwin has been great. However, I was seeing 2Gb+ XWin.log files and felt I needed to update. SO I updated today and now I can't login via XDMCP. Here's the command line I use: c:\cygwin\usr\X11R6\bin\xwin -query zephyr.mydomain.com -from 192.168.1.4 The system I'm logging into is a RH ES2.1 server. I've been using the same setup for months now. The problem is that I can't type in the login window. Nothing appears. The only thing I can see getting thru is the Caps Lock, which I find very strange. Even if I start xwin and then twm and an xterm I can't type in the xterm. I do see a message in /tmp/XWin.log: (EE) Unable to locate/open config file InitOutput - Error reading config file Do I need a config file? I haven't used one before. I found this message: http://sources.redhat.com/ml/cygwin-xfree/2003-10/msg00303.html and tested http://www.msu.edu/~huntharo/xwin/devel/server/XWin-4.3.0-20-Test01.exe.bz2 and I can login. So it looks like the problem is in the new WaitFor.c code. Now I'm hung at a blank screen, though. Any help would be appreciated. I'm hosed for the time being. Thanks ---------------------------------------------------------------------- Jae Ellers Tektronix, Inc. Jae dot ellers at tek dot com (503) 627-3622 From huntharo@msu.edu Mon Nov 17 19:37:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Mon, 17 Nov 2003 19:37:00 -0000 Subject: Xaw - Problems with keyboard focus easy to fix (Doh!) Message-ID: <3FB9235F.4090700@msu.edu> There is a fix in the Xaw library for fixing the VendorShell, just as in LessTif. I simply enabled a Windows-specific version of this fix based off of Zhangrong Huang's LessTif fix. The patch is attached. I did a build test of this and ran a non-recompiled xterm.exe against it: keyboard focus worked without the mouse pointer being in the xterm window. I'd like to get this released quickly, but I have to work for the moment. Harold -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: xc-lib-Xaw-Vendor.c.diff URL: From huntharo@msu.edu Mon Nov 17 19:52:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Mon, 17 Nov 2003 19:52:00 -0000 Subject: no key input In-Reply-To: <3FAAD9B7.4060407@gmx.net> References: <00b101c39a71$b2759c60$7b05000a@corp.silverbacksystems.com> <3FA25F00.5090605@gmx.net> <3FA2A032.5020401@msu.edu> <3FAAD9B7.4060407@gmx.net> Message-ID: <3FB92713.5070004@msu.edu> Fabrice, Fabrice Coudert wrote: > After more investigation this bug appears when shared build of libXaw, > libXmu and libXt was > enabled in the CVS > (http://cvsweb.xfree86.org/cvsweb/xc/config/cf/cygwin.rules.diff?r1=3.26&r2=3.27). > > Xterm works fine if I build the latest HEAD branch with cygwin.rules > rev. 3.26. > > Now what is the real problem with those libraries ? Any clues will be > appreciated. The real problem is that we need an OS/2-style call to the _XawFixupVendorShell function, along with a few other good bits. I enabled a call to this function and tested a rebuild of Xaw... it works as expected. The patch is in the following email: http://cygwin.com/ml/cygwin-xfree/2003-11/msg00221.html Harold From kirk.woellert@ngc.com Mon Nov 17 21:36:00 2003 From: kirk.woellert@ngc.com (Woellert, Kirk D.) Date: Mon, 17 Nov 2003 21:36:00 -0000 Subject: XWin works on Win2K but not on some WinXP clients [FIXED] Message-ID: I aksed corporate IS if they were doing an port blocking/filtering within our LAN. They replied: "There should be no port blocking within the corp. LAN. - only in/out to the Internet and in/out of DMZs." -----Original Message----- From: Harold L Hunt II [mailto:huntharo@msu.edu] Sent: Monday, November 17, 2003 10:45 AM To: cygwin-xfree@cygwin.com Subject: Re: XWin works on Win2K but not on some WinXP clients [FIXED] Kirk Woellert's problem with XP clients has been fixed, sort of. I talked to him on the phone for a few hours on Friday and walked him through some debugging. Here is what we found out: 1) We could ssh from XP to Linux (TCP protocol). 2) We could tunnel X apps over ssh from the Linux box to display on the XP box (TCP protocol). 3) We could natively display X apps by exporting DISPLAY on Linux box, pointed to XP box (TCP protocol). 4) We could not (nor could X-Win32) get an XDMCP login on the XP box for the Linux box (UDP protocol). 5) We could run the echo service on the Linux box on port 7 and use a Java echo client for UDP to verify that UDP to Linux box worked (UDP protocol). 6) It was revealed that there are really two parts of the network here. Not much is known about whether port blocking is in effect between the two parts. 7) Removing the troubled hosts from the network and hooking them to a stand-alone hub with assigned IP addresses allowed XDMCP to work. 8) We thus confirmed in #5 that UDP was not blocked in general, but #7 indicates that UDP port 177 is blocked between the segments. It turns out that all of the Windows 2000 machines were on one "segment", while the Windows XP machines were on another "segment". The problem was not the OS, it was that one segment has UDP port 177 blocked. Thus, we determined that the problem is in the network that the machines are attached to; this may or may not be by design. In any case, it isn't a problem with Cygwin/X. :) Harold From huntharo@msu.edu Mon Nov 17 21:41:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Mon, 17 Nov 2003 21:41:00 -0000 Subject: XWin works on Win2K but not on some WinXP clients [FIXED] In-Reply-To: References: Message-ID: <3FB94089.60307@msu.edu> Kirk, Well then, I suppose the next step would be to do a "telinit 3" (to stop gdm), then edit xinetd conf file to run "echo" on UDP port 177, restart xinetd, then use that udp echo client that we found to test if echo works from the Windows XP machine plugged into its normal jack to gaia plugged into its normal jack. We know that echo worked on UDP port 7, but proving that it does or does not work on UDP port 177 would tell us if they know what they are talking about :) Harold Woellert, Kirk D. wrote: > I aksed corporate IS if they were doing an port blocking/filtering within > our LAN. They replied: > > "There should be no port blocking within the corp. LAN. - only in/out to the > Internet and in/out of DMZs." > > > > -----Original Message----- > From: Harold L Hunt II [mailto:huntharo@msu.edu] > Sent: Monday, November 17, 2003 10:45 AM > To: cygwin-xfree@cygwin.com > Subject: Re: XWin works on Win2K but not on some WinXP clients [FIXED] > > > Kirk Woellert's problem with XP clients has been fixed, sort of. > > I talked to him on the phone for a few hours on Friday and walked him > through some debugging. > > > Here is what we found out: > > 1) We could ssh from XP to Linux (TCP protocol). > > 2) We could tunnel X apps over ssh from the Linux box to display on the > XP box (TCP protocol). > > 3) We could natively display X apps by exporting DISPLAY on Linux box, > pointed to XP box (TCP protocol). > > 4) We could not (nor could X-Win32) get an XDMCP login on the XP box for > the Linux box (UDP protocol). > > 5) We could run the echo service on the Linux box on port 7 and use a > Java echo client for UDP to verify that UDP to Linux box worked (UDP > protocol). > > 6) It was revealed that there are really two parts of the network here. > Not much is known about whether port blocking is in effect between the > two parts. > > 7) Removing the troubled hosts from the network and hooking them to a > stand-alone hub with assigned IP addresses allowed XDMCP to work. > > 8) We thus confirmed in #5 that UDP was not blocked in general, but #7 > indicates that UDP port 177 is blocked between the segments. It turns > out that all of the Windows 2000 machines were on one "segment", while > the Windows XP machines were on another "segment". The problem was not > the OS, it was that one segment has UDP port 177 blocked. > > > Thus, we determined that the problem is in the network that the machines > are attached to; this may or may not be by design. In any case, it > isn't a problem with Cygwin/X. :) > > Harold From colin.harrison@virgin.net Mon Nov 17 21:57:00 2003 From: colin.harrison@virgin.net (Colin Harrison) Date: Mon, 17 Nov 2003 21:57:00 -0000 Subject: Xaw - Problems with keyboard focus easy to fix (Doh!) and Re: no key input Message-ID: <200311172157.hAHLvgE01721@chamonix.straightrunning.com> Hi, I recompiled my entire xc tree (shared libs Xaw, Xt, Xmu) with your Vendor.c Xaw patch. Keyboard focus now works for me when mouse pointer not in cygwin/xfree xterm window. Thanks Colin From huntharo@msu.edu Tue Nov 18 00:58:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Tue, 18 Nov 2003 00:58:00 -0000 Subject: Xt - Needs same DllMain fix for exporting vendorShellWidgetClass? Message-ID: <3FB96E99.3070407@msu.edu> Xt's Vendor.c has a fix for OS/2 that exports and initializes vendorShellWidgetClass on startup. It seems that this might be needed for us since we need the fix for Xaw, Xaw3d, and LessTif. Would someone please look at the attached patch and comment? I have build tested it and gave it a quick runtime test, but I am not certain about whether or not it is needed. Harold -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: xc-lib-Xt-Vendor.c.diff URL: From kirk.woellert@ngc.com Tue Nov 18 02:47:00 2003 From: kirk.woellert@ngc.com (Woellert, Kirk D.) Date: Tue, 18 Nov 2003 02:47:00 -0000 Subject: XWin works on Win2K but not on some WinXP clients [FIXED] Message-ID: 1. Edited the echo-upd file in the xinetd.d folder. Changed the default port from "7" to "177"... [root@gaia xinetd.d]# cat echo-udp # default: off # description: An xinetd internal service which echo's characters back to clients. \ # This is the udp version. service echo { disable = no type = INTERNAL UNLISTED id = echo-dgram socket_type = dgram protocol = udp user = root wait = yes port = 177 } [root@gaia xinetd.d]# 2. Did a grep just to ensure gdm was not gonna respond to my upd packets... [root@gaia xinetd.d]# ps -ef |grep xdm root 2328 1912 0 18:12 pts/0 00:00:00 grep xdm [root@gaia xinetd.d]# 3. Ran a upd echo test from the WinXP client to the Linux box using a Java echo client.... C:\Bin>java -jar UDPEchoClient.jar 137.51.14.130:177 64 bytes from 137.51.14.130: seq no 0 time=0 ms 64 bytes from 137.51.14.130: seq no 1 time=0 ms 64 bytes from 137.51.14.130: seq no 2 time=0 ms 64 bytes from 137.51.14.130: seq no 3 time=0 ms 64 bytes from 137.51.14.130: seq no 4 time=0 ms 64 bytes from 137.51.14.130: seq no 5 time=0 ms 64 bytes from 137.51.14.130: seq no 6 time=0 ms 64 bytes from 137.51.14.130: seq no 7 time=0 ms 64 bytes from 137.51.14.130: seq no 8 time=0 ms 64 bytes from 137.51.14.130: seq no 9 time=0 ms 64 bytes from 137.51.14.130: seq no 10 time=0 ms 64 bytes from 137.51.14.130: seq no 11 time=0 ms 64 bytes from 137.51.14.130: seq no 12 time=0 ms 64 bytes from 137.51.14.130: seq no 13 time=0 ms 64 bytes from 137.51.14.130: seq no 14 time=0 ms 64 bytes from 137.51.14.130: seq no 15 time=0 ms 64 bytes from 137.51.14.130: seq no 16 time=0 ms 64 bytes from 137.51.14.130: seq no 17 time=0 ms 64 bytes from 137.51.14.130: seq no 18 time=0 ms 64 bytes from 137.51.14.130: seq no 19 time=0 ms 64 bytes from 137.51.14.130: seq no 20 time=0 ms 64 bytes from 137.51.14.130: seq no 21 time=0 ms 64 bytes from 137.51.14.130: seq no 22 time=0 ms 64 bytes from 137.51.14.130: seq no 23 time=0 ms 64 bytes from 137.51.14.130: seq no 24 time=0 ms 64 bytes from 137.51.14.130: seq no 25 time=0 ms 64 bytes from 137.51.14.130: seq no 26 time=0 ms 64 bytes from 137.51.14.130: seq no 27 time=0 ms 64 bytes from 137.51.14.130: seq no 28 time=0 ms 64 bytes from 137.51.14.130: seq no 29 time=0 ms 64 bytes from 137.51.14.130: seq no 30 time=0 ms 64 bytes from 137.51.14.130: seq no 31 time=0 ms 32 packets transmitted, 32 packets received, 0% packet loss round-trip min/avg/max = 0/0.0/0 ms C:\Bin> Having trouble getting Java to run on the Linux box, so I could not complete the echo test from the Linux host to the WinXP client. -----Original Message----- From: Harold L Hunt II [mailto:huntharo@msu.edu] Sent: Monday, November 17, 2003 4:41 PM To: cygwin-xfree@cygwin.com Subject: Re: XWin works on Win2K but not on some WinXP clients [FIXED] Kirk, Well then, I suppose the next step would be to do a "telinit 3" (to stop gdm), then edit xinetd conf file to run "echo" on UDP port 177, restart xinetd, then use that udp echo client that we found to test if echo works from the Windows XP machine plugged into its normal jack to gaia plugged into its normal jack. We know that echo worked on UDP port 7, but proving that it does or does not work on UDP port 177 would tell us if they know what they are talking about :) Harold Woellert, Kirk D. wrote: > I aksed corporate IS if they were doing an port blocking/filtering within > our LAN. They replied: > > "There should be no port blocking within the corp. LAN. - only in/out to the > Internet and in/out of DMZs." > > > > -----Original Message----- > From: Harold L Hunt II [mailto:huntharo@msu.edu] > Sent: Monday, November 17, 2003 10:45 AM > To: cygwin-xfree@cygwin.com > Subject: Re: XWin works on Win2K but not on some WinXP clients [FIXED] > > > Kirk Woellert's problem with XP clients has been fixed, sort of. > > I talked to him on the phone for a few hours on Friday and walked him > through some debugging. > > > Here is what we found out: > > 1) We could ssh from XP to Linux (TCP protocol). > > 2) We could tunnel X apps over ssh from the Linux box to display on the > XP box (TCP protocol). > > 3) We could natively display X apps by exporting DISPLAY on Linux box, > pointed to XP box (TCP protocol). > > 4) We could not (nor could X-Win32) get an XDMCP login on the XP box for > the Linux box (UDP protocol). > > 5) We could run the echo service on the Linux box on port 7 and use a > Java echo client for UDP to verify that UDP to Linux box worked (UDP > protocol). > > 6) It was revealed that there are really two parts of the network here. > Not much is known about whether port blocking is in effect between the > two parts. > > 7) Removing the troubled hosts from the network and hooking them to a > stand-alone hub with assigned IP addresses allowed XDMCP to work. > > 8) We thus confirmed in #5 that UDP was not blocked in general, but #7 > indicates that UDP port 177 is blocked between the segments. It turns > out that all of the Windows 2000 machines were on one "segment", while > the Windows XP machines were on another "segment". The problem was not > the OS, it was that one segment has UDP port 177 blocked. > > > Thus, we determined that the problem is in the network that the machines > are attached to; this may or may not be by design. In any case, it > isn't a problem with Cygwin/X. :) > > Harold From huntharo@msu.edu Tue Nov 18 04:57:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Tue, 18 Nov 2003 04:57:00 -0000 Subject: Updated: XFree86-bin-4.3.0-8, XFree86-etc-4.3.0-6, XFree86-fsrv-4.3.0-6, XFree86-prog-4.3.0-11, XFree86-xserv-4.3.0-23, XFree86-[nest,prt,vfb]-4.3.0-5 Message-ID: <3FB9A69B.1070602@msu.edu> The following packages have been updated in the Cygwin distribution: *** XFree86-bin-4.3.0-8 *** XFree86-etc-4.3.0-6 *** XFree86-fsrv-4.3.0-6 *** XFree86-nest-4.3.0-5 *** XFree86-prog-4.3.0-11 *** XFree86-prt-4.3.0-5 *** XFree86-vfb-4.3.0-5 *** XFree86-xserv-4.3.0-23 Changes ======= 1) General - Recompile all libraries and executables against fixed Xaw and Xt libraries. Enabled OS/2-style fix for VendorShell and vendorShellWidgetClass. (Harold L Hunt II) 2) xserv - winkeybd.c/winKeybdProc () - Check xkbi pointer for NULL. Fixes crash when XKB was disabled with ``-kb''. (Alexander Gottwald) 3) xserv - winconfig.c/winConfigKeyboard () - Read the AutoRepeat option from the configfile. (Alexander Gottwald) 4) xserv - winkeybd.c/winKeybdProc () - Initialize the XKB input layer with the AutoRepeat options from the configfile. (Alexander Gottwald) -- Harold Hunt To update your installation, click on the "Install Cygwin now" link on the http://cygwin.com/ web page. This downloads setup.exe to your system. Once you've downloaded setup.exe, run it and select "XFree86" and then click on the appropriate field until the above announced version number appears if it is not displayed already. If your mirror doesn't yet have the latest version of this package after 24 hours, you can either continue to wait for that site to be updated or you can try to find another mirror. Please send questions or comments to the Cygwin/XFree86 mailing list at: cygwin-xfree@cygwin.com If you want to subscribe go to: http://cygwin.com/ml/cygwin-xfree/ I would appreciate if you would use this mailing list rather than emailing me directly. This includes ideas and comments about the setup utility or Cygwin/XFree86 in general. If you want to make a point or ask a question the Cygwin/XFree86 mailing list is the appropriate place. From huntharo@msu.edu Tue Nov 18 05:19:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Tue, 18 Nov 2003 05:19:00 -0000 Subject: Can't type in login window via XDMCP In-Reply-To: <658B168FF59ED4119FC200508BF354BB0AF7A25B@exgate.tek.com> References: <658B168FF59ED4119FC200508BF354BB0AF7A25B@exgate.tek.com> Message-ID: <3FB9ABC6.4020601@msu.edu> Jae, jae.ellers@exgate.tek.com wrote: > Hi folks, > First thanks to all who contribute. Xfree on Cygwin has been great. > However, I was seeing 2Gb+ XWin.log files and felt I needed to update. SO I > updated today and now I can't login via XDMCP. Here's the command line I > use: > > c:\cygwin\usr\X11R6\bin\xwin -query zephyr.mydomain.com -from 192.168.1.4 > > The system I'm logging into is a RH ES2.1 server. I've been using the same > setup for months now. > > The problem is that I can't type in the login window. Nothing appears. The > only thing I can see getting thru is the Caps Lock, which I find very > strange. > > Even if I start xwin and then twm and an xterm I can't type in the xterm. > > I do see a message in /tmp/XWin.log: > (EE) Unable to locate/open config file > InitOutput - Error reading config file I am not sure I understand your problem. You are, of course, clicking in the text boxes where you type the user name and password, right? What sort of OS is the remote machine running? > Do I need a config file? I haven't used one before. No, you do not need a config file. > I found this message: > http://sources.redhat.com/ml/cygwin-xfree/2003-10/msg00303.html and tested > http://www.msu.edu/~huntharo/xwin/devel/server/XWin-4.3.0-20-Test01.exe.bz2 > and I can login. So it looks like the problem is in the new WaitFor.c code. Actually, I really doubt it is a problem with WaitFor.c. The changes were made in 4.3.0-16 on or around 2003/10/04: http://xfree86.cygwin.com/devel/server/changelog.html The keyboard focus problem referred to in that mailing list message was actually due to problems with shared Xt/Xaw/Xaw6/LessTif libraries. That has just now been fixed. You could try updating your installation tomorrow (when the new packages hit the mirrors) and see if it fixes your problem; it might. Harold From jscheef@yahoo.com Tue Nov 18 05:22:00 2003 From: jscheef@yahoo.com (Jim Scheef) Date: Tue, 18 Nov 2003 05:22:00 -0000 Subject: Cygwin XFree ignores the keyboard In-Reply-To: Message-ID: <20031118052243.20820.qmail@web41501.mail.yahoo.com> Edgar, No, I never got a reply. I have been monitoring the list to see if a solution might come along. Recently there has been some traffic about "no keyboard" so I'm planning to try the lastest update to see if it fixes the problem. Jim (not Jeff) --- Edgar_Camacho@oxy.com wrote: > Jeff, > > You posted the below issue in the Xfree mail list. I am experiencing the > same problem. Did you figure it out ? Or Did you get a response from the > user community ? If so, please drop me a line. > > Thanks. > > Edgar Camacho > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > Cygwin XFree ignores the keyboard > * From: Jim Scheef > * To: cygwin-xfree at cygwin dot com > * Date: Sun, 12 Oct 2003 12:34:38 -0700 (PDT) > * Subject: Cygwin XFree ignores the keyboard > * Reply-to: cygwin-xfree at cygwin dot com > > Hello everyone, > > I have been using Cygwin XFree86 for some time on a Winbook X1 running > XP > Pro, and it was working great with several Linux machines. A couple of > months > back it started to ignore the keyboard. IOW, I type and nothing happens > in > any Xwindows frame which makes things rather difficult. The mouse still > works. > > First I tried doing a 'reinstall' to no effect. Then I uninstalled > everything > and did a complete reinstall with the latest versions of Cygwin and > Xfree86. > The reinstall seemed to go well but I saw one script error reporting a > 'null' > value somewhere. At the time, there was no way to know (that I knew of) > to > see exactly which package gave the error so I ignored it and went on. > > This issue is not addressed in the FAQ so now I turn to you. All help > will be > greatly appreciated. > > Jim > > > __________________________________ Do you Yahoo!? Protect your identity with Yahoo! Mail AddressGuard http://antispam.yahoo.com/whatsnewfree From huntharo@msu.edu Tue Nov 18 05:28:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Tue, 18 Nov 2003 05:28:00 -0000 Subject: Cygwin XFree ignores the keyboard In-Reply-To: <20031118052243.20820.qmail@web41501.mail.yahoo.com> References: <20031118052243.20820.qmail@web41501.mail.yahoo.com> Message-ID: <3FB9ADFA.8050802@msu.edu> Jim, Jim Scheef wrote: > Edgar, > > No, I never got a reply. I have been monitoring the list to see if a solution > might come along. Recently there has been some traffic about "no keyboard" so > I'm planning to try the lastest update to see if it fixes the problem. You have to move the mouse into the window that you want to type in. It is a problem with the new shared Xt lib that we started distributing a month or two ago. That problem has been fixed with the latest release announcement I sent on 2003-11-17. Please understand that I do not respond to duplicate questions if I am busy... it is better to spend the time fixing the problems. Often, if I do not reply, no one does, so it is my fault that you didn't get a reply. Sorry about that. In the future, just check the mailing list archives at the following link to see if your problem has already been reported. If it has, then you might not get a reply if you post. http://cygwin.com/ml/cygwin-xfree/ Thanks for testing, Harold From huntharo@msu.edu Tue Nov 18 05:29:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Tue, 18 Nov 2003 05:29:00 -0000 Subject: Updated: XFree86-bin-4.3.0-8, XFree86-etc-4.3.0-6, XFree86-fsrv-4.3.0-6, XFree86-prog-4.3.0-11, XFree86-xserv-4.3.0-23, XFree86-[nest,prt,vfb]-4.3.0-5 In-Reply-To: <3FB9A69B.1070602@msu.edu> References: <3FB9A69B.1070602@msu.edu> Message-ID: <3FB9AE20.4030606@msu.edu> Oops. I remember people were asking this to be sent to only the announce mailing list. I forgot. Will try next time. Harold Harold L Hunt II wrote: > The following packages have been updated in the Cygwin distribution: > > *** XFree86-bin-4.3.0-8 > *** XFree86-etc-4.3.0-6 > *** XFree86-fsrv-4.3.0-6 > *** XFree86-nest-4.3.0-5 > *** XFree86-prog-4.3.0-11 > *** XFree86-prt-4.3.0-5 > *** XFree86-vfb-4.3.0-5 > *** XFree86-xserv-4.3.0-23 > > > Changes > ======= > > 1) General - Recompile all libraries and executables against fixed Xaw > and Xt libraries. Enabled OS/2-style fix for VendorShell and > vendorShellWidgetClass. (Harold L Hunt II) > > 2) xserv - winkeybd.c/winKeybdProc () - Check xkbi pointer for NULL. Fixes > crash when XKB was disabled with ``-kb''. (Alexander Gottwald) > > 3) xserv - winconfig.c/winConfigKeyboard () - Read the AutoRepeat option > from the configfile. (Alexander Gottwald) > > 4) xserv - winkeybd.c/winKeybdProc () - Initialize the XKB input layer > with the AutoRepeat options from the configfile. (Alexander Gottwald) > From huntharo@msu.edu Tue Nov 18 05:30:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Tue, 18 Nov 2003 05:30:00 -0000 Subject: Xaw - Problems with keyboard focus easy to fix (Doh!) and Re: no key input In-Reply-To: <200311172157.hAHLvgE01721@chamonix.straightrunning.com> References: <200311172157.hAHLvgE01721@chamonix.straightrunning.com> Message-ID: <3FB9AE64.7010901@msu.edu> Colin, Colin Harrison wrote: > Hi, > > I recompiled my entire xc tree (shared libs Xaw, Xt, Xmu) with your Vendor.c > Xaw patch. > Keyboard focus now works for me when mouse pointer not in cygwin/xfree xterm > window. Thanks for the sanity check. It is good to have someone else doing a smoke test on patches such as this. Your quick test allowed me to proceed quickly to a release. Thanks, Harold From sb@dod.no Tue Nov 18 09:51:00 2003 From: sb@dod.no (Steinar Bang) Date: Tue, 18 Nov 2003 09:51:00 -0000 Subject: Alt key isn't Meta in Cygwin xterm (Norwegian keyboard) References: <87llqktqn1.fsf@home.lan> Message-ID: <87k75yt375.fsf@home.lan> >>>>> Alexander Gottwald : > Hm, xev reports Alt+b but the bash gets ??. Must be a problem with xterm. > -> Press Control and click into the xterm window. You'll get a menu. > Select "Meta Sends Escape" from the menu. This menu entry was previously unselected. I selected it, and the behaviour remains unchanged. Ie. Alt-b still generates ??. The results from xev when pressing Alt-b, are: KeyPress event, serial 17, synthetic NO, window 0x1400001, root 0x3a, subw 0x0, time 944035290, (120,91), root:(267,161), state 0x0, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES, XLookupString gives 0 bytes: "" KeyPress event, serial 22, synthetic NO, window 0x1400001, root 0x3a, subw 0x0, time 944036182, (120,91), root:(267,161), state 0x8, keycode 56 (keysym 0x62, b), same_screen YES, XLookupString gives 1 bytes: "b" From dirk.goethals@alcatel.be Tue Nov 18 13:03:00 2003 From: dirk.goethals@alcatel.be (dirk.goethals@alcatel.be) Date: Tue, 18 Nov 2003 13:03:00 -0000 Subject: DDD segmentation error due to "Xt error" In-Reply-To: <3FB80677.8090004@alcatel.be> References: <3FB80677.8090004@alcatel.be> Message-ID: <3FBA1885.4030004@alcatel.be> (changed subject, originally: "Re: DDD Compilation Fails using GCC 3.3.1") It's the latest, according to cygwin setup. here the list (extracted with "cygcheck -cd" ): XFree86-base 4.3.0-1 XFree86-bin 4.3.0-5 XFree86-bin-icons 4.3.0-5 XFree86-doc 4.3.0-1 XFree86-etc 4.3.0-3 XFree86-f100 4.2.0-3 XFree86-fcyr 4.2.0-3 XFree86-fenc 4.2.0-3 XFree86-fnts 4.2.0-3 XFree86-fscl 4.2.0-3 XFree86-fsrv 4.3.0-4 XFree86-html 4.3.0-1 XFree86-jdoc 4.3.0-1 XFree86-lib 4.3.0-1 XFree86-lib-compat 4.3.0-1 XFree86-man 4.3.0-2 XFree86-nest 4.3.0-3 XFree86-prog 4.3.0-8 XFree86-prt 4.3.0-3 XFree86-ps 4.3.0-1 XFree86-startup-scripts 4.2.0-5 XFree86-vfb 4.3.0-3 XFree86-xserv 4.3.0-20 XFree86-xwinclip 4.3.0-1 lesstif 0.93.91-2 > On Mon, 17 Nov 2003 dirk.goethals@alcatel.be wrote: > >> Ihe same problem with ddd 3.3.8 and GCC 3.3.1. >> I was able to compile ddd with GCC 3.2.3, but >> when launching ddd I gat following problem: >> (btw ddd --help works fine) >> >> >> >> Warning: XmPrimitive ClassInitialize: XmeTraitSet failed >> Error: attempt to add non-widget child "DropSiteManager" to parent "ddd" >> which supports only widgets >> Xt error (attempt to add non-widget child "DropSiteManager" to parent >> "ddd" which supports only widgets). >> <<...>> >> DDD 3.3.8 (i686-pc-cygwin) gets `Segmentation fault' signal >> << >> > This is an Xfree86 issue. Redirecting to the proper list > (cygwin-xfree@cygwin.com). > > The error above was caused by the transition to a shared libXt/lesstif. > Please make sure your Xfree86 packages and lesstif are up to date. > > -- > Brian Ford > Senior Realtime Software Engineer > VITAL - Visual Simulation Systems > FlightSafety International > Phone: 314-551-8460 > Fax: 314-551-8444 From hans.dekker.ext@juntadeandalucia.es Tue Nov 18 13:53:00 2003 From: hans.dekker.ext@juntadeandalucia.es (Hans Dekker) Date: Tue, 18 Nov 2003 13:53:00 -0000 Subject: Alt key isn't Meta in Cygwin xterm (Norwegian keyboard) References: <87llqktqn1.fsf@home.lan> <87k75yt375.fsf@home.lan> Message-ID: <3FBA2442.8060206@juntadeandalucia.es> Hi Steinar and others, I experienced something similar: My RightAlt (Altgr) wasn't working well, a resolution to get the key working was to change the file /etc/X11/xkb/symbols/pc/ and define your key function there. The xev program now showed the is the right translation of the Alt key, but the keyboard map doesn't show definitions for RightAlt. Change to es file: key { type[Group1]="TWO_LEVEL", [ Mode_switch, Multi_key ] }; modifier_map Mod5 { }; See also the mail in cygwin-xfree list of 13/11/03 14:51 Maybe it helps in your case. Hans. Steinar Bang escribi??: >>>>>>Alexander Gottwald : >>>>> > >>Hm, xev reports Alt+b but the bash gets ??. Must be a problem with xterm. >>-> Press Control and click into the xterm window. You'll get a menu. >>Select "Meta Sends Escape" from the menu. > > > This menu entry was previously unselected. I selected it, and the > behaviour remains unchanged. Ie. Alt-b still generates ??. > > The results from xev when pressing Alt-b, are: > > KeyPress event, serial 17, synthetic NO, window 0x1400001, > root 0x3a, subw 0x0, time 944035290, (120,91), root:(267,161), > state 0x0, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES, > XLookupString gives 0 bytes: "" > > KeyPress event, serial 22, synthetic NO, window 0x1400001, > root 0x3a, subw 0x0, time 944036182, (120,91), root:(267,161), > state 0x8, keycode 56 (keysym 0x62, b), same_screen YES, > XLookupString gives 1 bytes: "b" > > > . > From huntharo@msu.edu Tue Nov 18 17:58:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Tue, 18 Nov 2003 17:58:00 -0000 Subject: DDD segmentation error due to "Xt error" In-Reply-To: <3FBA1885.4030004@alcatel.be> References: <3FB80677.8090004@alcatel.be> <3FBA1885.4030004@alcatel.be> Message-ID: <3FBA5DCD.4060200@msu.edu> Dirk, dirk.goethals@alcatel.be wrote: > > (changed subject, originally: "Re: DDD Compilation Fails using GCC 3.3.1") > > It's the latest, according to cygwin setup. > here the list (extracted with "cygcheck -cd" ): You need a different mirror. You certainly do not have the latest packages. For example, a newer version of most of those packages was released on October 29th. > XFree86-bin 4.3.0-5 XFree86-bin-4.3.0-6 was released here: http://cygwin.com/ml/cygwin-xfree-announce/2003-10/msg00017.html Furthermore, several releases of most of the packages have been made between the versions that you have and the versions that were released yesterday: http://cygwin.com/ml/cygwin-xfree-announce/2003-11/msg00003.html A lot of the changes made in the last two months were related to the new shared Xt library. Please, find a new mirror, update your installation, confirm that you have the versions listed in the second email above, and try the compilation again. Harold From jae.ellers@exgate.tek.com Tue Nov 18 19:14:00 2003 From: jae.ellers@exgate.tek.com (jae.ellers@exgate.tek.com) Date: Tue, 18 Nov 2003 19:14:00 -0000 Subject: Can't type in login window via XDMCP Message-ID: <658B168FF59ED4119FC200508BF354BB0AF7A2BC@exgate.tek.com> Harold, >Jae, I am not sure I understand your problem. You are, of course, clicking in >the text boxes where you type the user name and password, right? What sort of >OS is the remote machine running? Yes, I'm clicking in the boxes. As I said, the remote system is running RedHat ES (Enterprise Server) 2.1, analogous to approx RH 8.0 I think. My system is running WXP_SP1. You're right in that the WaitFor.c wasn't the problem. Here's the problem. I start X by running: xwin -query I get the XDMCP login. I can operate all controls with the mouse, but nothing shows in the login or password windows when I type. However, when I hit the capslock key, the login box tells me I have it pressed. I may try wiping things out and starting over. It sounds to me like there's a conflict in versions somewhere, but how to tell? Thanks ---------------------------------------------------------------------- Jae Ellers Tektronix, Inc. jae.ellers@tek.com From huntharo@msu.edu Tue Nov 18 19:25:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Tue, 18 Nov 2003 19:25:00 -0000 Subject: Can't type in login window via XDMCP In-Reply-To: <658B168FF59ED4119FC200508BF354BB0AF7A2BC@exgate.tek.com> References: <658B168FF59ED4119FC200508BF354BB0AF7A2BC@exgate.tek.com> Message-ID: <3FBA7212.7060800@msu.edu> Jae, Try clicking in the user name box, leaving the mouse over it, typing your user name, clicking in the password box, leaving the mouse over it, type your password, then click the Login button. See if it logs in :) If it logs in, then there is something wacky with output, not input. It would be nice to know which is really the problem here. Is everything using US keyboard layouts and English as the language? If not, then our non-U.S. experts will need to be consulted for further information. Harold jae.ellers@exgate.tek.com wrote: > Harold, > >>Jae, I am not sure I understand your problem. You are, of course, clicking > > in >the text boxes where you type the user name and password, right? What > sort of >OS is the remote machine running? > > Yes, I'm clicking in the boxes. As I said, the remote system is running > RedHat ES (Enterprise Server) 2.1, analogous to approx RH 8.0 I think. My > system is running WXP_SP1. > > You're right in that the WaitFor.c wasn't the problem. > > Here's the problem. I start X by running: > xwin -query > > I get the XDMCP login. I can operate all controls with the mouse, but > nothing shows in the login or password windows when I type. However, when I > hit the capslock key, the login box tells me I have it pressed. > > I may try wiping things out and starting over. It sounds to me like there's > a conflict in versions somewhere, but how to tell? > > Thanks > ---------------------------------------------------------------------- > Jae Ellers Tektronix, Inc. > jae.ellers@tek.com > From Dr.Volker.Zell@oracle.com Tue Nov 18 19:45:00 2003 From: Dr.Volker.Zell@oracle.com (Dr. Volker Zell) Date: Tue, 18 Nov 2003 19:45:00 -0000 Subject: Updated: XFree86-bin-4.3.0-8, XFree86-etc-4.3.0-6, XFree86-fsrv-4.3.0-6, XFree86-prog-4.3.0-11, XFree86-xserv-4.3.0-23, XFree86-[nest,prt,vfb]-4.3.0-5 In-Reply-To: <3FB9A69B.1070602@msu.edu> (Harold L. Hunt, II's message of "Mon, 17 Nov 2003 23:56:59 -0500") References: <3FB9A69B.1070602@msu.edu> Message-ID: <87brr9o41e.fsf@vzell-de.de.oracle.com> >>>>> "Harold" == Harold L Hunt, writes: Harold> The following packages have been updated in the Cygwin distribution: Harold> *** XFree86-fsrv-4.3.0-6 It's missing its man-page again. Harold> *** XFree86-prog-4.3.0-11 I get an additional symbolic link /usr/X11R6/include/X11/X11 --> /usr/X11R6/include/X11 after the postinstall script is run. I would recommend changing the postinstall script to: --------------------- cut ----------------------------------- #!/bin/sh # Create an empty host.def if one doesn't exist already touch /usr/X11R6/lib/X11/config/host.def # Create a link in /usr/include to the X11 includes directory if [ ! -L /usr/include/X11 ] then ln -sf /usr/X11R6/include/X11 /usr/include/X11 fi --------------------- cut ----------------------------------- Ciao Volker From huntharo@msu.edu Tue Nov 18 20:25:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Tue, 18 Nov 2003 20:25:00 -0000 Subject: XWin works on Win2K but not on some WinXP clients [FIXED] In-Reply-To: References: Message-ID: <3FBA802C.7030500@msu.edu> So echo on UDP port 177 works fine. This is not good. There must be something else in the gdm conf on the linux box that explicitly denies gdm connections from the Windows XP machine's IP addresses, since it worked fine when using 10.0.0.x addresses. Anyway you can change the IP of the XP machine to one not previously used as a test? Harold Woellert, Kirk D. wrote: > 1. Edited the echo-upd file in the xinetd.d folder. Changed the default port > from "7" to "177"... > > [root@gaia xinetd.d]# cat echo-udp > # default: off > # description: An xinetd internal service which echo's characters back to > clients. \ > # This is the udp version. > service echo > { > disable = no > type = INTERNAL UNLISTED > id = echo-dgram > socket_type = dgram > protocol = udp > user = root > wait = yes > port = 177 > } > [root@gaia xinetd.d]# > > 2. Did a grep just to ensure gdm was not gonna respond to my upd packets... > > [root@gaia xinetd.d]# ps -ef |grep xdm > root 2328 1912 0 18:12 pts/0 00:00:00 grep xdm > [root@gaia xinetd.d]# > > 3. Ran a upd echo test from the WinXP client to the Linux box using a Java > echo client.... > > C:\Bin>java -jar UDPEchoClient.jar 137.51.14.130:177 > 64 bytes from 137.51.14.130: seq no 0 time=0 ms > 64 bytes from 137.51.14.130: seq no 1 time=0 ms > 64 bytes from 137.51.14.130: seq no 2 time=0 ms > 64 bytes from 137.51.14.130: seq no 3 time=0 ms > 64 bytes from 137.51.14.130: seq no 4 time=0 ms > 64 bytes from 137.51.14.130: seq no 5 time=0 ms > 64 bytes from 137.51.14.130: seq no 6 time=0 ms > 64 bytes from 137.51.14.130: seq no 7 time=0 ms > 64 bytes from 137.51.14.130: seq no 8 time=0 ms > 64 bytes from 137.51.14.130: seq no 9 time=0 ms > 64 bytes from 137.51.14.130: seq no 10 time=0 ms > 64 bytes from 137.51.14.130: seq no 11 time=0 ms > 64 bytes from 137.51.14.130: seq no 12 time=0 ms > 64 bytes from 137.51.14.130: seq no 13 time=0 ms > 64 bytes from 137.51.14.130: seq no 14 time=0 ms > 64 bytes from 137.51.14.130: seq no 15 time=0 ms > 64 bytes from 137.51.14.130: seq no 16 time=0 ms > 64 bytes from 137.51.14.130: seq no 17 time=0 ms > 64 bytes from 137.51.14.130: seq no 18 time=0 ms > 64 bytes from 137.51.14.130: seq no 19 time=0 ms > 64 bytes from 137.51.14.130: seq no 20 time=0 ms > 64 bytes from 137.51.14.130: seq no 21 time=0 ms > 64 bytes from 137.51.14.130: seq no 22 time=0 ms > 64 bytes from 137.51.14.130: seq no 23 time=0 ms > 64 bytes from 137.51.14.130: seq no 24 time=0 ms > 64 bytes from 137.51.14.130: seq no 25 time=0 ms > 64 bytes from 137.51.14.130: seq no 26 time=0 ms > 64 bytes from 137.51.14.130: seq no 27 time=0 ms > 64 bytes from 137.51.14.130: seq no 28 time=0 ms > 64 bytes from 137.51.14.130: seq no 29 time=0 ms > 64 bytes from 137.51.14.130: seq no 30 time=0 ms > 64 bytes from 137.51.14.130: seq no 31 time=0 ms > 32 packets transmitted, 32 packets received, 0% packet loss > round-trip min/avg/max = 0/0.0/0 ms > > C:\Bin> > > Having trouble getting Java to run on the Linux box, so I could not complete > the echo test from the Linux host to the WinXP client. > > -----Original Message----- > From: Harold L Hunt II [mailto:huntharo@msu.edu] > Sent: Monday, November 17, 2003 4:41 PM > To: cygwin-xfree@cygwin.com > Subject: Re: XWin works on Win2K but not on some WinXP clients [FIXED] > > > Kirk, > > Well then, I suppose the next step would be to do a "telinit 3" (to stop > gdm), then edit xinetd conf file to run "echo" on UDP port 177, restart > xinetd, then use that udp echo client that we found to test if echo > works from the Windows XP machine plugged into its normal jack to gaia > plugged into its normal jack. We know that echo worked on UDP port 7, > but proving that it does or does not work on UDP port 177 would tell us > if they know what they are talking about :) > > Harold > > Woellert, Kirk D. wrote: > > >>I aksed corporate IS if they were doing an port blocking/filtering within >>our LAN. They replied: >> >>"There should be no port blocking within the corp. LAN. - only in/out to > > the > >>Internet and in/out of DMZs." >> >> >> >>-----Original Message----- >>From: Harold L Hunt II [mailto:huntharo@msu.edu] >>Sent: Monday, November 17, 2003 10:45 AM >>To: cygwin-xfree@cygwin.com >>Subject: Re: XWin works on Win2K but not on some WinXP clients [FIXED] >> >> >>Kirk Woellert's problem with XP clients has been fixed, sort of. >> >>I talked to him on the phone for a few hours on Friday and walked him >>through some debugging. >> >> >>Here is what we found out: >> >>1) We could ssh from XP to Linux (TCP protocol). >> >>2) We could tunnel X apps over ssh from the Linux box to display on the >>XP box (TCP protocol). >> >>3) We could natively display X apps by exporting DISPLAY on Linux box, >>pointed to XP box (TCP protocol). >> >>4) We could not (nor could X-Win32) get an XDMCP login on the XP box for >>the Linux box (UDP protocol). >> >>5) We could run the echo service on the Linux box on port 7 and use a >>Java echo client for UDP to verify that UDP to Linux box worked (UDP >>protocol). >> >>6) It was revealed that there are really two parts of the network here. >> Not much is known about whether port blocking is in effect between the >>two parts. >> >>7) Removing the troubled hosts from the network and hooking them to a >>stand-alone hub with assigned IP addresses allowed XDMCP to work. >> >>8) We thus confirmed in #5 that UDP was not blocked in general, but #7 >>indicates that UDP port 177 is blocked between the segments. It turns >>out that all of the Windows 2000 machines were on one "segment", while >>the Windows XP machines were on another "segment". The problem was not >>the OS, it was that one segment has UDP port 177 blocked. >> >> >>Thus, we determined that the problem is in the network that the machines >>are attached to; this may or may not be by design. In any case, it >>isn't a problem with Cygwin/X. :) >> >>Harold From jay@JaySmith.com Tue Nov 18 20:29:00 2003 From: jay@JaySmith.com (Jay Smith) Date: Tue, 18 Nov 2003 20:29:00 -0000 Subject: Can't type in login window via XDMCP In-Reply-To: <658B168FF59ED4119FC200508BF354BB0AF7A25B@exgate.tek.com> References: <658B168FF59ED4119FC200508BF354BB0AF7A25B@exgate.tek.com> Message-ID: <3FBA809E.4000502@JaySmith.com> Jae, I have been told on this list that it "shouldn't" (or was it "doesn't"?) make a difference, however, when logging into an RH8 box, I *had* to put the -query as the last element on the line. Try this to see if it makes any difference (you seem to be having somewhat different problems, thus I am not sure...) c:\cygwin\usr\X11R6\bin\xwin -from 192.168.1.4 -query zephyr.mydomain.com The other thing I wonder about is fonts. I am ignorant on the subject, but is there a chance that not all the fonts needed are being loaded (on either end?) Jay jae.ellers@exgate.tek.com said the following on 11/17/2003 02:13 PM: > Hi folks, > First thanks to all who contribute. Xfree on Cygwin has been great. > However, I was seeing 2Gb+ XWin.log files and felt I needed to update. SO I > updated today and now I can't login via XDMCP. Here's the command line I > use: > > c:\cygwin\usr\X11R6\bin\xwin -query zephyr.mydomain.com -from 192.168.1.4 > > The system I'm logging into is a RH ES2.1 server. I've been using the same > setup for months now. > > The problem is that I can't type in the login window. Nothing appears. The > only thing I can see getting thru is the Caps Lock, which I find very > strange. > > Even if I start xwin and then twm and an xterm I can't type in the xterm. > > I do see a message in /tmp/XWin.log: > (EE) Unable to locate/open config file > InitOutput - Error reading config file > > Do I need a config file? I haven't used one before. > > I found this message: > http://sources.redhat.com/ml/cygwin-xfree/2003-10/msg00303.html and tested > http://www.msu.edu/~huntharo/xwin/devel/server/XWin-4.3.0-20-Test01.exe.bz2 > and I can login. So it looks like the problem is in the new WaitFor.c code. > > Now I'm hung at a blank screen, though. > > Any help would be appreciated. I'm hosed for the time being. > > Thanks > ---------------------------------------------------------------------- > Jae Ellers Tektronix, Inc. > Jae dot ellers at tek dot com (503) 627-3622 -- Jay Smith e-mail: Jay@JaySmith.com mailto:Jay@JaySmith.com website: http://www.JaySmith.com Jay Smith & Associates P.O. Box 650 Snow Camp, NC 27349 USA Phone: Int+US+336-376-9991 Toll-Free Phone in US & Canada: 1-800-447-8267 Fax: Int+US+336-376-6750 From pechtcha@cs.nyu.edu Tue Nov 18 21:07:00 2003 From: pechtcha@cs.nyu.edu (Igor Pechtchanski) Date: Tue, 18 Nov 2003 21:07:00 -0000 Subject: XWin works on Win2K but not on some WinXP clients [FIXED] In-Reply-To: <3FBA802C.7030500@msu.edu> References: <3FBA802C.7030500@msu.edu> Message-ID: Kirk, Check /var/log/messages and see if there are any from gdm. This may be a DNS lookup issue (i.e., your XP machine is not registered in DNS, or registered, but not with the correct name). Confirm by "nslookup YOUR_IP" from the Linux machine. If it is a DNS issue, try adding your XP machine to /etc/hosts and restarting gdm ("kill -USR1 `cat /var/run/gdm.pid`"). Igor On Tue, 18 Nov 2003, Harold L Hunt II wrote: > So echo on UDP port 177 works fine. This is not good. There must be > something else in the gdm conf on the linux box that explicitly denies > gdm connections from the Windows XP machine's IP addresses, since it > worked fine when using 10.0.0.x addresses. Anyway you can change the IP > of the XP machine to one not previously used as a test? > > Harold > > Woellert, Kirk D. wrote: > > > 1. Edited the echo-upd file in the xinetd.d folder. Changed the default port > > from "7" to "177"... > > > > [root@gaia xinetd.d]# cat echo-udp > > # default: off > > # description: An xinetd internal service which echo's characters back to > > clients. \ > > # This is the udp version. > > service echo > > { > > disable = no > > type = INTERNAL UNLISTED > > id = echo-dgram > > socket_type = dgram > > protocol = udp > > user = root > > wait = yes > > port = 177 > > } > > [root@gaia xinetd.d]# > > > > 2. Did a grep just to ensure gdm was not gonna respond to my upd packets... > > > > [root@gaia xinetd.d]# ps -ef |grep xdm > > root 2328 1912 0 18:12 pts/0 00:00:00 grep xdm > > [root@gaia xinetd.d]# > > > > 3. Ran a upd echo test from the WinXP client to the Linux box using a Java > > echo client.... > > > > C:\Bin>java -jar UDPEchoClient.jar 137.51.14.130:177 > > 64 bytes from 137.51.14.130: seq no 0 time=0 ms > > 64 bytes from 137.51.14.130: seq no 1 time=0 ms > > 64 bytes from 137.51.14.130: seq no 2 time=0 ms > > 64 bytes from 137.51.14.130: seq no 3 time=0 ms > > 64 bytes from 137.51.14.130: seq no 4 time=0 ms > > 64 bytes from 137.51.14.130: seq no 5 time=0 ms > > 64 bytes from 137.51.14.130: seq no 6 time=0 ms > > 64 bytes from 137.51.14.130: seq no 7 time=0 ms > > 64 bytes from 137.51.14.130: seq no 8 time=0 ms > > 64 bytes from 137.51.14.130: seq no 9 time=0 ms > > 64 bytes from 137.51.14.130: seq no 10 time=0 ms > > 64 bytes from 137.51.14.130: seq no 11 time=0 ms > > 64 bytes from 137.51.14.130: seq no 12 time=0 ms > > 64 bytes from 137.51.14.130: seq no 13 time=0 ms > > 64 bytes from 137.51.14.130: seq no 14 time=0 ms > > 64 bytes from 137.51.14.130: seq no 15 time=0 ms > > 64 bytes from 137.51.14.130: seq no 16 time=0 ms > > 64 bytes from 137.51.14.130: seq no 17 time=0 ms > > 64 bytes from 137.51.14.130: seq no 18 time=0 ms > > 64 bytes from 137.51.14.130: seq no 19 time=0 ms > > 64 bytes from 137.51.14.130: seq no 20 time=0 ms > > 64 bytes from 137.51.14.130: seq no 21 time=0 ms > > 64 bytes from 137.51.14.130: seq no 22 time=0 ms > > 64 bytes from 137.51.14.130: seq no 23 time=0 ms > > 64 bytes from 137.51.14.130: seq no 24 time=0 ms > > 64 bytes from 137.51.14.130: seq no 25 time=0 ms > > 64 bytes from 137.51.14.130: seq no 26 time=0 ms > > 64 bytes from 137.51.14.130: seq no 27 time=0 ms > > 64 bytes from 137.51.14.130: seq no 28 time=0 ms > > 64 bytes from 137.51.14.130: seq no 29 time=0 ms > > 64 bytes from 137.51.14.130: seq no 30 time=0 ms > > 64 bytes from 137.51.14.130: seq no 31 time=0 ms > > 32 packets transmitted, 32 packets received, 0% packet loss > > round-trip min/avg/max = 0/0.0/0 ms > > > > C:\Bin> > > > > Having trouble getting Java to run on the Linux box, so I could not complete > > the echo test from the Linux host to the WinXP client. > > > > -----Original Message----- > > From: Harold L Hunt II [mailto:huntharo@msu.edu] > > Sent: Monday, November 17, 2003 4:41 PM > > To: cygwin-xfree@cygwin.com > > Subject: Re: XWin works on Win2K but not on some WinXP clients [FIXED] > > > > > > Kirk, > > > > Well then, I suppose the next step would be to do a "telinit 3" (to stop > > gdm), then edit xinetd conf file to run "echo" on UDP port 177, restart > > xinetd, then use that udp echo client that we found to test if echo > > works from the Windows XP machine plugged into its normal jack to gaia > > plugged into its normal jack. We know that echo worked on UDP port 7, > > but proving that it does or does not work on UDP port 177 would tell us > > if they know what they are talking about :) > > > > Harold > > > > Woellert, Kirk D. wrote: > > > > > >>I aksed corporate IS if they were doing an port blocking/filtering within > >>our LAN. They replied: > >> > >>"There should be no port blocking within the corp. LAN. - only in/out > >>to the Internet and in/out of DMZs." > >> > >> > >>-----Original Message----- > >>From: Harold L Hunt II [mailto:huntharo@msu.edu] > >>Sent: Monday, November 17, 2003 10:45 AM > >>To: cygwin-xfree@cygwin.com > >>Subject: Re: XWin works on Win2K but not on some WinXP clients [FIXED] > >> > >> > >>Kirk Woellert's problem with XP clients has been fixed, sort of. > >> > >>I talked to him on the phone for a few hours on Friday and walked him > >>through some debugging. > >> > >> > >>Here is what we found out: > >> > >>1) We could ssh from XP to Linux (TCP protocol). > >> > >>2) We could tunnel X apps over ssh from the Linux box to display on the > >>XP box (TCP protocol). > >> > >>3) We could natively display X apps by exporting DISPLAY on Linux box, > >>pointed to XP box (TCP protocol). > >> > >>4) We could not (nor could X-Win32) get an XDMCP login on the XP box for > >>the Linux box (UDP protocol). > >> > >>5) We could run the echo service on the Linux box on port 7 and use a > >>Java echo client for UDP to verify that UDP to Linux box worked (UDP > >>protocol). > >> > >>6) It was revealed that there are really two parts of the network here. > >> Not much is known about whether port blocking is in effect between the > >>two parts. > >> > >>7) Removing the troubled hosts from the network and hooking them to a > >>stand-alone hub with assigned IP addresses allowed XDMCP to work. > >> > >>8) We thus confirmed in #5 that UDP was not blocked in general, but #7 > >>indicates that UDP port 177 is blocked between the segments. It turns > >>out that all of the Windows 2000 machines were on one "segment", while > >>the Windows XP machines were on another "segment". The problem was not > >>the OS, it was that one segment has UDP port 177 blocked. > >> > >> > >>Thus, we determined that the problem is in the network that the machines > >>are attached to; this may or may not be by design. In any case, it > >>isn't a problem with Cygwin/X. :) > >> > >>Harold -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_ pechtcha@cs.nyu.edu ZZZzz /,`.-'`' -. ;-;;,_ igor@watson.ibm.com |,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 From zwin@users.sourceforge.net Tue Nov 18 21:32:00 2003 From: zwin@users.sourceforge.net (Zbynek Winkler) Date: Tue, 18 Nov 2003 21:32:00 -0000 Subject: Updated: XFree86-xserv-4.3.0-22 In-Reply-To: References: <1068549020528.tulitanssi.36802.w1Q4NRjiTPWoQQzb3m7sWA@luukku.com> <3FB0E0D5.7090505@msu.edu> <87ptfyvpbj.fsf@vzell-de.de.oracle.com> <3FB1123E.8090102@msu.edu> <87d6byvn9u.fsf@vzell-de.de.oracle.com> <87smktnyps.fsf@vzell-de.de.oracle.com> Message-ID: <3FBA8FE4.30902@users.sourceforge.net> Alexander Gottwald wrote: >Alexander Gottwald wrote: > > >>On Wed, 12 Nov 2003, Dr. Volker Zell wrote: >> >> >>No. The AutoRepeat option is not used yet. I'll change this. >> >> > >Done. > > As it happens, I was completely happy with the old behavior. Now it defaults to something else than I have set in the win32 environment. Could the default be (when no config file is found) the autorepeat that was before the change? Thus this upgrade would hit only the users who really want to customise it. Zbynek -- http://zw.matfyz.cz/ http://robotika.cz/ Faculty of Mathematics and Physics, Charles University, Prague, Czech Republic From huntharo@msu.edu Tue Nov 18 21:50:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Tue, 18 Nov 2003 21:50:00 -0000 Subject: Updated: XFree86-xserv-4.3.0-22 In-Reply-To: <3FBA8FE4.30902@users.sourceforge.net> References: <1068549020528.tulitanssi.36802.w1Q4NRjiTPWoQQzb3m7sWA@luukku.com> <3FB0E0D5.7090505@msu.edu> <87ptfyvpbj.fsf@vzell-de.de.oracle.com> <3FB1123E.8090102@msu.edu> <87d6byvn9u.fsf@vzell-de.de.oracle.com> <87smktnyps.fsf@vzell-de.de.oracle.com> <3FBA8FE4.30902@users.sourceforge.net> Message-ID: <3FBA9411.7010008@msu.edu> We were previously using two auto-repeat schemes at the same time: 1) xkb 2) Win32's auto repeat layer Convince me why it is good to have two layers handling auto repeat by default and I will accede to your request. Harold Zbynek Winkler wrote: > Alexander Gottwald wrote: > >> Alexander Gottwald wrote: >> >> >>> On Wed, 12 Nov 2003, Dr. Volker Zell wrote: >>> >>> No. The AutoRepeat option is not used yet. I'll change this. >>> >> >> >> Done. >> >> > As it happens, I was completely happy with the old behavior. Now it > defaults to something else than I have set in the win32 environment. > Could the default be (when no config file is found) the autorepeat that > was before the change? Thus this upgrade would hit only the users who > really want to customise it. > Zbynek > From zwin@users.sourceforge.net Tue Nov 18 22:22:00 2003 From: zwin@users.sourceforge.net (Zbynek Winkler) Date: Tue, 18 Nov 2003 22:22:00 -0000 Subject: Updated: XFree86-xserv-4.3.0-22 In-Reply-To: <3FBA9411.7010008@msu.edu> References: <1068549020528.tulitanssi.36802.w1Q4NRjiTPWoQQzb3m7sWA@luukku.com> <3FB0E0D5.7090505@msu.edu> <87ptfyvpbj.fsf@vzell-de.de.oracle.com> <3FB1123E.8090102@msu.edu> <87d6byvn9u.fsf@vzell-de.de.oracle.com> <87smktnyps.fsf@vzell-de.de.oracle.com> <3FBA8FE4.30902@users.sourceforge.net> <3FBA9411.7010008@msu.edu> Message-ID: <3FBA9BA6.3050307@users.sourceforge.net> I am not sure I know how the system worked internaly and I would cetrainly make no requests in that matter. I was just trying to point out the user point of view. You are (probably) saying that you have improved the software internaly (which is always good). However this improvement changed the original default behavior in such a way that in order to get it back I am going to have to browse the net for some XF86Config-4 file only to set it to same value I was perfectly happy with before I did the upgrade. Isn't it weird? And I know this will fix the problem only because I happend to subscribe a week ago to this list. Before that I didn't even know there was such an option. Could you make us all happy and use the win32 default unless told otherwise instead of pulling one out of thin air? Does it sound reasonable? We are talking here only about two numbers. I don't mean to be pain in the ... but I really think it is more logical to do it this way. Would it break anything? Zbynek Harold L Hunt II wrote: > We were previously using two auto-repeat schemes at the same time: > > 1) xkb > > 2) Win32's auto repeat layer > > Convince me why it is good to have two layers handling auto repeat by > default and I will accede to your request. > > Harold > > Zbynek Winkler wrote: > >> Alexander Gottwald wrote: >> >>> Alexander Gottwald wrote: >>> >>> >>>> On Wed, 12 Nov 2003, Dr. Volker Zell wrote: >>>> No. The AutoRepeat option is not used yet. I'll change this. >>>> >>> >>> >>> >>> Done. >>> >>> >> As it happens, I was completely happy with the old behavior. Now it >> defaults to something else than I have set in the win32 environment. >> Could the default be (when no config file is found) the autorepeat >> that was before the change? Thus this upgrade would hit only the >> users who really want to customise it. >> Zbynek >> -- http://zw.matfyz.cz/ http://robotika.cz/ Faculty of Mathematics and Physics, Charles University, Prague, Czech Republic From devzero@web.de Wed Nov 19 01:53:00 2003 From: devzero@web.de (roland@webde) Date: Wed, 19 Nov 2003 01:53:00 -0000 Subject: interface bindings of x-server References: <038f01c3ae12$35ca4a80$2000000a@schlepptopp> <3FBA82CC.6050500@msu.edu> Message-ID: <051801c3ae40$8e170880$2000000a@schlepptopp> hi ! i`d like to continue a discussion thread some miles away from xfree86.org ;) if you are security aware person or network/system-administrator with interest regarding "multi homing issues" related to X you should read this thread because i`d like comments from you. this thread shouldn`t be of any interest to the "ordinary X-desktop user". the thread: http://marc.theaimsgroup.com/?l=xfree86&m=106900960326385&w=2 Keith, could you put this (being able to specify the interface bindings of the xserver on the commandline) as a feature request on http://www.freedesktop.org/Software/XserverWishlist if you find this feature request useful ? i registerd a wiki account, but logging in doesn`t seem to work for me. regards roland > > ps: > > perhaps you could give some personal opinion to my thoughs regarding > >interface bindings of X-Server. Perhaps I should have adressed my > >comments about the xfree86 network interface bindings issue directly > >to cygwin/xfree86 ML because it was nomachine`s re-distributed > >cygwin/xwin.exe which made me recognize it. > > Please send this to cygwin-xfree@cygwin.com for further input. I can't > vouch for nomachine's version of XWin.exe... in fact, I was not aware > that they were distributing their own version. devel@xfree86.org would > not be the place to ask this question From keithp@keithp.com Wed Nov 19 04:13:00 2003 From: keithp@keithp.com (Keith Packard) Date: Wed, 19 Nov 2003 04:13:00 -0000 Subject: interface bindings of x-server In-Reply-To: Your message of "Wed, 19 Nov 2003 02:57:57 +0100." <051801c3ae40$8e170880$2000000a@schlepptopp> Message-ID: Around 2 o'clock on Nov 19, "roland@webde" wrote: > Keith, could you put this (being able to specify the interface bindings of > the xserver on the commandline) as a feature request on http:// > www.freedesktop.org/Software/XserverWishlist if you find this feature > request useful ? i registerd a wiki account, but logging in doesn`t seem to > work for me. I'd like to switch the server so that -nolisten tcp is the default; I don't see much sense in having it listen to even 127.0.0.1. But, if you wanted to make the list of IP addresses that the server bound to configurable, that seems like a good idea. ssh -X -C should be the only way to talk to an X server over the network, at least for now. If we find a better way in the future, we might revisit this. Patches to implement any such changes would be gratefully accepted to the fd.o X server tree. The wiki has anti-defacement "security"; please ask most anyone on #freedesktop to be added to the list of accounts with wiki write access. -keith From jay@JaySmith.com Wed Nov 19 04:26:00 2003 From: jay@JaySmith.com (Jay Smith) Date: Wed, 19 Nov 2003 04:26:00 -0000 Subject: Cut-Copy/Paste dies after several hours (-clipboard) Message-ID: <3FBAF02E.4020605@JaySmith.com> Hi again, 1) Is this a known problem? Any suggestions? I thought I was going nuts, but it has happened enough times that I am sure it is really happening. My usual workday is about 14 hours. After around 9-11 hours, the "-clipboard" cut-copy/paste between Windows and Linux stops functioning. It seems that it no longer puts the highlighted content into to the/a paste buffer. I have not been able to determine if this is simply "happening by itself" of if some event is occuring. However, if I accidenally leave my X sessions up overnight, the cut-copy/paste rarely still works in the morning even though it may have worked when I left the night before. My Windows machine is Windows 95b. The Linux server on which the X applications are running is Red Hat 8, up2date with most recent updates. I have not been able to find instructions on Cygwin.com how to get a list of installed Cygwin/XFree version numbers. (Advice?) However, I installed everything freshly on 18 October 2003 if that helps. I am using the -clipboard option. I am not sure why I am not using xwinclip -- there was something that did not work at some point. 2) In case anybody is inspired to work on it, I still have the problem that if I don't get logged in to the XDM "instantly", the cut-copy/paste does not function. I have mentioned this earlier and Harold said that he is otherwise occupied. I don't have the technical ability to do anything about it. When I say instantly, I mean that I have to absolutely type my name and password as fast as I possibly can -- and I am a very fast typist -- and about half the time, that is fast enough. If I am too slow, the cut-copy/paste does not work. Also, if the startup time of Xwin is too slow (i.e. first time run after PC is rebooted), then I rarely have a chance of cut-copy/paste working. Because of Win95 graphics resource issues, I have to reboot my machine every morning -- that means I have to log in to the XDM at least twice to get cut-copy/paste working. There is a particular "click" the hard disk makes (of the many that occur as programs are starting up) when this particular program is starting. I know 100% of the time that if the "click" happens before the login process is far enough along that the cut-copy-paste will not work. By the way, this also means if the Linux server is under heavy load and responding slowly at that moment that I am out of luck and will have to try again until things are fast enough getting logged in and up before cut-copy/paste will work. Jay -- Jay Smith e-mail: Jay@JaySmith.com mailto:Jay@JaySmith.com website: http://www.JaySmith.com Jay Smith & Associates P.O. Box 650 Snow Camp, NC 27349 USA Phone: Int+US+336-376-9991 Toll-Free Phone in US & Canada: 1-800-447-8267 Fax: Int+US+336-376-6750 From huntharo@msu.edu Wed Nov 19 04:34:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Wed, 19 Nov 2003 04:34:00 -0000 Subject: Cut-Copy/Paste dies after several hours (-clipboard) In-Reply-To: <3FBAF02E.4020605@JaySmith.com> References: <3FBAF02E.4020605@JaySmith.com> Message-ID: <3FBAF2C7.8000100@msu.edu> xwinclip was updated on October 30th: http://cygwin.com/ml/cygwin-xfree-announce/2003-10/msg00028.html Using the integrated -clipboard support prevents you from restarting the clipboard support if/when it dies. I would recommend using xwinclip in your case since you can restart it when it dies. It also might not die at all... since the external executable seems slightly more stable than the internal client running in a thread. You could also use the stand-alone xwinclip to delay the start of xwinclip until after you are logged into XDMCP. Kensuke backported the update to -clipboard to xwinclip... that is what the xwinclip-1.2.0-1 package was for. Note: XFree86-xwinclip is a dead package. It was renamed to just "xwinclip". Hope that helps, Harold Jay Smith wrote: > Hi again, > > 1) Is this a known problem? Any suggestions? > > I thought I was going nuts, but it has happened enough times that I > am sure it is really happening. My usual workday is about 14 hours. > After around 9-11 hours, the "-clipboard" cut-copy/paste between Windows > and Linux stops functioning. It seems that it no longer puts the > highlighted content into to the/a paste buffer. > > I have not been able to determine if this is simply "happening by > itself" of if some event is occuring. However, if I accidenally leave > my X sessions up overnight, the cut-copy/paste rarely still works in the > morning even though it may have worked when I left the night before. > > My Windows machine is Windows 95b. > > The Linux server on which the X applications are running is Red Hat > 8, up2date with most recent updates. > > I have not been able to find instructions on Cygwin.com how to get a > list of installed Cygwin/XFree version numbers. (Advice?) However, I > installed everything freshly on 18 October 2003 if that helps. > > I am using the -clipboard option. I am not sure why I am not using > xwinclip -- there was something that did not work at some point. > > 2) In case anybody is inspired to work on it, I still have the problem > that if I don't get logged in to the XDM "instantly", the cut-copy/paste > does not function. I have mentioned this earlier and Harold said that > he is otherwise occupied. I don't have the technical ability to do > anything about it. > > When I say instantly, I mean that I have to absolutely type my name > and password as fast as I possibly can -- and I am a very fast typist -- > and about half the time, that is fast enough. If I am too slow, the > cut-copy/paste does not work. > > Also, if the startup time of Xwin is too slow (i.e. first time run > after PC is rebooted), then I rarely have a chance of cut-copy/paste > working. Because of Win95 graphics resource issues, I have to reboot my > machine every morning -- that means I have to log in to the XDM at least > twice to get cut-copy/paste working. > > There is a particular "click" the hard disk makes (of the many that > occur as programs are starting up) when this particular program is > starting. I know 100% of the time that if the "click" happens before > the login process is far enough along that the cut-copy-paste will not > work. > > By the way, this also means if the Linux server is under heavy load > and responding slowly at that moment that I am out of luck and will have > to try again until things are fast enough getting logged in and up > before cut-copy/paste will work. > > Jay > From huntharo@msu.edu Wed Nov 19 06:20:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Wed, 19 Nov 2003 06:20:00 -0000 Subject: Updated: XFree86-bin-4.3.0-8, XFree86-etc-4.3.0-6, XFree86-fsrv-4.3.0-6, XFree86-prog-4.3.0-11, XFree86-xserv-4.3.0-23, XFree86-[nest,prt,vfb]-4.3.0-5 In-Reply-To: <87brr9o41e.fsf@vzell-de.de.oracle.com> References: <3FB9A69B.1070602@msu.edu> <87brr9o41e.fsf@vzell-de.de.oracle.com> Message-ID: <3FBB0BB2.8050501@msu.edu> Volker, Dr. Volker Zell wrote: >>>>>>"Harold" == Harold L Hunt, writes: > > > Harold> The following packages have been updated in the Cygwin distribution: > Harold> *** XFree86-fsrv-4.3.0-6 > > It's missing its man-page again. > > Harold> *** XFree86-prog-4.3.0-11 > > I get an additional symbolic link > > /usr/X11R6/include/X11/X11 --> /usr/X11R6/include/X11 > > after the postinstall script is run. I would recommend changing > the postinstall script to: > > > --------------------- cut ----------------------------------- > #!/bin/sh > > # Create an empty host.def if one doesn't exist already > touch /usr/X11R6/lib/X11/config/host.def > > # Create a link in /usr/include to the X11 includes directory > if [ ! -L /usr/include/X11 ] > then > ln -sf /usr/X11R6/include/X11 /usr/include/X11 > fi > --------------------- cut ----------------------------------- Man, you always bust me :) Thanks for keeping me honest. Harold From sand@blarg.net Wed Nov 19 06:30:00 2003 From: sand@blarg.net (sand@blarg.net) Date: Wed, 19 Nov 2003 06:30:00 -0000 Subject: PC104 "Windows" keys not generating keyboard events Message-ID: <16315.3651.33852.433965@priss.frightenedpiglet.com> My preferred X keyboard setup on Linux has the Alt key generating the Alt modifier, and the "Windows" key generating the Meta modifier. I've recently learned how to disable the various hotkeys under Windows, so I'm working my way towards the same setup on my work laptop (XP). I also have my home game box (2000) for testing. My work laptop has both Exceed and Cygwin/XFree86, and Exceed works pretty much as expected. The left Win key generates keycode 115, which I've set up to generate Meta_L. Cygwin/XFree86 on both my work machine and home machine don't see *anything* when I press and release the Win key. "xev" reports no events whatsoever. I've confirmed that the key is working properly using native Emacs on my home box. With hotkeys turned off and (setq w32-pass-lwindow-to-system nil) (setq w32-lwindow-modifier 'meta) in my init file, the Win key works exactly as you would expect. Can anyone give me suggestions on how to investigate the missing XFree86 events and fix this problem? Thanks, Derek -- Derek Upham sand@blarg.net "Ha! Your Leaping Tiger Kung Fu is no match for my Frightened Piglet style!" From keith@tungstengraphics.com Wed Nov 19 08:15:00 2003 From: keith@tungstengraphics.com (Keith Whitwell) Date: Wed, 19 Nov 2003 08:15:00 -0000 Subject: security, cvs, was Re: interface bindings of x-server In-Reply-To: References: Message-ID: <3FBB269A.9080306@tungstengraphics.com> Keith Packard wrote: > Around 2 o'clock on Nov 19, "roland@webde" wrote: > > >>Keith, could you put this (being able to specify the interface bindings of >>the xserver on the commandline) as a feature request on http:// >>www.freedesktop.org/Software/XserverWishlist if you find this feature >>request useful ? i registerd a wiki account, but logging in doesn`t seem to >>work for me. > > > I'd like to switch the server so that -nolisten tcp is the default; I > don't see much sense in having it listen to even 127.0.0.1. But, if you > wanted to make the list of IP addresses that the server bound to > configurable, that seems like a good idea. Yep - network transparency is all well & good, but do you really want something as complex as the X server sitting there with an open port to the world? On a related issue, does anyone understand what the actual flaw in pserver CVS is that allowed the linux backdoor attempt? There's been a lot of talk about the implications of the attempt, but I haven't heard anyone come out and say "This is the fault in CVS, here's a patch, everything's ok now". Is it foolhardy to continue running anoncvs, especially without the checks & balances which caught the backdoor attempt in linux? Keith From cheako911@yahoo.com Wed Nov 19 08:35:00 2003 From: cheako911@yahoo.com (Mike Mestnik) Date: Wed, 19 Nov 2003 08:35:00 -0000 Subject: [Dri-devel] security, cvs, was Re: interface bindings of x-server In-Reply-To: <3FBB269A.9080306@tungstengraphics.com> Message-ID: <20031119083439.30737.qmail@web11907.mail.yahoo.com> ssh uses IP4:127.0.0.1, and as many times as ppl have asked for unix socket support it has allways been denied. -nolisten tcp is something for the distros to set up, it should be *usable by default. * Meaning all non-devel features on and nothing extra for the user to do. --- Keith Whitwell wrote: > Keith Packard wrote: > > Around 2 o'clock on Nov 19, "roland@webde" wrote: > > > > > >>Keith, could you put this (being able to specify the interface bindings of > >>the xserver on the commandline) as a feature request on http:// > >>www.freedesktop.org/Software/XserverWishlist if you find this feature > >>request useful ? i registerd a wiki account, but logging in doesn`t seem to > >>work for me. > > > > > > I'd like to switch the server so that -nolisten tcp is the default; I > > don't see much sense in having it listen to even 127.0.0.1. But, if you > > wanted to make the list of IP addresses that the server bound to > > configurable, that seems like a good idea. > > Yep - network transparency is all well & good, but do you really want > something as complex as the X server sitting there with an open port to the world? > > Keith > > __________________________________ Do you Yahoo!? Protect your identity with Yahoo! Mail AddressGuard http://antispam.yahoo.com/whatsnewfree From murakami@ipl.t.u-tokyo.ac.jp Wed Nov 19 08:37:00 2003 From: murakami@ipl.t.u-tokyo.ac.jp (Takuma Murakami) Date: Wed, 19 Nov 2003 08:37:00 -0000 Subject: PC104 "Windows" keys not generating keyboard events In-Reply-To: <16315.3651.33852.433965@priss.frightenedpiglet.com> References: <16315.3651.33852.433965@priss.frightenedpiglet.com> Message-ID: <20031119165958.308F.MURAKAMI@ipl.t.u-tokyo.ac.jp> Cygwin/X specially handles Win keys by design. It simply discards Windows keyboard messages which notify a Win key is pressed or released. Thus no keyboard events are passed to the X Window layer. Takuma Murakami (murakami@ipl.t.u-tokyo.ac.jp) From keithp@keithp.com Wed Nov 19 08:49:00 2003 From: keithp@keithp.com (Keith Packard) Date: Wed, 19 Nov 2003 08:49:00 -0000 Subject: security, cvs, was Re: interface bindings of x-server In-Reply-To: Your message of "Wed, 19 Nov 2003 08:15:22 GMT." <3FBB269A.9080306@tungstengraphics.com> Message-ID: Around 8 o'clock on Nov 19, Keith Whitwell wrote: > Is it foolhardy to continue running anoncvs, especially without the checks & > balances which caught the backdoor attempt in linux? The pserver running on fd.o has been specially hacked to run as 'nobody' from the very start, unlike most pserver implementations which run as root and setuid to the user specified in the CVS password file. I think this should make it rather difficult to affect any of the repositories on fd.o unless files in those directories are world writable. But, if we want to be extra paranoid, the right solution is to have anoncvs use a separate mirror machine rsynced from the main repository. I'd like to avoid that as it makes anoncvs 'second class' which seems like it will encourage more people to ask for project membership that they otherwise don't really need just to avoid the anoncvs delay. Of course, an even better solution would be to throw CVS in the garbage and use some more robust configuration management system. Sigh. -keith From devzero@web.de Wed Nov 19 09:22:00 2003 From: devzero@web.de (roland@webde) Date: Wed, 19 Nov 2003 09:22:00 -0000 Subject: security, cvs, was Re: interface bindings of x-server References: <3FBB269A.9080306@tungstengraphics.com> Message-ID: <054901c3ae7f$16b6bc60$2000000a@schlepptopp> hi > Yep - network transparency is all well & good, but do you really want > something as complex as the X server sitting there with an open port to the world? exactly _THIS_ _IS_ what causese my headache! there _IS_ something as complex as the X server sitting there with an open port to the world - per default! the only chance to get rid of it, is to use unix domain socket (via -nolisten tcp) OR to add the option, to specify the interface bindings and be able to bind it to local loopback ONLY. I`d prefer the second one. BTW: on a server "out there on the internet" i even run samba - and i`m shure it never get`s hacked cause of a samba exploit. why? because i bound it to 127.0.0.1 only - and i`m doing ssh portforwarding with that. ahhhh - btw - i see: on http://www.tightvnc.com/changelog-unix.html 2001-01-17 01:55 const Xvnc/programs/Xserver/hw/vnc/: init.c, rfb.h, sockets.c: Support for Xvnc -interface option added (patch from Tim Waught). feature seems to be in tightvnc already - so maybe we need just some code transfer (since vnc is xfree86 based) ? ;) regards roland ----- Original Message ----- From: "Keith Whitwell" To: "Keith Packard" Cc: "roland@webde" ; ; ; "dri-devel" Sent: Wednesday, November 19, 2003 9:15 AM Subject: security, cvs, was Re: interface bindings of x-server > Keith Packard wrote: > > Around 2 o'clock on Nov 19, "roland@webde" wrote: > > > > > >>Keith, could you put this (being able to specify the interface bindings of > >>the xserver on the commandline) as a feature request on http:// > >>www.freedesktop.org/Software/XserverWishlist if you find this feature > >>request useful ? i registerd a wiki account, but logging in doesn`t seem to > >>work for me. > > > > > > I'd like to switch the server so that -nolisten tcp is the default; I > > don't see much sense in having it listen to even 127.0.0.1. But, if you > > wanted to make the list of IP addresses that the server bound to > > configurable, that seems like a good idea. > > Yep - network transparency is all well & good, but do you really want > something as complex as the X server sitting there with an open port to the world? > > On a related issue, does anyone understand what the actual flaw in pserver CVS > is that allowed the linux backdoor attempt? There's been a lot of talk about > the implications of the attempt, but I haven't heard anyone come out and say > "This is the fault in CVS, here's a patch, everything's ok now". > > Is it foolhardy to continue running anoncvs, especially without the checks & > balances which caught the backdoor attempt in linux? > > Keith > From keithp@keithp.com Wed Nov 19 09:35:00 2003 From: keithp@keithp.com (Keith Packard) Date: Wed, 19 Nov 2003 09:35:00 -0000 Subject: security, cvs, was Re: interface bindings of x-server In-Reply-To: Your message of "Wed, 19 Nov 2003 10:25:34 +0100." <054901c3ae7f$16b6bc60$2000000a@schlepptopp> Message-ID: Around 10 o'clock on Nov 19, "roland@webde" wrote: > the only chance to get rid of it, is to use unix domain socket (via > -nolisten tcp) That option should be the default; ssh refuses to listen on a unix domain socket, but appears quite happy to connect to a unix domain socket. I don't know of any compelling reason to run X raw over TCP/IP these days; it's insecure, and a bandwidth pig. -keith From corinna-cygwin@cygwin.com Wed Nov 19 09:52:00 2003 From: corinna-cygwin@cygwin.com (Corinna Vinschen) Date: Wed, 19 Nov 2003 09:52:00 -0000 Subject: security, cvs, was Re: interface bindings of x-server In-Reply-To: References: <054901c3ae7f$16b6bc60$2000000a@schlepptopp> Message-ID: <20031119095208.GB9027@cygbert.vinschen.de> On Wed, Nov 19, 2003 at 01:35:20AM -0800, Keith Packard wrote: > > Around 10 o'clock on Nov 19, "roland@webde" wrote: > > > the only chance to get rid of it, is to use unix domain socket (via > > -nolisten tcp) > > That option should be the default; ssh refuses to listen on a unix > domain socket, but appears quite happy to connect to a unix domain > socket. > > I don't know of any compelling reason to run X raw over TCP/IP these days; > it's insecure, and a bandwidth pig. AF_LOCAL sockets are implemented using AF_INET sockets on Cygwin, using a binding of 127.0.0.1 plus some overhead for security reasons. So AF_LOCAL sockets are a few percent slower than AF_INET sockets. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin@cygwin.com Red Hat, Inc. From ingber@ingber.com Wed Nov 19 10:57:00 2003 From: ingber@ingber.com (Lester Ingber) Date: Wed, 19 Nov 2003 10:57:00 -0000 Subject: still wmaker tiff problems? Message-ID: <20031119105709.GA3288@ingber.com> I've seen other reports about lost tiff icon images using wmaker, but I see they still have not been fixed? (I recall the poster was asked if he had his files mounted text, to which he replied binary -- mine are binary too.) I've been getting the following warnings whenever I start my initial session which brings up several xterms. I start wmaker in my startxwin.sh under tcsh using startxwin.sh >& log.xwin & In log.win I see: TIFFReadDirectory: Warning, /usr/X11R6/share/WINGs/Images.tiff: unknown field with tag 317 (0x13d) encountered. TIFFReadDirectory: Warning, /usr/X11R6/share/WindowMaker/Icons/Terminal.tiff: unknown field with tag 317 (0x13d) encountered. TIFFReadDirectory: Warning, /usr/X11R6/share/WindowMaker/Icons/Terminal.tiff: unknown field with tag 317 (0x13d) encountered. Thanks. Lester -- Prof. Lester Ingber ingber@ingber.com ingber@alumni.caltech.edu www.ingber.com www.alumni.caltech.edu/~ingber From xavier.elattaoui@synchrotron-soleil.fr Wed Nov 19 11:11:00 2003 From: xavier.elattaoui@synchrotron-soleil.fr (ELATTAOUI Xavier) Date: Wed, 19 Nov 2003 11:11:00 -0000 Subject: usb keyboard Message-ID: <24AD9A5266E9A94E93C2D7686B8CD08B6BE4DF@venus.synchrotron-soleil.fr> Hello every body, I'm new in Cygwin. I'm working under win2000 with a USB keyboard in azerty mode. So when I launch "Cygwin/XFree86 rl" to be log on a Unix server, my keyboard become qwerty and it's impossible to be logon. I want it to keep in azerty. Maybe, there's a parameter to change !!! Thank you in advance. Xavier ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Xavier Elattaoui Mail : xavier.elattaoui@synchrotron-soleil.fr Web : http://www.synchrotron-soleil.fr ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ From goebel@ires.ucl.ac.be Wed Nov 19 11:38:00 2003 From: goebel@ires.ucl.ac.be (Christian =?iso-8859-1?Q?G=F6bel?=) Date: Wed, 19 Nov 2003 11:38:00 -0000 Subject: Unexpected network-traffic Message-ID: <5.0.2.1.2.20031119121810.04d75010@pops.ires.ucl.ac.be> Hello, when I start the X via my personal Firewall asks me several permissions for access to the Internet: xterm.exe Destination IP:127.0.0.1:Port 6000 XWin.exe Destination IP: 130.104.1.1: DNS XWin.exe Source IP: 0.0.0.:Port 6000 Whatever I type in xterm within X my network-monitor shows me extensive nettwork traffic (outgoing and ingoing) after every single letter I type. Is this something to worry about? Can anybody explain me why the use of Cygwin-XFree86 causes network traffic whatever I type in xterm? Are there any security issues? Cygwing 1.5.5 on Win2000pro Thanks a lot Christian From alexander.gottwald@s1999.tu-chemnitz.de Wed Nov 19 13:58:00 2003 From: alexander.gottwald@s1999.tu-chemnitz.de (Alexander Gottwald) Date: Wed, 19 Nov 2003 13:58:00 -0000 Subject: Can't type in login window via XDMCP In-Reply-To: <3FBA809E.4000502@JaySmith.com> References: <658B168FF59ED4119FC200508BF354BB0AF7A25B@exgate.tek.com> <3FBA809E.4000502@JaySmith.com> Message-ID: On Tue, 18 Nov 2003, Jay Smith wrote: > The other thing I wonder about is fonts. I am ignorant on the subject, but > is there a chance that not all the fonts needed are being loaded (on either > end?) You will only have access to the fonts installed with Cygwin/XFree unless you run a fontserver on the linux machine and add tcp/linuxserver:7100 to the fontpath. bye ago -- Alexander.Gottwald@s1999.tu-chemnitz.de http://www.gotti.org ICQ: 126018723 From devzero@web.de Wed Nov 19 14:01:00 2003 From: devzero@web.de (devzero@web.de) Date: Wed, 19 Nov 2003 14:01:00 -0000 Subject: security, cvs, was Re: interface bindings of x-server Message-ID: <200311191401.hAJE1LQ03631@mailgate5.cinetic.de> Hi! i`d like if discussion "unix domain socket vs. 127.0.0.1/TCP for local X connections" would be a complete separate discussion thread. could we separate this? ok, it seems my thread has alreade become somewhat a separate one (the "was" in the subject line) ;) MY intention with this thread is , just to add feature to X-Server which enables binding to dedicated interfaces - which is a quite common feature for popular server-daemons. being able to tune the interface bindings of an applications is a matter of "good implementation style", IMHO. I wished if i could do that with ALL applications which bind to interfaces. I`m sure this feature is easy to implement (because there are tons of code examples on the net and because it seems to be already in tightvnc). is there anybody who already thinksa about doing that ? i`m really a bad programmer - maybe i could try my luck with that - but i don`t like it starting such work and fiddling around for some days and then somebody says: ok - i`ve done it. was just 5 mins - TRIVIAL ! :D regards roland Keith Packard schrieb am 19.11.03 10:35:24: > > > Around 10 o'clock on Nov 19, "roland@webde" wrote: > > > the only chance to get rid of it, is to use unix domain socket (via > > -nolisten tcp) > > That option should be the default; ssh refuses to listen on a unix > domain socket, but appears quite happy to connect to a unix domain > socket. > > I don't know of any compelling reason to run X raw over TCP/IP these days; > it's insecure, and a bandwidth pig. > > -keith > > ______________________________________________________________________________ WEB.DE FreeMail wird 5 Jahre jung! Feiern Sie mit uns und nutzen Sie die neuen Funktionen http://f.web.de/features/?mc=021130 From alexander.gottwald@s1999.tu-chemnitz.de Wed Nov 19 14:12:00 2003 From: alexander.gottwald@s1999.tu-chemnitz.de (Alexander Gottwald) Date: Wed, 19 Nov 2003 14:12:00 -0000 Subject: Updated: XFree86-xserv-4.3.0-22 In-Reply-To: <3FBA8FE4.30902@users.sourceforge.net> References: <1068549020528.tulitanssi.36802.w1Q4NRjiTPWoQQzb3m7sWA@luukku.com> <3FB0E0D5.7090505@msu.edu> <87ptfyvpbj.fsf@vzell-de.de.oracle.com> <3FB1123E.8090102@msu.edu> <87d6byvn9u.fsf@vzell-de.de.oracle.com> <87smktnyps.fsf@vzell-de.de.oracle.com> <3FBA8FE4.30902@users.sourceforge.net> Message-ID: On Tue, 18 Nov 2003, Zbynek Winkler wrote: > As it happens, I was completely happy with the old behavior. Now it > defaults to something else than I have set in the win32 environment. > Could the default be (when no config file is found) the autorepeat that > was before the change? Thus this upgrade would hit only the users who > really want to customise it. There were two changes recently. The first switched off the win32 autorepeat, the second added support for a AutoRepeat option in the configfile. The second may have changed default values (but I am quite sure that I've used exactly the values which were default before). But I think you missed the first change which changed the old behaviour. If this is the case I can add code to use the windows default autorepeat settings to configure Xwin. But this will again change the old behavior of Xwin and some users might be unhappy with it. bye ago -- Alexander.Gottwald@s1999.tu-chemnitz.de http://www.gotti.org ICQ: 126018723 From alexander.gottwald@s1999.tu-chemnitz.de Wed Nov 19 14:30:00 2003 From: alexander.gottwald@s1999.tu-chemnitz.de (Alexander Gottwald) Date: Wed, 19 Nov 2003 14:30:00 -0000 Subject: usb keyboard In-Reply-To: <24AD9A5266E9A94E93C2D7686B8CD08B6BE4DF@venus.synchrotron-soleil.fr> References: <24AD9A5266E9A94E93C2D7686B8CD08B6BE4DF@venus.synchrotron-soleil.fr> Message-ID: On Wed, 19 Nov 2003, ELATTAOUI Xavier wrote: > Hello every body, > > I'm new in Cygwin. > I'm working under win2000 with a USB keyboard in azerty mode. So when I launch "Cygwin/XFree86 rl" to be log on a Unix server, my keyboard > become qwerty and it's impossible to be logon. I want it to keep in azerty. Maybe, there's a parameter to change !!! please send /tmp/XWin.log bye ago -- Alexander.Gottwald@s1999.tu-chemnitz.de http://www.gotti.org ICQ: 126018723 From alexander.gottwald@s1999.tu-chemnitz.de Wed Nov 19 14:35:00 2003 From: alexander.gottwald@s1999.tu-chemnitz.de (Alexander Gottwald) Date: Wed, 19 Nov 2003 14:35:00 -0000 Subject: Unexpected network-traffic In-Reply-To: <5.0.2.1.2.20031119121810.04d75010@pops.ires.ucl.ac.be> References: <5.0.2.1.2.20031119121810.04d75010@pops.ires.ucl.ac.be> Message-ID: On Wed, 19 Nov 2003, Christian G??bel wrote: > Whatever I type in xterm within X my network-monitor shows me > extensive nettwork traffic (outgoing and ingoing) after every > single letter I type. > Is this something to worry about? > > Can anybody explain me why the use of Cygwin-XFree86 causes > network traffic whatever I type in xterm? Are there any security issues? X11 uses TCP as transportprotocol and therefore causes network traffic. bye ago -- Alexander.Gottwald@s1999.tu-chemnitz.de http://www.gotti.org ICQ: 126018723 From xavier.elattaoui@synchrotron-soleil.fr Wed Nov 19 14:44:00 2003 From: xavier.elattaoui@synchrotron-soleil.fr (ELATTAOUI Xavier) Date: Wed, 19 Nov 2003 14:44:00 -0000 Subject: usb keyboard Message-ID: <24AD9A5266E9A94E93C2D7686B8CD08B66E769@venus.synchrotron-soleil.fr> I have no XWin.log under /tmp but a XWinrl.log(in attachement). I've done an uninstall and reinstall it, but the trouble is still present ! Thanks xavier -----Message d'origine----- De : Alexander Gottwald [mailto:alexander.gottwald@s1999.tu-chemnitz.de] Envoy? : mercredi 19 novembre 2003 15:31 ? : cygwin-xfree@cygwin.com Objet : Re: usb keyboard On Wed, 19 Nov 2003, ELATTAOUI Xavier wrote: > Hello every body, > > I'm new in Cygwin. > I'm working under win2000 with a USB keyboard in azerty mode. So when I launch "Cygwin/XFree86 rl" to be log on a Unix server, my keyboard > become qwerty and it's impossible to be logon. I want it to keep in azerty. Maybe, there's a parameter to change !!! please send /tmp/XWin.log bye ago -- Alexander.Gottwald@s1999.tu-chemnitz.de http://www.gotti.org ICQ: 126018723 -------------- next part -------------- A non-text attachment was scrubbed... Name: XWinrl.log Type: application/octet-stream Size: 3798 bytes Desc: XWinrl.log URL: From alexander.gottwald@s1999.tu-chemnitz.de Wed Nov 19 14:50:00 2003 From: alexander.gottwald@s1999.tu-chemnitz.de (Alexander Gottwald) Date: Wed, 19 Nov 2003 14:50:00 -0000 Subject: usb keyboard In-Reply-To: <24AD9A5266E9A94E93C2D7686B8CD08B66E769@venus.synchrotron-soleil.fr> References: <24AD9A5266E9A94E93C2D7686B8CD08B66E769@venus.synchrotron-soleil.fr> Message-ID: On Wed, 19 Nov 2003, ELATTAOUI Xavier wrote: > I have no XWin.log under /tmp but a XWinrl.log(in attachement). > I've done an uninstall and reinstall it, but the trouble is still present ! You're using a very old version. Update the XFree86-xserv package. This might already contain the proper keyboardlayout. bye ago -- Alexander.Gottwald@s1999.tu-chemnitz.de http://www.gotti.org ICQ: 126018723 From jay@JaySmith.com Wed Nov 19 14:53:00 2003 From: jay@JaySmith.com (Jay Smith) Date: Wed, 19 Nov 2003 14:53:00 -0000 Subject: xwinclip installation problems (Re: Cut-Copy/Paste dies after several hours (-clipboard)) In-Reply-To: <3FBAF2C7.8000100@msu.edu> References: <3FBAF02E.4020605@JaySmith.com> <3FBAF2C7.8000100@msu.edu> Message-ID: <3FBB833C.20000@JaySmith.com> Harold, Maybe I am just being stupid, but I can't seem to find the clipboard program, because.... a) Using the Cygwin setup wizard to attempt to update my installation, I checked a couple mirrors and they don't seem to have xwinclip -- they only seem to have XFree86-xwinclip. b) I went to the XFree86 web site and then the xwinclip site http://xfree86.cygwin.com/devel/xwinclip/ Obviously that page is long out of date so I don't know if I can trust anything it says about installation. At this point I don' know how to get the program to install it. c) Using your http://cygwin.com/ml/cygwin-xfree-announce/2003-10/msg00028.html information, I am supposed to use the Cygwin installation wizard, but as I said in "a" above, I am not finding the program. What am I missing? Jay Harold L Hunt II said the following on 11/18/2003 11:34 PM: > xwinclip was updated on October 30th: > > http://cygwin.com/ml/cygwin-xfree-announce/2003-10/msg00028.html > > Using the integrated -clipboard support prevents you from restarting the > clipboard support if/when it dies. I would recommend using xwinclip in > your case since you can restart it when it dies. It also might not die > at all... since the external executable seems slightly more stable than > the internal client running in a thread. > > You could also use the stand-alone xwinclip to delay the start of > xwinclip until after you are logged into XDMCP. Kensuke backported the > update to -clipboard to xwinclip... that is what the xwinclip-1.2.0-1 > package was for. Note: XFree86-xwinclip is a dead package. It was > renamed to just "xwinclip". > > Hope that helps, > > Harold > > Jay Smith wrote: > >> Hi again, >> >> 1) Is this a known problem? Any suggestions? >> >> I thought I was going nuts, but it has happened enough times that I >> am sure it is really happening. My usual workday is about 14 hours. >> After around 9-11 hours, the "-clipboard" cut-copy/paste between >> Windows and Linux stops functioning. It seems that it no longer puts >> the highlighted content into to the/a paste buffer. >> >> I have not been able to determine if this is simply "happening by >> itself" of if some event is occuring. However, if I accidenally leave >> my X sessions up overnight, the cut-copy/paste rarely still works in >> the morning even though it may have worked when I left the night before. >> >> My Windows machine is Windows 95b. >> >> The Linux server on which the X applications are running is Red Hat >> 8, up2date with most recent updates. >> >> I have not been able to find instructions on Cygwin.com how to get >> a list of installed Cygwin/XFree version numbers. (Advice?) However, >> I installed everything freshly on 18 October 2003 if that helps. >> >> I am using the -clipboard option. I am not sure why I am not using >> xwinclip -- there was something that did not work at some point. >> >> 2) In case anybody is inspired to work on it, I still have the problem >> that if I don't get logged in to the XDM "instantly", the >> cut-copy/paste does not function. I have mentioned this earlier and >> Harold said that he is otherwise occupied. I don't have the technical >> ability to do anything about it. >> >> When I say instantly, I mean that I have to absolutely type my name >> and password as fast as I possibly can -- and I am a very fast typist >> -- and about half the time, that is fast enough. If I am too slow, >> the cut-copy/paste does not work. >> >> Also, if the startup time of Xwin is too slow (i.e. first time run >> after PC is rebooted), then I rarely have a chance of cut-copy/paste >> working. Because of Win95 graphics resource issues, I have to reboot >> my machine every morning -- that means I have to log in to the XDM at >> least twice to get cut-copy/paste working. >> >> There is a particular "click" the hard disk makes (of the many that >> occur as programs are starting up) when this particular program is >> starting. I know 100% of the time that if the "click" happens before >> the login process is far enough along that the cut-copy-paste will not >> work. >> >> By the way, this also means if the Linux server is under heavy load >> and responding slowly at that moment that I am out of luck and will >> have to try again until things are fast enough getting logged in and >> up before cut-copy/paste will work. >> >> Jay >> -- Jay Smith e-mail: Jay@JaySmith.com mailto:Jay@JaySmith.com website: http://www.JaySmith.com Jay Smith & Associates P.O. Box 650 Snow Camp, NC 27349 USA Phone: Int+US+336-376-9991 Toll-Free Phone in US & Canada: 1-800-447-8267 Fax: Int+US+336-376-6750 From yet-another-cygwin-user@yacu.dont.want.pm Wed Nov 19 15:22:00 2003 From: yet-another-cygwin-user@yacu.dont.want.pm (=?unknown-8bit?Q?Ga=EBl?= Gueguen) Date: Wed, 19 Nov 2003 15:22:00 -0000 Subject: Updated: XFree86-xserv-4.3.0-22 Message-ID: <20031119152228.GA1132@PRDRBNO> Alexander Gottwald wrote: > We were previously using two auto-repeat schemes at the same time: > > 1) xkb > > 2) Win32's auto repeat layer > > Convince me why it is good to have two layers handling auto repeat by > default and I will accede to your request. Not sure it will convince anybody, just my point of view. I'm using Cygwin/XFree to connect to some HP-UX and AIX boxes, and I can't use xkb because of this CDE/AltGr/whatever problem. (If I use xkb, I don't have access to |, @, etc...) So I launch X via "X -kb" and then load my own .xmodmap. This was working perfectly, but without Win32 autorepeat nor xkb autorepeat, I have no autorepeat at all :-( My suggestion: is it possible to enable Win32 autorepeat only if X is launched with the -kb switch ? Thanks for the very good job you all do, Gael. From vervoom@hotmail.com Wed Nov 19 15:51:00 2003 From: vervoom@hotmail.com (J S) Date: Wed, 19 Nov 2003 15:51:00 -0000 Subject: screen redraw problem Message-ID: Thanks for the help I got on this from Harold and Alan. The application was written in-house and after I asked the client for the source code, they managed to find the error themselves. For some reason, this only showed up in XFree86 though (not Exceed or Sun X-Windows). Here's what they said: "An XWindows Draw function was taking a clipping area as a parameter. Under Xfree86, depending on what you are doing, invalid clipping areas were being generated and so the Draw function was causing screen distortions. I have put a validation in which checks the clipping area and if invalid it does not paint. In the old days when I used to work on the Windows SDK and OS2/Presentation Manager we used to hit similiar problems. This fix appears to be working." >JS, > >Can you tell us about the application - is it available anywhere so I >can take a look too ? > >Alan. _________________________________________________________________ Use MSN Messenger to send music and pics to your friends http://www.msn.co.uk/messenger From huntharo@msu.edu Wed Nov 19 15:53:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Wed, 19 Nov 2003 15:53:00 -0000 Subject: still wmaker tiff problems? In-Reply-To: <20031119105709.GA3288@ingber.com> References: <20031119105709.GA3288@ingber.com> Message-ID: <3FBB91DF.7060104@msu.edu> Lester, Problem still there until someone wants to fix it. Charles Wilson posted very useful information (he maintains the tiff package), but I have not been able to follow up on it. Harold Lester Ingber wrote: > I've seen other reports about lost tiff icon images using wmaker, but I > see they still have not been fixed? (I recall the poster was asked if > he had his files mounted text, to which he replied binary -- mine are > binary too.) > > I've been getting the following warnings whenever I start my initial > session which brings up several xterms. I start wmaker in my startxwin.sh > under tcsh using > startxwin.sh >& log.xwin & > > In log.win I see: > > TIFFReadDirectory: Warning, /usr/X11R6/share/WINGs/Images.tiff: unknown field with tag 317 (0x13d) encountered. > TIFFReadDirectory: Warning, /usr/X11R6/share/WindowMaker/Icons/Terminal.tiff: unknown field with tag 317 (0x13d) encountered. > TIFFReadDirectory: Warning, /usr/X11R6/share/WindowMaker/Icons/Terminal.tiff: unknown field with tag 317 (0x13d) encountered. > > Thanks. > > Lester > > From vervoom@hotmail.com Wed Nov 19 15:56:00 2003 From: vervoom@hotmail.com (J S) Date: Wed, 19 Nov 2003 15:56:00 -0000 Subject: mapping the right mouse button Message-ID: I remember seeing recently that there was a fix for mapping the mouse buttons in XFree86. I'm trying to get an application called EMC (which does disk management on MVS) to work with XFree but the problem is the right mouse button doesn't seem to work. It should bring up a menu when I right click on one of the disk images. I found that I could use Shift-F10 instead though and wondered if someone could tell me how to map these keys to the right mouse button? Thanks for any help. JS. _________________________________________________________________ Express yourself with cool emoticons - download MSN Messenger today! http://www.msn.co.uk/messenger From holger.krull@gmx.de Wed Nov 19 15:59:00 2003 From: holger.krull@gmx.de (Holger Krull) Date: Wed, 19 Nov 2003 15:59:00 -0000 Subject: Cut-Copy/Paste dies after several hours (-clipboard) In-Reply-To: <3FBAF02E.4020605@JaySmith.com> References: <3FBAF02E.4020605@JaySmith.com> Message-ID: <3FBB937D.10808@gmx.de> Jay Smith schrieb: > I am using the -clipboard option. I am not sure why I am not using > xwinclip -- there was something that did not work at some point. I'm using xwinclip and it's stops sometimes too. In most cases a restart will help. I'm starting it with xwinclip --display 127.0.0.1:0.0 from bash. and xwin needs -ac as an option though i don't understand why. > 2) In case anybody is inspired to work on it, I still have the problem > that if I don't get logged in to the XDM "instantly", the cut-copy/paste Now i understand why i never got -clipboard to work. Holger Krull From huntharo@msu.edu Wed Nov 19 16:00:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Wed, 19 Nov 2003 16:00:00 -0000 Subject: xwinclip installation problems (Re: Cut-Copy/Paste dies after several hours (-clipboard)) In-Reply-To: <3FBB833C.20000@JaySmith.com> References: <3FBAF02E.4020605@JaySmith.com> <3FBAF2C7.8000100@msu.edu> <3FBB833C.20000@JaySmith.com> Message-ID: <3FBB9382.7090103@msu.edu> Jay, Jay Smith wrote: > Harold, > > Maybe I am just being stupid, but I can't seem to find the clipboard > program, because.... > > a) Using the Cygwin setup wizard to attempt to update my installation, I > checked a couple mirrors and they don't seem to have xwinclip -- they > only seem to have XFree86-xwinclip. It's on mirrors.rcn.net. Just confirmed and downloaded it. > b) I went to the XFree86 web site and then the xwinclip site > http://xfree86.cygwin.com/devel/xwinclip/ > Obviously that page is long out of date so I don't know if I can trust > anything it says about installation. At this point I don' know how to > get the program to install it. That development page is out of date because the distribution method changed to finally use setup.exe. I will update it at some point, but it isn't very important at this time. > c) Using your > http://cygwin.com/ml/cygwin-xfree-announce/2003-10/msg00028.html > information, I am supposed to use the Cygwin installation wizard, but as > I said in "a" above, I am not finding the program. > > What am I missing? Dunno. You are choosing "Install from Internet", right? The package is there... in the XFree86 category. Make sure you are looking below the XFree86-* packages. Harold From huntharo@msu.edu Wed Nov 19 16:01:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Wed, 19 Nov 2003 16:01:00 -0000 Subject: Updated: XFree86-xserv-4.3.0-22 In-Reply-To: <20031119152228.GA1132@PRDRBNO> References: <20031119152228.GA1132@PRDRBNO> Message-ID: <3FBB93B0.2000407@msu.edu> Might be a good idea. Ga??l Gueguen wrote: > Alexander Gottwald wrote: > > >>We were previously using two auto-repeat schemes at the same time: >> >>1) xkb >> >>2) Win32's auto repeat layer >> >>Convince me why it is good to have two layers handling auto repeat by >>default and I will accede to your request. > > > Not sure it will convince anybody, just my point of view. > I'm using Cygwin/XFree to connect to some HP-UX and AIX boxes, and I > can't use xkb because of this CDE/AltGr/whatever problem. (If I use xkb, > I don't have access to |, @, etc...) > So I launch X via "X -kb" and then load my own .xmodmap. > This was working perfectly, but without Win32 autorepeat nor xkb > autorepeat, I have no autorepeat at all :-( > My suggestion: is it possible to enable Win32 autorepeat only if X > is launched with the -kb switch ? > > Thanks for the very good job you all do, > Gael. From alexander.gottwald@s1999.tu-chemnitz.de Wed Nov 19 16:37:00 2003 From: alexander.gottwald@s1999.tu-chemnitz.de (Alexander Gottwald) Date: Wed, 19 Nov 2003 16:37:00 -0000 Subject: Updated: XFree86-xserv-4.3.0-22 In-Reply-To: <3FBB93B0.2000407@msu.edu> References: <20031119152228.GA1132@PRDRBNO> <3FBB93B0.2000407@msu.edu> Message-ID: On Wed, 19 Nov 2003, Harold L Hunt II wrote: > Might be a good idea. I've a patch ready, but no buildsystem to test it. Harold, can you please take a look? Changelog: 2003-11-19 * InitOutput.c (ddxProcessArgument): Keep track of the -kb parameter * winwndproc.c (winWindowProc): Only discard the windows autorepeat messages if the XKB layer is not disabled. -- Alexander.Gottwald@s1999.tu-chemnitz.de http://www.gotti.org ICQ: 126018723 -------------- next part -------------- Index: InitOutput.c =================================================================== RCS file: /cvsroot/xoncygwin/xc/programs/Xserver/hw/xwin/InitOutput.c,v retrieving revision 1.5 diff -u -r1.5 InitOutput.c --- InitOutput.c 8 Nov 2003 20:18:59 -0000 1.5 +++ InitOutput.c 19 Nov 2003 16:31:16 -0000 @@ -1237,6 +1237,15 @@ return 1; } + /* + * Look for the '-kb' argument + */ + if (IS_OPTION ("-kb")) + { + g_cmdline.noXkbExtension = TRUE; + return 0; /* Let DIX parse this again */ + } + return 0; } Index: winwndproc.c =================================================================== RCS file: /cvsroot/xoncygwin/xc/programs/Xserver/hw/xwin/winwndproc.c,v retrieving revision 1.4 diff -u -r1.4 winwndproc.c --- winwndproc.c 8 Nov 2003 20:18:59 -0000 1.4 +++ winwndproc.c 19 Nov 2003 16:31:17 -0000 @@ -905,9 +905,15 @@ if (wParam == VK_LWIN || wParam == VK_RWIN) break; - /* Discard presses generated from Windows auto-repeat */ - if (lParam & (1<<30)) - return 0; + /* + * Discard presses generated from Windows auto-repeat + * ago: Only discard them if XKB is not disabled + */ + if (!g_winInfo.xkb.disable) + { + if (lParam & (1<<30)) + return 0; + } /* Discard fake Ctrl_L presses that precede AltGR on non-US keyboards */ if (winIsFakeCtrl_L (message, wParam, lParam)) From jay@JaySmith.com Wed Nov 19 17:38:00 2003 From: jay@JaySmith.com (Jay Smith) Date: Wed, 19 Nov 2003 17:38:00 -0000 Subject: xwinclip & startxdmcp.bat questions/problems Message-ID: <3FBBA9EE.4040705@JaySmith.com> Okay, I used the 'rcn' mirror to get xwinclip (and updated other stuff). [It sure would be nice if we knew which mirrors to use -- without having to look at every one.] I changed the command in *my own script* (startxwinJSA.bat), which had worked up to this point, to read: start XWin -once -nodecoration -query jsa.jaysmith.com start xwinclip.exe (My own script (startxwinJSA.bat) did a bunch of extra logging to see where errors were occuring, etc.) That did *not* work; I got no login whereas I had previously. So, I had to use the startxdmcp.bat script (given at bottom of this message) and added the above command changes to it. I am not sure if startxdmcp.bat came with the XFree stuff or where it came from (it is possible that my systems guy came up with it, but I doubt it). Apparently running 'start Xwin' in some other script causes 'startxdmcp.bat' to run so stuff was running twice??? Anyway, the problem now is that: a) I am still (same as before this upgrade) left with a DOS window for the startxdmcp that has to be manually closed. Annoying, but not terrible. b) I am additionally now left with *another* DOS window for xwinclip. When I try to close it, it says that the program will terminate. It is not desirable to have it there because I normally already run with 6-10 Windows windows running and the task bar is pretty full. There are tons of "error" messages in the xwinclip DOS window (but the copy/paste is working fine). c) Harold mentioned "restarting" xwinclip. I have not been able to find any instructions on how to do this. The xwinclip readme does not cover that. Please advise. Thanks for your help. Sorry to be a pain, but to the non-tech user some of this is tough to parse out. Jay ===== startxdmcp.bat ====== @echo off SET DISPLAY=127.0.0.1:0.0 SET REMOTE_HOST=192.168.1.10 SET CYGWIN_ROOT=\cygwin REM Cleanup after last run. if not exist %CYGWIN_ROOT%\tmp\.X11-unix\X0 goto CLEANUP-FINISH attrib -s %CYGWIN_ROOT%\tmp\.X11-unix\X0 del %CYGWIN_ROOT%\tmp\.X11-unix\X0 :CLEANUP-FINISH if exist %CYGWIN_ROOT%\tmp\.X11-unix rmdir %CYGWIN_ROOT%\tmp\.X11-unix REM Startup the X Server and attempt to connect to a remote XDM server. if "%OS%" == "Windows_NT" goto OS_NT REM Windows 95/98/Me echo startxdmcp.bat - Starting on Windows 95/98/Me goto STARTUP :OS_NT REM Windows NT/2000/XP echo startxdmcp.bat - Starting on Windows NT/2000/XP :STARTUP start XWin -once -nodecoration -query jsa.jaysmith.com start xwinclip.exe From alexander.gottwald@s1999.tu-chemnitz.de Wed Nov 19 18:38:00 2003 From: alexander.gottwald@s1999.tu-chemnitz.de (Alexander Gottwald) Date: Wed, 19 Nov 2003 18:38:00 -0000 Subject: Updated: XFree86-xserv-4.3.0-22 In-Reply-To: References: <1068549020528.tulitanssi.36802.w1Q4NRjiTPWoQQzb3m7sWA@luukku.com> <3FB0E0D5.7090505@msu.edu> <87ptfyvpbj.fsf@vzell-de.de.oracle.com> <3FB1123E.8090102@msu.edu> <87d6byvn9u.fsf@vzell-de.de.oracle.com> <87smktnyps.fsf@vzell-de.de.oracle.com> <3FBA8FE4.30902@users.sourceforge.net> Message-ID: On Wed, 19 Nov 2003, Alexander Gottwald wrote: > If this is the case I can add code to use the windows default autorepeat > settings to configure Xwin. But this will again change the old behavior > of Xwin and some users might be unhappy with it. Just a note to myself: Querying the parameters with SystemParametersInfo and SPI_GETKEYBOARDDELAY or SPI_GETKEYBOARDSPEED -- Alexander.Gottwald@s1999.tu-chemnitz.de http://www.gotti.org ICQ: 126018723 From dirk.goethals@alcatel.be Wed Nov 19 19:25:00 2003 From: dirk.goethals@alcatel.be (dirk.goethals@alcatel.be) Date: Wed, 19 Nov 2003 19:25:00 -0000 Subject: DDD 3.3.8 segmentation error, related to Motif? In-Reply-To: References: <3FB80677.8090004@alcatel.be> Message-ID: <3FBBC39B.3030009@alcatel.be> I gat a more recent version now, and I recompiled ddd. Earlier problem solved, new problem pops up: The executable ends with: Warning: This DDD requires a Motif 2.1 library (using Motif -1617156.-609) Continue at own risk. Internal error (Segmentation fault). VERSIONS: lesstif 0.93.91-4 OK XFree86-base 4.3.0-1 OK XFree86-bin 4.3.0-8 OK XFree86-bin-icons 4.3.0-5 OK XFree86-doc 4.3.0-1 OK XFree86-etc 4.3.0-6 OK XFree86-f100 4.2.0-3 OK XFree86-fcyr 4.2.0-3 OK XFree86-fenc 4.2.0-3 OK XFree86-fnts 4.2.0-3 OK XFree86-fscl 4.2.0-3 OK XFree86-fsrv 4.3.0-7 OK XFree86-html 4.3.0-1 OK XFree86-jdoc 4.3.0-1 OK XFree86-lib 4.3.0-1 OK XFree86-lib-compat 4.3.0-2 OK XFree86-man 4.3.0-2 OK XFree86-nest 4.3.0-5 OK XFree86-prog 4.3.0-12 OK XFree86-prt 4.3.0-5 OK XFree86-ps 4.3.0-1 OK XFree86-startup-scripts 4.2.0-5 OK XFree86-vfb 4.3.0-5 OK XFree86-xserv 4.3.0-23 OK XFree86-xwinclip 4.3.0-2 OK Note: Not all mirror sites provided by the setup.exe tool are providing the latest packages. bt08pm: /w/ cygcheck ddd Found: D:\Cygwin\usr\local\bin\ddd.exe D:/Cygwin/usr/local/bin/ddd.exe D:\Cygwin\usr\X11R6\bin\cygXm-2.dll D:\Cygwin\usr\X11R6\bin\cygX11-6.dll D:\Cygwin\bin\cygcygipc-2.dll D:\Cygwin\bin\cygwin1.dll C:\WINNT\System32\KERNEL32.dll C:\WINNT\System32\ntdll.dll D:\Cygwin\usr\X11R6\bin\cygXft-2.dll D:\Cygwin\usr\X11R6\bin\cygXext-6.dll D:\Cygwin\bin\cygfontconfig-1.dll D:\Cygwin\bin\cygexpat-0.dll D:\Cygwin\bin\cygfreetype-6.dll D:\Cygwin\bin\cygz.dll D:\Cygwin\usr\X11R6\bin\cygXp-6.dll D:\Cygwin\usr\X11R6\bin\cygXrender-1.dll D:\Cygwin\usr\X11R6\bin\cygXt-6.dll D:\Cygwin\usr\X11R6\bin\cygICE-6.dll D:\Cygwin\usr\X11R6\bin\cygSM-6.dll D:\Cygwin\bin\cygncurses7.dll D:\Cygwin\usr\X11R6\bin\cygXaw-7.dll D:\Cygwin\usr\X11R6\bin\cygXmu-6.dll D:\Cygwin\usr\X11R6\bin\cygXpm-4.dll Brian d wrote: >On Mon, 17 Nov 2003 dirk.goethals@alcatel.be wrote: > > > >>Ihe same problem with ddd 3.3.8 and GCC 3.3.1. >>I was able to compile ddd with GCC 3.2.3, but >>when launching ddd I gat following problem: >>(btw ddd --help works fine) >> >> >> >>Warning: XmPrimitive ClassInitialize: XmeTraitSet failed >>Error: attempt to add non-widget child "DropSiteManager" to parent "ddd" >>which supports only widgets >>Xt error (attempt to add non-widget child "DropSiteManager" to parent >>"ddd" which supports only widgets). >><<...>> >> DDD 3.3.8 (i686-pc-cygwin) gets `Segmentation fault' signal >><< >> >> >> >This is an Xfree86 issue. Redirecting to the proper list >(cygwin-xfree@cygwin.com). > >The error above was caused by the transition to a shared libXt/lesstif. >Please make sure your Xfree86 packages and lesstif are up to date. > > > From Alan.Coopersmith@Sun.COM Wed Nov 19 19:34:00 2003 From: Alan.Coopersmith@Sun.COM (Alan Coopersmith) Date: Wed, 19 Nov 2003 19:34:00 -0000 Subject: security, cvs, was Re: interface bindings of x-server In-Reply-To: <054901c3ae7f$16b6bc60$2000000a@schlepptopp> References: <3FBB269A.9080306@tungstengraphics.com> <054901c3ae7f$16b6bc60$2000000a@schlepptopp> Message-ID: <3FBBC5C8.9030808@Sun.COM> roland@webde wrote: > the only chance to get rid of it, is to use unix domain socket (via -nolisten tcp) OR to > add the option, to specify the interface bindings and be able to bind it to local loopback > ONLY. I`d prefer the second one. Why? What benefit does a TCP loopback connection provide over the Unix domain socket (which is generally faster on most OS'es)? > ahhhh - btw - i see: > on http://www.tightvnc.com/changelog-unix.html > 2001-01-17 01:55 const > Xvnc/programs/Xserver/hw/vnc/: init.c, rfb.h, sockets.c: Support for Xvnc -interface > option added (patch from Tim Waught). > > feature seems to be in tightvnc already - so maybe we need just some code transfer (since vnc is xfree86 > based) ? ;) Only if the original author of the tightvnc changes agrees to distribute under the X license instead of tightvnc's GPL. -- -Alan Coopersmith- alan.coopersmith@sun.com Sun Microsystems, Inc. - Sun Software Group User Experience Engineering: G11N: X Window System From ford@vss.fsi.com Wed Nov 19 19:42:00 2003 From: ford@vss.fsi.com (Brian Ford) Date: Wed, 19 Nov 2003 19:42:00 -0000 Subject: DDD 3.3.8 segmentation error, related to Motif? In-Reply-To: <3FBBC39B.3030009@alcatel.be> References: <3FB80677.8090004@alcatel.be> <3FBBC39B.3030009@alcatel.be> Message-ID: This is *still* a cygwin-xfree issue. Please do not CC cygwin@cygwin.com. Also, please do not CC me, as I read cygwin-xfree. Thanks. On Wed, 19 Nov 2003 dirk.goethals@alcatel.be wrote: > I gat a more recent version now, and I recompiled ddd. > Earlier problem solved, new problem pops up: > Did you update all of Cygwin, or just the following packages? An attached cygcheck.out as requested in http://www.cygwin.com/problems.html would be helpfull. > The executable ends with: > Warning: This DDD requires a Motif 2.1 library (using Motif > -1617156.-609) > Continue at own risk. > > Internal error (Segmentation fault). > WAG: Your cygwin1.dll is pre 1.5? > Brian Fordd wrote: > >On Mon, 17 Nov 2003 dirk.goethals@alcatel.be wrote: > >>Ihe same problem with ddd 3.3.8 and GCC 3.3.1. > >>I was able to compile ddd with GCC 3.2.3, but > >>when launching ddd I gat following problem: > >>(btw ddd --help works fine) > >> > >>Warning: XmPrimitive ClassInitialize: XmeTraitSet failed > >>Error: attempt to add non-widget child "DropSiteManager" to parent "ddd" > >>which supports only widgets > >>Xt error (attempt to add non-widget child "DropSiteManager" to parent > >>"ddd" which supports only widgets). > >><<...>> > >> DDD 3.3.8 (i686-pc-cygwin) gets `Segmentation fault' signal > >><< > >This is an Xfree86 issue. Redirecting to the proper list > >(cygwin-xfree@cygwin.com). > > > >The error above was caused by the transition to a shared libXt/lesstif. > >Please make sure your Xfree86 packages and lesstif are up to date. > > -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444 From huntharo@msu.edu Wed Nov 19 19:43:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Wed, 19 Nov 2003 19:43:00 -0000 Subject: DDD 3.3.8 segmentation error, related to Motif? In-Reply-To: <3FBBC39B.3030009@alcatel.be> References: <3FB80677.8090004@alcatel.be> <3FBBC39B.3030009@alcatel.be> Message-ID: <3FBBC7F3.3000508@msu.edu> DDD can work with LessTif, but you have to tell it that you want it to be compile for LessTif, and you may have to find a better distribution of the source than you have now (one with more recent patches for the LessTif support). The following are useful (I googled for "DDD LessTif"): http://rsusu1.rnd.runnet.ru/cgi-bin/info2html?(ddd)LessTif http://mail.gnu.org/archive/html/bug-ddd/2003-06/msg00009.html Hope that helps, Harold dirk.goethals@alcatel.be wrote: > I gat a more recent version now, and I recompiled ddd. > Earlier problem solved, new problem pops up: > > The executable ends with: > Warning: This DDD requires a Motif 2.1 library (using Motif > -1617156.-609) > Continue at own risk. > > Internal error (Segmentation fault). > > VERSIONS: > lesstif 0.93.91-4 OK > XFree86-base 4.3.0-1 OK > XFree86-bin 4.3.0-8 OK > XFree86-bin-icons 4.3.0-5 OK > XFree86-doc 4.3.0-1 OK > XFree86-etc 4.3.0-6 OK > XFree86-f100 4.2.0-3 OK > XFree86-fcyr 4.2.0-3 OK > XFree86-fenc 4.2.0-3 OK > XFree86-fnts 4.2.0-3 OK > XFree86-fscl 4.2.0-3 OK > XFree86-fsrv 4.3.0-7 OK > XFree86-html 4.3.0-1 OK > XFree86-jdoc 4.3.0-1 OK > XFree86-lib 4.3.0-1 OK > XFree86-lib-compat 4.3.0-2 OK > XFree86-man 4.3.0-2 OK > XFree86-nest 4.3.0-5 OK > XFree86-prog 4.3.0-12 OK > XFree86-prt 4.3.0-5 OK > XFree86-ps 4.3.0-1 OK > XFree86-startup-scripts 4.2.0-5 OK > XFree86-vfb 4.3.0-5 OK > XFree86-xserv 4.3.0-23 OK > XFree86-xwinclip 4.3.0-2 OK > > Note: Not all mirror sites provided by the setup.exe tool > are providing the latest packages. > > > bt08pm: /w/ cygcheck ddd > Found: D:\Cygwin\usr\local\bin\ddd.exe > D:/Cygwin/usr/local/bin/ddd.exe > D:\Cygwin\usr\X11R6\bin\cygXm-2.dll > D:\Cygwin\usr\X11R6\bin\cygX11-6.dll > D:\Cygwin\bin\cygcygipc-2.dll > D:\Cygwin\bin\cygwin1.dll > C:\WINNT\System32\KERNEL32.dll > C:\WINNT\System32\ntdll.dll > D:\Cygwin\usr\X11R6\bin\cygXft-2.dll > D:\Cygwin\usr\X11R6\bin\cygXext-6.dll > D:\Cygwin\bin\cygfontconfig-1.dll > D:\Cygwin\bin\cygexpat-0.dll > D:\Cygwin\bin\cygfreetype-6.dll > D:\Cygwin\bin\cygz.dll > D:\Cygwin\usr\X11R6\bin\cygXp-6.dll > D:\Cygwin\usr\X11R6\bin\cygXrender-1.dll > D:\Cygwin\usr\X11R6\bin\cygXt-6.dll > D:\Cygwin\usr\X11R6\bin\cygICE-6.dll > D:\Cygwin\usr\X11R6\bin\cygSM-6.dll > D:\Cygwin\bin\cygncurses7.dll > D:\Cygwin\usr\X11R6\bin\cygXaw-7.dll > D:\Cygwin\usr\X11R6\bin\cygXmu-6.dll > D:\Cygwin\usr\X11R6\bin\cygXpm-4.dll > > > Brian d wrote: > >> On Mon, 17 Nov 2003 dirk.goethals@alcatel.be wrote: >> >> >> >>> Ihe same problem with ddd 3.3.8 and GCC 3.3.1. >>> I was able to compile ddd with GCC 3.2.3, but >>> when launching ddd I gat following problem: >>> (btw ddd --help works fine) >>> >>> >> >>> Warning: XmPrimitive ClassInitialize: XmeTraitSet failed >>> Error: attempt to add non-widget child "DropSiteManager" to parent "ddd" >>> which supports only widgets >>> Xt error (attempt to add non-widget child "DropSiteManager" to parent >>> "ddd" which supports only widgets). >>> <<...>> >>> DDD 3.3.8 (i686-pc-cygwin) gets `Segmentation fault' signal >>> << >>> >>> >> >> This is an Xfree86 issue. Redirecting to the proper list >> (cygwin-xfree@cygwin.com). >> >> The error above was caused by the transition to a shared libXt/lesstif. >> Please make sure your Xfree86 packages and lesstif are up to date. >> >> >> > From devzero@web.de Wed Nov 19 21:12:00 2003 From: devzero@web.de (roland@webde) Date: Wed, 19 Nov 2003 21:12:00 -0000 Subject: security, cvs, was Re: interface bindings of x-server References: <3FBB269A.9080306@tungstengraphics.com> <054901c3ae7f$16b6bc60$2000000a@schlepptopp> <3FBBC5C8.9030808@Sun.COM> Message-ID: <05ac01c3aee2$528dea20$2000000a@schlepptopp> hi ! > > the only chance to get rid of it, is to use unix domain socket (via -nolisten tcp) OR to > > add the option, to specify the interface bindings and be able to bind it to local loopback > > ONLY. I`d prefer the second one. > > Why? What benefit does a TCP loopback connection provide over the Unix > domain socket (which is generally faster on most OS'es)? the benefit would be compatibility, IMHO. think of a scenario where cygwin/xfree86 + native win32 ssh client are combined. i`m sure, this isn`t too exotic - e.g. i know a _LOT_ of people who do ssh-tunneling via native win32 ssh client "putty" in combination with a local separate xserver on their windoze box. does anybody know if any "native" or "non cygwin based" ssh client on windows is able to use cygwin/xfree86 unix domain socket on win32 machine? i`m not sure - but i don`t think so. but, anyway - being able to bind to 127.0.0.1 would be just ONE "special case" of a more general "dedicated interface binding feature". nobody says , that you _should_ use 127.0.0.1 - but you always would have an option, to do so. i`m sysadmin - i like options. ;) > > feature seems to be in tightvnc already - so maybe we need just some code transfer (since vnc is xfree86 > > based) ? ;) > > Only if the original author of the tightvnc changes agrees to > distribute under the X license instead of tightvnc's GPL. oh - pardon! sure! thanks for bringing that back to my mind that this needs to be adressed! i`m currently digging into tightvnc to get sure it IS the appropriate code at all. regards roland From kirk.woellert@ngc.com Wed Nov 19 21:36:00 2003 From: kirk.woellert@ngc.com (Woellert, Kirk D.) Date: Wed, 19 Nov 2003 21:36:00 -0000 Subject: XWin works on Win2K but not on some WinXP clients [FIXED] Message-ID: nslookup from the linux box reported the correct machine name for the WinXP client. Also the guy with the Win2K machine that can connect does not have his IP address in the hosts file. nevertheless did the test Igor suggested. # Do not remove the following line, or various programs # that require network functionality will fail. 127.0.0.1 localhost.localdomain localhost 137.51.14.130 gaia.ad.tasc.com gaia 137.51.14.56 lyceum.ad.tasc.com lyceum 137.51.14.54 ngc-d4o1xu3vg29.ad.tasc.com ngc-d4o1xu3vg29 ~ ~ ~ ~ ~ "hosts" 8L, 283C written [kdw@gaia /etc]# kill -USR1 `cat /var/run/gdm.pid` [kdw@gaia /etc]# telinit 3 [kdw@gaia /etc]# telinit 5 [kdw@gaia /etc]# [kdw@gaia /etc]# nslookup 137.51.14.54 Note: nslookup is deprecated and may be removed from future releases. Consider using the `dig' or `host' programs instead. Run nslookup with the `-sil[ent]' option to prevent this message from appearing. Server: 137.51.60.36 Address: 137.51.60.36#53 54.14.51.137.in-addr.arpa name = ngc-d4o1xu3vg29. [kdw@gaia /etc]# -----Original Message----- From: Igor Pechtchanski [mailto:pechtcha@cs.nyu.edu] Sent: Tuesday, November 18, 2003 4:07 PM To: cygwin-xfree@cygwin.com Cc: Woellert, Kirk D. Subject: Re: XWin works on Win2K but not on some WinXP clients [FIXED] Kirk, Check /var/log/messages and see if there are any from gdm. This may be a DNS lookup issue (i.e., your XP machine is not registered in DNS, or registered, but not with the correct name). Confirm by "nslookup YOUR_IP" from the Linux machine. If it is a DNS issue, try adding your XP machine to /etc/hosts and restarting gdm ("kill -USR1 `cat /var/run/gdm.pid`"). Igor On Tue, 18 Nov 2003, Harold L Hunt II wrote: > So echo on UDP port 177 works fine. This is not good. There must be > something else in the gdm conf on the linux box that explicitly denies > gdm connections from the Windows XP machine's IP addresses, since it > worked fine when using 10.0.0.x addresses. Anyway you can change the IP > of the XP machine to one not previously used as a test? > > Harold > > Woellert, Kirk D. wrote: > > > 1. Edited the echo-upd file in the xinetd.d folder. Changed the default port > > from "7" to "177"... > > > > [root@gaia xinetd.d]# cat echo-udp > > # default: off > > # description: An xinetd internal service which echo's characters back to > > clients. \ > > # This is the udp version. > > service echo > > { > > disable = no > > type = INTERNAL UNLISTED > > id = echo-dgram > > socket_type = dgram > > protocol = udp > > user = root > > wait = yes > > port = 177 > > } > > [root@gaia xinetd.d]# > > > > 2. Did a grep just to ensure gdm was not gonna respond to my upd packets... > > > > [root@gaia xinetd.d]# ps -ef |grep xdm > > root 2328 1912 0 18:12 pts/0 00:00:00 grep xdm > > [root@gaia xinetd.d]# > > > > 3. Ran a upd echo test from the WinXP client to the Linux box using a Java > > echo client.... > > > > C:\Bin>java -jar UDPEchoClient.jar 137.51.14.130:177 > > 64 bytes from 137.51.14.130: seq no 0 time=0 ms > > 64 bytes from 137.51.14.130: seq no 1 time=0 ms > > 64 bytes from 137.51.14.130: seq no 2 time=0 ms > > 64 bytes from 137.51.14.130: seq no 3 time=0 ms > > 64 bytes from 137.51.14.130: seq no 4 time=0 ms > > 64 bytes from 137.51.14.130: seq no 5 time=0 ms > > 64 bytes from 137.51.14.130: seq no 6 time=0 ms > > 64 bytes from 137.51.14.130: seq no 7 time=0 ms > > 64 bytes from 137.51.14.130: seq no 8 time=0 ms > > 64 bytes from 137.51.14.130: seq no 9 time=0 ms > > 64 bytes from 137.51.14.130: seq no 10 time=0 ms > > 64 bytes from 137.51.14.130: seq no 11 time=0 ms > > 64 bytes from 137.51.14.130: seq no 12 time=0 ms > > 64 bytes from 137.51.14.130: seq no 13 time=0 ms > > 64 bytes from 137.51.14.130: seq no 14 time=0 ms > > 64 bytes from 137.51.14.130: seq no 15 time=0 ms > > 64 bytes from 137.51.14.130: seq no 16 time=0 ms > > 64 bytes from 137.51.14.130: seq no 17 time=0 ms > > 64 bytes from 137.51.14.130: seq no 18 time=0 ms > > 64 bytes from 137.51.14.130: seq no 19 time=0 ms > > 64 bytes from 137.51.14.130: seq no 20 time=0 ms > > 64 bytes from 137.51.14.130: seq no 21 time=0 ms > > 64 bytes from 137.51.14.130: seq no 22 time=0 ms > > 64 bytes from 137.51.14.130: seq no 23 time=0 ms > > 64 bytes from 137.51.14.130: seq no 24 time=0 ms > > 64 bytes from 137.51.14.130: seq no 25 time=0 ms > > 64 bytes from 137.51.14.130: seq no 26 time=0 ms > > 64 bytes from 137.51.14.130: seq no 27 time=0 ms > > 64 bytes from 137.51.14.130: seq no 28 time=0 ms > > 64 bytes from 137.51.14.130: seq no 29 time=0 ms > > 64 bytes from 137.51.14.130: seq no 30 time=0 ms > > 64 bytes from 137.51.14.130: seq no 31 time=0 ms > > 32 packets transmitted, 32 packets received, 0% packet loss > > round-trip min/avg/max = 0/0.0/0 ms > > > > C:\Bin> > > > > Having trouble getting Java to run on the Linux box, so I could not complete > > the echo test from the Linux host to the WinXP client. > > > > -----Original Message----- > > From: Harold L Hunt II [mailto:huntharo@msu.edu] > > Sent: Monday, November 17, 2003 4:41 PM > > To: cygwin-xfree@cygwin.com > > Subject: Re: XWin works on Win2K but not on some WinXP clients [FIXED] > > > > > > Kirk, > > > > Well then, I suppose the next step would be to do a "telinit 3" (to stop > > gdm), then edit xinetd conf file to run "echo" on UDP port 177, restart > > xinetd, then use that udp echo client that we found to test if echo > > works from the Windows XP machine plugged into its normal jack to gaia > > plugged into its normal jack. We know that echo worked on UDP port 7, > > but proving that it does or does not work on UDP port 177 would tell us > > if they know what they are talking about :) > > > > Harold > > > > Woellert, Kirk D. wrote: > > > > > >>I aksed corporate IS if they were doing an port blocking/filtering within > >>our LAN. They replied: > >> > >>"There should be no port blocking within the corp. LAN. - only in/out > >>to the Internet and in/out of DMZs." > >> > >> > >>-----Original Message----- > >>From: Harold L Hunt II [mailto:huntharo@msu.edu] > >>Sent: Monday, November 17, 2003 10:45 AM > >>To: cygwin-xfree@cygwin.com > >>Subject: Re: XWin works on Win2K but not on some WinXP clients [FIXED] > >> > >> > >>Kirk Woellert's problem with XP clients has been fixed, sort of. > >> > >>I talked to him on the phone for a few hours on Friday and walked him > >>through some debugging. > >> > >> > >>Here is what we found out: > >> > >>1) We could ssh from XP to Linux (TCP protocol). > >> > >>2) We could tunnel X apps over ssh from the Linux box to display on the > >>XP box (TCP protocol). > >> > >>3) We could natively display X apps by exporting DISPLAY on Linux box, > >>pointed to XP box (TCP protocol). > >> > >>4) We could not (nor could X-Win32) get an XDMCP login on the XP box for > >>the Linux box (UDP protocol). > >> > >>5) We could run the echo service on the Linux box on port 7 and use a > >>Java echo client for UDP to verify that UDP to Linux box worked (UDP > >>protocol). > >> > >>6) It was revealed that there are really two parts of the network here. > >> Not much is known about whether port blocking is in effect between the > >>two parts. > >> > >>7) Removing the troubled hosts from the network and hooking them to a > >>stand-alone hub with assigned IP addresses allowed XDMCP to work. > >> > >>8) We thus confirmed in #5 that UDP was not blocked in general, but #7 > >>indicates that UDP port 177 is blocked between the segments. It turns > >>out that all of the Windows 2000 machines were on one "segment", while > >>the Windows XP machines were on another "segment". The problem was not > >>the OS, it was that one segment has UDP port 177 blocked. > >> > >> > >>Thus, we determined that the problem is in the network that the machines > >>are attached to; this may or may not be by design. In any case, it > >>isn't a problem with Cygwin/X. :) > >> > >>Harold -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_ pechtcha@cs.nyu.edu ZZZzz /,`.-'`' -. ;-;;,_ igor@watson.ibm.com |,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 From pechtcha@cs.nyu.edu Wed Nov 19 21:39:00 2003 From: pechtcha@cs.nyu.edu (Igor Pechtchanski) Date: Wed, 19 Nov 2003 21:39:00 -0000 Subject: XWin works on Win2K but not on some WinXP clients [FIXED] In-Reply-To: References: <3FBA802C.7030500@msu.edu> Message-ID: Kirk, Try to open an XDMCP session from your PC and see what that adds to /var/log/messages (don't scan the whole thing, the relevant messages will be appended). See if it shows something like Nov 17 17:03:10 gaia gdm[XXXX]: gdm_auth_secure_display: Error getting hentry for XPmachine Nov 17 17:03:10 gaia gdm[XXXX]: gdm_xdmcp_display_alloc: Error setting up cookies for XPmachine:0 In any case, there should be some indication that gdm received a connection request from your machine, even if it was refused. Igor On Tue, 18 Nov 2003, Igor Pechtchanski wrote: > Kirk, > > Check /var/log/messages and see if there are any from gdm. This may be a > DNS lookup issue (i.e., your XP machine is not registered in DNS, or > registered, but not with the correct name). Confirm by "nslookup YOUR_IP" > from the Linux machine. If it is a DNS issue, try adding your XP machine > to /etc/hosts and restarting gdm ("kill -USR1 `cat /var/run/gdm.pid`"). > Igor > > On Tue, 18 Nov 2003, Harold L Hunt II wrote: > > > So echo on UDP port 177 works fine. This is not good. There must be > > something else in the gdm conf on the linux box that explicitly denies > > gdm connections from the Windows XP machine's IP addresses, since it > > worked fine when using 10.0.0.x addresses. Anyway you can change the IP > > of the XP machine to one not previously used as a test? > > > > Harold > > > > Woellert, Kirk D. wrote: > > > > > 1. Edited the echo-upd file in the xinetd.d folder. Changed the default port > > > from "7" to "177"... > > > > > > [root@gaia xinetd.d]# cat echo-udp > > > # default: off > > > # description: An xinetd internal service which echo's characters back to > > > clients. \ > > > # This is the udp version. > > > service echo > > > { > > > disable = no > > > type = INTERNAL UNLISTED > > > id = echo-dgram > > > socket_type = dgram > > > protocol = udp > > > user = root > > > wait = yes > > > port = 177 > > > } > > > [root@gaia xinetd.d]# > > > > > > 2. Did a grep just to ensure gdm was not gonna respond to my upd packets... > > > > > > [root@gaia xinetd.d]# ps -ef |grep xdm > > > root 2328 1912 0 18:12 pts/0 00:00:00 grep xdm > > > [root@gaia xinetd.d]# > > > > > > 3. Ran a upd echo test from the WinXP client to the Linux box using a Java > > > echo client.... > > > > > > C:\Bin>java -jar UDPEchoClient.jar 137.51.14.130:177 > > > 64 bytes from 137.51.14.130: seq no 0 time=0 ms > > > 64 bytes from 137.51.14.130: seq no 1 time=0 ms > > > 64 bytes from 137.51.14.130: seq no 2 time=0 ms > > > 64 bytes from 137.51.14.130: seq no 3 time=0 ms > > > 64 bytes from 137.51.14.130: seq no 4 time=0 ms > > > 64 bytes from 137.51.14.130: seq no 5 time=0 ms > > > 64 bytes from 137.51.14.130: seq no 6 time=0 ms > > > 64 bytes from 137.51.14.130: seq no 7 time=0 ms > > > 64 bytes from 137.51.14.130: seq no 8 time=0 ms > > > 64 bytes from 137.51.14.130: seq no 9 time=0 ms > > > 64 bytes from 137.51.14.130: seq no 10 time=0 ms > > > 64 bytes from 137.51.14.130: seq no 11 time=0 ms > > > 64 bytes from 137.51.14.130: seq no 12 time=0 ms > > > 64 bytes from 137.51.14.130: seq no 13 time=0 ms > > > 64 bytes from 137.51.14.130: seq no 14 time=0 ms > > > 64 bytes from 137.51.14.130: seq no 15 time=0 ms > > > 64 bytes from 137.51.14.130: seq no 16 time=0 ms > > > 64 bytes from 137.51.14.130: seq no 17 time=0 ms > > > 64 bytes from 137.51.14.130: seq no 18 time=0 ms > > > 64 bytes from 137.51.14.130: seq no 19 time=0 ms > > > 64 bytes from 137.51.14.130: seq no 20 time=0 ms > > > 64 bytes from 137.51.14.130: seq no 21 time=0 ms > > > 64 bytes from 137.51.14.130: seq no 22 time=0 ms > > > 64 bytes from 137.51.14.130: seq no 23 time=0 ms > > > 64 bytes from 137.51.14.130: seq no 24 time=0 ms > > > 64 bytes from 137.51.14.130: seq no 25 time=0 ms > > > 64 bytes from 137.51.14.130: seq no 26 time=0 ms > > > 64 bytes from 137.51.14.130: seq no 27 time=0 ms > > > 64 bytes from 137.51.14.130: seq no 28 time=0 ms > > > 64 bytes from 137.51.14.130: seq no 29 time=0 ms > > > 64 bytes from 137.51.14.130: seq no 30 time=0 ms > > > 64 bytes from 137.51.14.130: seq no 31 time=0 ms > > > 32 packets transmitted, 32 packets received, 0% packet loss > > > round-trip min/avg/max = 0/0.0/0 ms > > > > > > C:\Bin> > > > > > > Having trouble getting Java to run on the Linux box, so I could not complete > > > the echo test from the Linux host to the WinXP client. > > > > > > -----Original Message----- > > > From: Harold L Hunt II [mailto:huntharo@msu.edu] > > > Sent: Monday, November 17, 2003 4:41 PM > > > To: cygwin-xfree@cygwin.com > > > Subject: Re: XWin works on Win2K but not on some WinXP clients [FIXED] > > > > > > > > > Kirk, > > > > > > Well then, I suppose the next step would be to do a "telinit 3" (to stop > > > gdm), then edit xinetd conf file to run "echo" on UDP port 177, restart > > > xinetd, then use that udp echo client that we found to test if echo > > > works from the Windows XP machine plugged into its normal jack to gaia > > > plugged into its normal jack. We know that echo worked on UDP port 7, > > > but proving that it does or does not work on UDP port 177 would tell us > > > if they know what they are talking about :) > > > > > > Harold > > > > > > Woellert, Kirk D. wrote: > > > > > > > > >>I aksed corporate IS if they were doing an port blocking/filtering within > > >>our LAN. They replied: > > >> > > >>"There should be no port blocking within the corp. LAN. - only in/out > > >>to the Internet and in/out of DMZs." > > >> > > >> > > >>-----Original Message----- > > >>From: Harold L Hunt II [mailto:huntharo@msu.edu] > > >>Sent: Monday, November 17, 2003 10:45 AM > > >>To: cygwin-xfree@cygwin.com > > >>Subject: Re: XWin works on Win2K but not on some WinXP clients [FIXED] > > >> > > >> > > >>Kirk Woellert's problem with XP clients has been fixed, sort of. > > >> > > >>I talked to him on the phone for a few hours on Friday and walked him > > >>through some debugging. > > >> > > >> > > >>Here is what we found out: > > >> > > >>1) We could ssh from XP to Linux (TCP protocol). > > >> > > >>2) We could tunnel X apps over ssh from the Linux box to display on the > > >>XP box (TCP protocol). > > >> > > >>3) We could natively display X apps by exporting DISPLAY on Linux box, > > >>pointed to XP box (TCP protocol). > > >> > > >>4) We could not (nor could X-Win32) get an XDMCP login on the XP box for > > >>the Linux box (UDP protocol). > > >> > > >>5) We could run the echo service on the Linux box on port 7 and use a > > >>Java echo client for UDP to verify that UDP to Linux box worked (UDP > > >>protocol). > > >> > > >>6) It was revealed that there are really two parts of the network here. > > >> Not much is known about whether port blocking is in effect between the > > >>two parts. > > >> > > >>7) Removing the troubled hosts from the network and hooking them to a > > >>stand-alone hub with assigned IP addresses allowed XDMCP to work. > > >> > > >>8) We thus confirmed in #5 that UDP was not blocked in general, but #7 > > >>indicates that UDP port 177 is blocked between the segments. It turns > > >>out that all of the Windows 2000 machines were on one "segment", while > > >>the Windows XP machines were on another "segment". The problem was not > > >>the OS, it was that one segment has UDP port 177 blocked. > > >> > > >> > > >>Thus, we determined that the problem is in the network that the machines > > >>are attached to; this may or may not be by design. In any case, it > > >>isn't a problem with Cygwin/X. :) > > >> > > >>Harold > > -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_ pechtcha@cs.nyu.edu ZZZzz /,`.-'`' -. ;-;;,_ igor@watson.ibm.com |,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 From huntharo@msu.edu Wed Nov 19 21:41:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Wed, 19 Nov 2003 21:41:00 -0000 Subject: XWin works on Win2K but not on some WinXP clients [FIXED] In-Reply-To: References: Message-ID: <3FBBE371.5000300@msu.edu> Kirk, Did you then do a test login with startxdmcp.bat with the hosts setup? Harold Woellert, Kirk D. wrote: > nslookup from the linux box reported the correct machine name for the WinXP > client. Also the guy with the Win2K machine that can connect does not have > his IP address in the hosts file. > > nevertheless did the test Igor suggested. > > # Do not remove the following line, or various programs > # that require network functionality will fail. > 127.0.0.1 localhost.localdomain localhost > 137.51.14.130 gaia.ad.tasc.com gaia > 137.51.14.56 lyceum.ad.tasc.com lyceum > 137.51.14.54 ngc-d4o1xu3vg29.ad.tasc.com ngc-d4o1xu3vg29 > ~ > ~ > ~ > ~ > ~ > "hosts" 8L, 283C written > [kdw@gaia /etc]# kill -USR1 `cat /var/run/gdm.pid` > [kdw@gaia /etc]# telinit 3 > [kdw@gaia /etc]# telinit 5 > [kdw@gaia /etc]# > > [kdw@gaia /etc]# nslookup 137.51.14.54 > Note: nslookup is deprecated and may be removed from future releases. > Consider using the `dig' or `host' programs instead. Run nslookup with > the `-sil[ent]' option to prevent this message from appearing. > Server: 137.51.60.36 > Address: 137.51.60.36#53 > > 54.14.51.137.in-addr.arpa name = ngc-d4o1xu3vg29. > > [kdw@gaia /etc]# > > > -----Original Message----- > From: Igor Pechtchanski [mailto:pechtcha@cs.nyu.edu] > Sent: Tuesday, November 18, 2003 4:07 PM > To: cygwin-xfree@cygwin.com > Cc: Woellert, Kirk D. > Subject: Re: XWin works on Win2K but not on some WinXP clients [FIXED] > > > Kirk, > > Check /var/log/messages and see if there are any from gdm. This may be a > DNS lookup issue (i.e., your XP machine is not registered in DNS, or > registered, but not with the correct name). Confirm by "nslookup YOUR_IP" > from the Linux machine. If it is a DNS issue, try adding your XP machine > to /etc/hosts and restarting gdm ("kill -USR1 `cat /var/run/gdm.pid`"). > Igor > > On Tue, 18 Nov 2003, Harold L Hunt II wrote: > > >>So echo on UDP port 177 works fine. This is not good. There must be >>something else in the gdm conf on the linux box that explicitly denies >>gdm connections from the Windows XP machine's IP addresses, since it >>worked fine when using 10.0.0.x addresses. Anyway you can change the IP >>of the XP machine to one not previously used as a test? >> >>Harold >> >>Woellert, Kirk D. wrote: >> >> >>>1. Edited the echo-upd file in the xinetd.d folder. Changed the default > > port > >>>from "7" to "177"... >>> >>>[root@gaia xinetd.d]# cat echo-udp >>># default: off >>># description: An xinetd internal service which echo's characters back > > to > >>>clients. \ >>># This is the udp version. >>>service echo >>>{ >>> disable = no >>> type = INTERNAL UNLISTED >>> id = echo-dgram >>> socket_type = dgram >>> protocol = udp >>> user = root >>> wait = yes >>> port = 177 >>>} >>>[root@gaia xinetd.d]# >>> >>>2. Did a grep just to ensure gdm was not gonna respond to my upd > > packets... > >>>[root@gaia xinetd.d]# ps -ef |grep xdm >>>root 2328 1912 0 18:12 pts/0 00:00:00 grep xdm >>>[root@gaia xinetd.d]# >>> >>>3. Ran a upd echo test from the WinXP client to the Linux box using a > > Java > >>>echo client.... >>> >>>C:\Bin>java -jar UDPEchoClient.jar 137.51.14.130:177 >>>64 bytes from 137.51.14.130: seq no 0 time=0 ms >>>64 bytes from 137.51.14.130: seq no 1 time=0 ms >>>64 bytes from 137.51.14.130: seq no 2 time=0 ms >>>64 bytes from 137.51.14.130: seq no 3 time=0 ms >>>64 bytes from 137.51.14.130: seq no 4 time=0 ms >>>64 bytes from 137.51.14.130: seq no 5 time=0 ms >>>64 bytes from 137.51.14.130: seq no 6 time=0 ms >>>64 bytes from 137.51.14.130: seq no 7 time=0 ms >>>64 bytes from 137.51.14.130: seq no 8 time=0 ms >>>64 bytes from 137.51.14.130: seq no 9 time=0 ms >>>64 bytes from 137.51.14.130: seq no 10 time=0 ms >>>64 bytes from 137.51.14.130: seq no 11 time=0 ms >>>64 bytes from 137.51.14.130: seq no 12 time=0 ms >>>64 bytes from 137.51.14.130: seq no 13 time=0 ms >>>64 bytes from 137.51.14.130: seq no 14 time=0 ms >>>64 bytes from 137.51.14.130: seq no 15 time=0 ms >>>64 bytes from 137.51.14.130: seq no 16 time=0 ms >>>64 bytes from 137.51.14.130: seq no 17 time=0 ms >>>64 bytes from 137.51.14.130: seq no 18 time=0 ms >>>64 bytes from 137.51.14.130: seq no 19 time=0 ms >>>64 bytes from 137.51.14.130: seq no 20 time=0 ms >>>64 bytes from 137.51.14.130: seq no 21 time=0 ms >>>64 bytes from 137.51.14.130: seq no 22 time=0 ms >>>64 bytes from 137.51.14.130: seq no 23 time=0 ms >>>64 bytes from 137.51.14.130: seq no 24 time=0 ms >>>64 bytes from 137.51.14.130: seq no 25 time=0 ms >>>64 bytes from 137.51.14.130: seq no 26 time=0 ms >>>64 bytes from 137.51.14.130: seq no 27 time=0 ms >>>64 bytes from 137.51.14.130: seq no 28 time=0 ms >>>64 bytes from 137.51.14.130: seq no 29 time=0 ms >>>64 bytes from 137.51.14.130: seq no 30 time=0 ms >>>64 bytes from 137.51.14.130: seq no 31 time=0 ms >>>32 packets transmitted, 32 packets received, 0% packet loss >>>round-trip min/avg/max = 0/0.0/0 ms >>> >>>C:\Bin> >>> >>>Having trouble getting Java to run on the Linux box, so I could not > > complete > >>>the echo test from the Linux host to the WinXP client. >>> >>>-----Original Message----- >>>From: Harold L Hunt II [mailto:huntharo@msu.edu] >>>Sent: Monday, November 17, 2003 4:41 PM >>>To: cygwin-xfree@cygwin.com >>>Subject: Re: XWin works on Win2K but not on some WinXP clients [FIXED] >>> >>> >>>Kirk, >>> >>>Well then, I suppose the next step would be to do a "telinit 3" (to stop >>>gdm), then edit xinetd conf file to run "echo" on UDP port 177, restart >>>xinetd, then use that udp echo client that we found to test if echo >>>works from the Windows XP machine plugged into its normal jack to gaia >>>plugged into its normal jack. We know that echo worked on UDP port 7, >>>but proving that it does or does not work on UDP port 177 would tell us >>>if they know what they are talking about :) >>> >>>Harold >>> >>>Woellert, Kirk D. wrote: >>> >>> >>> >>>>I aksed corporate IS if they were doing an port blocking/filtering > > within > >>>>our LAN. They replied: >>>> >>>>"There should be no port blocking within the corp. LAN. - only in/out >>>>to the Internet and in/out of DMZs." >>>> >>>> >>>>-----Original Message----- >>>>From: Harold L Hunt II [mailto:huntharo@msu.edu] >>>>Sent: Monday, November 17, 2003 10:45 AM >>>>To: cygwin-xfree@cygwin.com >>>>Subject: Re: XWin works on Win2K but not on some WinXP clients [FIXED] >>>> >>>> >>>>Kirk Woellert's problem with XP clients has been fixed, sort of. >>>> >>>>I talked to him on the phone for a few hours on Friday and walked him >>>>through some debugging. >>>> >>>> >>>>Here is what we found out: >>>> >>>>1) We could ssh from XP to Linux (TCP protocol). >>>> >>>>2) We could tunnel X apps over ssh from the Linux box to display on the >>>>XP box (TCP protocol). >>>> >>>>3) We could natively display X apps by exporting DISPLAY on Linux box, >>>>pointed to XP box (TCP protocol). >>>> >>>>4) We could not (nor could X-Win32) get an XDMCP login on the XP box for >>>>the Linux box (UDP protocol). >>>> >>>>5) We could run the echo service on the Linux box on port 7 and use a >>>>Java echo client for UDP to verify that UDP to Linux box worked (UDP >>>>protocol). >>>> >>>>6) It was revealed that there are really two parts of the network here. >>>> Not much is known about whether port blocking is in effect between the >>>>two parts. >>>> >>>>7) Removing the troubled hosts from the network and hooking them to a >>>>stand-alone hub with assigned IP addresses allowed XDMCP to work. >>>> >>>>8) We thus confirmed in #5 that UDP was not blocked in general, but #7 >>>>indicates that UDP port 177 is blocked between the segments. It turns >>>>out that all of the Windows 2000 machines were on one "segment", while >>>>the Windows XP machines were on another "segment". The problem was not >>>>the OS, it was that one segment has UDP port 177 blocked. >>>> >>>> >>>>Thus, we determined that the problem is in the network that the machines >>>>are attached to; this may or may not be by design. In any case, it >>>>isn't a problem with Cygwin/X. :) >>>> >>>>Harold > > From ditasaka@silverbacksystems.com Wed Nov 19 23:40:00 2003 From: ditasaka@silverbacksystems.com (Dai Itasaka) Date: Wed, 19 Nov 2003 23:40:00 -0000 Subject: twm takes no control Message-ID: <004701c3aef6$6b0eb660$7b05000a@corp.silverbacksystems.com> Quoted is what I posted as "no key input" last month. Today I did the update and now twm doesn't take any key input anymore. I can't move the keyboard focus from one window to another by pressing the f.downiconmgr or the likes. In fact, no key command (f.iconify, f.raiselower, f.zoom....) works now. My preference is to use Ctrl key plus Shift key plus a letter key. For example, f.downiconmgr is Ctrl+Shift+j. In .twmrc, it is like "j" = c|s : all : f.downiconmgr It looks as if this Shift key is not detected as pressed. So instead of taking it as Ctrl-Shift-x, it takes as Ctrl-x, and it is passed through twm to whatever application that has the focus at the time because it is no longer interpreted as a valid twm command key. This was working before. What wasn't working is xterm, not twm. But now, twm isn't. Dai ) My startxwin.sh gives me the root window and an xterm window in it. ) I login to a remote host from this xterm after doing xhost for it. ) From there, I invoke xterm specifying the local PC as the display. ) Now I have two xterm windows here: one invoked locally, the other ) invoked from the remote host. ) ) TWM is my window manager. My preference is to show the IconManager ) at the upper right hand corner of the root, in which I can move ) from one icon to the next by pressing the keyboard combo specified ) in the ~/.twmrc as "f.downiconmgr" or "f.upiconmgr". If I press ) the key combo, no matter where the mouse cursor is at, it jumps ) to the IconManager area and points to the window that has the keyboard ) focus at the time. As I press the "up" or the "down" key, the mouse ) cursor jumps to one icon up or down, and the keyboard focus moves ) to the corresponding window at once. This is the equivalent of ) MS Windows' Alt-Tab for me in X(no autoraise by default though). ) This is how I move the keyboard focus from one window to another. ) I can't live without this as I have been doing this for over 10 ) years now. I'm so accustomed to it that I sometimes do it in MS ) Windows. ) ) Now, with the latest Cygwin install, I still can move the keyboard ) focus by pressing the "up" or "down" key, thus I can toggle the ) keyboard focus between the two xterm windows I mentioned above. ) But, the xterm that is locally executed(cygwin xterm) doesnt take ) any key input unless I move the mouse cursor over the xterm ) window area, while the one that is remotely executed can take key ) inputs as usual without moving a mouse(the mouse cursor stays in ) the IconManager area). ) ) Until the one before the latest(XFree86-xserv-4.3.0-18?), this was ) not the case. I was able to move around AND TYPE. Something that ) was added since then broke this capability. ) ) From dododge@dododge.net Wed Nov 19 23:49:00 2003 From: dododge@dododge.net (Dave Dodge) Date: Wed, 19 Nov 2003 23:49:00 -0000 Subject: security, cvs, was Re: interface bindings of x-server In-Reply-To: <3FBBC5C8.9030808@Sun.COM> Message-ID: On Wed, 19 Nov 2003, Alan Coopersmith wrote: > roland@webde wrote: > > the only chance to get rid of it, is to use unix domain socket > > (via -nolisten tcp) OR to add the option, to specify the interface > > bindings and be able to bind it to local loopback ONLY. I`d prefer > > the second one. > > Why? What benefit does a TCP loopback connection provide over the Unix > domain socket (which is generally faster on most OS'es)? Just a data point: I have lots of special-purpose accounts on my desktop system, for example when building package XYZ I might create a specific "xyz" user and group to do the build work, own the resulting files, etc. So it's very common for me to su over to one of these accounts and run things like emacs or application-specific GUI tools as that special user. I use "xhost +localhost" to let these other accounts display on my desktop; but I basically never have the need for connections to port 6000 from off-machine anymore (I use ssh for that instead). [I realize xauth, or changing permissions on the unix socket, could probably solve this as well. But the localhost method is really, really easy :-] -Dave Dodge From ditasaka@silverbacksystems.com Wed Nov 19 23:53:00 2003 From: ditasaka@silverbacksystems.com (Dai Itasaka) Date: Wed, 19 Nov 2003 23:53:00 -0000 Subject: twm takes no control Message-ID: <004d01c3aef8$46511ff0$7b05000a@corp.silverbacksystems.com> I noticed that the mouse cursor jumps to the IconMgr area if no window has the keyboard focus. This is a normal twm behavior. In that sense, it looks as if it is working. But once somebody claims the focus, twm can't take over. This is not normal. Dai From Alan.Coopersmith@Sun.COM Thu Nov 20 00:13:00 2003 From: Alan.Coopersmith@Sun.COM (Alan Coopersmith) Date: Thu, 20 Nov 2003 00:13:00 -0000 Subject: security, cvs, was Re: interface bindings of x-server In-Reply-To: References: Message-ID: <3FBC071A.6050002@Sun.COM> Dave Dodge wrote: >>Why? What benefit does a TCP loopback connection provide over the Unix >>domain socket (which is generally faster on most OS'es)? > > > Just a data point: I have lots of special-purpose accounts on my > desktop system, for example when building package XYZ I might create a > specific "xyz" user and group to do the build work, own the resulting > files, etc. So it's very common for me to su over to one of these > accounts and run things like emacs or application-specific GUI tools > as that special user. I use "xhost +localhost" to let these other > accounts display on my desktop; but I basically never have the need > for connections to port 6000 from off-machine anymore (I use ssh for > that instead). > > [I realize xauth, or changing permissions on the unix socket, could > probably solve this as well. But the localhost method is really, > really easy :-] "xhost +LOCAL:" would be the equivalent for the Unix socket or other local communications mechanisms. -- -Alan Coopersmith- alan.coopersmith@sun.com Sun Microsystems, Inc. - Sun Software Group User Experience Engineering: G11N: X Window System From keithp@keithp.com Thu Nov 20 00:13:00 2003 From: keithp@keithp.com (Keith Packard) Date: Thu, 20 Nov 2003 00:13:00 -0000 Subject: security, cvs, was Re: interface bindings of x-server In-Reply-To: Your message of "Wed, 19 Nov 2003 18:49:36 EST." Message-ID: Around 18 o'clock on Nov 19, Dave Dodge wrote: > [I realize xauth, or changing permissions on the unix socket, could > probably solve this as well. But the localhost method is really, > really easy :-] When you say 'xhost +localhost' you're also granting permission for applications to connect throught the unix domain socket. On a system with Unix domain sockets, it's hard to see a valid use for 127.0.0.1:6000. This is in no way meant to disuade people from adding suitable options to configure which interfaces the (deprecated) IP listening sockets should bind to; I think that's a very useful idea. I'm just trying to show that the need for any IP connections is even less than people imagine. -keith From dododge@dododge.net Thu Nov 20 00:32:00 2003 From: dododge@dododge.net (Dave Dodge) Date: Thu, 20 Nov 2003 00:32:00 -0000 Subject: security, cvs, was Re: interface bindings of x-server In-Reply-To: Message-ID: On Wed, 19 Nov 2003, Keith Packard wrote: > Around 18 o'clock on Nov 19, Dave Dodge wrote: > > [I realize xauth, or changing permissions on the unix socket, could > > probably solve this as well. But the localhost method is really, > > really easy :-] > > When you say 'xhost +localhost' you're also granting permission for > applications to connect throught the unix domain socket. Yeah, about five minutes after I sent that message I started thinking that I used to use xhost +localhost and then unix:0 to connect from other accounts, so the xhost must have affected the unix socket somehow as well. At some point in the past I switched from using unix:0 to localhost:0 for those cases, but I can't remember if there was a specific reason for doing so (probably user error). -Dave Dodge From huntharo@msu.edu Thu Nov 20 03:05:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Thu, 20 Nov 2003 03:05:00 -0000 Subject: twm takes no control In-Reply-To: <004701c3aef6$6b0eb660$7b05000a@corp.silverbacksystems.com> References: <004701c3aef6$6b0eb660$7b05000a@corp.silverbacksystems.com> Message-ID: <3FBC2F6B.20304@msu.edu> Dai, twm is yours. I don't use it, I don't know how it works, most of my users don't use it, I have no reason to fix it, I don't understand its source code... I place the wounded twm at your feet and let you decide what to do with it. twm is all yours. Fix the bugs that are important to you, or point me to the correct fix if something needs to be fixed with Xt/Xaw/etc. I'm not saying this to be mean. I am simply saying that I don't use twm and I have no need for it to work correctly. It will be much better in your hands. Harold Dai Itasaka wrote: > Quoted is what I posted as "no key input" last month. > > Today I did the update and now twm doesn't take any key input > anymore. I can't move the keyboard focus from one window to another > by pressing the f.downiconmgr or the likes. In fact, no key command > (f.iconify, f.raiselower, f.zoom....) works now. > > My preference is to use Ctrl key plus Shift key plus a letter key. > For example, f.downiconmgr is Ctrl+Shift+j. In .twmrc, it is like > > "j" = c|s : all : f.downiconmgr > > It looks as if this Shift key is not detected as pressed. So instead > of taking it as Ctrl-Shift-x, it takes as Ctrl-x, and it is passed > through twm to whatever application that has the focus at the time > because it is no longer interpreted as a valid twm command key. > > This was working before. What wasn't working is xterm, not twm. > But now, twm isn't. > > Dai > > > ) My startxwin.sh gives me the root window and an xterm window in it. > ) I login to a remote host from this xterm after doing xhost for it. > ) From there, I invoke xterm specifying the local PC as the display. > ) Now I have two xterm windows here: one invoked locally, the other > ) invoked from the remote host. > ) > ) TWM is my window manager. My preference is to show the IconManager > ) at the upper right hand corner of the root, in which I can move > ) from one icon to the next by pressing the keyboard combo specified > ) in the ~/.twmrc as "f.downiconmgr" or "f.upiconmgr". If I press > ) the key combo, no matter where the mouse cursor is at, it jumps > ) to the IconManager area and points to the window that has the keyboard > ) focus at the time. As I press the "up" or the "down" key, the mouse > ) cursor jumps to one icon up or down, and the keyboard focus moves > ) to the corresponding window at once. This is the equivalent of > ) MS Windows' Alt-Tab for me in X(no autoraise by default though). > ) This is how I move the keyboard focus from one window to another. > ) I can't live without this as I have been doing this for over 10 > ) years now. I'm so accustomed to it that I sometimes do it in MS > ) Windows. > ) > ) Now, with the latest Cygwin install, I still can move the keyboard > ) focus by pressing the "up" or "down" key, thus I can toggle the > ) keyboard focus between the two xterm windows I mentioned above. > ) But, the xterm that is locally executed(cygwin xterm) doesnt take > ) any key input unless I move the mouse cursor over the xterm > ) window area, while the one that is remotely executed can take key > ) inputs as usual without moving a mouse(the mouse cursor stays in > ) the IconManager area). > ) > ) Until the one before the latest(XFree86-xserv-4.3.0-18?), this was > ) not the case. I was able to move around AND TYPE. Something that > ) was added since then broke this capability. > ) > ) > From murakami@ipl.t.u-tokyo.ac.jp Thu Nov 20 04:36:00 2003 From: murakami@ipl.t.u-tokyo.ac.jp (Takuma Murakami) Date: Thu, 20 Nov 2003 04:36:00 -0000 Subject: wmaker TIFF (actually libtiff4) problem In-Reply-To: <3FB563B6.1060006@cwilson.fastmail.fm> References: <20031114192300.GB23163@redhat.com> <3FB563B6.1060006@cwilson.fastmail.fm> Message-ID: <20031120125755.128E.MURAKAMI@ipl.t.u-tokyo.ac.jp> I have tried to fix the wmaker problem but get stuck since I don't know how to debug DLLs... > So there are a number of differences between cygtiff3 and cygtiff4. I > tend to suspect the jpeg changes -- are "some TIFF images" which fail to > load all jpeg-compressed, while the ones that succeed are not, perhaps? Although I don't know much about TIFF files, I ran tiffinfo on two systems. The target TIFF file is /usr/X11R6/share/WINGs/Images.tiff in cygwin WindowMaker distribution. On the problematic cygwin (WindowMaker-0.80.2-1, tiff-3.6.0-5) the output is: TIFFReadDirectory: Warning, /usr/X11R6/share/WINGs/Images.tiff: unknown field wi th tag 317 (0x13d) encountered. TIFF Directory at offset 0x449c Image Width: 128 Image Length: 128 Resolution: 72, 72 pixels/inch Bits/Sample: 8 Compression Scheme: LZW Photometric Interpretation: RGB color Extra Samples: 1 FillOrder: lsb-to-msb Document Name: "/usr/src/Applications/windowmaker/WindowMaker/WINGs/Resources/ Images.tiff" Image Description: "Created with The GIMP" Orientation: row 0 top, col 0 lhs Samples/Pixel: 4 Rows/Strip: 16 Planar Configuration: single image plane On a FreeBSD 4.8 system, the output is: TIFF Directory at offset 0x449c Image Width: 128 Image Length: 128 Resolution: 72, 72 pixels/inch Bits/Sample: 8 Compression Scheme: LZW Photometric Interpretation: RGB color Extra Samples: 1 FillOrder: lsb-to-msb Document Name: "/usr/src/Applications/windowmaker/WindowMaker/WINGs/Resources/Images.tiff" Image Description: "Created with The GIMP" Orientation: row 0 top, col 0 lhs Samples/Pixel: 4 Rows/Strip: 16 Planar Configuration: single image plane Predictor: horizontal differencing 2 (0x2) The differences are the warning and the last line. The 'Compression Scheme' field indicates LZW. Is this relevant to the problem? Takuma Murakami (murakami@ipl.t.u-tokyo.ac.jp) From kirk.erickson@Sun.COM Thu Nov 20 06:56:00 2003 From: kirk.erickson@Sun.COM (Kirk Erickson) Date: Thu, 20 Nov 2003 06:56:00 -0000 Subject: TTF-font rendering not working anymore Message-ID: <3FBC6533.5070608@sun.com> Sorry I didn't report this earlier. I've been plagued by the TTF font problem reported by Fridger Schrempp and Michael Bax and Fridger Schrempp. Perhaps if someone were to review the checkins previous to Michael's reporting the problem (11 Nov 2003), it could be resolved. This is really a showstopper class bug that folks who made recent checkins should be made aware of. -- kirk From cygwin@cwilson.fastmail.fm Thu Nov 20 07:41:00 2003 From: cygwin@cwilson.fastmail.fm (Charles Wilson) Date: Thu, 20 Nov 2003 07:41:00 -0000 Subject: wmaker TIFF (actually libtiff4) problem In-Reply-To: <20031120125755.128E.MURAKAMI@ipl.t.u-tokyo.ac.jp> References: <20031114192300.GB23163@redhat.com> <3FB563B6.1060006@cwilson.fastmail.fm> <20031120125755.128E.MURAKAMI@ipl.t.u-tokyo.ac.jp> Message-ID: <3FBC70AD.9030604@cwilson.fastmail.fm> Takuma Murakami wrote: > I have tried to fix the wmaker problem but get stuck > since I don't know how to debug DLLs... > > Although I don't know much about TIFF files, I ran > tiffinfo on two systems. The target TIFF file is > /usr/X11R6/share/WINGs/Images.tiff in cygwin > WindowMaker distribution. > > On the problematic cygwin (WindowMaker-0.80.2-1, > tiff-3.6.0-5) the output is: > TIFFReadDirectory: Warning, /usr/X11R6/share/WINGs/Images.tiff: unknown field wi > th tag 317 (0x13d) encountered. ... > Compression Scheme: LZW ... > Predictor: horizontal differencing 2 (0x2) > The 'Compression Scheme' field indicates LZW. > Is this relevant to the problem? Yes. LZW support is not included in and has never been included in any cygwin distribution of libtiff. This is because LZW is patented by Unisys and they do not allow the algorithms to be used without royalty payments. Now, the patent did expire in September 2003 in the US, but the patent is still valid in several other countries. Therefore, we STILL do not include LZW support in the binary distributions of libtiff. (Of course, this makes me wonder: (a) there were reports that "this used to work -- or still works -- with cygtiff3. But THAT dll did not provide LZW support either. See below for random speculation. (b) Why is WindowMaker distributing TIFFs that cannot be read by free (as in speech) software without violating patents in some countries? Do they only care about the US? This is an issue that should be raised on the relevant WindowMaker lists) IF you want to test this proposition, the tiff -src package distributed by cygwin provides the source code and instructions for rebuilding cygtiff4 wiht LZW for your own personal use, if you happen to live in a country where the UniSys patent has lapsed -- like the US -- or if you have purchased a license from UniSys. Then you could see if rebuilding cygtiff4 WITH LZW fixes the problem. (Random speculation: perhaps the person who reported success by copying their cygtiff3 onto cygtiff4 did exactly that -- rebuilt cygtiff3 with LZW, but so long ago that they forgot. That would explain all of the reported behaviors...) -- Chuck From xavier.elattaoui@synchrotron-soleil.fr Thu Nov 20 08:19:00 2003 From: xavier.elattaoui@synchrotron-soleil.fr (ELATTAOUI Xavier) Date: Thu, 20 Nov 2003 08:19:00 -0000 Subject: usb keyboard Message-ID: <24AD9A5266E9A94E93C2D7686B8CD08B66E76A@venus.synchrotron-soleil.fr> Hi Alexander, I've updated the XFree86-xserv package. Now it run well, I've no problem with my keyboard. Thanks for your help xavier -----Message d'origine----- De : Alexander Gottwald [mailto:alexander.gottwald@s1999.tu-chemnitz.de] Envoy? : mercredi 19 novembre 2003 15:50 ? : cygwin-xfree@cygwin.com Objet : RE: usb keyboard On Wed, 19 Nov 2003, ELATTAOUI Xavier wrote: > I have no XWin.log under /tmp but a XWinrl.log(in attachement). > I've done an uninstall and reinstall it, but the trouble is still present ! You're using a very old version. Update the XFree86-xserv package. This might already contain the proper keyboardlayout. bye ago -- Alexander.Gottwald@s1999.tu-chemnitz.de http://www.gotti.org ICQ: 126018723 From alexander.gottwald@s1999.tu-chemnitz.de Thu Nov 20 09:09:00 2003 From: alexander.gottwald@s1999.tu-chemnitz.de (Alexander Gottwald) Date: Thu, 20 Nov 2003 09:09:00 -0000 Subject: Unexpected network-traffic In-Reply-To: <5.0.2.1.2.20031120085606.00af8c98@pops.ires.ucl.ac.be> References: <5.0.2.1.2.20031119121810.04d75010@pops.ires.ucl.ac.be> <5.0.2.1.2.20031119121810.04d75010@pops.ires.ucl.ac.be> <5.0.2.1.2.20031120085606.00af8c98@pops.ires.ucl.ac.be> Message-ID: On Thu, 20 Nov 2003, Christian G??bel wrote: > What I expect is that X11 causes network traffic when I am connected to a > X-server somewhere over a network - but why it causes network traffic without > beeing connected to another computer? > Is there any (perhaps technical) explanation for that? Yes. X11 can be used over TCP and over Unix Domain Sockets. Unix Domain Sockets is emulated in cygwin with TCP. So X11 in cygwin does always use TCP. You might have noticed that xterm connects to a 127.0.0.0 address which is a local only address. The xserver connects to IN_ADDR_ANY and not to a specific network interface. All network traffic (except the DNS query) is only local. bye ago -- Alexander.Gottwald@s1999.tu-chemnitz.de http://www.gotti.org ICQ: 126018723 From hschultz@premitech.com Thu Nov 20 14:18:00 2003 From: hschultz@premitech.com (Henrik Schultz) Date: Thu, 20 Nov 2003 14:18:00 -0000 Subject: Alt Gr keys are not functioning ? Message-ID: <81AC7B3F6CA6D4118AB00050BA8755668117E1@EXCHANGE> Have just installed latest version of Cygwin/XFree86 on my Windows 2000 laptop. Everything seems to be working fine, except for one thing: when I open an xterm from a remote Solaris 2.6 system, the @,?,$, etc. keys are not working, i.e. all the keys that are accessed by using the Alt Gr key are not producing any output. This is what I have done to investigate the problem: - If I from a BASH shell telnet over to the Solaris box, ALL characters work A-OK. - When I open an xterm back to the XFree86 server, our 3 Danish national characters ?,?,? are working fine, so the correct keyboard map seems to have been loaded. However this is where the problem with the missing @,?,$ etc. comes up. - Ran xkeycaps on the Solaris box, from which I noted that there was ex. no '$' character mapped to the '4' key, nor was there any other special characters mapped to keys usually accessed by Alt Gr. - Alt Gr is mapped to ISO_Level3_Shift. - Running 'xev' correctly lists events for Alt Gr and other keys, however whereas SHIFT-'h' produces 'H' etc., Alt Gr-'4' does not produce any visible character. Here is the list for the latter: KeyPress event, serial 17, synthetic NO, window 0x200001, root 0x3a, subw 0x0, time 25838834, (431,266), root:(437,291), state 0x0, keycode 113 (keysym 0xfe03, ISO_Level3_Shift), same_screen YES, XLookupString gives 0 bytes: "" KeyPress event, serial 22, synthetic NO, window 0x200001, root 0x3a, subw 0x0, time 25840146, (431,266), root:(437,291), state 0x80, keycode 13 (keysym 0x0, NoSymbol), same_screen YES, XLookupString gives 0 bytes: "" KeyRelease event, serial 22, synthetic NO, window 0x200001, root 0x3a, subw 0x0, time 25840206, (431,266), root:(437,291), state 0x80, keycode 13 (keysym 0x0, NoSymbol), same_screen YES, XLookupString gives 0 bytes: "" KeyRelease event, serial 22, synthetic NO, window 0x200001, root 0x3a, subw 0x0, time 25840997, (431,266), root:(437,291), state 0x80, keycode 113 (keysym 0xfe03, ISO_Level3_Shift), same_screen YES, XLookupString gives 0 bytes: "" Would anyone have a clue how to proceed with debugging this? Thanks! Henrik Schultz Senior Systems Architect PremiTech A/S, Teknikerbyen 5, DK-2830 Virum Tel: +45 4595 8500 Mob: +45 2212 2429 Web: http://www.premitech.com/ From johncsl82@yahoo.com Thu Nov 20 15:07:00 2003 From: johncsl82@yahoo.com (Chan Seng Loong) Date: Thu, 20 Nov 2003 15:07:00 -0000 Subject: Cygwin XFree86 startx Problem Message-ID: <20031120150754.62955.qmail@web60307.mail.yahoo.com> hi... I having problem using startx to startx the X window or X server....... here are the error: Chan Seng Loong@amd1500mhz ~ $ 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 From huntharo@msu.edu Thu Nov 20 15:22:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Thu, 20 Nov 2003 15:22:00 -0000 Subject: wmaker TIFF (actually libtiff4) problem In-Reply-To: <3FBC70AD.9030604@cwilson.fastmail.fm> References: <20031114192300.GB23163@redhat.com> <3FB563B6.1060006@cwilson.fastmail.fm> <20031120125755.128E.MURAKAMI@ipl.t.u-tokyo.ac.jp> <3FBC70AD.9030604@cwilson.fastmail.fm> Message-ID: <3FBCDC2B.1050107@msu.edu> Thanks Chuck. That closes the problem from my standpoint. Harold Charles Wilson wrote: > Takuma Murakami wrote: > >> I have tried to fix the wmaker problem but get stuck >> since I don't know how to debug DLLs... > > >> >> Although I don't know much about TIFF files, I ran >> tiffinfo on two systems. The target TIFF file is >> /usr/X11R6/share/WINGs/Images.tiff in cygwin >> WindowMaker distribution. >> >> On the problematic cygwin (WindowMaker-0.80.2-1, >> tiff-3.6.0-5) the output is: >> TIFFReadDirectory: Warning, /usr/X11R6/share/WINGs/Images.tiff: >> unknown field wi >> th tag 317 (0x13d) encountered. > > ... > >> Compression Scheme: LZW > > ... > >> Predictor: horizontal differencing 2 (0x2) > > > >> The 'Compression Scheme' field indicates LZW. >> Is this relevant to the problem? > > > > Yes. LZW support is not included in and has never been included in any > cygwin distribution of libtiff. This is because LZW is patented by > Unisys and they do not allow the algorithms to be used without royalty > payments. > > Now, the patent did expire in September 2003 in the US, but the patent > is still valid in several other countries. Therefore, we STILL do not > include LZW support in the binary distributions of libtiff. > > (Of course, this makes me wonder: (a) there were reports that "this used > to work -- or still works -- with cygtiff3. But THAT dll did not > provide LZW support either. See below for random speculation. (b) Why > is WindowMaker distributing TIFFs that cannot be read by free (as in > speech) software without violating patents in some countries? Do they > only care about the US? This is an issue that should be raised on the > relevant WindowMaker lists) > > IF you want to test this proposition, the tiff -src package distributed > by cygwin provides the source code and instructions for rebuilding > cygtiff4 wiht LZW for your own personal use, if you happen to live in a > country where the UniSys patent has lapsed -- like the US -- or if you > have purchased a license from UniSys. > > Then you could see if rebuilding cygtiff4 WITH LZW fixes the problem. > (Random speculation: perhaps the person who reported success by copying > their cygtiff3 onto cygtiff4 did exactly that -- rebuilt cygtiff3 with > LZW, but so long ago that they forgot. That would explain all of the > reported behaviors...) > > -- > Chuck > From huntharo@msu.edu Thu Nov 20 15:24:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Thu, 20 Nov 2003 15:24:00 -0000 Subject: Cygwin XFree86 startx Problem In-Reply-To: <20031120150754.62955.qmail@web60307.mail.yahoo.com> References: <20031120150754.62955.qmail@web60307.mail.yahoo.com> Message-ID: <3FBCDCAF.5080909@msu.edu> 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 Loong@amd1500mhz ~ > $ 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 From hschultz@premitech.com Thu Nov 20 15:26:00 2003 From: hschultz@premitech.com (Henrik Schultz) Date: Thu, 20 Nov 2003 15:26:00 -0000 Subject: Cygwin XFree86 startx Problem Message-ID: <81AC7B3F6CA6D4118AB00050BA8755668117E9@EXCHANGE> >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 From huntharo@msu.edu Thu Nov 20 15:28:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Thu, 20 Nov 2003 15:28:00 -0000 Subject: TTF-font rendering not working anymore In-Reply-To: <3FBC6533.5070608@sun.com> References: <3FBC6533.5070608@sun.com> Message-ID: <3FBCDD87.3070707@msu.edu> Kirk, Somebody needs to give me a three-click test case or I won't even be able to confirm that this is indeed a problem. You do have the "fontconfig" and "freetype2" packages installed on your machine, right? Harold Kirk Erickson wrote: > Sorry I didn't report this earlier. I've been plagued by the > TTF font problem reported by Fridger Schrempp and Michael Bax > and Fridger Schrempp. > > Perhaps if someone were to review the checkins previous to > Michael's reporting the problem (11 Nov 2003), it could be resolved. > > This is really a showstopper class bug that folks who made > recent checkins should be made aware of. > From cgf-no-personal-reply-please@cygwin.com Thu Nov 20 15:33:00 2003 From: cgf-no-personal-reply-please@cygwin.com (Christopher Faylor) Date: Thu, 20 Nov 2003 15:33:00 -0000 Subject: unable to open the display on local machine In-Reply-To: <28343.1069312376@www12.gmx.net> References: <28343.1069312376@www12.gmx.net> Message-ID: <20031120153301.GB32016@redhat.com> On Thu, Nov 20, 2003 at 08:12:56AM +0100, daniel43@gmx.ch wrote: >Hello, > >I have installed cygwin localy on a W2K PC. >I have installed the package ghostview, using the setup.exe utility. >Now, if I try to start ghostview, I type: >$ gv & >I get the error message: >gv: Unable to open the display. > >I tried to set the DISPLAY variable: >$setenv DISPLAY localhost:0.0 >But the setenv command is not known. >So I tried with set: >$set DISPLAY localhost:0.0 >But this does not seem to do anything. >When I echo the variable DISPLAY: >$echo $DISPLAY >I just get a blank line. > >Help would be very apreciated. Redirecting to the mailing list devoted to Cygwin/X and shutting down this thread. cgf From huntharo@msu.edu Thu Nov 20 15:33:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Thu, 20 Nov 2003 15:33:00 -0000 Subject: Cygwin XFree86 startx Problem In-Reply-To: <81AC7B3F6CA6D4118AB00050BA8755668117E9@EXCHANGE> References: <81AC7B3F6CA6D4118AB00050BA8755668117E9@EXCHANGE> Message-ID: <3FBCDEAF.5080706@msu.edu> 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 From huntharo@msu.edu Thu Nov 20 15:36:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Thu, 20 Nov 2003 15:36:00 -0000 Subject: unable to open the display on local machine In-Reply-To: <20031120153301.GB32016@redhat.com> References: <28343.1069312376@www12.gmx.net> <20031120153301.GB32016@redhat.com> Message-ID: <3FBCDF8F.1040109@msu.edu> Run startxwin.bat first, then run "gv" from within the xterm that pops up. Harold Christopher Faylor wrote: > On Thu, Nov 20, 2003 at 08:12:56AM +0100, daniel43@gmx.ch wrote: > >>Hello, >> >>I have installed cygwin localy on a W2K PC. >>I have installed the package ghostview, using the setup.exe utility. >>Now, if I try to start ghostview, I type: >>$ gv & >>I get the error message: >>gv: Unable to open the display. >> >>I tried to set the DISPLAY variable: >>$setenv DISPLAY localhost:0.0 >>But the setenv command is not known. >>So I tried with set: >>$set DISPLAY localhost:0.0 >>But this does not seem to do anything. >>When I echo the variable DISPLAY: >>$echo $DISPLAY >>I just get a blank line. >> >>Help would be very apreciated. > > > Redirecting to the mailing list devoted to Cygwin/X and shutting down this > thread. > > cgf From ihok@hotmail.com Thu Nov 20 17:06:00 2003 From: ihok@hotmail.com (Jack Tanner) Date: Thu, 20 Nov 2003 17:06:00 -0000 Subject: Updated: XFree86-xserv-4.3.0-22 In-Reply-To: References: <1068549020528.tulitanssi.36802.w1Q4NRjiTPWoQQzb3m7sWA@luukku.com> <3FB0E0D5.7090505@msu.edu> <87ptfyvpbj.fsf@vzell-de.de.oracle.com> <3FB1123E.8090102@msu.edu> <87d6byvn9u.fsf@vzell-de.de.oracle.com> <87smktnyps.fsf@vzell-de.de.oracle.com> <3FBA8FE4.30902@users.sourceforge.net> Message-ID: Alexander Gottwald wrote: > If this is the case I can add code to use the windows default autorepeat > settings to configure Xwin. But this will again change the old behavior > of Xwin and some users might be unhappy with it. It would be consistent with other behavior to get autorepeat settings from Windows, not from X settings. For example, we try to use the Windows language settings, right? Since Xwin is a Windows application, there's little reason for it to have its own autorepeat configuration. -JT From huntharo@msu.edu Thu Nov 20 17:16:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Thu, 20 Nov 2003 17:16:00 -0000 Subject: Keyboard autorepeat settings [Was: Updated: XFree86-xserv-4.3.0-22] In-Reply-To: References: <1068549020528.tulitanssi.36802.w1Q4NRjiTPWoQQzb3m7sWA@luukku.com> <3FB0E0D5.7090505@msu.edu> <87ptfyvpbj.fsf@vzell-de.de.oracle.com> <3FB1123E.8090102@msu.edu> <87d6byvn9u.fsf@vzell-de.de.oracle.com> <87smktnyps.fsf@vzell-de.de.oracle.com> <3FBA8FE4.30902@users.sourceforge.net> Message-ID: <3FBCF6D0.4090500@msu.edu> Jack Tanner wrote: > Alexander Gottwald wrote: > >> If this is the case I can add code to use the windows default >> autorepeat settings to configure Xwin. But this will again change the >> old behavior >> of Xwin and some users might be unhappy with it. > > > It would be consistent with other behavior to get autorepeat settings > from Windows, not from X settings. For example, we try to use the > Windows language settings, right? Sort of... it isn't quite that cut and dried. Besides, we have been using *both* X autorepeat and Windows autorepeat until recently. This was not a good solution. > Since Xwin is a Windows application, there's little reason for it to > have its own autorepeat configuration. It might be nice, but the Windows autorepeat caused problems with systems running in Japanese... so they need the XKB autorepeat functionality, since the Windows autorepeat needs to be disabled for them. So, we can't just remove XKB support or disable it permanently... it is required by some non-U.S. users. It may seems like we are being indecisive here... but there are really a lot of concerns that need to be considered in order to get a correct solution. Harold From b.izzuddin@imperial.ac.uk Thu Nov 20 17:17:00 2003 From: b.izzuddin@imperial.ac.uk (Izzuddin, Bassam A) Date: Thu, 20 Nov 2003 17:17:00 -0000 Subject: Lesstif segmentation fault after cygwin update Message-ID: <3FBCF70D.6050604@imperial.ac.uk> I have just updated my cygwin installation, including XFree86 4.3.0-1 and Lesstif 0.93.91-4. My program compiles, but with info messages which I did not get with my previous cygwin installation, as follows: cc -g -I/usr/X11R6/include -o prog.exe callBacks.o draw.o drawingRegion.o drawPrims.o elems2Prims.o fileReading.o inter.o menu.o orient.o readDetails.o savRet.o selection.o util.o vector.o -L/usr/X11R6/lib -lXm -lXt -lSM -lICE -lX11 -lm -lXp -lXext Info: resolving __XmStrings by linking to __imp___XmStrings (auto-import) Info: resolving _XtStrings by linking to __imp__XtStrings (auto-import) Info: resolving _xmDrawingAreaWidgetClass by linking to __imp__xmDrawingAreaWidgetClass (auto-import) Info: resolving _xmBulletinBoardWidgetClass by linking to __imp__xmBulletinBoardWidgetClass (auto-import) Info: resolving _xmSeparatorGadgetClass by linking to __imp__xmSeparatorGadgetClass (auto-import) Info: resolving _xmPushButtonGadgetClass by linking to __imp__xmPushButtonGadgetClass (auto-import) Info: resolving _xmLabelGadgetClass by linking to __imp__xmLabelGadgetClass (auto-import) Info: resolving _xmCascadeButtonGadgetClass by linking to __imp__xmCascadeButtonGadgetClass (auto-import) Info: resolving _xmArrowButtonGadgetClass by linking to __imp__xmArrowButtonGadgetClass (auto-import) When I run, I get a segmentation fault which I traced using gdb to the following functions: #0 0x10032103 in cygX11-6!XGetGCValues () from /cygdrive/c/Program Files/Cygwin/usr/X11R6/bin/cygX11-6.dll #1 0x00513b26 in cygXm-2!_XmArrowBG_TraitAddCallback () from /cygdrive/c/Program Files/Cygwin/usr/X11R6/bin/cygXm-2.dll #2 0x007a5ecc in cygXt-6!XtSetSensitive () from /cygdrive/c/Program Files/Cygwin/usr/X11R6/bin/cygXt-6.dll #3 0x007a64cb in cygXt-6!XtSetValues () from /cygdrive/c/Program Files/Cygwin/usr/X11R6/bin/cygXt-6.dll #4 0x007a5c6f in cygXt-6!XtGetSelectionParameters () from /cygdrive/c/Program Files/Cygwin/usr/X11R6/bin/cygXt-6.dll #5 0x007a5d87 in cygXt-6!XtSetSensitive () from /cygdrive/c/Program Files/Cygwin/usr/X11R6/bin/cygXt-6.dll #6 0x004397d0 in setGraphicsSensitive (status=0 '\0') at util.c:16 #7 0x00401113 in manageSelection (callWidget=0x1015d730, data=0x4421e4, event=0x22fa20) at callBacks.c:69 #8 0x007826b3 in cygXt-6!XtCallCallbackList () from /cygdrive/c/Program Files/Cygwin/usr/X11R6/bin/cygXt-6.dll #9 0x0057744a in cygXm-2!_XmPushBG_TraitAddCallback () from /cygdrive/c/Program Files/Cygwin/usr/X11R6/bin/cygXm-2.dll #10 0x00576275 in cygXm-2!_XmPushB_TraitAddCallback () from /cygdrive/c/Program Files/Cygwin/usr/X11R6/bin/cygXm-2.dll #11 0x005498bf in cygXm-2!_XmDispatchGadgetInput () from /cygdrive/c/Program Files/Cygwin/usr/X11R6/bin/cygXm-2.dll #12 0x005841c4 in cygXm-2!_XmMenuBtnUp () #13 0x007b6f41 in cygXt-6!_XtMatchAtom () from /cygdrive/c/Program Files/Cygwin/usr/X11R6/bin/cygXt-6.dll #14 0x007b73e9 in cygXt-6!_XtMatchAtom () from /cygdrive/c/Program Files/Cygwin/usr/X11R6/bin/cygXt-6.dll #15 0x007b797b in cygXt-6!_XtTranslateEvent () from /cygdrive/c/Program Files/Cygwin/usr/X11R6/bin/cygXt-6.dll #16 0x00790165 in cygXt-6!XtDispatchEventToWidget () from /cygdrive/c/Program Files/Cygwin/usr/X11R6/bin/cygXt-6.dll #17 0x00790c6f in cygXt-6!_XtOnGrabList () from /cygdrive/c/Program Files/Cygwin/usr/X11R6/bin/cygXt-6.dll #18 0x00790ebf in cygXt-6!XtDispatchEvent () from /cygdrive/c/Program Files/Cygwin/usr/X11R6/bin/cygXt-6.dll #19 0x007913e4 in cygXt-6!XtAppMainLoop () from /cygdrive/c/Program Files/Cygwin/usr/X11R6/bin/cygXt-6.dll #20 0x007913a3 in cygXt-6!XtMainLoop () from /cygdrive/c/Program Files/Cygwin/usr/X11R6/bin/cygXt-6.dll #21 0x0041fe43 in _fu292__xmBulletinBoardWidgetClass () at inter.c:62 #22 0x61005018 in forkpty () from /usr/bin/cygwin1.dll #23 0x610052ed in dll_crt0@0 () from /usr/bin/cygwin1.dll #24 0x0043af71 in cygwin_crt0 () #25 0x0040103c in mainCRTStartup () #26 0x77e814c7 in KERNEL32!GetCurrentDirectoryW () from /cygdrive/c/WINDOWS/system32/kernel32.dll I have tried many things, including a reinstall of all the Cygwin packages, but no luck! I would appreciate any help on how to remedy this problem. Bassam. From huntharo@msu.edu Thu Nov 20 17:24:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Thu, 20 Nov 2003 17:24:00 -0000 Subject: Lesstif segmentation fault after cygwin update In-Reply-To: <3FBCF70D.6050604@imperial.ac.uk> References: <3FBCF70D.6050604@imperial.ac.uk> Message-ID: <3FBCF8E9.5020307@msu.edu> Just replying to say that I don't have any ideas. At least you got a reply. Other LessTif users may be able to help you. Harold Izzuddin, Bassam A wrote: > I have just updated my cygwin installation, including XFree86 4.3.0-1 > and Lesstif 0.93.91-4. My program compiles, but with info messages which > I did not get with my previous cygwin installation, as follows: > > cc -g -I/usr/X11R6/include -o prog.exe callBacks.o draw.o > drawingRegion.o drawPrims.o elems2Prims.o fileReading.o inter.o menu.o > orient.o readDetails.o savRet.o selection.o util.o vector.o > -L/usr/X11R6/lib -lXm -lXt -lSM -lICE -lX11 -lm -lXp -lXext > > Info: resolving __XmStrings by linking to __imp___XmStrings (auto-import) > Info: resolving _XtStrings by linking to __imp__XtStrings (auto-import) > Info: resolving _xmDrawingAreaWidgetClass by linking to > __imp__xmDrawingAreaWidgetClass (auto-import) > Info: resolving _xmBulletinBoardWidgetClass by linking to > __imp__xmBulletinBoardWidgetClass (auto-import) > Info: resolving _xmSeparatorGadgetClass by linking to > __imp__xmSeparatorGadgetClass (auto-import) > Info: resolving _xmPushButtonGadgetClass by linking to > __imp__xmPushButtonGadgetClass (auto-import) > Info: resolving _xmLabelGadgetClass by linking to > __imp__xmLabelGadgetClass (auto-import) > Info: resolving _xmCascadeButtonGadgetClass by linking to > __imp__xmCascadeButtonGadgetClass (auto-import) > Info: resolving _xmArrowButtonGadgetClass by linking to > __imp__xmArrowButtonGadgetClass (auto-import) > > When I run, I get a segmentation fault which I traced using gdb to the > following functions: > > #0 0x10032103 in cygX11-6!XGetGCValues () from /cygdrive/c/Program > Files/Cygwin/usr/X11R6/bin/cygX11-6.dll > #1 0x00513b26 in cygXm-2!_XmArrowBG_TraitAddCallback () from > /cygdrive/c/Program Files/Cygwin/usr/X11R6/bin/cygXm-2.dll > #2 0x007a5ecc in cygXt-6!XtSetSensitive () from /cygdrive/c/Program > Files/Cygwin/usr/X11R6/bin/cygXt-6.dll > #3 0x007a64cb in cygXt-6!XtSetValues () from /cygdrive/c/Program > Files/Cygwin/usr/X11R6/bin/cygXt-6.dll > #4 0x007a5c6f in cygXt-6!XtGetSelectionParameters () from > /cygdrive/c/Program Files/Cygwin/usr/X11R6/bin/cygXt-6.dll > #5 0x007a5d87 in cygXt-6!XtSetSensitive () from /cygdrive/c/Program > Files/Cygwin/usr/X11R6/bin/cygXt-6.dll > #6 0x004397d0 in setGraphicsSensitive (status=0 '\0') at util.c:16 > #7 0x00401113 in manageSelection (callWidget=0x1015d730, data=0x4421e4, > event=0x22fa20) at callBacks.c:69 > #8 0x007826b3 in cygXt-6!XtCallCallbackList () from /cygdrive/c/Program > Files/Cygwin/usr/X11R6/bin/cygXt-6.dll > #9 0x0057744a in cygXm-2!_XmPushBG_TraitAddCallback () from > /cygdrive/c/Program Files/Cygwin/usr/X11R6/bin/cygXm-2.dll > #10 0x00576275 in cygXm-2!_XmPushB_TraitAddCallback () from > /cygdrive/c/Program Files/Cygwin/usr/X11R6/bin/cygXm-2.dll > #11 0x005498bf in cygXm-2!_XmDispatchGadgetInput () from > /cygdrive/c/Program Files/Cygwin/usr/X11R6/bin/cygXm-2.dll > #12 0x005841c4 in cygXm-2!_XmMenuBtnUp () > #13 0x007b6f41 in cygXt-6!_XtMatchAtom () from /cygdrive/c/Program > Files/Cygwin/usr/X11R6/bin/cygXt-6.dll > #14 0x007b73e9 in cygXt-6!_XtMatchAtom () from /cygdrive/c/Program > Files/Cygwin/usr/X11R6/bin/cygXt-6.dll > #15 0x007b797b in cygXt-6!_XtTranslateEvent () from /cygdrive/c/Program > Files/Cygwin/usr/X11R6/bin/cygXt-6.dll > #16 0x00790165 in cygXt-6!XtDispatchEventToWidget () from > /cygdrive/c/Program Files/Cygwin/usr/X11R6/bin/cygXt-6.dll > #17 0x00790c6f in cygXt-6!_XtOnGrabList () from /cygdrive/c/Program > Files/Cygwin/usr/X11R6/bin/cygXt-6.dll > #18 0x00790ebf in cygXt-6!XtDispatchEvent () from /cygdrive/c/Program > Files/Cygwin/usr/X11R6/bin/cygXt-6.dll > #19 0x007913e4 in cygXt-6!XtAppMainLoop () from /cygdrive/c/Program > Files/Cygwin/usr/X11R6/bin/cygXt-6.dll > #20 0x007913a3 in cygXt-6!XtMainLoop () from /cygdrive/c/Program > Files/Cygwin/usr/X11R6/bin/cygXt-6.dll > #21 0x0041fe43 in _fu292__xmBulletinBoardWidgetClass () at inter.c:62 > #22 0x61005018 in forkpty () from /usr/bin/cygwin1.dll > #23 0x610052ed in dll_crt0@0 () from /usr/bin/cygwin1.dll > #24 0x0043af71 in cygwin_crt0 () > #25 0x0040103c in mainCRTStartup () > #26 0x77e814c7 in KERNEL32!GetCurrentDirectoryW () from > /cygdrive/c/WINDOWS/system32/kernel32.dll > > I have tried many things, including a reinstall of all the Cygwin > packages, but no luck! I would appreciate any help on how to remedy this > problem. > > Bassam. > From pechtcha@cs.nyu.edu Thu Nov 20 17:30:00 2003 From: pechtcha@cs.nyu.edu (Igor Pechtchanski) Date: Thu, 20 Nov 2003 17:30:00 -0000 Subject: Cygwin XFree86 startx Problem In-Reply-To: <20031120150754.62955.qmail@web60307.mail.yahoo.com> References: <20031120150754.62955.qmail@web60307.mail.yahoo.com> Message-ID: 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 Loong@amd1500mhz ~ > $ 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/ |\ _,,,---,,_ pechtcha@cs.nyu.edu ZZZzz /,`.-'`' -. ;-;;,_ igor@watson.ibm.com |,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 -------------- next part -------------- --- startx-orig 2003-10-28 12:10:43.000000000 -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\"" else - serverargs="$serverargs $1" + serverargs="$serverargs \"$1\"" fi fi ;; @@ -69,14 +66,15 @@ while [ x"$1" != x ]; do ;; *) if [ "$whoseargs" = "client" ]; then - clientargs="$clientargs $1" + clientargs="$clientargs \"$1\"" else # display must be the FIRST server argument - if [ x"$serverargs" = x ] && expr "$1" : ':[0-9][0-9]*$' > /dev/null 2>&1; then + 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 ;; @@ -90,7 +88,7 @@ if [ x"$client" = x ]; then if [ x"$clientargs" = x ]; then client="$defaultclientargs" else - client=$defaultclient + client="$defaultclient" fi fi @@ -100,39 +98,26 @@ 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 removelist= +#xinit $client $clientargs -- $server $display $serverargs -xinit $client $clientargs -- $server $display $serverargs +# correctly process quotes, etc +eval "set -- $client $clientargs -- $server $display $serverargs" + +xinit "$@" if [ x"$removelist" != x ]; then + # Note: this is still not space-friendly! xauth remove $removelist fi - - - - - - - - - - - - - - - - - - From ditasaka@silverbacksystems.com Thu Nov 20 17:50:00 2003 From: ditasaka@silverbacksystems.com (Dai Itasaka) Date: Thu, 20 Nov 2003 17:50:00 -0000 Subject: twm takes no control Message-ID: <008d01c3af8e$bbc1e850$7b05000a@corp.silverbacksystems.com> It is not just Cygwin version of twm. Exactly the same symptom is observed when using a twm on a RedHat or SuSE box managing a cygwin display. It is obvious that it is not twm that is broken. Dai ) twm is yours. I don't use it, I don't know how it works, most of my ) users don't use it, I have no reason to fix it, I don't understand its ) source code... I place the wounded twm at your feet and let you decide ) what to do with it. twm is all yours. Fix the bugs that are important ) to you, or point me to the correct fix if something needs to be fixed ) with Xt/Xaw/etc. ) ) I'm not saying this to be mean. I am simply saying that I don't use twm ) and I have no need for it to work correctly. It will be much better in ) your hands. ) ) From johncsl82@yahoo.com Thu Nov 20 17:54:00 2003 From: johncsl82@yahoo.com (Chan Seng Loong) Date: Thu, 20 Nov 2003 17:54:00 -0000 Subject: Cygwin XFree86 startx Problem Message-ID: <20031120175424.30040.qmail@web60309.mail.yahoo.com> hi... again I tried using the "$HOME" -> qutoes....but 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 From huntharo@msu.edu Thu Nov 20 17:57:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Thu, 20 Nov 2003 17:57:00 -0000 Subject: Cygwin XFree86 startx Problem In-Reply-To: <20031120175424.30040.qmail@web60309.mail.yahoo.com> References: <20031120175424.30040.qmail@web60309.mail.yahoo.com> Message-ID: <3FBD006C.9000304@msu.edu> 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" -> qutoes....but 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 From moser@decodon.com Thu Nov 20 18:09:00 2003 From: moser@decodon.com (Frank-Michael Moser) Date: Thu, 20 Nov 2003 18:09:00 -0000 Subject: TTF-font rendering not working anymore In-Reply-To: <3FBCDD87.3070707@msu.edu> References: <3FBC6533.5070608@sun.com> <3FBCDD87.3070707@msu.edu> Message-ID: <3FBD0347.1030701@decodon.com> If you need another "me, too", here you are - but sorry, I know that this is not really helpful. I'm not experienced with C programming at all, but if someone has a piece of code or anything else to be tested on my box - you are welcome. Furthermore I found that I have the following line in my .xinitrc xset fp+ "$(cygpath -W)/FONTS" This has worked for me a long time. Without that line I do not get any TTF-fonts listed by xfontsel. With that line they are listed but not displayed any longer. Is using that command deprecated. I remember that I have used a tool to create the description files "fonts.scale", "fonts.dir", and "encodings.dir" for that font path. I do not remember which tool it was. Maybe I have to recreate these files? Any ideas? If anybody needs further information or testing, let me know. Frank-Michael. Harold L Hunt II wrote: > Kirk, > > Somebody needs to give me a three-click test case or I won't even be > able to confirm that this is indeed a problem. > > You do have the "fontconfig" and "freetype2" packages installed on your > machine, right? > > Harold > > Kirk Erickson wrote: > >> Sorry I didn't report this earlier. I've been plagued by the >> TTF font problem reported by Fridger Schrempp and Michael Bax >> and Fridger Schrempp. >> >> Perhaps if someone were to review the checkins previous to >> Michael's reporting the problem (11 Nov 2003), it could be resolved. >> >> This is really a showstopper class bug that folks who made >> recent checkins should be made aware of. >> -- ------------------------------------------------------------ DECODON GmbH phone: +49(0)3834 515231 W.-Rathenau-Str. 49a fax: +49(0)3834 515239 17489 Greifswald email: moser@decodon.com Germany web: www.decodon.com ------------------------------------------------------------ From huntharo@msu.edu Thu Nov 20 18:28:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Thu, 20 Nov 2003 18:28:00 -0000 Subject: twm takes no control In-Reply-To: <008d01c3af8e$bbc1e850$7b05000a@corp.silverbacksystems.com> References: <008d01c3af8e$bbc1e850$7b05000a@corp.silverbacksystems.com> Message-ID: <3FBD07B6.1020405@msu.edu> Dai, Dai Itasaka wrote: > It is not just Cygwin version of twm. Exactly the same symptom is > observed when using a twm on a RedHat or SuSE box managing a cygwin > display. > > It is obvious that it is not twm that is broken. So it is another little issue related to the shared Xt and Xaw libraries. I did a search in the twm sources for "Vendor", "Shell", "VendorShell", etc. but didn't find anything. I am sure that you can probably find info on how the OS/2 guys handled this bug, but searching for "OS2" turned up nothing in the twm sources either. I am at a loss. As I said, this is yours to debug further. If twm is the only app that is broken by the shared libs, then I am still not particularly concerned. If it turns out that every other app is broken, or a significant number of other apps are broken, then I will certainly become concerned. Harold From ihok@hotmail.com Thu Nov 20 18:53:00 2003 From: ihok@hotmail.com (Jack Tanner) Date: Thu, 20 Nov 2003 18:53:00 -0000 Subject: Keyboard autorepeat settings [Was: Updated: XFree86-xserv-4.3.0-22] In-Reply-To: <3FBCF6D0.4090500@msu.edu> References: <1068549020528.tulitanssi.36802.w1Q4NRjiTPWoQQzb3m7sWA@luukku.com> <3FB0E0D5.7090505@msu.edu> <87ptfyvpbj.fsf@vzell-de.de.oracle.com> <3FB1123E.8090102@msu.edu> <87d6byvn9u.fsf@vzell-de.de.oracle.com> <87smktnyps.fsf@vzell-de.de.oracle.com> <3FBA8FE4.30902@users.sourceforge.net> <3FBCF6D0.4090500@msu.edu> Message-ID: Harold L Hunt II wrote: > It might be nice, but the Windows autorepeat caused problems with > systems running in Japanese... so they need the XKB autorepeat > functionality, since the Windows autorepeat needs to be disabled for them. Huh. Not that I'm completely amazed, but it seems strange that Windows would be unable to handle Japanese keyboards. Is this an underlying Windows bug? Perhaps there's some workaround from Microsoft? -JT From huntharo@msu.edu Thu Nov 20 18:58:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Thu, 20 Nov 2003 18:58:00 -0000 Subject: Keyboard autorepeat settings [Was: Updated: XFree86-xserv-4.3.0-22] In-Reply-To: References: <1068549020528.tulitanssi.36802.w1Q4NRjiTPWoQQzb3m7sWA@luukku.com> <3FB0E0D5.7090505@msu.edu> <87ptfyvpbj.fsf@vzell-de.de.oracle.com> <3FB1123E.8090102@msu.edu> <87d6byvn9u.fsf@vzell-de.de.oracle.com> <87smktnyps.fsf@vzell-de.de.oracle.com> <3FBA8FE4.30902@users.sourceforge.net> <3FBCF6D0.4090500@msu.edu> Message-ID: <3FBD0ED3.60205@msu.edu> Jack Tanner wrote: > Harold L Hunt II wrote: > >> It might be nice, but the Windows autorepeat caused problems with >> systems running in Japanese... so they need the XKB autorepeat >> functionality, since the Windows autorepeat needs to be disabled for >> them. > > > Huh. Not that I'm completely amazed, but it seems strange that Windows > would be unable to handle Japanese keyboards. Is this an underlying > Windows bug? Perhaps there's some workaround from Microsoft? It's not that it is unable to handle Japanese keyboards, it is that it sends fake autorepeat messages that screwup our handling of certain keys. As Takuma for a better explanation. Harold From ford@vss.fsi.com Thu Nov 20 19:14:00 2003 From: ford@vss.fsi.com (Brian Ford) Date: Thu, 20 Nov 2003 19:14:00 -0000 Subject: twm takes no control In-Reply-To: <3FBD07B6.1020405@msu.edu> References: <008d01c3af8e$bbc1e850$7b05000a@corp.silverbacksystems.com> <3FBD07B6.1020405@msu.edu> Message-ID: On Thu, 20 Nov 2003, Harold L Hunt II wrote: > Dai, > > Dai Itasaka wrote: > > > It is not just Cygwin version of twm. Exactly the same symptom is > > observed when using a twm on a RedHat or SuSE box managing a cygwin > > display. > > > > It is obvious that it is not twm that is broken. > > So it is another little issue related to the shared Xt and Xaw > libraries. I did a search in the twm sources for "Vendor", "Shell", > "VendorShell", etc. but didn't find anything. I am sure that you can > probably find info on how the OS/2 guys handled this bug, but searching > for "OS2" turned up nothing in the twm sources either. > I don't think so, Harold. If this happens with twm run from other OSs, that eliminates twm itself and all its dlls, doesn't it? It must be internal to the Cygwin X server, or its dlls, right? Dai, could you test the inverse? Cygwin's twm controlling a RedHat or SuSE X server? I think that would definately rule out twm and its dlls. > I am at a loss. As I said, this is yours to debug further. If twm is > the only app that is broken by the shared libs, then I am still not > particularly concerned. If it turns out that every other app is broken, > or a significant number of other apps are broken, then I will certainly > become concerned. > I don't have any examples, but to me, the description implies the latter ought to be the case. -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444 From huntharo@msu.edu Thu Nov 20 19:32:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Thu, 20 Nov 2003 19:32:00 -0000 Subject: twm takes no control In-Reply-To: References: <008d01c3af8e$bbc1e850$7b05000a@corp.silverbacksystems.com> <3FBD07B6.1020405@msu.edu> Message-ID: <3FBD16C0.6050801@msu.edu> Brian, Brian Ford wrote: > On Thu, 20 Nov 2003, Harold L Hunt II wrote: > > >>Dai, >> >>Dai Itasaka wrote: >> >> >>>It is not just Cygwin version of twm. Exactly the same symptom is >>>observed when using a twm on a RedHat or SuSE box managing a cygwin >>>display. >>> >>>It is obvious that it is not twm that is broken. >> >>So it is another little issue related to the shared Xt and Xaw >>libraries. I did a search in the twm sources for "Vendor", "Shell", >>"VendorShell", etc. but didn't find anything. I am sure that you can >>probably find info on how the OS/2 guys handled this bug, but searching >>for "OS2" turned up nothing in the twm sources either. >> > > I don't think so, Harold. If this happens with twm run from other OSs, > that eliminates twm itself and all its dlls, doesn't it? It must be > internal to the Cygwin X server, or its dlls, right? Hmmm... sounds reasonable. Harold From Cary.Jamison@powerquest.com Thu Nov 20 20:35:00 2003 From: Cary.Jamison@powerquest.com (Cary Jamison) Date: Thu, 20 Nov 2003 20:35:00 -0000 Subject: Keyboard autorepeat settings [Was: Updated: XFree86-xserv-4.3.0-22] Message-ID: "Harold L Hunt II" wrote in message news:<3FBCF6D0.4090500@msu.edu>... > Jack Tanner wrote: > > > Alexander Gottwald wrote: > > > >> If this is the case I can add code to use the windows default > >> autorepeat settings to configure Xwin. But this will again change the > >> old behavior > >> of Xwin and some users might be unhappy with it. > > > > > > It would be consistent with other behavior to get autorepeat settings > > from Windows, not from X settings. For example, we try to use the > > Windows language settings, right? > > Sort of... it isn't quite that cut and dried. > > Besides, we have been using *both* X autorepeat and Windows autorepeat > until recently. This was not a good solution. > > > Since Xwin is a Windows application, there's little reason for it to > > have its own autorepeat configuration. > > It might be nice, but the Windows autorepeat caused problems with > systems running in Japanese... so they need the XKB autorepeat > functionality, since the Windows autorepeat needs to be disabled for them. > > So, we can't just remove XKB support or disable it permanently... it is > required by some non-U.S. users. It seems to me that what is being asked for is that XKB support is kept but its default configuration (delay, repeat rate, etc.) is whatever Windows is currently set to. I think this makes very good since - if I really want a repeat rate different for X applications I can configure it, otherwise it should be the same as it is on all my other Windows apps. >From the above comments it looks like Alexander understood this but Harold thought everyone was asking to remove XKB support and go back to using Windows autorepeat. Forgive me if I misread you, Harold. > It may seems like we are being indecisive here... but there are really a > lot of concerns that need to be considered in order to get a correct > solution. > > Harold Cary From huntharo@msu.edu Thu Nov 20 20:46:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Thu, 20 Nov 2003 20:46:00 -0000 Subject: Keyboard autorepeat settings [Was: Updated: XFree86-xserv-4.3.0-22] In-Reply-To: References: Message-ID: <3FBD282F.406@msu.edu> Cary, Cary Jamison wrote: > It seems to me that what is being asked for is that XKB support is kept > but its default configuration (delay, repeat rate, etc.) is whatever > Windows is currently set to. I think this makes very good since - if I > really want a repeat rate different for X applications I can configure > it, otherwise it should be the same as it is on all my other Windows > apps. > > From the above comments it looks like Alexander understood this but > Harold thought everyone was asking to remove XKB support and go back to > using Windows autorepeat. Forgive me if I misread you, Harold. I think you hit the nail on the head. People are asking for XKB to handle the generation of autorepeat key events, but for it to grab its default settings from the Windows autorepeat settings? Is that what is going on here? Harold From Cary.Jamison@powerquest.com Fri Nov 21 02:27:00 2003 From: Cary.Jamison@powerquest.com (Cary Jamison) Date: Fri, 21 Nov 2003 02:27:00 -0000 Subject: mapping the right mouse button Message-ID: "J S" wrote in message news:... > I remember seeing recently that there was a fix for mapping the mouse > buttons in XFree86. I'm trying to get an application called EMC (which does > disk management on MVS) to work with XFree but the problem is the right > mouse button doesn't seem to work. > > It should bring up a menu when I right click on one of the disk images. I > found that I could use Shift-F10 instead though and wondered if someone > could tell me how to map these keys to the right mouse button? > > Thanks for any help. Make sure your numlock is off - that has caused similar problems for some people. > JS. Cary From lev.bishop@yale.edu Fri Nov 21 07:34:00 2003 From: lev.bishop@yale.edu (Lev Bishop) Date: Fri, 21 Nov 2003 07:34:00 -0000 Subject: TTF-font rendering not working anymore Message-ID: Harold, you wanted a three-click test case: $ xfontsel wait for it to finish parsing all the fonts. Note that it displays the alphabet in some default font at the bottom of the window. Click on family and choose a TTF from the list, eg. one of the Luxis. Note that the alphabet is no longer displayed. Just one click, three is not needed. There are programmes ttfmkfdir, mkfontscale, mkfontdir, which need to be run when adding new fonts or directories, but the files they create are already present and rerunning them doesn't change things. Anyway, the fonts show up in the xfontsel list, so I think the problem is with the rendering, not anything else. This is not a problem with the "new style" fonts stuff, fontconfig, etc, as used by xterm, etc, which work very well for me with the recent versions, much prettier than the older ones, and even somewhat better than the version of the freetype2 library that I compiled a while ago for myself. (So well done everyone for getting all that working!) However, I expect it is related to the seperating out of the freetype stuff from the X server. I believe the "old style" (server side) fonts rendering stuff uses hacked up parts of freetype1 and freetype2 for dealing with TTF so presumably in the seperation process something got broken. Hope that's useful. Lev From lev.bishop@yale.edu Fri Nov 21 07:45:00 2003 From: lev.bishop@yale.edu (Lev Bishop) Date: Fri, 21 Nov 2003 07:45:00 -0000 Subject: xterm doesn't properly erase chars with descenders Message-ID: I've been using xterm with lucida console and up until the recent versions of cygwin-xfree it worked fine. With the latest versions, however, there were problems with the vertical spacing and overwriting and stuff. Characters with descenders ("g" "q" etc) would get slightly overwritten by characters on the line below, and backspacing over these chars with descenders wouldn't erase the bottom of the descender parts. (Ie., in xterm write qqqqqq and then backspace a few times, and a row of dots remains behind at the bottom of the line). I fixed this problem by adding a line to my /etc/fonts/local.conf: true Not sure if this is a problem specific to Lucida Console, and if so whether its a problem with the font itself or with freetype2 or whatever, but anyway with the above line added, everything works just great. Lev From lev.bishop@yale.edu Fri Nov 21 07:53:00 2003 From: lev.bishop@yale.edu (Lev Bishop) Date: Fri, 21 Nov 2003 07:53:00 -0000 Subject: .Xdefaults "xterm*ColorMode: True" Message-ID: I always used to have the line: xterm*ColorMode:True in my ~/.Xdefaults and it worked. With the last few versions of cygwin/xfree it started complaining $ xterm Warning: Cannot convert string "true" to type Int Although the xterm actually seemed to work ok, even doing the ColorMode stuff right. So I changed the relevant line to an integer like it seemed to be asking xterm*ColorMode: 1 and it stopped complaining. Dunno what that's all about. Probably not a cygwin-specific thing, but I mention it here in case it is. Lev From zwin@users.sourceforge.net Fri Nov 21 08:29:00 2003 From: zwin@users.sourceforge.net (Zbynek Winkler) Date: Fri, 21 Nov 2003 08:29:00 -0000 Subject: Keyboard autorepeat settings [Was: Updated: XFree86-xserv-4.3.0-22] In-Reply-To: <3FBD282F.406@msu.edu> References: <3FBD282F.406@msu.edu> Message-ID: <3FBDCCD2.4040702@users.sourceforge.net> Harold L Hunt II wrote: > Cary, > > Cary Jamison wrote: > >> It seems to me that what is being asked for is that XKB support is kept >> but its default configuration (delay, repeat rate, etc.) is whatever >> Windows is currently set to. I think this makes very good since - if I >> really want a repeat rate different for X applications I can configure >> it, otherwise it should be the same as it is on all my other Windows >> apps. >> >> From the above comments it looks like Alexander understood this but >> Harold thought everyone was asking to remove XKB support and go back to >> using Windows autorepeat. Forgive me if I misread you, Harold. > > > I think you hit the nail on the head. > > People are asking for XKB to handle the generation of autorepeat key > events, but for it to grab its default settings from the Windows > autorepeat settings? Is that what is going on here? Yes, that was the original nature of my request. Forgive me for not being clear enough. I didn't understand the underlaying consequences to explain it better. Zbynek -- http://zw.matfyz.cz/ http://robotika.cz/ Faculty of Mathematics and Physics, Charles University, Prague, Czech Republic From vervoom@hotmail.com Fri Nov 21 09:00:00 2003 From: vervoom@hotmail.com (J S) Date: Fri, 21 Nov 2003 09:00:00 -0000 Subject: mapping the right mouse button Message-ID: > > I remember seeing recently that there was a fix for mapping the mouse > > buttons in XFree86. I'm trying to get an application called EMC (which >does > > disk management on MVS) to work with XFree but the problem is the >right > > mouse button doesn't seem to work. > > > > It should bring up a menu when I right click on one of the disk >images. I > > found that I could use Shift-F10 instead though and wondered if >someone > > could tell me how to map these keys to the right mouse button? > > > > Thanks for any help. > >Make sure your numlock is off - that has caused similar problems for >some people. > > > JS. > >Cary I've been caught out with the Num-lock before, but not this time! It's not that. _________________________________________________________________ Sign-up for a FREE BT Broadband connection today! http://www.msn.co.uk/specials/btbroadband From murakami@ipl.t.u-tokyo.ac.jp Fri Nov 21 09:22:00 2003 From: murakami@ipl.t.u-tokyo.ac.jp (Takuma Murakami) Date: Fri, 21 Nov 2003 09:22:00 -0000 Subject: Keyboard autorepeat settings [Was: Updated: XFree86-xserv-4.3.0-22] In-Reply-To: <3FBCF6D0.4090500@msu.edu> References: <3FBCF6D0.4090500@msu.edu> Message-ID: <20031121171819.F6E4.MURAKAMI@ipl.t.u-tokyo.ac.jp> It is my mistake that "silently" changing the default behaviour. I apologize and add some comments to show my intention. Harold L Hunt II wrote: > It might be nice, but the Windows autorepeat caused problems with > systems running in Japanese... so they need the XKB autorepeat > functionality, since the Windows autorepeat needs to be disabled for them. The Windows autorepeat is not crucial to Japanese language handling. Disabling it was a part of the patch to improve mode key states synchronization. Sorry for confusing you, Harold. I disabled it for the two reasons below: 1) Having both Windows and XKB autorepeat breaks the state synchronization. For example, if we press Caps Lock for a while, Windows toggles the state exactly once but XKB repeatedly toggles the state since it receives many KeyPress events generated by Windows autorepeat. 2) Having two schemes for autorepeat looks not so good as Harold said. Adoption of XKB layer is just my choice. Because we are using an X server, it is natural for me to configure it using X Window's manner (i.e. xset). Please consider keymaps; we set keymaps via xmodmap, setxkbmap and/or XF86Config file -- all those are X Window's manner. Anyway, now we seem to find a better solution to get default values from Windows and enable Windows autorepeat if XKB is disabled. It looks that Alexander is implementing the features, is it right? I really appreciate him. Takuma Murakami (murakami@ipl.t.u-tokyo.ac.jp) From hschultz@premitech.com Fri Nov 21 10:02:00 2003 From: hschultz@premitech.com (Henrik Schultz) Date: Fri, 21 Nov 2003 10:02:00 -0000 Subject: FW: I've given up on XF86, can' t make my AltGr keys work Message-ID: <81AC7B3F6CA6D4118AB00050BA8755668117EC@EXCHANGE> Sorry to say, but I've given up on resolving the problems I'm having with getting my keyboard under Cygwin/XF86 to work correctly with my Solaris box. I simply don't have the time to dig down into the intricacies of how keyboard maps, keysyms, etc. relate, and I seem unable to find problem descriptions in the FAQ or mailinglist archives that mach my problem, nor is there a step-by-step list to guide one through a problem solving process. I'm sure you have a fine product, but I guess I'll just have to dish out money on a Hummingbird license or whatever... sigh! - Henrik Henrik Schultz Senior Systems Architect PremiTech A/S, Teknikerbyen 5, DK-2830 Virum Tel: +45 4595 8500 Mob: +45 2212 2429 Web: http://www.premitech.com/ From murakami@ipl.t.u-tokyo.ac.jp Fri Nov 21 10:33:00 2003 From: murakami@ipl.t.u-tokyo.ac.jp (Takuma Murakami) Date: Fri, 21 Nov 2003 10:33:00 -0000 Subject: mapping the right mouse button In-Reply-To: References: Message-ID: <20031121183801.F6E7.MURAKAMI@ipl.t.u-tokyo.ac.jp> Let me narrow down your problem. > I remember seeing recently that there was a fix for mapping the mouse > buttons in XFree86. I'm trying to get an application called EMC (which does > disk management on MVS) to work with XFree but the problem is the right > mouse button doesn't seem to work. If you mean that the right click menu had worked before but it lost the function recently, then my patch may do something wrong. Otherwise, it is better to confirm EMC works well. A good experiment is to run EMC on another X server (e.g. XFree on Linux). You can also use xev and xmodmap to debug. Note that the right button is button 3 on X. > It should bring up a menu when I right click on one of the disk images. I > found that I could use Shift-F10 instead though and wondered if someone > could tell me how to map these keys to the right mouse button? My patch enables remapping among mouse buttons; for example, you can exchange left and right buttons. However, assigning arbitrary keys to mouse buttons is beyond X server's responsibility. Please configure EMC as you like or find a tool to assign it. Takuma Murakami (murakami@ipl.t.u-tokyo.ac.jp) From miny@test.fxh42.net Fri Nov 21 11:07:00 2003 From: miny@test.fxh42.net (=?ISO-8859-1?Q?Mikael_Nystr=F6m?=) Date: Fri, 21 Nov 2003 11:07:00 -0000 Subject: Listen_tcp Message-ID: My X-server listens on 0.0.0.0:6000. When I do xhost +remote_host and then try to display something on my X-server, the response is that it can't open the display. If I run it thru ssh -X, it works fine. Does 0.0.0.0 means that the X-server listens on localhost only? If so, how can I make it listen on my external address? //Mike From murakami@ipl.t.u-tokyo.ac.jp Fri Nov 21 11:07:00 2003 From: murakami@ipl.t.u-tokyo.ac.jp (Takuma Murakami) Date: Fri, 21 Nov 2003 11:07:00 -0000 Subject: wmaker TIFF (actually libtiff4) problem In-Reply-To: <3FBC70AD.9030604@cwilson.fastmail.fm> References: <20031120125755.128E.MURAKAMI@ipl.t.u-tokyo.ac.jp> <3FBC70AD.9030604@cwilson.fastmail.fm> Message-ID: <20031121194630.F6FD.MURAKAMI@ipl.t.u-tokyo.ac.jp> Thank you for clarification of patent issues. > (Of course, this makes me wonder: (a) there were reports that "this used > to work -- or still works -- with cygtiff3. But THAT dll did not > provide LZW support either. See below for random speculation. (b) Why Actually I have a system with a rather old cygwin installation. WindowMaker surely works fine on the system. In the old system WindowMaker is version 0.80.0-2 in contrast to the new system having version 0.80.2-1. The old wmaker.exe is linked against cygtiff3.dll. Since their cygtiff3.dll are identical in two systems the old wmaker.exe also works fine on the new system. I believe I have not recompiled any TIFF packages. For now I will not go further because I'm not using WindowMaker. It seems too hard for me to track down. Takuma Murakami (murakami@ipl.t.u-tokyo.ac.jp) From hans.dekker.ext@juntadeandalucia.es Fri Nov 21 12:18:00 2003 From: hans.dekker.ext@juntadeandalucia.es (Hans Dekker) Date: Fri, 21 Nov 2003 12:18:00 -0000 Subject: Alt Gr keys are not functioning ? References: <81AC7B3F6CA6D4118AB00050BA8755668117E1@EXCHANGE> Message-ID: <3FBE0282.9010306@juntadeandalucia.es> Hi Henrik, I had the same problem on systems running Linux & HP-Ux with a CDE/Xcdmp session. It seems to me the 3rd key in the keyboard layout isn't mapped. Check xmodmap -pk in a X-Window to see what's mapped on your keyboard. You can use the following command to map a vertical bar to the AltGr 1, for example. xmodmap -e "Keycode 113 = Mode_switch" xmodmap -e "KeySym 1 = 1 exclam bar" Check the settings in these configuration files in your Cygwin directory: /etc/X11/XF86Config /etc/X11/xkb/symbols/pc/ Also look at the mails of Alexander Gottwald in the mail group. It is a temporal solution though, because I think XFree86 should send the right keyboard map to the X server in use. Apart from foreign language keyboard mapping XFree86 seems to me a stable and well working product. I have no profound knowledge of X to know how to resolve this otherwise. You'll probably find some other commands to map a keyboard. Also the lack of time to dig into the code and start debugging plays parts. Regards, Hans. Henrik Schultz escribi??: > Have just installed latest version of Cygwin/XFree86 on my Windows 2000 > laptop. > > Everything seems to be working fine, except for one thing: when I open an > xterm from a remote Solaris 2.6 system, the @,??,$, etc. keys are not > working, i.e. all the keys that are accessed by using the Alt Gr key are not > producing any output. > > This is what I have done to investigate the problem: > > - If I from a BASH shell telnet over to the Solaris box, ALL characters work > A-OK. > - When I open an xterm back to the XFree86 server, our 3 Danish national > characters ??,??,?? are working fine, so the correct keyboard map seems to have > been loaded. However this is where the problem with the missing @,??,$ etc. > comes up. > - Ran xkeycaps on the Solaris box, from which I noted that there was ex. no > '$' character mapped to the '4' key, nor was there any other special > characters mapped to keys usually accessed by Alt Gr. > - Alt Gr is mapped to ISO_Level3_Shift. > - Running 'xev' correctly lists events for Alt Gr and other keys, however > whereas SHIFT-'h' produces 'H' etc., Alt Gr-'4' does not produce any visible > character. Here is the list for the latter: > > KeyPress event, serial 17, synthetic NO, window 0x200001, > root 0x3a, subw 0x0, time 25838834, (431,266), root:(437,291), > state 0x0, keycode 113 (keysym 0xfe03, ISO_Level3_Shift), same_screen > YES, > XLookupString gives 0 bytes: "" > > KeyPress event, serial 22, synthetic NO, window 0x200001, > root 0x3a, subw 0x0, time 25840146, (431,266), root:(437,291), > state 0x80, keycode 13 (keysym 0x0, NoSymbol), same_screen YES, > XLookupString gives 0 bytes: "" > > KeyRelease event, serial 22, synthetic NO, window 0x200001, > root 0x3a, subw 0x0, time 25840206, (431,266), root:(437,291), > state 0x80, keycode 13 (keysym 0x0, NoSymbol), same_screen YES, > XLookupString gives 0 bytes: "" > > KeyRelease event, serial 22, synthetic NO, window 0x200001, > root 0x3a, subw 0x0, time 25840997, (431,266), root:(437,291), > state 0x80, keycode 113 (keysym 0xfe03, ISO_Level3_Shift), same_screen > YES, > XLookupString gives 0 bytes: "" > > Would anyone have a clue how to proceed with debugging this? > > Thanks! > > Henrik Schultz > Senior Systems Architect > PremiTech A/S, Teknikerbyen 5, DK-2830 Virum > Tel: +45 4595 8500 > Mob: +45 2212 2429 > Web: http://www.premitech.com/ > > . > From kris.thielemans@csc.mrc.ac.uk Fri Nov 21 12:48:00 2003 From: kris.thielemans@csc.mrc.ac.uk (Kris Thielemans) Date: Fri, 21 Nov 2003 12:48:00 -0000 Subject: xterm keyboard problems when login-in to a sun Message-ID: Hi I'm using XFree86 on my NT box with very good results. Thanks! I'm using it in default mode (no multiwindow). I have one problem: I launch xterm on my PC, then rlogin (or ssh -X) to a SUN (default shell on the SUN is csh). Then I cannot delete characters that I type on the command line: backspace gets displayed as ^H delete gets displayed as ~[[3 I guess this can be solved somehow with stty, but 1) I don't know how and 2) I thought this shouldn't happen when you come from an xterm as it is supported by SUN termcap obviously (I'm not surprised when this happens when login in via a cygwin terminal). [the latter point is why I'm posting this here] Note that backspace does work when I launch a bash shell, but fine. Note also that when then launching xterm on the SUN (displaying on my PC) the Delete key works (to delete the previous character), while backspace still displays as ^H. Here is the output of "stty -a" I got from the SUN (with xterm on the PC). speed 9600 baud; rows = 46 columns = 80; ypixels = 694 xpixels = 739 intr = ^c; quit = ^|; erase = ^?; kill = ^u; eof = ^d; eol = ; eol2 = ; swtch = ; start = ^q; stop = ^s; susp = ^z; dsusp = ^y; rprnt = ^r; flush = ^o; werase = ^w; lnext = ^v; -parenb -parodd cs8 -cstopb -hupcl cread -clocal -loblk -parext -ignbrk brkint ignpar -parmrk -inpck -istrip -inlcr -igncr icrnl -iuclc ixon -ixany -ixoff imaxbel isig icanon -xcase echo echoe echok -echonl -noflsh -tostop echoctl -echoprt echoke -defecho -flusho -pendin iexten opost -olcuc onlcr -ocrnl -onocr -onlret -ofill -ofdel -tabs "stty -a" with xterm on the SUN looks very similar. Kris Thielemans PS: when xterm displays a shell from the PC, backspace works as I expect, but that's because stty -a reports 'erase=^H'. I wouldn't mind if anybody told me who sets all this and where. It's an eternal problem with Unix systems. PPS: please reply to myself and to the list if you don't mind. From kirk.woellert@ngc.com Fri Nov 21 13:25:00 2003 From: kirk.woellert@ngc.com (Woellert, Kirk D.) Date: Fri, 21 Nov 2003 13:25:00 -0000 Subject: XWin works on Win2K but not on some WinXP clients [FIXED] Message-ID: Well it picked up my Putty SSH session but it did not pick up my XDM attempt. I tried sever times. Nov 20 23:55:52 gaia last message repeated 7 times Nov 20 23:56:06 gaia last message repeated 7 times Nov 21 04:04:45 gaia su(pam_unix)[2891]: session opened for user news by (uid=0) Nov 21 04:04:45 gaia su(pam_unix)[2891]: session closed for user news Nov 21 07:59:10 gaia sshd(pam_unix)[3253]: authentication failure; logname= uid=0 euid=0 tty=NODEVssh ruser= rhost=ngc-d4o1xu3vg29.ad.tasc.com user=kdw Nov 21 07:59:24 gaia sshd(pam_unix)[3255]: session opened for user kdw by (uid=505) Nov 21 07:59:52 gaia su(pam_unix)[3280]: session opened for user root by kdw(uid=505) [kdw@gaia log]# -----Original Message----- From: Igor Pechtchanski [mailto:pechtcha@cs.nyu.edu] Sent: Wednesday, November 19, 2003 4:40 PM To: Woellert, Kirk D. Cc: cygwin-xfree@cygwin.com Subject: Re: XWin works on Win2K but not on some WinXP clients [FIXED] Kirk, Try to open an XDMCP session from your PC and see what that adds to /var/log/messages (don't scan the whole thing, the relevant messages will be appended). See if it shows something like Nov 17 17:03:10 gaia gdm[XXXX]: gdm_auth_secure_display: Error getting hentry for XPmachine Nov 17 17:03:10 gaia gdm[XXXX]: gdm_xdmcp_display_alloc: Error setting up cookies for XPmachine:0 In any case, there should be some indication that gdm received a connection request from your machine, even if it was refused. Igor On Tue, 18 Nov 2003, Igor Pechtchanski wrote: > Kirk, > > Check /var/log/messages and see if there are any from gdm. This may be a > DNS lookup issue (i.e., your XP machine is not registered in DNS, or > registered, but not with the correct name). Confirm by "nslookup YOUR_IP" > from the Linux machine. If it is a DNS issue, try adding your XP machine > to /etc/hosts and restarting gdm ("kill -USR1 `cat /var/run/gdm.pid`"). > Igor > > On Tue, 18 Nov 2003, Harold L Hunt II wrote: > > > So echo on UDP port 177 works fine. This is not good. There must be > > something else in the gdm conf on the linux box that explicitly denies > > gdm connections from the Windows XP machine's IP addresses, since it > > worked fine when using 10.0.0.x addresses. Anyway you can change the IP > > of the XP machine to one not previously used as a test? > > > > Harold > > > > Woellert, Kirk D. wrote: > > > > > 1. Edited the echo-upd file in the xinetd.d folder. Changed the default port > > > from "7" to "177"... > > > > > > [root@gaia xinetd.d]# cat echo-udp > > > # default: off > > > # description: An xinetd internal service which echo's characters back to > > > clients. \ > > > # This is the udp version. > > > service echo > > > { > > > disable = no > > > type = INTERNAL UNLISTED > > > id = echo-dgram > > > socket_type = dgram > > > protocol = udp > > > user = root > > > wait = yes > > > port = 177 > > > } > > > [root@gaia xinetd.d]# > > > > > > 2. Did a grep just to ensure gdm was not gonna respond to my upd packets... > > > > > > [root@gaia xinetd.d]# ps -ef |grep xdm > > > root 2328 1912 0 18:12 pts/0 00:00:00 grep xdm > > > [root@gaia xinetd.d]# > > > > > > 3. Ran a upd echo test from the WinXP client to the Linux box using a Java > > > echo client.... > > > > > > C:\Bin>java -jar UDPEchoClient.jar 137.51.14.130:177 > > > 64 bytes from 137.51.14.130: seq no 0 time=0 ms > > > 64 bytes from 137.51.14.130: seq no 1 time=0 ms > > > 64 bytes from 137.51.14.130: seq no 2 time=0 ms > > > 64 bytes from 137.51.14.130: seq no 3 time=0 ms > > > 64 bytes from 137.51.14.130: seq no 4 time=0 ms > > > 64 bytes from 137.51.14.130: seq no 5 time=0 ms > > > 64 bytes from 137.51.14.130: seq no 6 time=0 ms > > > 64 bytes from 137.51.14.130: seq no 7 time=0 ms > > > 64 bytes from 137.51.14.130: seq no 8 time=0 ms > > > 64 bytes from 137.51.14.130: seq no 9 time=0 ms > > > 64 bytes from 137.51.14.130: seq no 10 time=0 ms > > > 64 bytes from 137.51.14.130: seq no 11 time=0 ms > > > 64 bytes from 137.51.14.130: seq no 12 time=0 ms > > > 64 bytes from 137.51.14.130: seq no 13 time=0 ms > > > 64 bytes from 137.51.14.130: seq no 14 time=0 ms > > > 64 bytes from 137.51.14.130: seq no 15 time=0 ms > > > 64 bytes from 137.51.14.130: seq no 16 time=0 ms > > > 64 bytes from 137.51.14.130: seq no 17 time=0 ms > > > 64 bytes from 137.51.14.130: seq no 18 time=0 ms > > > 64 bytes from 137.51.14.130: seq no 19 time=0 ms > > > 64 bytes from 137.51.14.130: seq no 20 time=0 ms > > > 64 bytes from 137.51.14.130: seq no 21 time=0 ms > > > 64 bytes from 137.51.14.130: seq no 22 time=0 ms > > > 64 bytes from 137.51.14.130: seq no 23 time=0 ms > > > 64 bytes from 137.51.14.130: seq no 24 time=0 ms > > > 64 bytes from 137.51.14.130: seq no 25 time=0 ms > > > 64 bytes from 137.51.14.130: seq no 26 time=0 ms > > > 64 bytes from 137.51.14.130: seq no 27 time=0 ms > > > 64 bytes from 137.51.14.130: seq no 28 time=0 ms > > > 64 bytes from 137.51.14.130: seq no 29 time=0 ms > > > 64 bytes from 137.51.14.130: seq no 30 time=0 ms > > > 64 bytes from 137.51.14.130: seq no 31 time=0 ms > > > 32 packets transmitted, 32 packets received, 0% packet loss > > > round-trip min/avg/max = 0/0.0/0 ms > > > > > > C:\Bin> > > > > > > Having trouble getting Java to run on the Linux box, so I could not complete > > > the echo test from the Linux host to the WinXP client. > > > > > > -----Original Message----- > > > From: Harold L Hunt II [mailto:huntharo@msu.edu] > > > Sent: Monday, November 17, 2003 4:41 PM > > > To: cygwin-xfree@cygwin.com > > > Subject: Re: XWin works on Win2K but not on some WinXP clients [FIXED] > > > > > > > > > Kirk, > > > > > > Well then, I suppose the next step would be to do a "telinit 3" (to stop > > > gdm), then edit xinetd conf file to run "echo" on UDP port 177, restart > > > xinetd, then use that udp echo client that we found to test if echo > > > works from the Windows XP machine plugged into its normal jack to gaia > > > plugged into its normal jack. We know that echo worked on UDP port 7, > > > but proving that it does or does not work on UDP port 177 would tell us > > > if they know what they are talking about :) > > > > > > Harold > > > > > > Woellert, Kirk D. wrote: > > > > > > > > >>I aksed corporate IS if they were doing an port blocking/filtering within > > >>our LAN. They replied: > > >> > > >>"There should be no port blocking within the corp. LAN. - only in/out > > >>to the Internet and in/out of DMZs." > > >> > > >> > > >>-----Original Message----- > > >>From: Harold L Hunt II [mailto:huntharo@msu.edu] > > >>Sent: Monday, November 17, 2003 10:45 AM > > >>To: cygwin-xfree@cygwin.com > > >>Subject: Re: XWin works on Win2K but not on some WinXP clients [FIXED] > > >> > > >> > > >>Kirk Woellert's problem with XP clients has been fixed, sort of. > > >> > > >>I talked to him on the phone for a few hours on Friday and walked him > > >>through some debugging. > > >> > > >> > > >>Here is what we found out: > > >> > > >>1) We could ssh from XP to Linux (TCP protocol). > > >> > > >>2) We could tunnel X apps over ssh from the Linux box to display on the > > >>XP box (TCP protocol). > > >> > > >>3) We could natively display X apps by exporting DISPLAY on Linux box, > > >>pointed to XP box (TCP protocol). > > >> > > >>4) We could not (nor could X-Win32) get an XDMCP login on the XP box for > > >>the Linux box (UDP protocol). > > >> > > >>5) We could run the echo service on the Linux box on port 7 and use a > > >>Java echo client for UDP to verify that UDP to Linux box worked (UDP > > >>protocol). > > >> > > >>6) It was revealed that there are really two parts of the network here. > > >> Not much is known about whether port blocking is in effect between the > > >>two parts. > > >> > > >>7) Removing the troubled hosts from the network and hooking them to a > > >>stand-alone hub with assigned IP addresses allowed XDMCP to work. > > >> > > >>8) We thus confirmed in #5 that UDP was not blocked in general, but #7 > > >>indicates that UDP port 177 is blocked between the segments. It turns > > >>out that all of the Windows 2000 machines were on one "segment", while > > >>the Windows XP machines were on another "segment". The problem was not > > >>the OS, it was that one segment has UDP port 177 blocked. > > >> > > >> > > >>Thus, we determined that the problem is in the network that the machines > > >>are attached to; this may or may not be by design. In any case, it > > >>isn't a problem with Cygwin/X. :) > > >> > > >>Harold > > -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_ pechtcha@cs.nyu.edu ZZZzz /,`.-'`' -. ;-;;,_ igor@watson.ibm.com |,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 From hschultz@premitech.com Fri Nov 21 13:49:00 2003 From: hschultz@premitech.com (Henrik Schultz) Date: Fri, 21 Nov 2003 13:49:00 -0000 Subject: xterm keyboard problems when login-in to a sun Message-ID: <81AC7B3F6CA6D4118AB00050BA8755668117F4@EXCHANGE> This is usually remedied like this: % stty erase [hit backspace key here] Then your backspace key works as intended. Regards - Henrik -----Original Message----- From: Kris Thielemans [mailto:kris.thielemans@csc.mrc.ac.uk] Sent: 21. november 2003 13:48 To: Cygwin-Xfree Cc: Kris Thielemans Subject: xterm keyboard problems when login-in to a sun Hi I'm using XFree86 on my NT box with very good results. Thanks! I'm using it in default mode (no multiwindow). I have one problem: I launch xterm on my PC, then rlogin (or ssh -X) to a SUN (default shell on the SUN is csh). Then I cannot delete characters that I type on the command line: backspace gets displayed as ^H delete gets displayed as ~[[3 I guess this can be solved somehow with stty, but 1) I don't know how and 2) I thought this shouldn't happen when you come from an xterm as it is supported by SUN termcap obviously (I'm not surprised when this happens when login in via a cygwin terminal). [the latter point is why I'm posting this here] Note that backspace does work when I launch a bash shell, but fine. Note also that when then launching xterm on the SUN (displaying on my PC) the Delete key works (to delete the previous character), while backspace still displays as ^H. Here is the output of "stty -a" I got from the SUN (with xterm on the PC). speed 9600 baud; rows = 46 columns = 80; ypixels = 694 xpixels = 739 intr = ^c; quit = ^|; erase = ^?; kill = ^u; eof = ^d; eol = ; eol2 = ; swtch = ; start = ^q; stop = ^s; susp = ^z; dsusp = ^y; rprnt = ^r; flush = ^o; werase = ^w; lnext = ^v; -parenb -parodd cs8 -cstopb -hupcl cread -clocal -loblk -parext -ignbrk brkint ignpar -parmrk -inpck -istrip -inlcr -igncr icrnl -iuclc ixon -ixany -ixoff imaxbel isig icanon -xcase echo echoe echok -echonl -noflsh -tostop echoctl -echoprt echoke -defecho -flusho -pendin iexten opost -olcuc onlcr -ocrnl -onocr -onlret -ofill -ofdel -tabs "stty -a" with xterm on the SUN looks very similar. Kris Thielemans PS: when xterm displays a shell from the PC, backspace works as I expect, but that's because stty -a reports 'erase=^H'. I wouldn't mind if anybody told me who sets all this and where. It's an eternal problem with Unix systems. PPS: please reply to myself and to the list if you don't mind. From hschultz@premitech.com Fri Nov 21 14:14:00 2003 From: hschultz@premitech.com (Henrik Schultz) Date: Fri, 21 Nov 2003 14:14:00 -0000 Subject: Alt Gr keys are not functioning ? Message-ID: <81AC7B3F6CA6D4118AB00050BA8755668117F5@EXCHANGE> Hans wrote: >You can use the following command to map a vertical bar to the AltGr 1, >for example. >xmodmap -e "Keycode 113 = Mode_switch" >xmodmap -e "KeySym 1 = 1 exclam bar" This in fact works! Thanks, this is surely one way to proceed to get me going. Now I can only wonder about the underlying problem; it could be be that the Alt Gr maps to BOTH ISO_Level3_Shift AND Mode_switch, and the Cygwin client uses the ISO_Level3_Shift modifier, and the Solaris xterm client uses the Mode_switch modifier. In fact, it ONLY works when I change the Alt Gr key to send Mode_Switch too, so somehow this must be related. I'll now add these xmodmap entries to my .bashrc file if there is a valid display setting. Thanks again - Henrik From Alexander.Gottwald@s1999.tu-chemnitz.de Fri Nov 21 14:30:00 2003 From: Alexander.Gottwald@s1999.tu-chemnitz.de (Alexander Gottwald) Date: Fri, 21 Nov 2003 14:30:00 -0000 Subject: Keyboard autorepeat settings [Was: Updated: XFree86-xserv-4.3.0-22] In-Reply-To: References: Message-ID: Cary Jamison wrote: > > It seems to me that what is being asked for is that XKB support is kept > but its default configuration (delay, repeat rate, etc.) is whatever > Windows is currently set to. I think this makes very good since - if I > really want a repeat rate different for X applications I can configure > it, otherwise it should be the same as it is on all my other Windows > apps. It's on my todo list. I'll start with it right after I finish with getting the fiasco microkernel running. bye ago -- Alexander.Gottwald@informatik.tu-chemnitz.de http://www.gotti.org ICQ: 126018723 From Alexander.Gottwald@s1999.tu-chemnitz.de Fri Nov 21 14:42:00 2003 From: Alexander.Gottwald@s1999.tu-chemnitz.de (Alexander Gottwald) Date: Fri, 21 Nov 2003 14:42:00 -0000 Subject: FW: I've given up on XF86, can' t make my AltGr keys work In-Reply-To: <81AC7B3F6CA6D4118AB00050BA8755668117EC@EXCHANGE> References: <81AC7B3F6CA6D4118AB00050BA8755668117EC@EXCHANGE> Message-ID: Henrik Schultz wrote: > I simply don't have the time to dig down into the intricacies of how > keyboard maps, keysyms, etc. relate, and I seem unable to find problem > descriptions in the FAQ or mailinglist archives that mach my problem, nor is > there a step-by-step list to guide one through a problem solving process. > > I'm sure you have a fine product, but I guess I'll just have to dish out > money on a Hummingbird license or whatever... sigh! I'm sorry to hear. If someone could donate an old sparc or HP-UX machine I'd be willing to debug the problems with xdmcp, fonts and keyboardlayouts with those machines. bye ago -- Alexander.Gottwald@informatik.tu-chemnitz.de http://www.gotti.org ICQ: 126018723 From Alexander.Gottwald@s1999.tu-chemnitz.de Fri Nov 21 14:44:00 2003 From: Alexander.Gottwald@s1999.tu-chemnitz.de (Alexander Gottwald) Date: Fri, 21 Nov 2003 14:44:00 -0000 Subject: Listen_tcp In-Reply-To: References: Message-ID: Mikael Nystr?m wrote: > > My X-server listens on 0.0.0.0:6000. > When I do xhost +remote_host and then try to display something on my > X-server, the response is that it can't open the display. > If I run it thru ssh -X, it works fine. Maybe there is a firewall inbetween and blocks the connection. > Does 0.0.0.0 means that the X-server listens on localhost only? > If so, how can I make it listen on my external address? 0.0.0.0 means it listens on all interfaces. bye ago NP: Lacrimosa - Verm?chtnis der Sonne -- Alexander.Gottwald@informatik.tu-chemnitz.de http://www.gotti.org ICQ: 126018723 From holger.krull@gmx.de Fri Nov 21 15:23:00 2003 From: holger.krull@gmx.de (Holger Krull) Date: Fri, 21 Nov 2003 15:23:00 -0000 Subject: xwinclip & startxdmcp.bat questions/problems In-Reply-To: <3FBBA9EE.4040705@JaySmith.com> References: <3FBBA9EE.4040705@JaySmith.com> Message-ID: <3FBE2E1D.4060404@gmx.de> Jay Smith schrieb: > a) I am still (same as before this upgrade) left with a DOS window for > the startxdmcp that has to be manually closed. Annoying, but not terrible. You could start xwinclip with a link like this to prevent the DOS Window D:\cygwin\bin\bash.exe -l -c "xwin +kb -xkbmap de -query murpel -from 192.168.1.2 -fp tcp/192.168.1.1:7100 -dpi 100 -once -ac &" > b) I am additionally now left with *another* DOS window for xwinclip. > When I try to close it, it says that the program will terminate. It is As to my knowledge you have to live with that window, i know no way to get it in the background. That would be a bad idea anyway because > c) Harold mentioned "restarting" xwinclip. I have not been able to find > any instructions on how to do this. The xwinclip readme does not cover you need to restart it manually if it stops working. I have a bash shell running and start xwinclip --display 127.0.0.1:0.0 CTRL-C if it stops working and restart. Holger From dirk.goethals@alcatel.be Fri Nov 21 15:25:00 2003 From: dirk.goethals@alcatel.be (dirk.goethals@alcatel.be) Date: Fri, 21 Nov 2003 15:25:00 -0000 Subject: DDD 3.3.8 segmentation error, related to Motif? In-Reply-To: References: <3FB80677.8090004@alcatel.be> <3FBBC39B.3030009@alcatel.be> Message-ID: <3FBE2E7E.8040805@alcatel.be> From: Harold L Hunt II : > DDD can work with LessTif, but you have to tell it that you want it to > be compile for LessTif, and you may have to find a better distribution > of the source than you have now (one with more recent patches for the > LessTif support). The following are useful (I googled for "DDD LessTif"): > >http://rsusu1.rnd.runnet.ru/cgi-bin/info2html?(ddd)LessTif > Interesting link, but problem still there. ;-(( I don't understand why DDD wants Motif 2.1, althouht its configuration is reporting "GNU/LessTif Version 2.1 Release 0.93.91" ? Some details follow: bt08pm: /usr/X11R6/include/Xm/ ddd --lesstif-version 93 Warning: This DDD requires a Motif 2.1 library (using Motif -1617156.-609) Continue at own risk. Warning: No type converter registered for 'String' to 'Orientation' conversion. Warning: No type converter registered for 'String' to 'Orientation' conversion. Warning: No type converter registered for 'String' to 'Orientation' conversion. Internal error (Segmentation fault). Although: bt08pm: /usr/bin/ ddd --configuration GNU DDD 3.3.8 (i686-pc-cygwin) Copyright (C) 1995-1999 Technische Universit?t Braunschweig, Germany. Copyright (C) 1999-2001 Universit?t Passau, Germany. Copyright (C) 2001 Universit?t des Saarlandes, Germany. Compiled with GCC 3.2 20020927 (prerelease) Requires X11R6, Xt11R6, Motif 2.1 (GNU/LessTif Version 2.1 Release 0.93.91) Includes XPM 3.4.11, Athena Panner (7000002L), DDD core Built 2003-11-14 by goethald . And indeed report this same release: /usr/X11R6/include/Xm/Xm.h:#define LESSTIF_VERSION 0 /usr/X11R6/include/Xm/Xm.h:#define LESSTIF_REVISION 93 /usr/X11R6/include/Xm/Xm.h:#define LesstifVersion (LESSTIF_VERSION * 1000 + LESSTIF_REVISION) /usr/X11R6/include/Xm/Xm.h:#define LesstifVERSION_STRING "@(#)GNU/LessTif Version 2.1 Release 0.93.91" /usr/X11R6/include/Xm/Xm.h:#define XmVERSION_STRING LesstifVERSION_STRING >http://mail.gnu.org/archive/html/bug-ddd/2003-06/msg00009.html > No help from that link :-( > > > Hope that helps, > > Harold From huntharo@msu.edu Fri Nov 21 15:49:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Fri, 21 Nov 2003 15:49:00 -0000 Subject: DDD 3.3.8 segmentation error, related to Motif? In-Reply-To: <3FBE2E7E.8040805@alcatel.be> References: <3FB80677.8090004@alcatel.be> <3FBBC39B.3030009@alcatel.be> <3FBE2E7E.8040805@alcatel.be> Message-ID: <3FBE33F6.2090404@msu.edu> Dirk, dirk.goethals@alcatel.be wrote: > > From: Harold L Hunt II : > >> DDD can work with LessTif, but you have to tell it that you want it to >> be compile for LessTif, and you may have to find a better distribution >> of the source than you have now (one with more recent patches for the >> LessTif support). The following are useful (I googled for "DDD LessTif"): >> >> http://rsusu1.rnd.runnet.ru/cgi-bin/info2html?(ddd)LessTif >> > Interesting link, but problem still there. ;-(( > I don't understand why DDD wants Motif 2.1, althouht its configuration > is reporting "GNU/LessTif Version 2.1 Release 0.93.91" ? > Some details follow: The idea is that you have to tell ddd to use LessTif at *compile time*, not at run time. You did a recompile using whatever option it is that you need to do this, right? Harold From ford@vss.fsi.com Fri Nov 21 15:58:00 2003 From: ford@vss.fsi.com (Brian Ford) Date: Fri, 21 Nov 2003 15:58:00 -0000 Subject: DDD 3.3.8 segmentation error, related to Motif? In-Reply-To: <3FBE2E7E.8040805@alcatel.be> References: <3FB80677.8090004@alcatel.be> <3FBBC39B.3030009@alcatel.be> <3FBE2E7E.8040805@alcatel.be> Message-ID: On Fri, 21 Nov 2003 dirk.goethals@alcatel.be wrote: > bt08pm: /usr/X11R6/include/Xm/ ddd --lesstif-version 93 > Warning: This DDD requires a Motif 2.1 library (using Motif > -1617156.-609) > Could you post cygcheck `type ddd`? > bt08pm: /usr/bin/ ddd --configuration > GNU DDD 3.3.8 (i686-pc-cygwin) > Copyright (C) 1995-1999 Technische Universit?t Braunschweig, Germany. > Copyright (C) 1999-2001 Universit?t Passau, Germany. > Copyright (C) 2001 Universit?t des Saarlandes, Germany. > > Compiled with GCC 3.2 20020927 (prerelease) > Why not the current Cygwin gcc? -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444 From pechtcha@cs.nyu.edu Fri Nov 21 17:35:00 2003 From: pechtcha@cs.nyu.edu (Igor Pechtchanski) Date: Fri, 21 Nov 2003 17:35:00 -0000 Subject: XWin works on Win2K but not on some WinXP clients [FIXED] In-Reply-To: References: Message-ID: Kirk, There is no need to Cc: either me or Harold - we both read the cygwin-xfree list, AFAIK. As for your problem, this doesn't look right -- you used to get gdm messages, and now you don't. A silly question: did you restart gdm after your Java echo test before attempting to connect? Igor On Fri, 21 Nov 2003, Woellert, Kirk D. wrote: > Well it picked up my Putty SSH session but it did not pick up my XDM > attempt. I tried sever times. > > Nov 20 23:55:52 gaia last message repeated 7 times > Nov 20 23:56:06 gaia last message repeated 7 times > Nov 21 04:04:45 gaia su(pam_unix)[2891]: session opened for user news by > (uid=0) > Nov 21 04:04:45 gaia su(pam_unix)[2891]: session closed for user news > Nov 21 07:59:10 gaia sshd(pam_unix)[3253]: authentication failure; logname= > uid=0 euid=0 tty=NODEVssh ruser= rhost=ngc-d4o1xu3vg29.ad.tasc.com user=kdw > Nov 21 07:59:24 gaia sshd(pam_unix)[3255]: session opened for user kdw by > (uid=505) > Nov 21 07:59:52 gaia su(pam_unix)[3280]: session opened for user root by > kdw(uid=505) > [kdw@gaia log]# > > -----Original Message----- > From: Igor Pechtchanski [mailto:pechtcha@cs.nyu.edu] > Sent: Wednesday, November 19, 2003 4:40 PM > To: Woellert, Kirk D. > Cc: cygwin-xfree@cygwin.com > Subject: Re: XWin works on Win2K but not on some WinXP clients [FIXED] > > > Kirk, > > Try to open an XDMCP session from your PC and see what that adds to > /var/log/messages (don't scan the whole thing, the relevant messages will > be appended). See if it shows something like > > Nov 17 17:03:10 gaia gdm[XXXX]: gdm_auth_secure_display: Error getting hentry for XPmachine > Nov 17 17:03:10 gaia gdm[XXXX]: gdm_xdmcp_display_alloc: Error setting up cookies for XPmachine:0 > > In any case, there should be some indication that gdm received a > connection request from your machine, even if it was refused. > Igor > > On Tue, 18 Nov 2003, Igor Pechtchanski wrote: > > > Kirk, > > > > Check /var/log/messages and see if there are any from gdm. This may be a > > DNS lookup issue (i.e., your XP machine is not registered in DNS, or > > registered, but not with the correct name). Confirm by "nslookup YOUR_IP" > > from the Linux machine. If it is a DNS issue, try adding your XP machine > > to /etc/hosts and restarting gdm ("kill -USR1 `cat /var/run/gdm.pid`"). > > Igor > > > > On Tue, 18 Nov 2003, Harold L Hunt II wrote: > > > > > So echo on UDP port 177 works fine. This is not good. There must be > > > something else in the gdm conf on the linux box that explicitly denies > > > gdm connections from the Windows XP machine's IP addresses, since it > > > worked fine when using 10.0.0.x addresses. Anyway you can change the IP > > > of the XP machine to one not previously used as a test? > > > > > > Harold > > > > > > Woellert, Kirk D. wrote: > > > > > > > 1. Edited the echo-upd file in the xinetd.d folder. Changed the > > > > default port from "7" to "177"... > > > > > > > > [root@gaia xinetd.d]# cat echo-udp > > > > # default: off > > > > # description: An xinetd internal service which echo's characters back to clients. \ > > > > # This is the udp version. > > > > service echo > > > > { > > > > disable = no > > > > type = INTERNAL UNLISTED > > > > id = echo-dgram > > > > socket_type = dgram > > > > protocol = udp > > > > user = root > > > > wait = yes > > > > port = 177 > > > > } > > > > [root@gaia xinetd.d]# > > > > > > > > 2. Did a grep just to ensure gdm was not gonna respond to my upd > > > > packets... > > > > > > > > [root@gaia xinetd.d]# ps -ef |grep xdm > > > > root 2328 1912 0 18:12 pts/0 00:00:00 grep xdm > > > > [root@gaia xinetd.d]# > > > > > > > > 3. Ran a upd echo test from the WinXP client to the Linux box > > > > using a Java echo client.... > > > > > > > > C:\Bin>java -jar UDPEchoClient.jar 137.51.14.130:177 > > > > 64 bytes from 137.51.14.130: seq no 0 time=0 ms > > > > 64 bytes from 137.51.14.130: seq no 1 time=0 ms > > > > 64 bytes from 137.51.14.130: seq no 2 time=0 ms > > > > 64 bytes from 137.51.14.130: seq no 3 time=0 ms > > > > 64 bytes from 137.51.14.130: seq no 4 time=0 ms > > > > 64 bytes from 137.51.14.130: seq no 5 time=0 ms > > > > 64 bytes from 137.51.14.130: seq no 6 time=0 ms > > > > 64 bytes from 137.51.14.130: seq no 7 time=0 ms > > > > 64 bytes from 137.51.14.130: seq no 8 time=0 ms > > > > 64 bytes from 137.51.14.130: seq no 9 time=0 ms > > > > 64 bytes from 137.51.14.130: seq no 10 time=0 ms > > > > 64 bytes from 137.51.14.130: seq no 11 time=0 ms > > > > 64 bytes from 137.51.14.130: seq no 12 time=0 ms > > > > 64 bytes from 137.51.14.130: seq no 13 time=0 ms > > > > 64 bytes from 137.51.14.130: seq no 14 time=0 ms > > > > 64 bytes from 137.51.14.130: seq no 15 time=0 ms > > > > 64 bytes from 137.51.14.130: seq no 16 time=0 ms > > > > 64 bytes from 137.51.14.130: seq no 17 time=0 ms > > > > 64 bytes from 137.51.14.130: seq no 18 time=0 ms > > > > 64 bytes from 137.51.14.130: seq no 19 time=0 ms > > > > 64 bytes from 137.51.14.130: seq no 20 time=0 ms > > > > 64 bytes from 137.51.14.130: seq no 21 time=0 ms > > > > 64 bytes from 137.51.14.130: seq no 22 time=0 ms > > > > 64 bytes from 137.51.14.130: seq no 23 time=0 ms > > > > 64 bytes from 137.51.14.130: seq no 24 time=0 ms > > > > 64 bytes from 137.51.14.130: seq no 25 time=0 ms > > > > 64 bytes from 137.51.14.130: seq no 26 time=0 ms > > > > 64 bytes from 137.51.14.130: seq no 27 time=0 ms > > > > 64 bytes from 137.51.14.130: seq no 28 time=0 ms > > > > 64 bytes from 137.51.14.130: seq no 29 time=0 ms > > > > 64 bytes from 137.51.14.130: seq no 30 time=0 ms > > > > 64 bytes from 137.51.14.130: seq no 31 time=0 ms > > > > 32 packets transmitted, 32 packets received, 0% packet loss round-trip min/avg/max = 0/0.0/0 ms > > > > > > > > C:\Bin> > > > > > > > > Having trouble getting Java to run on the Linux box, so I could > > > > not complete the echo test from the Linux host to the WinXP > > > > client. > > > > > > > > -----Original Message----- > > > > From: Harold L Hunt II [mailto:huntharo@msu.edu] > > > > Sent: Monday, November 17, 2003 4:41 PM > > > > To: cygwin-xfree@cygwin.com > > > > Subject: Re: XWin works on Win2K but not on some WinXP clients [FIXED] > > > > > > > > > > > > Kirk, > > > > > > > > Well then, I suppose the next step would be to do a "telinit 3" > > > > (to stop gdm), then edit xinetd conf file to run "echo" on UDP > > > > port 177, restart xinetd, then use that udp echo client that we > > > > found to test if echo works from the Windows XP machine plugged > > > > into its normal jack to gaia plugged into its normal jack. We > > > > know that echo worked on UDP port 7, but proving that it does or > > > > does not work on UDP port 177 would tell us if they know what they > > > > are talking about :) > > > > > > > > Harold > > > > > > > > Woellert, Kirk D. wrote: > > > > > > > > > > > >>I aksed corporate IS if they were doing an port blocking/filtering > > > >>within our LAN. They replied: > > > >> > > > >>"There should be no port blocking within the corp. LAN. - only in/out > > > >>to the Internet and in/out of DMZs." > > > >> > > > >> > > > >>-----Original Message----- > > > >>From: Harold L Hunt II [mailto:huntharo@msu.edu] > > > >>Sent: Monday, November 17, 2003 10:45 AM > > > >>To: cygwin-xfree@cygwin.com > > > >>Subject: Re: XWin works on Win2K but not on some WinXP clients [FIXED] > > > >> > > > >> > > > >>Kirk Woellert's problem with XP clients has been fixed, sort of. > > > >> > > > >>I talked to him on the phone for a few hours on Friday and walked him > > > >>through some debugging. > > > >> > > > >> > > > >>Here is what we found out: > > > >> > > > >>1) We could ssh from XP to Linux (TCP protocol). > > > >> > > > >>2) We could tunnel X apps over ssh from the Linux box to display > > > >>on the XP box (TCP protocol). > > > >> > > > >>3) We could natively display X apps by exporting DISPLAY on Linux box, > > > >>pointed to XP box (TCP protocol). > > > >> > > > >>4) We could not (nor could X-Win32) get an XDMCP login on the XP > > > >>box for the Linux box (UDP protocol). > > > >> > > > >>5) We could run the echo service on the Linux box on port 7 and use a > > > >>Java echo client for UDP to verify that UDP to Linux box worked (UDP > > > >>protocol). > > > >> > > > >>6) It was revealed that there are really two parts of the network > > > >>here. > > > >> Not much is known about whether port blocking is in effect between > > > >>the two parts. > > > >> > > > >>7) Removing the troubled hosts from the network and hooking them to a > > > >>stand-alone hub with assigned IP addresses allowed XDMCP to work. > > > >> > > > >>8) We thus confirmed in #5 that UDP was not blocked in general, > > > >>but #7 indicates that UDP port 177 is blocked between the > > > >>segments. It turns out that all of the Windows 2000 machines were > > > >>on one "segment", while the Windows XP machines were on another > > > >>"segment". The problem was not the OS, it was that one segment > > > >>has UDP port 177 blocked. > > > >> > > > >> > > > >>Thus, we determined that the problem is in the network that the > > > >>machines are attached to; this may or may not be by design. In > > > >>any case, it isn't a problem with Cygwin/X. :) > > > >> > > > >>Harold -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_ pechtcha@cs.nyu.edu ZZZzz /,`.-'`' -. ;-;;,_ igor@watson.ibm.com |,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 From pechtcha@cs.nyu.edu Fri Nov 21 17:47:00 2003 From: pechtcha@cs.nyu.edu (Igor Pechtchanski) Date: Fri, 21 Nov 2003 17:47:00 -0000 Subject: xwinclip & startxdmcp.bat questions/problems In-Reply-To: <3FBE2E1D.4060404@gmx.de> References: <3FBBA9EE.4040705@JaySmith.com> <3FBE2E1D.4060404@gmx.de> Message-ID: On Fri, 21 Nov 2003, Holger Krull wrote: > Jay Smith schrieb: > > > b) I am additionally now left with *another* DOS window for xwinclip. > > When I try to close it, it says that the program will terminate. It is > > As to my knowledge you have to live with that window, i know no way to > get it in the background. That would be a bad idea anyway because Try "/usr/X11R6/bin/run.exe /usr/X11R6/bin/xwinclip ...". HTH, Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_ pechtcha@cs.nyu.edu ZZZzz /,`.-'`' -. ;-;;,_ igor@watson.ibm.com |,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 From kirk.woellert@ngc.com Fri Nov 21 18:41:00 2003 From: kirk.woellert@ngc.com (Woellert, Kirk D.) Date: Fri, 21 Nov 2003 18:41:00 -0000 Subject: XWin works on Win2K but not on some WinXP clients [FIXED] Message-ID: **SSH into gaia from PuTTY a few minutes after you posted. PID 1037/1088 indicate GDM is running-right?** login as: kdw Sent username "kdw" kdw@137.51.14.130's password: [kdw@gaia ~]$ ps -ef grep gdm [kdw@gaia ~]$ ps -ef | grep gdm root 1037 1 0 Nov20 ? 00:00:00 /usr/bin/gdm-binary -nodaemon root 1088 1037 0 Nov20 ? 00:00:00 /usr/bin/gdm-binary -nodaemon root 1089 1088 0 Nov20 ? 00:05:44 /usr/X11R6/bin/X :0 -auth /var/gdm/:0.Xauth vt7 gdm 1098 1088 0 Nov20 ? 00:00:37 /usr/bin/gdmgreeter kdw 3761 3735 0 12:46 pts/0 00:00:00 grep gdm [kdw@gaia ~]$ **/var/log/messages excerpt for only Nov 21st.** Nov 21 04:04:45 gaia su(pam_unix)[2891]: session opened for user news by (uid=0) Nov 21 04:04:45 gaia su(pam_unix)[2891]: session closed for user news Nov 21 07:59:10 gaia sshd(pam_unix)[3253]: authentication failure; logname= uid=0 euid=0 tty=NODEVssh ruser= rhost=ngc-d4o1xu3vg29.ad.tasc.com user=kdw Nov 21 07:59:24 gaia sshd(pam_unix)[3255]: session opened for user kdw by (uid=505) Nov 21 07:59:52 gaia su(pam_unix)[3280]: session opened for user root by kdw(uid=505) Nov 21 08:56:10 gaia net-snmp[744]: Connection from 140.188.192.253 Nov 21 08:56:24 gaia last message repeated 7 times Nov 21 09:04:56 gaia sshd(pam_unix)[3255]: session closed for user kdw Nov 21 09:04:56 gaia su(pam_unix)[3280]: session closed for user root Nov 21 12:46:11 gaia sshd(pam_unix)[3732]: authentication failure; logname= uid=0 euid=0 tty=NODEVssh ruser= rhost=ngc-d4o1xu3vg29.ad.tasc.com user=kdw Nov 21 12:46:16 gaia sshd(pam_unix)[3734]: session opened for user kdw by (uid=505) Nov 21 13:11:26 gaia su(pam_unix)[3839]: session opened for user root by kdw(uid=505) [kdw@gaia log]# **ipconfig /all listing from the WinXP client in question** Windows IP Configuration Ethernet adapter Local Area Connection: Connection-specific DNS Suffix . : ad.tasc.com IP Address. . . . . . . . . . . . : 137.51.14.54 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 137.51.14.254 C:\WINDOWS\system32>ipconfig /all Windows IP Configuration Host Name . . . . . . . . . . . . : ngc-d4o1xu3vg29 Primary Dns Suffix . . . . . . . : Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No Ethernet adapter Local Area Connection: Connection-specific DNS Suffix . : ad.tasc.com Description . . . . . . . . . . . : Intel(R) PRO/100 Network Connection Physical Address. . . . . . . . . : 00-07-E9-78-16-9C Dhcp Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes IP Address. . . . . . . . . . . . : 137.51.14.54 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 137.51.14.254 DHCP Server . . . . . . . . . . . : 137.51.14.15 DNS Servers . . . . . . . . . . . : 137.51.60.36 137.51.218.24 Primary WINS Server . . . . . . . : 140.188.192.238 Secondary WINS Server . . . . . . : 137.51.60.36 Lease Obtained. . . . . . . . . . : Friday, November 21, 2003 11:07:30 AM Lease Expires . . . . . . . . . . : Friday, December 05, 2003 11:07:30 AM -----Original Message----- From: Igor Pechtchanski [mailto:pechtcha@cs.nyu.edu] Sent: Friday, November 21, 2003 12:35 PM To: Woellert, Kirk D. Cc: cygwin-xfree@cygwin.com Subject: RE: XWin works on Win2K but not on some WinXP clients [FIXED] Kirk, There is no need to Cc: either me or Harold - we both read the cygwin-xfree list, AFAIK. As for your problem, this doesn't look right -- you used to get gdm messages, and now you don't. A silly question: did you restart gdm after your Java echo test before attempting to connect? Igor On Fri, 21 Nov 2003, Woellert, Kirk D. wrote: > Well it picked up my Putty SSH session but it did not pick up my XDM > attempt. I tried sever times. > > Nov 20 23:55:52 gaia last message repeated 7 times > Nov 20 23:56:06 gaia last message repeated 7 times > Nov 21 04:04:45 gaia su(pam_unix)[2891]: session opened for user news by > (uid=0) > Nov 21 04:04:45 gaia su(pam_unix)[2891]: session closed for user news > Nov 21 07:59:10 gaia sshd(pam_unix)[3253]: authentication failure; logname= > uid=0 euid=0 tty=NODEVssh ruser= rhost=ngc-d4o1xu3vg29.ad.tasc.com user=kdw > Nov 21 07:59:24 gaia sshd(pam_unix)[3255]: session opened for user kdw by > (uid=505) > Nov 21 07:59:52 gaia su(pam_unix)[3280]: session opened for user root by > kdw(uid=505) > [kdw@gaia log]# > > -----Original Message----- > From: Igor Pechtchanski [mailto:pechtcha@cs.nyu.edu] > Sent: Wednesday, November 19, 2003 4:40 PM > To: Woellert, Kirk D. > Cc: cygwin-xfree@cygwin.com > Subject: Re: XWin works on Win2K but not on some WinXP clients [FIXED] > > > Kirk, > > Try to open an XDMCP session from your PC and see what that adds to > /var/log/messages (don't scan the whole thing, the relevant messages will > be appended). See if it shows something like > > Nov 17 17:03:10 gaia gdm[XXXX]: gdm_auth_secure_display: Error getting hentry for XPmachine > Nov 17 17:03:10 gaia gdm[XXXX]: gdm_xdmcp_display_alloc: Error setting up cookies for XPmachine:0 > > In any case, there should be some indication that gdm received a > connection request from your machine, even if it was refused. > Igor > > On Tue, 18 Nov 2003, Igor Pechtchanski wrote: > > > Kirk, > > > > Check /var/log/messages and see if there are any from gdm. This may be a > > DNS lookup issue (i.e., your XP machine is not registered in DNS, or > > registered, but not with the correct name). Confirm by "nslookup YOUR_IP" > > from the Linux machine. If it is a DNS issue, try adding your XP machine > > to /etc/hosts and restarting gdm ("kill -USR1 `cat /var/run/gdm.pid`"). > > Igor > > > > On Tue, 18 Nov 2003, Harold L Hunt II wrote: > > > > > So echo on UDP port 177 works fine. This is not good. There must be > > > something else in the gdm conf on the linux box that explicitly denies > > > gdm connections from the Windows XP machine's IP addresses, since it > > > worked fine when using 10.0.0.x addresses. Anyway you can change the IP > > > of the XP machine to one not previously used as a test? > > > > > > Harold > > > > > > Woellert, Kirk D. wrote: > > > > > > > 1. Edited the echo-upd file in the xinetd.d folder. Changed the > > > > default port from "7" to "177"... > > > > > > > > [root@gaia xinetd.d]# cat echo-udp > > > > # default: off > > > > # description: An xinetd internal service which echo's characters back to clients. \ > > > > # This is the udp version. > > > > service echo > > > > { > > > > disable = no > > > > type = INTERNAL UNLISTED > > > > id = echo-dgram > > > > socket_type = dgram > > > > protocol = udp > > > > user = root > > > > wait = yes > > > > port = 177 > > > > } > > > > [root@gaia xinetd.d]# > > > > > > > > 2. Did a grep just to ensure gdm was not gonna respond to my upd > > > > packets... > > > > > > > > [root@gaia xinetd.d]# ps -ef |grep xdm > > > > root 2328 1912 0 18:12 pts/0 00:00:00 grep xdm > > > > [root@gaia xinetd.d]# > > > > > > > > 3. Ran a upd echo test from the WinXP client to the Linux box > > > > using a Java echo client.... > > > > > > > > C:\Bin>java -jar UDPEchoClient.jar 137.51.14.130:177 > > > > 64 bytes from 137.51.14.130: seq no 0 time=0 ms > > > > 64 bytes from 137.51.14.130: seq no 1 time=0 ms > > > > 64 bytes from 137.51.14.130: seq no 2 time=0 ms > > > > 64 bytes from 137.51.14.130: seq no 3 time=0 ms > > > > 64 bytes from 137.51.14.130: seq no 4 time=0 ms > > > > 64 bytes from 137.51.14.130: seq no 5 time=0 ms > > > > 64 bytes from 137.51.14.130: seq no 6 time=0 ms > > > > 64 bytes from 137.51.14.130: seq no 7 time=0 ms > > > > 64 bytes from 137.51.14.130: seq no 8 time=0 ms > > > > 64 bytes from 137.51.14.130: seq no 9 time=0 ms > > > > 64 bytes from 137.51.14.130: seq no 10 time=0 ms > > > > 64 bytes from 137.51.14.130: seq no 11 time=0 ms > > > > 64 bytes from 137.51.14.130: seq no 12 time=0 ms > > > > 64 bytes from 137.51.14.130: seq no 13 time=0 ms > > > > 64 bytes from 137.51.14.130: seq no 14 time=0 ms > > > > 64 bytes from 137.51.14.130: seq no 15 time=0 ms > > > > 64 bytes from 137.51.14.130: seq no 16 time=0 ms > > > > 64 bytes from 137.51.14.130: seq no 17 time=0 ms > > > > 64 bytes from 137.51.14.130: seq no 18 time=0 ms > > > > 64 bytes from 137.51.14.130: seq no 19 time=0 ms > > > > 64 bytes from 137.51.14.130: seq no 20 time=0 ms > > > > 64 bytes from 137.51.14.130: seq no 21 time=0 ms > > > > 64 bytes from 137.51.14.130: seq no 22 time=0 ms > > > > 64 bytes from 137.51.14.130: seq no 23 time=0 ms > > > > 64 bytes from 137.51.14.130: seq no 24 time=0 ms > > > > 64 bytes from 137.51.14.130: seq no 25 time=0 ms > > > > 64 bytes from 137.51.14.130: seq no 26 time=0 ms > > > > 64 bytes from 137.51.14.130: seq no 27 time=0 ms > > > > 64 bytes from 137.51.14.130: seq no 28 time=0 ms > > > > 64 bytes from 137.51.14.130: seq no 29 time=0 ms > > > > 64 bytes from 137.51.14.130: seq no 30 time=0 ms > > > > 64 bytes from 137.51.14.130: seq no 31 time=0 ms > > > > 32 packets transmitted, 32 packets received, 0% packet loss round-trip min/avg/max = 0/0.0/0 ms > > > > > > > > C:\Bin> > > > > > > > > Having trouble getting Java to run on the Linux box, so I could > > > > not complete the echo test from the Linux host to the WinXP > > > > client. > > > > > > > > -----Original Message----- > > > > From: Harold L Hunt II [mailto:huntharo@msu.edu] > > > > Sent: Monday, November 17, 2003 4:41 PM > > > > To: cygwin-xfree@cygwin.com > > > > Subject: Re: XWin works on Win2K but not on some WinXP clients [FIXED] > > > > > > > > > > > > Kirk, > > > > > > > > Well then, I suppose the next step would be to do a "telinit 3" > > > > (to stop gdm), then edit xinetd conf file to run "echo" on UDP > > > > port 177, restart xinetd, then use that udp echo client that we > > > > found to test if echo works from the Windows XP machine plugged > > > > into its normal jack to gaia plugged into its normal jack. We > > > > know that echo worked on UDP port 7, but proving that it does or > > > > does not work on UDP port 177 would tell us if they know what they > > > > are talking about :) > > > > > > > > Harold > > > > > > > > Woellert, Kirk D. wrote: > > > > > > > > > > > >>I aksed corporate IS if they were doing an port blocking/filtering > > > >>within our LAN. They replied: > > > >> > > > >>"There should be no port blocking within the corp. LAN. - only in/out > > > >>to the Internet and in/out of DMZs." > > > >> > > > >> > > > >>-----Original Message----- > > > >>From: Harold L Hunt II [mailto:huntharo@msu.edu] > > > >>Sent: Monday, November 17, 2003 10:45 AM > > > >>To: cygwin-xfree@cygwin.com > > > >>Subject: Re: XWin works on Win2K but not on some WinXP clients [FIXED] > > > >> > > > >> > > > >>Kirk Woellert's problem with XP clients has been fixed, sort of. > > > >> > > > >>I talked to him on the phone for a few hours on Friday and walked him > > > >>through some debugging. > > > >> > > > >> > > > >>Here is what we found out: > > > >> > > > >>1) We could ssh from XP to Linux (TCP protocol). > > > >> > > > >>2) We could tunnel X apps over ssh from the Linux box to display > > > >>on the XP box (TCP protocol). > > > >> > > > >>3) We could natively display X apps by exporting DISPLAY on Linux box, > > > >>pointed to XP box (TCP protocol). > > > >> > > > >>4) We could not (nor could X-Win32) get an XDMCP login on the XP > > > >>box for the Linux box (UDP protocol). > > > >> > > > >>5) We could run the echo service on the Linux box on port 7 and use a > > > >>Java echo client for UDP to verify that UDP to Linux box worked (UDP > > > >>protocol). > > > >> > > > >>6) It was revealed that there are really two parts of the network > > > >>here. > > > >> Not much is known about whether port blocking is in effect between > > > >>the two parts. > > > >> > > > >>7) Removing the troubled hosts from the network and hooking them to a > > > >>stand-alone hub with assigned IP addresses allowed XDMCP to work. > > > >> > > > >>8) We thus confirmed in #5 that UDP was not blocked in general, > > > >>but #7 indicates that UDP port 177 is blocked between the > > > >>segments. It turns out that all of the Windows 2000 machines were > > > >>on one "segment", while the Windows XP machines were on another > > > >>"segment". The problem was not the OS, it was that one segment > > > >>has UDP port 177 blocked. > > > >> > > > >> > > > >>Thus, we determined that the problem is in the network that the > > > >>machines are attached to; this may or may not be by design. In > > > >>any case, it isn't a problem with Cygwin/X. :) > > > >> > > > >>Harold -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_ pechtcha@cs.nyu.edu ZZZzz /,`.-'`' -. ;-;;,_ igor@watson.ibm.com |,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 From johncsl82@yahoo.com Fri Nov 21 19:20:00 2003 From: johncsl82@yahoo.com (Chan Seng Loong) Date: Fri, 21 Nov 2003 19:20:00 -0000 Subject: Cygwin XFree86 startx Problem Message-ID: <20031121192050.14367.qmail@web60304.mail.yahoo.com> hi again... Thanks to Mr. Igor Pechtchanski, the "[: Seng: unknown operand" problem is eleminated with the power of "" qutoes :-D Chan Seng Loong@amd1500mhz ~ $ 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 From pechtcha@cs.nyu.edu Fri Nov 21 19:52:00 2003 From: pechtcha@cs.nyu.edu (Igor Pechtchanski) Date: Fri, 21 Nov 2003 19:52:00 -0000 Subject: Cygwin XFree86 startx Problem In-Reply-To: <20031121192050.14367.qmail@web60304.mail.yahoo.com> References: <20031121192050.14367.qmail@web60304.mail.yahoo.com> Message-ID: 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/ |\ _,,,---,,_ pechtcha@cs.nyu.edu ZZZzz /,`.-'`' -. ;-;;,_ igor@watson.ibm.com |,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 From huntharo@msu.edu Fri Nov 21 20:04:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Fri, 21 Nov 2003 20:04:00 -0000 Subject: Cygwin XFree86 startx Problem In-Reply-To: References: <20031121192050.14367.qmail@web60304.mail.yahoo.com> Message-ID: <3FBE6FCF.6090002@msu.edu> 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 From Cary.Jamison@powerquest.com Fri Nov 21 21:13:00 2003 From: Cary.Jamison@powerquest.com (Cary Jamison) Date: Fri, 21 Nov 2003 21:13:00 -0000 Subject: FW: I've given up on XF86, can' t make my AltGr keys work Message-ID: "Alexander Gottwald" wrote in message news:... > Henrik Schultz wrote: > > > I simply don't have the time to dig down into the intricacies of how > > keyboard maps, keysyms, etc. relate, and I seem unable to find problem > > descriptions in the FAQ or mailinglist archives that mach my problem, nor is > > there a step-by-step list to guide one through a problem solving process. > > > > I'm sure you have a fine product, but I guess I'll just have to dish out > > money on a Hummingbird license or whatever... sigh! > > I'm sorry to hear. > > If someone could donate an old sparc or HP-UX machine I'd be willing to > debug the problems with xdmcp, fonts and keyboardlayouts with those machines. > > bye > ago I wonder if this could be reproduced with Solaris-86? I believe it is still freely downloadable. Do you have an extra PC you could install it on? (Or were you just hoping someone would give you a sparc? :-) Cary From Benjamin.Riefenstahl@epost.de Fri Nov 21 22:16:00 2003 From: Benjamin.Riefenstahl@epost.de (Benjamin Riefenstahl) Date: Fri, 21 Nov 2003 22:16:00 -0000 Subject: FW: I've given up on XF86, can' t make my AltGr keys work In-Reply-To: (Alexander Gottwald's message of "Fri, 21 Nov 2003 15:42:15 +0100 (MET)") References: <81AC7B3F6CA6D4118AB00050BA8755668117EC@EXCHANGE> Message-ID: Hi Alexander, Henrik, Alexander Gottwald writes: > If someone could donate an old sparc or HP-UX machine I'd be willing > to debug the problems with xdmcp, fonts and keyboardlayouts with > those machines. Wouldn't it be enough to get a temporary SSH account on a Sparc machine to reproduce this and debug the X server side? Not that I have a machine available, but maybe Henrik could arrange something. Just a thought ... benny From kral@axiom-micro.com Sat Nov 22 00:27:00 2003 From: kral@axiom-micro.com (Alexandre Kral) Date: Sat, 22 Nov 2003 00:27:00 -0000 Subject: CYGWIN/XFREE XWIN BUG in version XFree86-xserv-4.3.0-23 Message-ID: <00a801c3b08f$5c3672f0$ed01a8c0@SanOnofre> To whom it may concern: The version XFree86-xserv-4.3.0-23 has a bug. I use it to remotely login as an X terminal into a Linux session. It used to work fine with my older version of Cygwin/XFree86 but now it crashes on a regular basis shortly after I leave that window to focus on another Windows application (within the hour, Cygwin/XFree has crashed). I copied a XWin.exe.stackdump file that i found on my desktop hoping that this would help you debug it. Thank you, Alexandre Kral XWin.exe.stackdump: -------------------------------- Exception: STATUS_ACCESS_VIOLATION at eip=00608496 eax=000000DB ebx=1252FC20 ecx=125324F4 edx=0077B198 esi=100FAA88 edi=00000010 ebp=0022F9B8 esp=0022F9A0 program=C:\cygwin\usr\X11R6\bin\XWin.exe cs=001B ds=0023 es=0023 fs=0038 gs=0000 ss=0023 Stack trace: Frame Function Args 0022F9B8 00608496 (1252FC20, 00000000, 0022FA08, 00516C56) 0022F9C8 0053D0B7 (120D2D80, 00000001, 0022F9F8, 0043940F) 0022FA08 00516C56 (126B1940, 120D07C0, 120D07C0, 00000000) 0022FA38 005151E7 (10DB73B0, 00000002, 00000000, 02400003) 0022FE68 00407DCC (00000002, 00000000, 100F1BC0, 00000001) 0022FEB0 004017E8 (00000006, 100F1BC0, 100F0330, 00000001) 0022FF40 61005018 (610CFEE0, FFFFFFFE, 000007D0, 610CFE04) 0022FF90 610052ED (00000000, 00000000, 00000000, 805B402B) 0022FFB0 00729191 (00401450, 037F0009, 0022FFF0, 77E7EB69) 0022FFC0 0040103C (00000000, 00000000, 7FFDF000, F3233CF4) 0022FFF0 77E7EB69 (00401000, 00000000, 78746341, 00000020) End of stack trace From johncsl82@yahoo.com Sat Nov 22 02:02:00 2003 From: johncsl82@yahoo.com (Chan Seng Loong) Date: Sat, 22 Nov 2003 02:02:00 -0000 Subject: Cygwin XFree86 startx Problem Message-ID: <20031122020220.19457.qmail@web60304.mail.yahoo.com> hi....again 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 Loong@amd1500mhz ~ $ 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 From dandersen@compuserve.com Sat Nov 22 03:04:00 2003 From: dandersen@compuserve.com (David Andersen) Date: Sat, 22 Nov 2003 03:04:00 -0000 Subject: Cygwin XFree86 startx Problem References: <20031122020220.19457.qmail@web60304.mail.yahoo.com> Message-ID: <004601c3b0a5$5a633790$0c9fc0d8@david5mryz7blb> 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" 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 From andrew.markebo@comhem.se Sat Nov 22 04:40:00 2003 From: andrew.markebo@comhem.se (Andrew Markebo) Date: Sat, 22 Nov 2003 04:40:00 -0000 Subject: Cygwin XFree86 startx Problem References: <20031122020220.19457.qmail@web60304.mail.yahoo.com> Message-ID: / Chan Seng Loong 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. From bmj2001@bellsouth.net Sat Nov 22 04:53:00 2003 From: bmj2001@bellsouth.net (Robert McNulty Junior) Date: Sat, 22 Nov 2003 04:53:00 -0000 Subject: Cygwin XFree86 startx Problem In-Reply-To: Message-ID: 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: cygwin-xfree-owner@cygwin.com [mailto:cygwin-xfree-owner@cygwin.com]On Behalf Of Andrew Markebo Sent: Friday, November 21, 2003 10:35 PM To: cygwin-xfree@cygwin.com Subject: Re: Cygwin XFree86 startx Problem / Chan Seng Loong 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. From bhami@pobox.com Sat Nov 22 06:42:00 2003 From: bhami@pobox.com (Bruce A. Hamilton) Date: Sat, 22 Nov 2003 06:42:00 -0000 Subject: Slow performance over VPN/cable modem Message-ID: <5.2.1.1.2.20031121222630.01ee51f8@mail.earthlink.net> XP Pro SP1, Pentium 2.66 GHz, 1 GB memory. I am running the latest cygwin including XFree86 4.3.0. Performance connecting to my workplace via VPN over cable modem is painfully slow, similar to what I used to see running X over dialup years ago. I'm running a local window manager fvwm2 then "ssh -X" to hosts at work via my local xterms. The app I'm most interested in is Veritas NetBackup 4.5 jnbSA, which is written in Java and not exactly speedy even at work, but at work we are talking a couple of seconds to refresh the screen, versus nearly a minute for the tiniest changes at home. My Internet connection in general is very fast, on the order of 2 Mb/sec, and I get excellent response over my VPN to work using vanilla text apps and MS Outlook. Thanks for any suggestions. I'm quite sure this in an X issue. Wasn't MIT supposed to be working on "low-bandwidth X" years ago? Three years ago I had the good fortune to be able to use Graphon's Go-Global to channel X over dialup and was VERY impressed. More recently I played a little bit with VNC and it seemed to have its own performance issues so I have no pursued it further at this time, but I'll consider it if you recommend it. --Bruce (Bruce Hamilton, Redondo Beach, CA) bhami@pobox.com http://bhami.com/ From davidf@sjsoft.com Sat Nov 22 07:31:00 2003 From: davidf@sjsoft.com (David Fraser) Date: Sat, 22 Nov 2003 07:31:00 -0000 Subject: Slow performance over VPN/cable modem In-Reply-To: <5.2.1.1.2.20031121222630.01ee51f8@mail.earthlink.net> References: <5.2.1.1.2.20031121222630.01ee51f8@mail.earthlink.net> Message-ID: <3FBF10DE.20709@sjsoft.com> Bruce A. Hamilton wrote: > XP Pro SP1, Pentium 2.66 GHz, 1 GB memory. > > I am running the latest cygwin including XFree86 4.3.0. > > Performance connecting to my workplace via VPN over cable modem is > painfully slow, similar to what I used to see running X over dialup > years ago. I'm running a local window manager fvwm2 then "ssh -X" to > hosts at work via my local xterms. > > The app I'm most interested in is Veritas NetBackup 4.5 jnbSA, which > is written in Java and not exactly speedy even at work, but at work we > are talking a couple of seconds to refresh the screen, versus nearly a > minute for the tiniest changes at home. > > My Internet connection in general is very fast, on the order of 2 > Mb/sec, and I get excellent response over my VPN to work using vanilla > text apps and MS Outlook. > > Thanks for any suggestions. I'm quite sure this in an X issue. Wasn't > MIT supposed to be working on "low-bandwidth X" years ago? > > Three years ago I had the good fortune to be able to use Graphon's > Go-Global to channel X over dialup and was VERY impressed. > > More recently I played a little bit with VNC and it seemed to have its > own performance issues so I have no pursued it further at this time, > but I'll consider it if you recommend it. > > --Bruce (Bruce Hamilton, Redondo Beach, CA) > bhami@pobox.com > http://bhami.com/ > > I would recommend trying the latest version of VNC (4.0b4) from realvnc.com if you are having bandwidth constraints, though there may be other suggestions about X... David From ruth.ivimey-cook@ivimey.org Sat Nov 22 11:02:00 2003 From: ruth.ivimey-cook@ivimey.org (Ruth Ivimey-Cook) Date: Sat, 22 Nov 2003 11:02:00 -0000 Subject: Slow performance over VPN/cable modem In-Reply-To: <5.2.1.1.2.20031121222630.01ee51f8@mail.earthlink.net> References: <5.2.1.1.2.20031121222630.01ee51f8@mail.earthlink.net> Message-ID: <3FBF4225.1060000@ivimey.org> Bruce A. Hamilton wrote: > XP Pro SP1, Pentium 2.66 GHz, 1 GB memory. > I am running the latest cygwin including XFree86 4.3.0. > > Thanks for any suggestions. I'm quite sure this in an X issue. Wasn't > MIT supposed to be working on "low-bandwidth X" years ago? Yes, they did and it's been available for a while now. You run the app "lbxproxy" on the local end (home) set up to connect to your work server, and then do a normal X connect to the local server connection that is presented by lbxproxy. This assumes the normal case, that the remote server includes the LBX server extension. Hope this helps. Ruth From alexander.gottwald@s1999.tu-chemnitz.de Sat Nov 22 11:29:00 2003 From: alexander.gottwald@s1999.tu-chemnitz.de (Alexander Gottwald) Date: Sat, 22 Nov 2003 11:29:00 -0000 Subject: FW: I've given up on XF86, can' t make my AltGr keys work In-Reply-To: References: Message-ID: On Fri, 21 Nov 2003, Cary Jamison wrote: > I wonder if this could be reproduced with Solaris-86? I believe it is > still freely downloadable. Do you have an extra PC you could install it > on? No. The Pentium 90 I recently bought (5 EUR *g*) was not sufficient for Solaris-x86. And working with Solaris-x86 in VmWare is a pain. bye ago -- Alexander.Gottwald@s1999.tu-chemnitz.de http://www.gotti.org ICQ: 126018723 From alexander.gottwald@s1999.tu-chemnitz.de Sat Nov 22 11:38:00 2003 From: alexander.gottwald@s1999.tu-chemnitz.de (Alexander Gottwald) Date: Sat, 22 Nov 2003 11:38:00 -0000 Subject: Slow performance over VPN/cable modem In-Reply-To: <5.2.1.1.2.20031121222630.01ee51f8@mail.earthlink.net> References: <5.2.1.1.2.20031121222630.01ee51f8@mail.earthlink.net> Message-ID: On Fri, 21 Nov 2003, Bruce A. Hamilton wrote: > XP Pro SP1, Pentium 2.66 GHz, 1 GB memory. > > I am running the latest cygwin including XFree86 4.3.0. > > Performance connecting to my workplace via VPN over cable modem is > painfully slow, similar to what I used to see running X over dialup years > ago. I'm running a local window manager fvwm2 then "ssh -X" to hosts at > work via my local xterms. Afair cable modems have a high latency. > The app I'm most interested in is Veritas NetBackup 4.5 jnbSA, which is > written in Java and not exactly speedy even at work, but at work we are > talking a couple of seconds to refresh the screen, versus nearly a minute > for the tiniest changes at home. Does this application use Swing? If so then the slow performance is not a problem of X11 but a design error of Java/Swing. All graphicsoperations in Swing are localy drawn into a bitmap and the bitmap is then transferred to the xserver. This is much more expensive than letting the xserver perform the drawing operations. > Thanks for any suggestions. I'm quite sure this in an X issue. Wasn't MIT > supposed to be working on "low-bandwidth X" years ago? They never thought of Java. bye ago -- Alexander.Gottwald@s1999.tu-chemnitz.de http://www.gotti.org ICQ: 126018723 From pechtcha@cs.nyu.edu Sat Nov 22 14:25:00 2003 From: pechtcha@cs.nyu.edu (Igor Pechtchanski) Date: Sat, 22 Nov 2003 14:25:00 -0000 Subject: Cygwin XFree86 startx Problem In-Reply-To: <3FBE6FCF.6090002@msu.edu> References: <20031121192050.14367.qmail@web60304.mail.yahoo.com> <3FBE6FCF.6090002@msu.edu> Message-ID: 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/ |\ _,,,---,,_ pechtcha@cs.nyu.edu ZZZzz /,`.-'`' -. ;-;;,_ igor@watson.ibm.com |,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 From bhami@pobox.com Sat Nov 22 17:00:00 2003 From: bhami@pobox.com (Bruce A. Hamilton) Date: Sat, 22 Nov 2003 17:00:00 -0000 Subject: Slow performance over VPN/cable modem In-Reply-To: <1069511139.32742.ezmlm@cygwin.com> Message-ID: <5.2.1.1.2.20031122085225.01ea6110@mail.earthlink.net> At 06:25 AM 11/22/2003, you wrote: >Bruce A. Hamilton wrote: > >>XP Pro SP1, Pentium 2.66 GHz, 1 GB memory. >>I am running the latest cygwin including XFree86 4.3.0. >> >>Thanks for any suggestions. I'm quite sure this in an X issue. Wasn't MIT >>supposed to be working on "low-bandwidth X" years ago? > >Yes, they did and it's been available for a while now. You run the app >"lbxproxy" on the local end (home) set up to connect to your work server, >and then do a normal X connect to the local server connection that is >presented by lbxproxy. > >This assumes the normal case, that the remote server includes the LBX >server extension. Thanks, but I get the following error % lbxproxy _LBXPROXYTransmkdir: Owner of /tmp/.X11-unix should be set to root If I try to hack up a bogus root user by adding it to the cygwin /etc/passwd, then chown says % chown root .X11-unix chown: changing ownership of `.X11-unix': Invalid argument which is different than if I try to chown it to some non-existent user: % chown foo .X11-unix chown: `foo': invalid user ??? --Bruce (Bruce Hamilton, Redondo Beach, CA) bhami@pobox.com http://bhami.com/ From huntharo@msu.edu Sat Nov 22 18:36:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Sat, 22 Nov 2003 18:36:00 -0000 Subject: Cygwin XFree86 startx Problem In-Reply-To: References: <20031121192050.14367.qmail@web60304.mail.yahoo.com> <3FBE6FCF.6090002@msu.edu> Message-ID: <3FBFACC6.80305@msu.edu> 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 From pechtcha@cs.nyu.edu Sat Nov 22 23:25:00 2003 From: pechtcha@cs.nyu.edu (Igor Pechtchanski) Date: Sat, 22 Nov 2003 23:25:00 -0000 Subject: Cygwin XFree86 startx Problem In-Reply-To: References: Message-ID: 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: cygwin-xfree-owner@cygwin.com > [mailto:cygwin-xfree-owner@cygwin.com]On Behalf Of Andrew Markebo > Sent: Friday, November 21, 2003 10:35 PM > To: cygwin-xfree@cygwin.com > Subject: Re: Cygwin XFree86 startx Problem > > > / Chan Seng Loong 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/ |\ _,,,---,,_ pechtcha@cs.nyu.edu ZZZzz /,`.-'`' -. ;-;;,_ igor@watson.ibm.com |,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 From pechtcha@cs.nyu.edu Sat Nov 22 23:30:00 2003 From: pechtcha@cs.nyu.edu (Igor Pechtchanski) Date: Sat, 22 Nov 2003 23:30:00 -0000 Subject: Slow performance over VPN/cable modem In-Reply-To: <5.2.1.1.2.20031122085225.01ea6110@mail.earthlink.net> References: <5.2.1.1.2.20031122085225.01ea6110@mail.earthlink.net> Message-ID: On Sat, 22 Nov 2003, Bruce A. Hamilton wrote: > At 06:25 AM 11/22/2003, you wrote: > >Bruce A. Hamilton wrote: > > > >>XP Pro SP1, Pentium 2.66 GHz, 1 GB memory. > >>I am running the latest cygwin including XFree86 4.3.0. > >> > >>Thanks for any suggestions. I'm quite sure this in an X issue. Wasn't MIT > >>supposed to be working on "low-bandwidth X" years ago? > > > >Yes, they did and it's been available for a while now. You run the app > >"lbxproxy" on the local end (home) set up to connect to your work server, > >and then do a normal X connect to the local server connection that is > >presented by lbxproxy. > > > >This assumes the normal case, that the remote server includes the LBX > >server extension. > > Thanks, but I get the following error > > % lbxproxy > _LBXPROXYTransmkdir: Owner of /tmp/.X11-unix should be set to root > > If I try to hack up a bogus root user by adding it to the cygwin > /etc/passwd, then chown says > > % chown root .X11-unix > chown: changing ownership of `.X11-unix': Invalid argument > > which is different than if I try to chown it to some non-existent user: > > % chown foo .X11-unix > chown: `foo': invalid user > > ??? The bogus root user should nevertheless have a real SID (and a UID of 0). I suggest copying the SYSTEM entry and changing the username to root and UID to 0 and making sure it appears before the real SYSTEM entry in /etc/passwd (note that this may present problems with some apps, notably apache, that hardcode the SYSTEM UID as 18 on Cygwin). Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_ pechtcha@cs.nyu.edu ZZZzz /,`.-'`' -. ;-;;,_ igor@watson.ibm.com |,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 From jch@honig.net Sun Nov 23 05:30:00 2003 From: jch@honig.net (Jeffrey C Honig) Date: Sun, 23 Nov 2003 05:30:00 -0000 Subject: How to get my auto repeat back? Message-ID: <200311230530.hAN5UQD26439@escapade.honig.net> As happened to many people, the recent changes to the server disabled the windows autorepeat and left it up to X. I'm using ``fullscreen'' mode with ``-engine 1'', no XF86Config-4 file and am unable to get autorepeat to work. I tried the ``+kb'' argument to Xwin, with and w/o that ``xset r rate 200 40'' says that there is not an extension present for handling rate. I really miss auto-repeat. How can I find it again? Thanks. Jeff -- Jeffrey C. Honig http://www.honig.net/jch GnuPG ID:14E29E13 From murakami@ipl.t.u-tokyo.ac.jp Sun Nov 23 05:43:00 2003 From: murakami@ipl.t.u-tokyo.ac.jp (Takuma Murakami) Date: Sun, 23 Nov 2003 05:43:00 -0000 Subject: Slow performance over VPN/cable modem In-Reply-To: <5.2.1.1.2.20031121222630.01ee51f8@mail.earthlink.net> References: <5.2.1.1.2.20031121222630.01ee51f8@mail.earthlink.net> Message-ID: <20031123144043.AD58.MURAKAMI@ipl.t.u-tokyo.ac.jp> Have you tried "ssh -C -X" ? Takuma Murakami (murakami@ipl.t.u-tokyo.ac.jp) From huntharo@msu.edu Sun Nov 23 16:53:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Sun, 23 Nov 2003 16:53:00 -0000 Subject: How to get my auto repeat back? In-Reply-To: <200311230530.hAN5UQD26439@escapade.honig.net> References: <200311230530.hAN5UQD26439@escapade.honig.net> Message-ID: <3FC0E5F9.90303@msu.edu> Jeff, You got this version: http://cygwin.com/ml/cygwin-xfree-announce/2003-11/msg00006.html If so, remove all flags that you have added (e.g. "-kb", "+kb", etc.) and stop using your config file if you were not using it before. I think you should be back to normal. Harold Jeffrey C Honig wrote: > As happened to many people, the recent changes to the server disabled > the windows autorepeat and left it up to X. > > I'm using ``fullscreen'' mode with ``-engine 1'', no XF86Config-4 file > and am unable to get autorepeat to work. > > I tried the ``+kb'' argument to Xwin, with and w/o that ``xset r rate > 200 40'' says that there is not an extension present for handling rate. > > I really miss auto-repeat. How can I find it again? > > Thanks. > > Jeff > From jch@honig.net Sun Nov 23 17:57:00 2003 From: jch@honig.net (Jeffrey C Honig) Date: Sun, 23 Nov 2003 17:57:00 -0000 Subject: How to get my auto repeat back? In-Reply-To: Message from Jeffrey C Honig on Sun, 23 Nov 2003 00:30:26 -0500. Message-ID: <200311231757.hANHvoD16813@escapade.honig.net> > You got this version: > http://cygwin.com/ml/cygwin-xfree-announce/2003-11/msg00006.html > If so, remove all flags that you have added (e.g. "-kb", "+kb", etc.) > and stop using your config file if you were not using it before. I > think you should be back to normal. Already have it. I've removed all keyboard related options. And I have never installed a config file. Still no auto-repeat. :-( My arguments to Xwin are: -clipboard -fullscreen -emulate3buttons -nowinkill -unixkill -engine 1 Thanks. Jeff -- Jeffrey C. Honig http://www.honig.net/jch GnuPG ID:14E29E13 From huntharo@msu.edu Sun Nov 23 18:14:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Sun, 23 Nov 2003 18:14:00 -0000 Subject: How to get my auto repeat back? In-Reply-To: <200311231757.hANHvoD16813@escapade.honig.net> References: <200311231757.hANHvoD16813@escapade.honig.net> Message-ID: <3FC0F91A.9010200@msu.edu> Okay, now try with -kb. Harold Jeffrey C Honig wrote: >>You got this version: > > >>http://cygwin.com/ml/cygwin-xfree-announce/2003-11/msg00006.html > > >>If so, remove all flags that you have added (e.g. "-kb", "+kb", etc.) >>and stop using your config file if you were not using it before. I >>think you should be back to normal. > > > Already have it. I've removed all keyboard related options. And I have > never installed a config file. Still no auto-repeat. :-( > > My arguments to Xwin are: > > -clipboard -fullscreen -emulate3buttons -nowinkill -unixkill -engine 1 > > > Thanks. > > Jeff > From huntharo@msu.edu Sun Nov 23 18:24:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Sun, 23 Nov 2003 18:24:00 -0000 Subject: How to get my auto repeat back? In-Reply-To: <3FC0F91A.9010200@msu.edu> References: <200311231757.hANHvoD16813@escapade.honig.net> <3FC0F91A.9010200@msu.edu> Message-ID: <3FC0FB58.1070306@msu.edu> Jeff, Also, please run the following from a Cygwin bash prompt and send in the resulting cygcheck.out fiel (it may take a minute or two to finish running): cygcheck -c > cygcheck.out 2>&1 Harold From pechtcha@cs.nyu.edu Sun Nov 23 19:23:00 2003 From: pechtcha@cs.nyu.edu (Igor Pechtchanski) Date: Sun, 23 Nov 2003 19:23:00 -0000 Subject: How to get my auto repeat back? In-Reply-To: <3FC0FB58.1070306@msu.edu> References: <200311231757.hANHvoD16813@escapade.honig.net> <3FC0F91A.9010200@msu.edu> <3FC0FB58.1070306@msu.edu> Message-ID: On Sun, 23 Nov 2003, Harold L Hunt II wrote: > Jeff, > > Also, please run the following from a Cygwin bash prompt and send in the > resulting cygcheck.out fiel (it may take a minute or two to finish running): > > cygcheck -c > cygcheck.out 2>&1 > > Harold Harold, The above is the right command if you want to make sure all the files from all the installed packages are present. If all you want are the installed package versions, you should use "cygcheck -cd" (or "cygcheck --check-setup --dump-only"). Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_ pechtcha@cs.nyu.edu ZZZzz /,`.-'`' -. ;-;;,_ igor@watson.ibm.com |,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 From huntharo@msu.edu Sun Nov 23 19:25:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Sun, 23 Nov 2003 19:25:00 -0000 Subject: How to get my auto repeat back? In-Reply-To: References: <200311231757.hANHvoD16813@escapade.honig.net> <3FC0F91A.9010200@msu.edu> <3FC0FB58.1070306@msu.edu> Message-ID: <3FC1099B.9000901@msu.edu> Igor Pechtchanski wrote: > On Sun, 23 Nov 2003, Harold L Hunt II wrote: > > >>Jeff, >> >>Also, please run the following from a Cygwin bash prompt and send in the >>resulting cygcheck.out fiel (it may take a minute or two to finish running): >> >>cygcheck -c > cygcheck.out 2>&1 >> >>Harold > > > Harold, > > The above is the right command if you want to make sure all the files from > all the installed packages are present. If all you want are the installed > package versions, you should use "cygcheck -cd" (or "cygcheck > --check-setup --dump-only"). Igor, In this case I do want to actually check if all files are present. Harold From pechtcha@cs.nyu.edu Sun Nov 23 21:24:00 2003 From: pechtcha@cs.nyu.edu (Igor Pechtchanski) Date: Sun, 23 Nov 2003 21:24:00 -0000 Subject: How to get my auto repeat back? In-Reply-To: <3FC1099B.9000901@msu.edu> References: <200311231757.hANHvoD16813@escapade.honig.net> <3FC0F91A.9010200@msu.edu> <3FC0FB58.1070306@msu.edu> <3FC1099B.9000901@msu.edu> Message-ID: On Sun, 23 Nov 2003, Harold L Hunt II wrote: > Igor Pechtchanski wrote: > > > On Sun, 23 Nov 2003, Harold L Hunt II wrote: > > > >>Jeff, > >> > >>Also, please run the following from a Cygwin bash prompt and send in the > >>resulting cygcheck.out fiel (it may take a minute or two to finish running): > >> > >>cygcheck -c > cygcheck.out 2>&1 > >> > >>Harold > > > > > > Harold, > > > > The above is the right command if you want to make sure all the files from > > all the installed packages are present. If all you want are the installed > > package versions, you should use "cygcheck -cd" (or "cygcheck > > --check-setup --dump-only"). > > Igor, > > In this case I do want to actually check if all files are present. > > Harold Sure, just thought I'd get that info into the archives. BTW, two notes about the above functionality: (a) some packages, notably apache, will show up as incomplete due to a directory rename in the postinstall script, so it's probably better to specify exactly which packages you'd like to check, and (b) cygcheck will not check whether the files are the same as in the distribution tarball, just whether they are present. Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_ pechtcha@cs.nyu.edu ZZZzz /,`.-'`' -. ;-;;,_ igor@watson.ibm.com |,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 From Alexander.Gottwald@s1999.tu-chemnitz.de Sun Nov 23 23:09:00 2003 From: Alexander.Gottwald@s1999.tu-chemnitz.de (Alexander Gottwald) Date: Sun, 23 Nov 2003 23:09:00 -0000 Subject: FW: I've given up on XF86, can' t make my AltGr keys work In-Reply-To: References: <81AC7B3F6CA6D4118AB00050BA8755668117EC@EXCHANGE> Message-ID: Benjamin Riefenstahl wrote: > > If someone could donate an old sparc or HP-UX machine I'd be willing > > to debug the problems with xdmcp, fonts and keyboardlayouts with > > those machines. > > Wouldn't it be enough to get a temporary SSH account on a Sparc > machine to reproduce this and debug the X server side? For the testing I need a machine where I have full (root) access. Maybe the yearly "our-university-sells-old-hardware-auction" has some HP-UX boxes. Anyway, such a sparc or HP-UX would be a nice donation *g* bye ago -- Alexander.Gottwald@informatik.tu-chemnitz.de http://www.gotti.org ICQ: 126018723 From fma@doe.carleton.ca Mon Nov 24 00:11:00 2003 From: fma@doe.carleton.ca (Fred Ma) Date: Mon, 24 Nov 2003 00:11:00 -0000 Subject: DDD 3.3.8 segmentation error, related to Motif? Message-ID: <3FC14C97.E9D22F22@doe.carleton.ca> On Fri, 21 Nov 2003 Brian Ford wrote: > > On Fri, 21 Nov 2003 dirk.goethals@alcatel.be wrote: > > > > bt08pm: /usr/X11R6/include/Xm/ ddd --lesstif-version 93 > > Warning: This DDD requires a Motif 2.1 library (using Motif > > -1617156.-609) > > Could you post cygcheck `type ddd`? > > > bt08pm: /usr/bin/ ddd --configuration > > GNU DDD 3.3.8 (i686-pc-cygwin) > > Copyright (C) 1995-1999 Technische Universit??t Braunschweig, Germany. > > Copyright (C) 1999-2001 Universit??t Passau, Germany. > > Copyright (C) 2001 Universit??t des Saarlandes, Germany. > > > > Compiled with GCC 3.2 20020927 (prerelease) > > Why not the current Cygwin gcc? I'm having similar problems trying to build ddd-3.3.8 immediately after update cygwin (1.5.5-1) and all components. This includes lesstif 0.93.91-4, Xfree86-lib-compat 4.3.0-2, and XFree86-prog 4.3.0-2. The last two are what comes up on a search for libXt in Cygwin's Setup Package Search. The "configure" output also claims "Motif...libraries in default path, headers in default path". The reason gcc-3.2 is used is because the most recent (I believe it's 3.3.x) causes fatal link errors during the "make" step. The suspected cause that I've read is that some cygwin components are built with gcc-3.2. The exact error happens when I run "make check": make[1]: Entering directory `/home/fmadmin/INSTROOT/ddd-3.3.8/ddd' MALLOC_CHECK_=2 \ DDD_HOME=./.. \ XUSERFILESEARCHPATH=%N XAPPLRESDIR=. \ ./ddd.exe cxxtest.exe Warning: This DDD requires a Motif 2.1 library (using Motif -6281.-729) Continue at own risk. Internal error (Segmentation fault). Oops! You have found a bug in DDD. If you can reproduce this bug, please send a bug report to , giving a subject like DDD 3.3.8 (i686-pc-cygwin) gets `Segmentation fault' signal I've attached "cycheck -cvs" output. Thanks for any suggestions of what further things to try. Fred -- Fred Ma Dept. of Electronics, Carleton University 1125 Colonel By Drive, Ottawa, Ontario Canada, K1S 5B6 -------------- next part -------------- Cygwin Package Information Last downloaded files to: C:\WINNT\Profiles\Administrator\Desktop Last downloaded files from: http://mirrors.rcn.net/pub/sourceware/cygwin Package Version Status _update-info-dir 00223-1 OK a2ps 4.13-1 OK ash 20031007-1 OK base-files 2.6-1 OK base-passwd 1.1-1 OK bash 2.05b-16 OK binutils 20030901-1 OK bzip2 1.0.2-5 OK clear 1.0-1 OK cron 3.0.1-11 OK crypt 1.1-1 OK cvs 1.11.6-3 OK cygipc 2.02-1 OK cygrunsrv 0.96-2 OK cygutils 1.2.2-1 OK cygwin 1.5.5-1 OK cygwin-doc 1.3-6 OK diffutils 2.8.4-1 OK ed 0.2-1 OK editrights 1.01-1 OK enscript 1.6.3-3 OK expat 1.95.6-2 OK fileutils 4.1-2 OK findutils 4.1.7-4 OK fontconfig 2.2.0-1 OK freetype2 2.1.5-1 OK gawk 3.1.3-4 OK gcc 3.2-3 OK gcc-g++ 3.3.1-3 OK gcc-mingw-core 20031020-1 OK gcc-mingw-g++ 20031020-1 OK gdb 20030919-1 OK gdbm 1.8.3-7 OK gettext 0.12.1-3 OK ghostscript 7.05-2 OK ghostscript-base 7.05-2 OK ghostscript-x11 7.05-2 OK gnugo 3.4-1 OK grep 2.5-1 OK groff 1.18.1-2 OK gzip 1.3.5-1 OK jpeg 6b-11 OK keychain 1.9-1 OK less 381-1 OK lesstif 0.93.91-4 OK libbz2_1 1.0.2-5 OK libcharset1 1.9.1-3 OK libdb3.1 3.1.17-2 OK libdb4.1 4.1.25-1 OK libfontconfig-devel 2.2.0-1 OK libfontconfig1 2.2.0-1 OK libfreetype2-devel 2.1.5-1 OK libfreetype26 2.1.5-1 OK libgdbm 1.8.0-5 OK libgdbm-devel 1.8.3-7 OK libgdbm3 1.8.3-3 OK libgdbm4 1.8.3-7 OK libgettextpo0 0.12.1-3 OK libiconv2 1.9.1-3 OK libintl 0.10.38-3 OK libintl1 0.10.40-1 OK libintl2 0.12.1-3 OK libjpeg62 6b-11 OK libjpeg6b 6b-8 OK libncurses5 5.2-1 OK libncurses6 5.2-8 OK libncurses7 5.3-4 OK libpcre 4.1-1 OK libpcre0 4.4-2 OK libpng 1.2.5-4 OK libpng10 1.0.15-4 OK libpng12 1.2.5-4 OK libpopt0 1.6.4-4 OK libreadline4 4.1-2 OK libreadline5 4.3-5 OK libtiff-devel 3.6.0-5 OK libtiff3 3.6.0-2 OK libtiff4 3.6.0-5 OK libungif 4.1.0-2 OK login 1.9-7 OK lynx 2.8.4-7 OK make 3.80-1 OK man 1.5j-2 OK mingw-runtime 3.2-1 OK mktemp 1.5-3 OK more 2.11o-1 OK mutt 1.4.1-1 OK ncurses 5.3-4 OK openssh 3.7.1p2-2 OK openssl 0.9.7c-1 OK openssl096 0.9.6j-1 OK patch 2.5.8-8 OK pcre 4.4-2 OK pcre-doc 4.4-2 OK perl 5.8.2-1 OK perl_manpages 5.8.2-1 OK procps 010801-2 OK psutils 1.17-1 OK readline 4.3-5 OK sed 4.0.7-3 OK sh-utils 2.0.15-4 OK sharutils 4.2.1-3 OK shutdown 1.4-1 OK ssmtp 2.38.7-4 OK tar 1.13.25-5 OK tcltk 20030901-1 OK tcsh 6.12.00-7 OK termcap 20021106-2 OK terminfo 5.3_20030726-1 OK texinfo 4.2-4 OK textutils 2.0.21-1 OK tiff 3.6.0-5 OK time 1.7-1 OK unzip 5.50-5 OK vim 6.2.098-1 OK w32api 2.4-1 OK which 1.5-2 OK whois 4.6.7-1 OK Xaw3d 1.5D-4 OK Empty package XFree86-base XFree86-base 4.3.0-1 OK XFree86-bin 4.3.0-8 OK XFree86-etc 4.3.0-6 OK XFree86-fenc 4.2.0-3 OK XFree86-fnts 4.2.0-3 OK XFree86-lib 4.3.0-1 OK XFree86-lib-compat 4.3.0-2 OK XFree86-prog 4.3.0-12 OK XFree86-startup-scripts 4.2.0-5 OK XFree86-xserv 4.3.0-23 OK xwinclip 1.2.0-1 OK zip 2.3-5 OK zlib 1.1.4-4 OK Cygwin Win95/NT Configuration Diagnostics Current System Time: Sun Nov 23 18:49:25 2003 Windows 2000 Professional Ver 5.0 Build 2195 Service Pack 4 Path: C:\cygwin\home\fmadmin\bin C:\cygwin\usr\local\bin C:\cygwin\bin C:\cygwin\bin c:\WINNT\system32 c:\WINNT c:\WINNT\system32\WBEM C:\cygwin\bin C:\cygwin\usr\X11R6\bin Output from C:\cygwin\bin\id.exe (nontsec) UID: 1008(fmadmin) GID: 513(None) 513(None) Output from C:\cygwin\bin\id.exe (ntsec) UID: 1008(fmadmin) GID: 513(None) 513(None) 544(Administrators) 547(Power Users) 545(Users) SysDir: C:\WINNT\system32 WinDir: C:\WINNT CYGWIN = `ntsec tty' HOME = `C:\cygwin\home\fmadmin' MAKE_MODE = `unix' PWD = `/home/fmadmin/Mail' USER = `fmadmin' ABEL5DB = `c:\epd\1.1\fpga\2000.2\manager\lib5\devices' ABEL5DEV = `c:\epd\1.1\fpga\2000.2\manager\lib5' ALLUSERSPROFILE = `C:\WINNT\Profiles\All Users' APPDATA = `C:\WINNT\Profiles\fmadmin\Application Data' CITEMAKERF55 = `C:\CiteMaker\Frame55' COMMONPROGRAMFILES = `C:\Program Files\Common Files' COMPUTERNAME = `DALI' COMSPEC = `C:\WINNT\system32\cmd.exe' CTCM = `C:\WINNT' CVS_RSH = `/bin/ssh' EDITOR = `vi' EPD_ARCH = `win32' EPD_DX = `dx\2000.2' EPD_FPGA = `fpga\2000.2' EPD_FPGA_MANAGER_BIN = `c:\epd\1.1\fpga\2000.2\manager\win32\bin' EPD_FPGA_MANAGER_STD = `c:\epd\1.1\fpga\2000.2\manager\win32\standard' EPD_HSSD = `hssd\2000.2' EPD_LOCAL = `C:\WINNT\Profiles\Administrator\Application Data\viewlogic\1.1' EPD_ROOT = `c:\epd\1.1' EPD_SIM = `sim\2000.2' EPD_START = `start' EPD_STARTBAT = `start /b /wait' EPD_VLPERL_BIN = `c:\epd\1.1\common\win32\perl\bin\mswin32-x86' EPD_WV = `wv\2000.2' HISTFILE = `/home/fmadmin/.bash_history' HISTFILESIZE = `100' HISTSIZE = `100' HOMEDRIVE = `C:' HOMEPATH = `\' HOST = `dali' HOSTNAME = `dali' ICAPSDIR = `c:\epd\1.1\sim\2000.2\viewanalog' INSTALLDIR = `C:\avanti\2000.2' IS@@@ = `c:\epd\1.1\sim\2000.2\viewanalog\sn' LM_LICENSE_FILE = `C:\avanti\2000.2\license.dat' LOGONSERVER = `\\DALI' MANPATH = `:/usr/ssl/man' NOCLOBBER = `' NUMBER_OF_PROCESSORS = `1' OLDPWD = `/home/fmadmin' OS2LIBPATH = `C:\WINNT\system32\os2\dll;' OS = `Windows_NT' PATHEXT = `.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH' PERLINTERP = `c:\epd\1.1\common\win32\perl\bin\MSWin32-x86\perl' PKG_CONFIG_PATH = `:/usr/X11R6/lib/pkgconfig' PROCESSOR_ARCHITECTURE = `x86' PROCESSOR_IDENTIFIER = `x86 Family 6 Model 7 Stepping 3, GenuineIntel' PROCESSOR_LEVEL = `6' PROCESSOR_REVISION = `0703' PROGRAMFILES = `C:\Program Files' PROMPT = `$P$G' PS1 = `\[\033]0;\w\007 \033[32m\]\u@\h \[\033[33m\w\033[0m\] $ ' QUADBIN = `c:\epd\1.1\hssd\2000.2\analysis\exec\nt_4' QUADHOME = `c:\epd\1.1\hssd\2000.2\analysis' SHELL = `/bin/bash' SHLVL = `1' SYSTEMDRIVE = `C:' SYSTEMROOT = `C:\WINNT' TEMP = `c:\WINNT\Profiles\fmadmin\LOCALS~1\Temp' TERM = `cygwin' TEXEDIT = `vi +%d %s' TMP = `c:\WINNT\Profiles\fmadmin\LOCALS~1\Temp' TMPDIR = `c:\TEMP' USERDOMAIN = `DALI' USERNAME = `fmadmin' USERPROFILE = `C:\WINNT\Profiles\fmadmin' VANTAGE_VSS = `c:\epd\1.1\sim\2000.2\van_vss\win32' VCSI_HOME = `c:/epd/1.1/sim/2000.2/vcsi/win32' VCS_HOME = `c:/epd/1.1/sim/2000.2/vcs/win32' WDIR = `W:%HMEDRIVE%;c:\epd\1.1\standard;c:\epd\1.1\fpga\2000.2\manager\standard' WINDIR = `C:\WINNT' _ = `/usr/bin/cygcheck' noclobber = `' Use `-r' to scan registry a: fd N/A N/A c: hd NTFS 7781Mb 91% CP CS UN PA FC d: cd N/A N/A e: hd FAT 1984Mb 31% CP UN USER f: cd N/A N/A h: net NTFS 40196Mb 91% CP CS PA fma C:\cygwin / system binmode c: /c system binmode c: /cygdrive/c system binmode f: /f system binmode h: /h system binmode C:\cygwin/bin /usr/bin system binmode C:\cygwin/lib /usr/lib system binmode C:\cygwin\usr\X11R6\lib\X11\fonts /usr/X11R6/lib/X11/fonts system binmode . /cygdrive system binmode,cygdrive Found: C:\cygwin\bin\awk.exe Found: C:\cygwin\bin\bash.exe Found: C:\cygwin\bin\cat.exe Found: C:\cygwin\bin\cp.exe Found: C:\cygwin\bin\cpp.exe Found: C:\cygwin\bin\find.exe Found: C:\cygwin\bin\gcc.exe Found: C:\cygwin\bin\gdb.exe Found: C:\cygwin\bin\grep.exe Found: C:\cygwin\bin\ld.exe Found: C:\cygwin\bin\ls.exe Found: C:\cygwin\bin\make.exe Found: C:\cygwin\bin\mv.exe Found: C:\cygwin\bin\rm.exe Found: C:\cygwin\bin\sed.exe Found: C:\cygwin\bin\sh.exe Found: C:\cygwin\bin\tar.exe 61k 2003/08/09 C:\cygwin\bin\cygbz2-1.dll - os=4.0 img=1.0 sys=4.0 "cygbz2-1.dll" v0.0 ts=2003/8/9 2:35 14k 2003/08/10 C:\cygwin\bin\cygcharset-1.dll - os=4.0 img=1.0 sys=4.0 "cygcharset-1.dll" v0.0 ts=2003/8/10 16:57 7k 2003/10/19 C:\cygwin\bin\cygcrypt-0.dll - os=4.0 img=1.0 sys=4.0 "cygcrypt-0.dll" v0.0 ts=2003/10/19 3:57 842k 2003/09/30 C:\cygwin\bin\cygcrypto-0.9.7.dll - os=4.0 img=1.0 sys=4.0 "cygcrypto-0.9.7.dll" v0.0 ts=2003/9/30 12:49 645k 2003/04/11 C:\cygwin\bin\cygcrypto.dll - os=4.0 img=1.0 sys=4.0 "cygcrypto.dll" v0.0 ts=2003/4/11 6:37 22k 2003/10/17 C:\cygwin\bin\cygcygipc-2.dll - os=4.0 img=1.0 sys=4.0 "cygcygipc-2.dll" v0.0 ts=2003/10/17 1:24 380k 2002/07/24 C:\cygwin\bin\cygdb-3.1.dll - os=4.0 img=1.0 sys=4.0 "cygdb-3.1.dll" v0.0 ts=2002/7/24 12:24 831k 2003/09/20 C:\cygwin\bin\cygdb-4.1.dll - os=4.0 img=1.0 sys=4.0 "cygdb-4.1.dll" v0.0 ts=2003/9/20 17:51 487k 2002/07/24 C:\cygwin\bin\cygdb_cxx-3.1.dll - os=4.0 img=1.0 sys=4.0 "cygdb_cxx-3.1.dll" v0.0 ts=2002/7/24 12:25 1080k 2003/09/20 C:\cygwin\bin\cygdb_cxx-4.1.dll - os=4.0 img=1.0 sys=4.0 "cygdb_cxx-4.1.dll" v0.0 ts=2003/9/20 17:53 132k 2003/07/12 C:\cygwin\bin\cygexpat-0.dll - os=4.0 img=1.0 sys=4.0 "cygexpat-0.dll" v0.0 ts=2003/7/12 7:33 131k 2003/10/28 C:\cygwin\bin\cygfontconfig-1.dll - os=4.0 img=1.0 sys=4.0 "cygfontconfig-1.dll" v0.0 ts=2003/10/28 17:44 45k 2001/04/25 C:\cygwin\bin\cygform5.dll - os=4.0 img=1.0 sys=4.0 "cygform5.dll" v0.0 ts=2001/4/25 1:28 35k 2002/01/09 C:\cygwin\bin\cygform6.dll - os=4.0 img=1.0 sys=4.0 "cygform6.dll" v0.0 ts=2002/1/9 1:03 48k 2003/08/09 C:\cygwin\bin\cygform7.dll - os=4.0 img=1.0 sys=4.0 "cygform7.dll" v0.0 ts=2003/8/9 5:25 361k 2003/10/25 C:\cygwin\bin\cygfreetype-6.dll - os=4.0 img=1.0 sys=4.0 "cygfreetype-6.dll" v0.0 ts=2003/10/22 0:18 28k 2003/07/20 C:\cygwin\bin\cyggdbm-3.dll - os=4.0 img=1.0 sys=4.0 "cyggdbm-3.dll" v0.0 ts=2003/7/20 3:58 30k 2003/08/11 C:\cygwin\bin\cyggdbm-4.dll - os=4.0 img=1.0 sys=4.0 "cyggdbm-4.dll" v0.0 ts=2003/8/10 22:12 19k 2003/03/22 C:\cygwin\bin\cyggdbm.dll - os=4.0 img=1.0 sys=4.0 "cyggdbm.dll" v0.0 ts=2002/2/19 22:05 15k 2003/07/20 C:\cygwin\bin\cyggdbm_compat-3.dll - os=4.0 img=1.0 sys=4.0 "cyggdbm_compat-3.dll" v0.0 ts=2003/7/20 4:00 15k 2003/08/11 C:\cygwin\bin\cyggdbm_compat-4.dll - os=4.0 img=1.0 sys=4.0 "cyggdbm_compat-4.dll" v0.0 ts=2003/8/10 22:13 69k 2003/08/10 C:\cygwin\bin\cyggettextlib-0-12-1.dll - os=4.0 img=1.0 sys=4.0 "cyggettextlib-0-12-1.dll" v0.0 ts=2003/8/10 18:10 12k 2003/08/10 C:\cygwin\bin\cyggettextpo-0.dll - os=4.0 img=1.0 sys=4.0 "cyggettextpo-0.dll" v0.0 ts=2003/8/10 18:11 134k 2003/08/10 C:\cygwin\bin\cyggettextsrc-0-12-1.dll - os=4.0 img=1.0 sys=4.0 "cyggettextsrc-0-12-1.dll" v0.0 ts=2003/8/10 18:10 17k 2001/06/28 C:\cygwin\bin\cyghistory4.dll - os=4.0 img=1.0 sys=4.0 "cyghistory4.dll" v0.0 ts=2001/1/6 23:34 29k 2003/08/10 C:\cygwin\bin\cyghistory5.dll - os=4.0 img=1.0 sys=4.0 "cyghistory5.dll" v0.0 ts=2003/8/10 19:16 958k 2003/08/10 C:\cygwin\bin\cygiconv-2.dll - os=4.0 img=1.0 sys=4.0 "cygiconv-2.dll" v0.0 ts=2003/8/10 16:57 22k 2001/12/13 C:\cygwin\bin\cygintl-1.dll - os=4.0 img=1.0 sys=4.0 "cygintl-1.dll" v0.0 ts=2001/12/13 4:28 37k 2003/08/10 C:\cygwin\bin\cygintl-2.dll - os=4.0 img=1.0 sys=4.0 "cygintl-2.dll" v0.0 ts=2003/8/10 17:50 21k 2001/06/20 C:\cygwin\bin\cygintl.dll - os=4.0 img=1.0 sys=4.0 "cygintl.dll" v0.0 ts=2001/6/20 13:09 132k 2003/08/11 C:\cygwin\bin\cygjpeg-62.dll - os=4.0 img=1.0 sys=4.0 "cygjpeg-62.dll" v0.0 ts=2003/8/10 20:37 119k 2002/02/09 C:\cygwin\bin\cygjpeg6b.dll - os=4.0 img=1.0 sys=4.0 "cygjpeg6b.dll" v0.0 ts=2002/2/9 0:19 26k 2001/04/25 C:\cygwin\bin\cygmenu5.dll - os=4.0 img=1.0 sys=4.0 "cygmenu5.dll" v0.0 ts=2001/4/25 1:27 20k 2002/01/09 C:\cygwin\bin\cygmenu6.dll - os=4.0 img=1.0 sys=4.0 "cygmenu6.dll" v0.0 ts=2002/1/9 1:03 29k 2003/08/09 C:\cygwin\bin\cygmenu7.dll - os=4.0 img=1.0 sys=4.0 "cygmenu7.dll" v0.0 ts=2003/8/9 5:25 156k 2001/04/25 C:\cygwin\bin\cygncurses++5.dll - os=4.0 img=1.0 sys=4.0 "cygncurses++5.dll" v0.0 ts=2001/4/25 1:29 175k 2002/01/09 C:\cygwin\bin\cygncurses++6.dll - os=4.0 img=1.0 sys=4.0 "cygncurses++6.dll" v0.0 ts=2002/1/9 1:03 226k 2001/04/25 C:\cygwin\bin\cygncurses5.dll - os=4.0 img=1.0 sys=4.0 "cygncurses5.dll" v0.0 ts=2001/4/25 1:17 202k 2002/01/09 C:\cygwin\bin\cygncurses6.dll - os=4.0 img=1.0 sys=4.0 "cygncurses6.dll" v0.0 ts=2002/1/9 1:03 224k 2003/08/09 C:\cygwin\bin\cygncurses7.dll - os=4.0 img=1.0 sys=4.0 "cygncurses7.dll" v0.0 ts=2003/8/9 5:24 15k 2001/04/25 C:\cygwin\bin\cygpanel5.dll - os=4.0 img=1.0 sys=4.0 "cygpanel5.dll" v0.0 ts=2001/4/25 1:27 12k 2002/01/09 C:\cygwin\bin\cygpanel6.dll - os=4.0 img=1.0 sys=4.0 "cygpanel6.dll" v0.0 ts=2002/1/9 1:03 19k 2003/08/09 C:\cygwin\bin\cygpanel7.dll - os=4.0 img=1.0 sys=4.0 "cygpanel7.dll" v0.0 ts=2003/8/9 5:24 67k 2003/09/10 C:\cygwin\bin\cygpcre-0.dll - os=4.0 img=1.0 sys=4.0 "cygpcre-0.dll" v0.0 ts=2003/9/10 10:25 63k 2003/04/11 C:\cygwin\bin\cygpcre.dll - os=4.0 img=1.0 sys=4.0 "cygpcre.dll" v0.0 ts=2003/4/11 4:31 15k 2003/09/10 C:\cygwin\bin\cygpcreposix-0.dll - os=4.0 img=1.0 sys=4.0 "cygpcreposix-0.dll" v0.0 ts=2003/9/10 10:25 61k 2003/04/11 C:\cygwin\bin\cygpcreposix.dll - os=4.0 img=1.0 sys=4.0 "cygpcreposix.dll" v0.0 ts=2003/4/11 4:31 1049k 2003/11/07 C:\cygwin\bin\cygperl5_8_2.dll - os=4.0 img=1.0 sys=4.0 "cygperl5_8_2.dll" v0.0 ts=2003/11/7 6:08 168k 2003/08/10 C:\cygwin\bin\cygpng10.dll - os=4.0 img=1.0 sys=4.0 "cygpng10.dll" v0.0 ts=2003/8/10 18:31 173k 2003/08/10 C:\cygwin\bin\cygpng12.dll - os=4.0 img=1.0 sys=4.0 "cygpng12.dll" v0.0 ts=2003/8/10 18:35 22k 2002/06/09 C:\cygwin\bin\cygpopt-0.dll - os=4.0 img=1.0 sys=4.0 "cygpopt-0.dll" v0.0 ts=2002/6/9 1:45 108k 2001/06/28 C:\cygwin\bin\cygreadline4.dll - os=4.0 img=1.0 sys=4.0 "cygreadline4.dll" v0.0 ts=2001/1/6 23:34 148k 2003/08/10 C:\cygwin\bin\cygreadline5.dll - os=4.0 img=1.0 sys=4.0 "cygreadline5.dll" v0.0 ts=2003/8/10 19:16 171k 2003/09/30 C:\cygwin\bin\cygssl-0.9.7.dll - os=4.0 img=1.0 sys=4.0 "cygssl-0.9.7.dll" v0.0 ts=2003/9/30 12:49 165k 2003/04/11 C:\cygwin\bin\cygssl.dll - os=4.0 img=1.0 sys=4.0 "cygssl.dll" v0.0 ts=2003/4/11 6:37 281k 2003/02/24 C:\cygwin\bin\cygtiff3.dll - os=4.0 img=1.0 sys=4.0 "cygtiff3.dll" v0.0 ts=2003/2/23 23:58 282k 2003/08/11 C:\cygwin\bin\cygtiff4.dll - os=4.0 img=1.0 sys=4.0 "cygtiff4.dll" v0.0 ts=2003/8/10 22:32 25k 2002/07/14 C:\cygwin\bin\cygungif-4.dll - os=4.0 img=1.0 sys=4.0 "cygungif-4.dll" v0.0 ts=2002/7/14 10:58 60k 2003/08/09 C:\cygwin\bin\cygz.dll - os=4.0 img=1.0 sys=4.0 "cygz.dll" v0.0 ts=2003/8/9 2:28 949k 2003/09/20 C:\cygwin\bin\cygwin1.dll - os=4.0 img=1.0 sys=4.0 "cygwin1.dll" v0.0 ts=2003/9/20 16:31 Cygwin DLL version info: DLL version: 1.5.5 DLL epoch: 19 DLL bad signal mask: 19005 DLL old termios: 5 DLL malloc env: 28 API major: 0 API minor: 94 Shared data: 3 DLL identifier: cygwin1 Mount registry: 2 Cygnus registry name: Cygnus Solutions Cygwin registry name: Cygwin Program options name: Program Options Cygwin mount registry name: mounts v2 Cygdrive flags: cygdrive flags Cygdrive prefix: cygdrive prefix Cygdrive default prefix: Build date: Sat Sep 20 16:31:15 EDT 2003 CVS tag: cr-0x9b Shared id: cygwin1S3 237k 2003/11/18 C:\cygwin\usr\X11R6\bin\cygdps-1.dll - os=4.0 img=1.0 sys=4.0 "cygdps-1.dll" v0.0 ts=2003/11/17 20:41 121k 2003/11/18 C:\cygwin\usr\X11R6\bin\cygdpstk-1.dll - os=4.0 img=1.0 sys=4.0 "cygdpstk-1.dll" v0.0 ts=2003/11/17 20:41 28k 2003/10/29 C:\cygwin\usr\X11R6\bin\cygDtPrint-1.dll - os=4.0 img=1.0 sys=4.0 "cygDtPrint-1.dll" v0.0 ts=2003/10/28 19:59 282k 2003/10/28 C:\cygwin\usr\X11R6\bin\cygfreetype-9.dll - os=4.0 img=1.0 sys=4.0 "cygfreetype-9.dll" v0.0 ts=2003/10/18 2:44 373k 2003/11/18 C:\cygwin\usr\X11R6\bin\cygGL-1.dll - os=4.0 img=1.0 sys=4.0 "cygGL-1.dll" v0.0 ts=2003/11/17 20:39 439k 2003/11/18 C:\cygwin\usr\X11R6\bin\cygGLU-1.dll - os=4.0 img=1.0 sys=4.0 "cygGLU-1.dll" v0.0 ts=2003/11/17 20:40 74k 2003/11/18 C:\cygwin\usr\X11R6\bin\cygICE-6.dll - os=4.0 img=1.0 sys=4.0 "cygICE-6.dll" v0.0 ts=2003/11/17 20:30 77k 2003/10/29 C:\cygwin\usr\X11R6\bin\cygMrm-2.dll - os=4.0 img=1.0 sys=4.0 "cygMrm-2.dll" v0.0 ts=2003/10/28 19:59 9k 2003/11/18 C:\cygwin\usr\X11R6\bin\cygoldX-6.dll - os=4.0 img=1.0 sys=4.0 "cygoldX-6.dll" v0.0 ts=2003/11/17 20:30 1271k 2003/11/18 C:\cygwin\usr\X11R6\bin\cygOSMesa-4.dll - os=4.0 img=1.0 sys=4.0 "cygOSMesa-4.dll" v0.0 ts=2003/11/17 20:39 20k 2003/11/18 C:\cygwin\usr\X11R6\bin\cygpsres-1.dll - os=4.0 img=1.0 sys=4.0 "cygpsres-1.dll" v0.0 ts=2003/11/17 20:42 30k 2003/11/18 C:\cygwin\usr\X11R6\bin\cygSM-6.dll - os=4.0 img=1.0 sys=4.0 "cygSM-6.dll" v0.0 ts=2003/11/17 20:30 66k 2003/10/29 C:\cygwin\usr\X11R6\bin\cygUil-2.dll - os=4.0 img=1.0 sys=4.0 "cygUil-2.dll" v0.0 ts=2003/10/28 19:59 864k 2003/11/18 C:\cygwin\usr\X11R6\bin\cygX11-6.dll - os=4.0 img=1.0 sys=4.0 "cygX11-6.dll" v0.0 ts=2003/11/17 20:30 253k 2003/11/18 C:\cygwin\usr\X11R6\bin\cygXaw-6.dll - os=4.0 img=1.0 sys=4.0 "cygXaw-6.dll" v0.0 ts=2003/11/17 20:33 355k 2003/11/18 C:\cygwin\usr\X11R6\bin\cygXaw-7.dll - os=4.0 img=1.0 sys=4.0 "cygXaw-7.dll" v0.0 ts=2003/11/17 20:34 281k 2003/10/30 C:\cygwin\usr\X11R6\bin\cygXaw3d-7.dll - os=4.0 img=1.0 sys=4.0 "cygXaw3d-7.dll" v0.0 ts=2003/10/30 11:14 36k 2003/11/18 C:\cygwin\usr\X11R6\bin\cygXcursor-1.dll - os=4.0 img=1.0 sys=4.0 "cygXcursor-1.dll" v0.0 ts=2003/11/17 20:43 49k 2003/11/18 C:\cygwin\usr\X11R6\bin\cygXext-6.dll - os=4.0 img=1.0 sys=4.0 "cygXext-6.dll" v0.0 ts=2003/11/17 20:30 56k 2003/11/18 C:\cygwin\usr\X11R6\bin\cygXft-1.dll - os=4.0 img=1.0 sys=4.0 "cygXft-1.dll" v0.0 ts=2003/11/17 20:42 74k 2003/11/18 C:\cygwin\usr\X11R6\bin\cygXft-2.dll - os=4.0 img=1.0 sys=4.0 "cygXft-2.dll" v0.0 ts=2003/11/17 20:42 27k 2003/11/18 C:\cygwin\usr\X11R6\bin\cygXi-6.dll - os=4.0 img=1.0 sys=4.0 "cygXi-6.dll" v0.0 ts=2003/11/17 20:34 1324k 2003/10/29 C:\cygwin\usr\X11R6\bin\cygXm-2.dll - os=4.0 img=1.0 sys=4.0 "cygXm-2.dll" v0.0 ts=2003/10/28 19:44 76k 2003/11/18 C:\cygwin\usr\X11R6\bin\cygXmu-6.dll - os=4.0 img=1.0 sys=4.0 "cygXmu-6.dll" v0.0 ts=2003/11/17 20:32 11k 2003/11/18 C:\cygwin\usr\X11R6\bin\cygXmuu-1.dll - os=4.0 img=1.0 sys=4.0 "cygXmuu-1.dll" v0.0 ts=2003/11/17 20:32 26k 2003/11/18 C:\cygwin\usr\X11R6\bin\cygXp-6.dll - os=4.0 img=1.0 sys=4.0 "cygXp-6.dll" v0.0 ts=2003/11/17 20:35 51k 2003/11/18 C:\cygwin\usr\X11R6\bin\cygXpm-4.dll - os=4.0 img=1.0 sys=4.0 "cygXpm-4.dll" v0.0 ts=2003/11/17 20:32 14k 2003/11/18 C:\cygwin\usr\X11R6\bin\cygXrandr-2.dll - os=4.0 img=1.0 sys=4.0 "cygXrandr-2.dll" v0.0 ts=2003/11/17 20:43 26k 2003/11/18 C:\cygwin\usr\X11R6\bin\cygXrender-1.dll - os=4.0 img=1.0 sys=4.0 "cygXrender-1.dll" v0.0 ts=2003/11/17 20:42 282k 2003/11/18 C:\cygwin\usr\X11R6\bin\cygXt-6.dll - os=4.0 img=1.0 sys=4.0 "cygXt-6.dll" v0.0 ts=2003/11/17 20:31 27k 2003/11/18 C:\cygwin\usr\X11R6\bin\cygXTrap-6.dll - os=4.0 img=1.0 sys=4.0 "cygXTrap-6.dll" v0.0 ts=2003/11/17 20:43 17k 2003/11/18 C:\cygwin\usr\X11R6\bin\cygXtst-6.dll - os=4.0 img=1.0 sys=4.0 "cygXtst-6.dll" v0.0 ts=2003/11/17 20:34 15k 2003/11/18 C:\cygwin\usr\X11R6\bin\cygXv-1.dll - os=4.0 img=1.0 sys=4.0 "cygXv-1.dll" v0.0 ts=2003/11/17 20:35 Use -h to see help about each section From huntharo@msu.edu Mon Nov 24 01:33:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Mon, 24 Nov 2003 01:33:00 -0000 Subject: DDD needs a porter [Was: DDD 3.3.8 segmentation error, related to Motif?] In-Reply-To: <3FC14C97.E9D22F22@doe.carleton.ca> References: <3FC14C97.E9D22F22@doe.carleton.ca> Message-ID: <3FC15FEC.10006@msu.edu> Fred, Fred Ma wrote: > On Fri, 21 Nov 2003 Brian Ford wrote: > >>On Fri, 21 Nov 2003 dirk.goethals@alcatel.be wrote: >> >>> bt08pm: /usr/X11R6/include/Xm/ ddd --lesstif-version 93 >>> Warning: This DDD requires a Motif 2.1 library (using Motif >>>-1617156.-609) >> >>Could you post cygcheck `type ddd`? >> >> >>> bt08pm: /usr/bin/ ddd --configuration >>> GNU DDD 3.3.8 (i686-pc-cygwin) >>> Copyright (C) 1995-1999 Technische Universit??t Braunschweig, Germany. >>> Copyright (C) 1999-2001 Universit??t Passau, Germany. >>> Copyright (C) 2001 Universit??t des Saarlandes, Germany. >>> >>> Compiled with GCC 3.2 20020927 (prerelease) >> >>Why not the current Cygwin gcc? > > > I'm having similar problems trying to build ddd-3.3.8 immediately > after update cygwin (1.5.5-1) and all components. This includes > lesstif 0.93.91-4, Xfree86-lib-compat 4.3.0-2, and XFree86-prog > 4.3.0-2. The last two are what comes up on a search for libXt in > Cygwin's Setup Package Search. The "configure" output also > claims "Motif...libraries in default path, headers in default > path". XFree86-prog-4.3.0-2 is ancient. XFree86-prog-4.3.0-12 is the current release: http://cygwin.com/ml/cygwin-xfree-announce/2003-11/msg00005.html libXt refers to the static Xt library; the new shared Xt library isn't called libXt, so you won't find it in a package search for the new versions. It is best if you just run setup.exe and let it automatically select packages that have new versions. With that being said, if you are successfully compiling ddd and still have the same problem, then you have proven that the problem has nothing to do with the shared Xt library, since your are linking against the static Xt library that is distributed with XFree86-prog-4.3.0-2. > The reason gcc-3.2 is used is because the most recent (I believe > it's 3.3.x) causes fatal link errors during the "make" step. The > suspected cause that I've read is that some cygwin components are > built with gcc-3.2. > > The exact error happens when I run "make check": > > make[1]: Entering directory `/home/fmadmin/INSTROOT/ddd-3.3.8/ddd' > MALLOC_CHECK_=2 \ > DDD_HOME=./.. \ > XUSERFILESEARCHPATH=%N XAPPLRESDIR=. \ > ./ddd.exe cxxtest.exe > Warning: This DDD requires a Motif 2.1 library (using Motif -6281.-729) > Continue at own risk. > > Internal error (Segmentation fault). > > Oops! You have found a bug in DDD. > > If you can reproduce this bug, please send a bug report > to , giving a subject like I said before that there appear to be flags that tell ddd that it is being compiled and linked against LessTif instead of Motif. Either these flags don't exist (as the emails that I found suggest), or you guys aren't trying them if they do exist. If they do exist, then that should at least get you closer to a working ddd. I have now realized something that should have been said from the start: DDD needs a porter Somebody needs to take it upon themself to port DDD and make appropriate fixes to make it work on Cygwin/X. This has not been done to date, as far as I can recall, and it is likely to need to be done before ddd will "just work". I don't see a lot happening with DDD until someone steps forward to port it properly. We can all continue to offer tips, but I don't think we are going to get anywhere. Harold From murakami@ipl.t.u-tokyo.ac.jp Mon Nov 24 06:27:00 2003 From: murakami@ipl.t.u-tokyo.ac.jp (Takuma Murakami) Date: Mon, 24 Nov 2003 06:27:00 -0000 Subject: Updated: XFree86-xserv-4.3.0-24 In-Reply-To: <3FBE6DC7.6030109@msu.edu> References: <3FBE6DC7.6030109@msu.edu> Message-ID: <20031124151128.E7CE.MURAKAMI@ipl.t.u-tokyo.ac.jp> Dear Harold and Alexander, Thank you for working on my stupid change. I noticed a problem with it. When "-kb" option is set, winconfig.c:417 should flag g_winInfo.xkb.disable field. However, it is enclosed in the condition (kbd != NULL) at line 387 so it won't be executed if no primary keyboard is specified. Therefore Windows autorepeat is still disabled no matter whether XKB is disabled or not. If my observation is right, could you fix it? Takuma Murakami (murakami@ipl.t.u-tokyo.ac.jp) From wolfgang.reichel@teepack.com Mon Nov 24 07:44:00 2003 From: wolfgang.reichel@teepack.com (Reichel, Wolfgang ) Date: Mon, 24 Nov 2003 07:44:00 -0000 Subject: startx problem on Win-XP Message-ID: <200311240957.21885.wolfgang.reichel@teepack.com> Hello ! I have installed the newest cygwin-version on my Win-XP box. But i can't start the X-System. It doesn't make any different how i try to start it. I tried the following way... startx 2>/tmp/mistlog and got this result: 1 [unknown (0xFEC)] XWin 2816 fhandler_console::fixup_after_exec: error opening input console handle after exec, errno 13, Win32 error 5 24355 [unknown (0xFEC)] XWin 2816 fhandler_console::fixup_after_exec: error opening input console handle after exec, errno 13, Win32 error 5 45493 [unknown (0xFEC)] XWin 2816 fhandler_console::fixup_after_exec: error opening input console handle after exec, errno 13, Win32 error 5 65932 [unknown (0xFEC)] XWin 2816 fhandler_console::fixup_after_exec: error opening input console handle after exec, errno 13, Win32 error 5 2 [unknown (0x860)] sh 3960 fhandler_console::fixup_after_exec: error opening input console handle after exec, errno 13, Win32 error 5 19020 [unknown (0x860)] sh 3960 fhandler_console::fixup_after_exec: error opening input console handle after exec, errno 13, Win32 error 5 47281 [main] sh 3960 fhandler_console::dup: error opening console, Win32 error 5 2 [unknown (0xCB4)] xkbcomp 2776 fhandler_console::fixup_after_exec: error opening input console handle after exec, errno 13, Win32 error 5 16842 [unknown (0xCB4)] xkbcomp 2776 fhandler_console::fixup_after_exec: error opening input console handle after exec, errno 13, Win32 error 5 XIO: fatal IO error 104 (Connection reset by peer) on X server ":0.0" after 0 requests (0 known processed) with 0 events remaining. What can i do ? Wolfgang Reichel From hans.dekker.ext@juntadeandalucia.es Mon Nov 24 08:10:00 2003 From: hans.dekker.ext@juntadeandalucia.es (Hans Dekker) Date: Mon, 24 Nov 2003 08:10:00 -0000 Subject: Cygwin XFree86 startx Problem References: Message-ID: <3FC1BBC5.3020903@juntadeandalucia.es> 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: cygwin-xfree-owner@cygwin.com >>[mailto:cygwin-xfree-owner@cygwin.com]On Behalf Of Andrew Markebo >>Sent: Friday, November 21, 2003 10:35 PM >>To: cygwin-xfree@cygwin.com >>Subject: Re: Cygwin XFree86 startx Problem >> >> >>/ Chan Seng Loong 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. >> >> >> > > From hans.dekker.ext@juntadeandalucia.es Mon Nov 24 08:18:00 2003 From: hans.dekker.ext@juntadeandalucia.es (Hans Dekker) Date: Mon, 24 Nov 2003 08:18:00 -0000 Subject: FW: I've given up on XF86, can' t make my AltGr keys work References: <81AC7B3F6CA6D4118AB00050BA8755668117EC@EXCHANGE> Message-ID: <3FC1BD1E.206@juntadeandalucia.es> FYI: Problems with xdmcp and AltGr keys also arise on Linux boxes I noticed. Solaris and HP-UX are not the only ones. Regards, Hans. Alexander Gottwald escribi??: > Benjamin Riefenstahl wrote: > > >>>If someone could donate an old sparc or HP-UX machine I'd be willing >>>to debug the problems with xdmcp, fonts and keyboardlayouts with >>>those machines. >> >>Wouldn't it be enough to get a temporary SSH account on a Sparc >>machine to reproduce this and debug the X server side? > > > For the testing I need a machine where I have full (root) access. Maybe the > yearly "our-university-sells-old-hardware-auction" has some HP-UX boxes. > > Anyway, such a sparc or HP-UX would be a nice donation *g* > > bye > ago From yet-another-cygwin-user@yacu.dont.want.pm Mon Nov 24 10:28:00 2003 From: yet-another-cygwin-user@yacu.dont.want.pm (Gael Gueguen) Date: Mon, 24 Nov 2003 10:28:00 -0000 Subject: Updated: XFree86-xserv-4.3.0-24 Message-ID: <20031124102820.GA1548@PRDRBNO> Takuma wrote: > When "-kb" option is set, winconfig.c:417 should flag > g_winInfo.xkb.disable field. However, it is enclosed in > the condition (kbd != NULL) at line 387 so it won't be > executed if no primary keyboard is specified. > > Therefore Windows autorepeat is still disabled no > matter whether XKB is disabled or not. Just tested: - with -kb, but without XF86Config: no autorepeat at all... /tmp/XWin.log: (--) Setting autorepeat to delay=500, rate=31 winKeybdProc - Error initializing keyboard AutoRepeat (No XKB) - with -kb and XF86Config: autorepeat is ok /tmp/XWin.log: (--) Setting autorepeat to delay=500, rate=31 (**) Option "AutoRepeat" "500 30" (**) AutoRepeat: 500 30 winKeybdProc - Error initializing keyboard AutoRepeat (No XKB) - with +kb and no XF86Config: autorepeat is ok /tmp/XWin.log: (--) Setting autorepeat to delay=500, rate=31 - with +kb and XF86Config (--) Setting autorepeat to delay=500, rate=31 (**) Option "AutoRepeat" "500 30" (**) AutoRepeat: 500 30 I think Takuma is right. By the way, most of the messages are duplicate in XWin.log: it seems like X is starting 2 times. Is this by design ? I've attached XWin.log for the first case tested. From yet-another-cygwin-user@yacu.dont.want.pm Mon Nov 24 10:36:00 2003 From: yet-another-cygwin-user@yacu.dont.want.pm (Gael Gueguen) Date: Mon, 24 Nov 2003 10:36:00 -0000 Subject: Updated: XFree86-xserv-4.3.0-24 In-Reply-To: <20031124102820.GA1548@PRDRBNO> References: <20031124102820.GA1548@PRDRBNO> Message-ID: <20031124103549.GA1244@PRDRBNO> Gael wrote: > > I've attached XWin.log for the first case tested. Oops, here it is. -------------- next part -------------- ddxProcessArgument - Initializing default screens winInitializeDefaultScreens - w 1152 h 864 winInitializeDefaultScreens - Returning OsVendorInit - Creating bogus screen 0 _XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root (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 0000001f InitOutput - g_iNumScreens: 1 iMaxConsecutiveScreen: 1 winSetEngine - Using Shadow DirectDraw NonLocking winAdjustVideoModeShadowDDNL - Using Windows display depth of 16 bits per pixel winCreateBoundingWindowWindowed - User w: 1152 h: 864 winCreateBoundingWindowWindowed - Current w: 1152 h: 864 winAdjustForAutoHide - Original WorkArea: 0 0 836 1152 winAdjustForAutoHide - Adjusted WorkArea: 0 0 836 1152 winCreateBoundingWindowWindowed - WindowClient w 1152 h 836 r 1152 l 0 b 836 t 0 winCreateBoundingWindowWindowed - Returning winCreatePrimarySurfaceShadowDDNL - Creating primary surface winCreatePrimarySurfaceShadowDDNL - Created primary surface winCreatePrimarySurfaceShadowDDNL - Attached clipper to primary surface winAllocateFBShadowDDNL - lPitch: 2304 winAllocateFBShadowDDNL - Created shadow pitch: 2304 winAllocateFBShadowDDNL - Created shadow stride: 1152 winFinishScreenInitFB - Masks: 0000f800 000007e0 0000001f winInitVisualsShadowDDNL - Masks 0000f800 000007e0 0000001f BPRGB 6 d 16 bpp 16 winCreateDefColormap - Deferring to fbCreateDefColormap () winFinishScreenInitFB - returning winScreenInit - returning LoadPreferences: Done parsing the configuration file... InitOutput - Returning. MIT-SHM extension disabled due to lack of kernel support XFree86-Bigfont extension local-client optimization disabled due to lack of shared memory support in the kernel (--) Setting autorepeat to delay=500, rate=31 (--) winConfigKeyboard - Layout: "0000040C" (0000040c) (--) Using preset keyboard for "French (Standard)" (40c), type "4" (EE) No primary keyboard configured (==) Using compiletime defaults for keyboard Rules = "xfree86" Model = "pc105" Layout = "fr" Variant = "(null)" Options = "(null)" winKeybdProc - Error initializing keyboard AutoRepeat (No XKB) winPointerWarpCursor - Discarding first warp: 576 418 winBlockHandler - Releasing pmServerStarted winBlockHandler - pthread_mutex_unlock () returned (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 0000001f InitOutput - g_iNumScreens: 1 iMaxConsecutiveScreen: 1 winSetEngine - Using Shadow DirectDraw NonLocking winCreateBoundingWindowWindowed - User w: 1152 h: 864 winCreateBoundingWindowWindowed - Current w: 1152 h: 836 winAdjustForAutoHide - Original WorkArea: 0 0 836 1152 winAdjustForAutoHide - Adjusted WorkArea: 0 0 836 1152 winCreateBoundingWindowWindowed - WindowClient w 1152 h 836 r 1152 l 0 b 836 t 0 winCreateBoundingWindowWindowed - Returning winCreatePrimarySurfaceShadowDDNL - Creating primary surface winCreatePrimarySurfaceShadowDDNL - Created primary surface winCreatePrimarySurfaceShadowDDNL - Attached clipper to primary surface winAllocateFBShadowDDNL - lPitch: 2304 winAllocateFBShadowDDNL - Created shadow pitch: 2304 winAllocateFBShadowDDNL - Created shadow stride: 1152 winFinishScreenInitFB - Masks: 0000f800 000007e0 0000001f winInitVisualsShadowDDNL - Masks 0000f800 000007e0 0000001f BPRGB 6 d 16 bpp 16 winCreateDefColormap - Deferring to fbCreateDefColormap () winFinishScreenInitFB - returning winScreenInit - returning LoadPreferences: Done parsing the configuration file... InitOutput - Returning. MIT-SHM extension disabled due to lack of kernel support XFree86-Bigfont extension local-client optimization disabled due to lack of shared memory support in the kernel (--) Setting autorepeat to delay=500, rate=31 (--) winConfigKeyboard - Layout: "0000040C" (0000040c) (--) Using preset keyboard for "French (Standard)" (40c), type "4" (EE) No primary keyboard configured (==) Using compiletime defaults for keyboard Rules = "xfree86" Model = "pc105" Layout = "fr" Variant = "(null)" Options = "(null)" winKeybdProc - Error initializing keyboard AutoRepeat (No XKB) winDeinitClipboard - Noting shutdown in progress winDeinitMultiWindowWM - Noting shutdown in progress From alexander.gottwald@s1999.tu-chemnitz.de Mon Nov 24 13:35:00 2003 From: alexander.gottwald@s1999.tu-chemnitz.de (Alexander Gottwald) Date: Mon, 24 Nov 2003 13:35:00 -0000 Subject: FW: I've given up on XF86, can' t make my AltGr keys work In-Reply-To: <3FC1BD1E.206@juntadeandalucia.es> References: <81AC7B3F6CA6D4118AB00050BA8755668117EC@EXCHANGE> <3FC1BD1E.206@juntadeandalucia.es> Message-ID: On Mon, 24 Nov 2003, Hans Dekker wrote: > FYI: Problems with xdmcp and AltGr keys also arise on Linux boxes I > noticed. Solaris and HP-UX are not the only ones. I've never noticed such problems with linux boxes. Maybe a configuration where the xdmcp server calls xmodmap and resets the layout will lead to these problems with linux too. bye ago -- Alexander.Gottwald@s1999.tu-chemnitz.de http://www.gotti.org ICQ: 126018723 From alexander.gottwald@s1999.tu-chemnitz.de Mon Nov 24 14:20:00 2003 From: alexander.gottwald@s1999.tu-chemnitz.de (Alexander Gottwald) Date: Mon, 24 Nov 2003 14:20:00 -0000 Subject: Updated: XFree86-xserv-4.3.0-24 In-Reply-To: <20031124151128.E7CE.MURAKAMI@ipl.t.u-tokyo.ac.jp> References: <3FBE6DC7.6030109@msu.edu> <20031124151128.E7CE.MURAKAMI@ipl.t.u-tokyo.ac.jp> Message-ID: On Mon, 24 Nov 2003, Takuma Murakami wrote: > When "-kb" option is set, winconfig.c:417 should flag > g_winInfo.xkb.disable field. However, it is enclosed in > the condition (kbd != NULL) at line 387 so it won't be > executed if no primary keyboard is specified. > > Therefore Windows autorepeat is still disabled no > matter whether XKB is disabled or not. > > If my observation is right, could you fix it? I've checked in two patches for the problem, but was not able to test them. But they are small and I don't expect any problems with it. @Harold: Can you do a testbuild? bye ago -- Alexander.Gottwald@s1999.tu-chemnitz.de http://www.gotti.org ICQ: 126018723 From huntharo@msu.edu Mon Nov 24 14:27:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Mon, 24 Nov 2003 14:27:00 -0000 Subject: startx problem on Win-XP In-Reply-To: <200311240957.21885.wolfgang.reichel@teepack.com> References: <200311240957.21885.wolfgang.reichel@teepack.com> Message-ID: <3FC2154F.1010306@msu.edu> Wolfgang, Reichel, Wolfgang wrote: > Hello ! > > I have installed the newest cygwin-version > on my Win-XP box. > > But i can't start the X-System. > It doesn't make any different how i try to start it. > > I tried the following way... > > startx 2>/tmp/mistlog Use startxwin.bat instead: http://xfree86.cygwin.com/docs/ug/using.html#using-starting-bat Harold From huntharo@msu.edu Mon Nov 24 15:00:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Mon, 24 Nov 2003 15:00:00 -0000 Subject: Updated: XFree86-xserv-4.3.0-24 In-Reply-To: References: <3FBE6DC7.6030109@msu.edu> <20031124151128.E7CE.MURAKAMI@ipl.t.u-tokyo.ac.jp> Message-ID: <3FC21D0B.4050805@msu.edu> http://xfree86.cygwin.com/devel/server/changelog.html Alexander Gottwald wrote: > On Mon, 24 Nov 2003, Takuma Murakami wrote: > > >>When "-kb" option is set, winconfig.c:417 should flag >>g_winInfo.xkb.disable field. However, it is enclosed in >>the condition (kbd != NULL) at line 387 so it won't be >>executed if no primary keyboard is specified. >> >>Therefore Windows autorepeat is still disabled no >>matter whether XKB is disabled or not. >> >>If my observation is right, could you fix it? > > > I've checked in two patches for the problem, but was not able to > test them. But they are small and I don't expect any problems with > it. > > @Harold: Can you do a testbuild? > > bye > ago From cec112@psu.edu Mon Nov 24 15:12:00 2003 From: cec112@psu.edu (Charles E. Cooper) Date: Mon, 24 Nov 2003 15:12:00 -0000 Subject: startx problem on Win-XP In-Reply-To: <3FC2154F.1010306@msu.edu> References: <200311240957.21885.wolfgang.reichel@teepack.com> <200311240957.21885.wolfgang.reichel@teepack.com> Message-ID: <5.1.0.14.2.20031124100900.02e4e0b0@email.psu.edu> I've also been struggling to get a useable windows system. I use cygwin to log into Sun systems. I tried the startxwin.bat method and get a window up, but it won't let me redirect remote windows back to my Windows platform. I then ssh into the sun machine setenv DISPLAY machinename:0.0 textedit filename as I can do when I use "startx" I basically don't like the "twm" window manager, but haven't figure out how to start something better. Chuck At 09:27 AM 11/24/2003 -0500, you wrote: >Wolfgang, > >Reichel, Wolfgang wrote: >>Hello ! >>I have installed the newest cygwin-version >>on my Win-XP box. >>But i can't start the X-System. >>It doesn't make any different how i try to start it. >>I tried the following way... >> startx 2>/tmp/mistlog > >Use startxwin.bat instead: > >http://xfree86.cygwin.com/docs/ug/using.html#using-starting-bat > > >Harold > Charles E. Cooper Swift Program Applied Research Laboratory The Pennsylvania State University (814) 865-6829 ccooper@psu.edu From huntharo@msu.edu Mon Nov 24 15:26:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Mon, 24 Nov 2003 15:26:00 -0000 Subject: startx problem on Win-XP In-Reply-To: <5.1.0.14.2.20031124100900.02e4e0b0@email.psu.edu> References: <200311240957.21885.wolfgang.reichel@teepack.com> <200311240957.21885.wolfgang.reichel@teepack.com> <5.1.0.14.2.20031124100900.02e4e0b0@email.psu.edu> Message-ID: <3FC2231D.2080305@msu.edu> Chuck, Charles E. Cooper wrote: > I've also been struggling to get a useable windows system. > I use cygwin to log into Sun systems. > > I tried the startxwin.bat method and get a window up, but it won't let > me redirect remote windows back to my Windows platform. If you are doing this via telnet or ssh without the "-X" parameter, then you need to run "xhost remotemachine_ip_or_dns_name" to allow connections from that machine to your local X Server. This method is not secure and is not recommended, but here is how to do it if you really want to know: http://xfree86.cygwin.com/docs/ug/using-remote-apps.html#using-remote-apps-telnet > I then ssh into the sun machine > setenv DISPLAY machinename:0.0 > textedit filename That is silly. ssh supports "tunneling" X apps, which sends them over a secure and optionally compressed (with the "-C" parameter) channel. Here is how to use it: http://xfree86.cygwin.com/docs/ug/using-remote-apps.html#using-remote-apps-ssh > as I can do when I use "startx" > > I basically don't like the "twm" window manager, but haven't figure out > how to start something better. You really need to use startxwin.bat... it uses the "multi-window window manager" by default, which uses Windows as the window manager. Here is how to use startxwin.bat: http://xfree86.cygwin.com/docs/ug/using.html#using-starting-bat Finally, run setup.exe again and make sure that you have the latest packages. Let setup.exe determine what has been updated and let it install whatever it selects automatically. Harold From huntharo@msu.edu Mon Nov 24 15:28:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Mon, 24 Nov 2003 15:28:00 -0000 Subject: Updated: XFree86-xserv-4.3.0-24 In-Reply-To: <20031124102820.GA1548@PRDRBNO> References: <20031124102820.GA1548@PRDRBNO> Message-ID: <3FC2238D.7060603@msu.edu> Gael, Try the 4.3.0-25 release when it shows up on your mirror. Harold Gael Gueguen wrote: > Takuma wrote: > > >>When "-kb" option is set, winconfig.c:417 should flag >>g_winInfo.xkb.disable field. However, it is enclosed in >>the condition (kbd != NULL) at line 387 so it won't be >>executed if no primary keyboard is specified. >> >>Therefore Windows autorepeat is still disabled no >>matter whether XKB is disabled or not. > > > Just tested: > - with -kb, but without XF86Config: no autorepeat at all... > /tmp/XWin.log: > (--) Setting autorepeat to delay=500, rate=31 > winKeybdProc - Error initializing keyboard AutoRepeat (No XKB) > > - with -kb and XF86Config: autorepeat is ok > /tmp/XWin.log: > (--) Setting autorepeat to delay=500, rate=31 > (**) Option "AutoRepeat" "500 30" > (**) AutoRepeat: 500 30 > winKeybdProc - Error initializing keyboard AutoRepeat (No XKB) > > - with +kb and no XF86Config: autorepeat is ok > /tmp/XWin.log: > (--) Setting autorepeat to delay=500, rate=31 > > - with +kb and XF86Config > (--) Setting autorepeat to delay=500, rate=31 > (**) Option "AutoRepeat" "500 30" > (**) AutoRepeat: 500 30 > > I think Takuma is right. > > By the way, most of the messages are duplicate in XWin.log: it seems > like X is starting 2 times. Is this by design ? > > I've attached XWin.log for the first case tested. From huntharo@msu.edu Mon Nov 24 15:43:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Mon, 24 Nov 2003 15:43:00 -0000 Subject: Cygwin/X Announcements - Only sent to cygwin-xfree-announce@cygwin.com Message-ID: <3FC22738.8000409@msu.edu> The subject says it all. Due to popular demand I have started sending announcements *only* to cygwin-xfree-announce@cygwin.com. I no longer post announcements to cygwin-xfree@cygwin.com. Now is the time to subscribe to the cygwin-xfree-announce@cygwin.com mailing list if you have not already done so: http://cygwin.com/lists.html Harold From cec112@psu.edu Mon Nov 24 15:52:00 2003 From: cec112@psu.edu (Charles E. Cooper) Date: Mon, 24 Nov 2003 15:52:00 -0000 Subject: startx problem on Win-XP In-Reply-To: <3FC2231D.2080305@msu.edu> References: <5.1.0.14.2.20031124100900.02e4e0b0@email.psu.edu> <200311240957.21885.wolfgang.reichel@teepack.com> <200311240957.21885.wolfgang.reichel@teepack.com> <5.1.0.14.2.20031124100900.02e4e0b0@email.psu.edu> Message-ID: <5.1.0.14.2.20031124104950.02e8a008@email.psu.edu> OK, must have been too early on Monday morning, as I knew about the xhost, but didn't do it. I now seem to have it working using the windows manager, this is a vast improvement as I can do radical things like resize and close windows! Thanks for the tips. Chuck At 10:26 AM 11/24/2003 -0500, you wrote: >Chuck, > >Charles E. Cooper wrote: > >>I've also been struggling to get a useable windows system. >>I use cygwin to log into Sun systems. >>I tried the startxwin.bat method and get a window up, but it won't let me >>redirect remote windows back to my Windows platform. > >If you are doing this via telnet or ssh without the "-X" parameter, then >you need to run "xhost remotemachine_ip_or_dns_name" to allow connections >from that machine to your local X Server. > >This method is not secure and is not recommended, but here is how to do it >if you really want to know: > >http://xfree86.cygwin.com/docs/ug/using-remote-apps.html#using-remote-apps-telnet > >> I then ssh into the sun machine >> setenv DISPLAY machinename:0.0 >> textedit filename > >That is silly. ssh supports "tunneling" X apps, which sends them over a >secure and optionally compressed (with the "-C" parameter) channel. Here >is how to use it: > >http://xfree86.cygwin.com/docs/ug/using-remote-apps.html#using-remote-apps-ssh > >>as I can do when I use "startx" >>I basically don't like the "twm" window manager, but haven't figure out >>how to start something better. > >You really need to use startxwin.bat... it uses the "multi-window window >manager" by default, which uses Windows as the window manager. Here is >how to use startxwin.bat: > >http://xfree86.cygwin.com/docs/ug/using.html#using-starting-bat > > >Finally, run setup.exe again and make sure that you have the latest >packages. Let setup.exe determine what has been updated and let it >install whatever it selects automatically. > > >Harold > Charles E. Cooper Swift Program Applied Research Laboratory The Pennsylvania State University (814) 865-6829 ccooper@psu.edu From pechtcha@cs.nyu.edu Mon Nov 24 16:13:00 2003 From: pechtcha@cs.nyu.edu (Igor Pechtchanski) Date: Mon, 24 Nov 2003 16:13:00 -0000 Subject: Cygwin XFree86 startx Problem In-Reply-To: <3FC1BBC5.3020903@juntadeandalucia.es> References: <3FC1BBC5.3020903@juntadeandalucia.es> Message-ID: 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: cygwin-xfree-owner@cygwin.com > >>[mailto:cygwin-xfree-owner@cygwin.com]On Behalf Of Andrew Markebo > >>Sent: Friday, November 21, 2003 10:35 PM > >>To: cygwin-xfree@cygwin.com > >>Subject: Re: Cygwin XFree86 startx Problem > >> > >> > >>/ Chan Seng Loong 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/ |\ _,,,---,,_ pechtcha@cs.nyu.edu ZZZzz /,`.-'`' -. ;-;;,_ igor@watson.ibm.com |,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 From yet-another-cygwin-user@yacu.dont.want.pm Mon Nov 24 16:31:00 2003 From: yet-another-cygwin-user@yacu.dont.want.pm (Gael Gueguen) Date: Mon, 24 Nov 2003 16:31:00 -0000 Subject: Updated: XFree86-xserv-4.3.0-24 Message-ID: <20031124163149.GA2216@PRDRBNO> Harold wrote: > Try the 4.3.0-25 release when it shows up on your mirror. Works fine, thanks for the quick patch. Gael. From huntharo@msu.edu Mon Nov 24 16:33:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Mon, 24 Nov 2003 16:33:00 -0000 Subject: Updated: XFree86-xserv-4.3.0-24 In-Reply-To: <20031124163149.GA2216@PRDRBNO> References: <20031124163149.GA2216@PRDRBNO> Message-ID: <3FC232DC.90606@msu.edu> Gael, Great, thanks for the confirmation. Harold Gael Gueguen wrote: > Harold wrote: > > >>Try the 4.3.0-25 release when it shows up on your mirror. > > > Works fine, thanks for the quick patch. > > Gael. From cec112@psu.edu Mon Nov 24 16:36:00 2003 From: cec112@psu.edu (Charles E. Cooper) Date: Mon, 24 Nov 2003 16:36:00 -0000 Subject: startx problem on Win-XP In-Reply-To: <3FC2231D.2080305@msu.edu> References: <5.1.0.14.2.20031124100900.02e4e0b0@email.psu.edu> <200311240957.21885.wolfgang.reichel@teepack.com> <200311240957.21885.wolfgang.reichel@teepack.com> <5.1.0.14.2.20031124100900.02e4e0b0@email.psu.edu> Message-ID: <5.1.0.14.2.20031124113415.02e57ad8@email.psu.edu> OK, my excitement has dwindled. I tried used "textedit" remotely and the cursor is non-functional in the remoted display. I can't edit or scroll without the cursor. to summarize what I'm doing: xhost + machinename ssh -X -l username machinename when logged into machinename setenv DISPLAY localmachinename:0.0 textedit filename & am I missing something? Chuck At 10:26 AM 11/24/2003 -0500, you wrote: >Chuck, > >Charles E. Cooper wrote: > >>I've also been struggling to get a useable windows system. >>I use cygwin to log into Sun systems. >>I tried the startxwin.bat method and get a window up, but it won't let me >>redirect remote windows back to my Windows platform. > >If you are doing this via telnet or ssh without the "-X" parameter, then >you need to run "xhost remotemachine_ip_or_dns_name" to allow connections >from that machine to your local X Server. > >This method is not secure and is not recommended, but here is how to do it >if you really want to know: > >http://xfree86.cygwin.com/docs/ug/using-remote-apps.html#using-remote-apps-telnet > >> I then ssh into the sun machine >> setenv DISPLAY machinename:0.0 >> textedit filename > >That is silly. ssh supports "tunneling" X apps, which sends them over a >secure and optionally compressed (with the "-C" parameter) channel. Here >is how to use it: > >http://xfree86.cygwin.com/docs/ug/using-remote-apps.html#using-remote-apps-ssh > >>as I can do when I use "startx" >>I basically don't like the "twm" window manager, but haven't figure out >>how to start something better. > >You really need to use startxwin.bat... it uses the "multi-window window >manager" by default, which uses Windows as the window manager. Here is >how to use startxwin.bat: > >http://xfree86.cygwin.com/docs/ug/using.html#using-starting-bat > > >Finally, run setup.exe again and make sure that you have the latest >packages. Let setup.exe determine what has been updated and let it >install whatever it selects automatically. > > >Harold > Charles E. Cooper Swift Program Applied Research Laboratory The Pennsylvania State University (814) 865-6829 ccooper@psu.edu From huntharo@msu.edu Mon Nov 24 16:53:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Mon, 24 Nov 2003 16:53:00 -0000 Subject: startx problem on Win-XP In-Reply-To: <5.1.0.14.2.20031124113415.02e57ad8@email.psu.edu> References: <5.1.0.14.2.20031124100900.02e4e0b0@email.psu.edu> <200311240957.21885.wolfgang.reichel@teepack.com> <200311240957.21885.wolfgang.reichel@teepack.com> <5.1.0.14.2.20031124100900.02e4e0b0@email.psu.edu> <5.1.0.14.2.20031124113415.02e57ad8@email.psu.edu> Message-ID: <3FC2378F.9040400@msu.edu> Charles E. Cooper wrote: > OK, my excitement has dwindled. > I tried used "textedit" remotely and the cursor is non-functional in the > remoted display. > I can't edit or scroll without the cursor. > > to summarize what I'm doing: > xhost + machinename > ssh -X -l username machinename > > when logged into machinename > setenv DISPLAY localmachinename:0.0 > textedit filename & You need to read the instructions I sent you: http://xfree86.cygwin.com/docs/ug/using-remote-apps.html#using-remote-apps-ssh Do not assume that you should add steps of your own. The instructions list exactly which steps must be taken; anything left out is left out for a very good reason (i.e. it is not needed). The "xhost" step is not needed when using "ssh -X". The "setenv" step is not needed when using "ssh -X". Note that neither of these steps is in the instructions at the page above. Harold From richard.campbell@air2web.com Mon Nov 24 17:55:00 2003 From: richard.campbell@air2web.com (Richard Campbell) Date: Mon, 24 Nov 2003 17:55:00 -0000 Subject: DDD needs a porter [Was: DDD 3.3.8 segmentation error, relate d to Motif?] Message-ID: >Somebody needs to take it upon themself to port DDD and make appropriate >fixes to make it work on Cygwin/X. This has not been done to date, as >far as I can recall, and it is likely to need to be done before ddd will >"just work". I don't see a lot happening with DDD until someone steps >forward to port it properly. In previous versions (cygwin, xfree, ddd), DDD did compile and run out of the box. I believe that is why no one took it upon themselves previously. see http://www.cygwin.com/ml/cygwin/2003-09/msg00241.html -Richard Campbell. From huntharo@msu.edu Mon Nov 24 18:15:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Mon, 24 Nov 2003 18:15:00 -0000 Subject: DDD needs a porter [Was: DDD 3.3.8 segmentation error, relate d to Motif?] In-Reply-To: References: Message-ID: <3FC24AA6.9020708@msu.edu> Richard, Richard Campbell wrote: >>Somebody needs to take it upon themself to port DDD and make appropriate >>fixes to make it work on Cygwin/X. This has not been done to date, as >>far as I can recall, and it is likely to need to be done before ddd will >>"just work". I don't see a lot happening with DDD until someone steps >>forward to port it properly. > > > In previous versions (cygwin, xfree, ddd), DDD did compile and run out > of the box. I believe that is why no one took it upon themselves > previously. > > see http://www.cygwin.com/ml/cygwin/2003-09/msg00241.html Okay. That is good to know. However, a lot has happened since then and I stand by my point that someone will have to dedicate some time to getting this to work. The LessTif questions could be a red herring... the problem might be that there are some #ifdef __CYGWIN__'s in the code that cause problems with the new Cygwin 1.5.3-x + versions. However, it could be any number of issues. Harold From johncsl82@yahoo.com Mon Nov 24 20:03:00 2003 From: johncsl82@yahoo.com (Chan Seng Loong) Date: Mon, 24 Nov 2003 20:03:00 -0000 Subject: Install KDE or GNOME to cygwin xfee86 Message-ID: <20031124194849.25335.qmail@web60310.mail.yahoo.com> hi... Can I install KDE from www.kde.org or GNOME from www.gnome directly into cygwin xfree86? Thanks :-) __________________________________ Do you Yahoo!? Protect your identity with Yahoo! Mail AddressGuard http://antispam.yahoo.com/whatsnewfree From penne296@netscape.net Mon Nov 24 20:21:00 2003 From: penne296@netscape.net (mike) Date: Mon, 24 Nov 2003 20:21:00 -0000 Subject: problem with ooffice and kde Message-ID: When i do an X -query to my debian unstable box menus are not displayed in ooffice and icons are not displayed in kde screenshot : http://penne296.free.fr/tux.jpg gnome apps work fine. mike From davidf@sjsoft.com Mon Nov 24 20:38:00 2003 From: davidf@sjsoft.com (David Fraser) Date: Mon, 24 Nov 2003 20:38:00 -0000 Subject: Install KDE or GNOME to cygwin xfee86 In-Reply-To: <20031124194849.25335.qmail@web60310.mail.yahoo.com> References: <20031124194849.25335.qmail@web60310.mail.yahoo.com> Message-ID: <3FC26C41.3050803@sjsoft.com> Chan Seng Loong wrote: >hi... > >Can I install KDE from www.kde.org or GNOME from >www.gnome directly into cygwin xfree86? > >Thanks > >:-) > > Neither www.kde.org nor www.gnome.org provide binaries compiled for cygwin (AFAIK). Compiling the source yourself is reasonably difficult and not to be taken on unless you have a reason for doing so... On the other hand, there are projects that provide nice packages binaries: http://kde-cygwin.sourceforge.net - very good package that runs kde on cygwin and http://cygnome.sourceforge.net/ - slightly less easy to use package (IMO) that runs gnome on cygwin You would do best to try those out, and ask on their mailing lists for help rather than here, as that's where the experts are... David From ats@acm.org Mon Nov 24 20:50:00 2003 From: ats@acm.org (Alan Shutko) Date: Mon, 24 Nov 2003 20:50:00 -0000 Subject: Problem with WinXP, XF86, Caps lock, xterm and cursor keys Message-ID: <874qwtilv2.fsf@wesley.springies.com> I've just gotten a new laptop at work with WinXP, and put Cygwin and XF86 on it. I'm currently running the latest as of today (4.3.0-25 server). I've disabled my capslock key and turned it into a control key with this registry hack: REGEDIT4 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Keyboard Layout] "Scancode Map"=hex:00,00,00,00,00,00,00,00,02,00,00,00,1d,00,3a,00,00,00,00,00 My caps lock key correctly works as a control key in all windows applications, and xev shows it acts just like Control_L. In xterm, I can use the caps lock key as a control key. Except, each time I press it, my arrow keys toggle between sending the correct "^[[A" and the strange "^[[1;2A" (for up; left, down and right have similar changes). Apparently, it's toggling the cursor keys into "shifted" state, because that's the "shifted" up arrow key. This only affects the arrow keys, and page up/page down (which are toggled into scrolling). It seems like there's a bug somewhere tracking the caps lock, since I seem to have correctly disabled caps lock for number keys, but not arrows. -- Alan Shutko - I am the rocks. I'm not even going to ignore that. From wolfgang.reichel@teepack.com Tue Nov 25 08:44:00 2003 From: wolfgang.reichel@teepack.com (Reichel, Wolfgang ) Date: Tue, 25 Nov 2003 08:44:00 -0000 Subject: startx problem on Win-XP Message-ID: <200311251057.11859.wolfgang.reichel@teepack.com> Harold , >>Reichel, Wolfgang wrote: >>Hello ! >>I have installed the newest cygwin-version >>on my Win-XP box. >>But i can't start the X-System. >>It doesn't make any different how i try to start it. >>I tried the following way... >>startx 2>/tmp/mistlog > Use startxwin.bat instead: > http://xfree86.cygwin.com/docs/ug/using.html#using-starting-bat > Harold Thanks for your answer. But i tried all ways described in the docs to start. Nothing works. The startxwin.bat runs but nothing happens. What can be the reason ? Wolfgang From alexander.gottwald@s1999.tu-chemnitz.de Tue Nov 25 09:51:00 2003 From: alexander.gottwald@s1999.tu-chemnitz.de (Alexander Gottwald) Date: Tue, 25 Nov 2003 09:51:00 -0000 Subject: Problem with WinXP, XF86, Caps lock, xterm and cursor keys In-Reply-To: <874qwtilv2.fsf@wesley.springies.com> References: <874qwtilv2.fsf@wesley.springies.com> Message-ID: On Mon, 24 Nov 2003, Alan Shutko wrote: > I've just gotten a new laptop at work with WinXP, and put Cygwin and > XF86 on it. I'm currently running the latest as of today (4.3.0-25 > server). > > I've disabled my capslock key and turned it into a control key with > this registry hack: > > REGEDIT4 > > [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Keyboard Layout] > "Scancode Map"=hex:00,00,00,00,00,00,00,00,02,00,00,00,1d,00,3a,00,00,00,00,00 > > My caps lock key correctly works as a control key in all windows > applications, and xev shows it acts just like Control_L. > > In xterm, I can use the caps lock key as a control key. Except, each > time I press it, my arrow keys toggle between sending the correct > "^[[A" and the strange "^[[1;2A" (for up; left, down and right have > similar changes). Apparently, it's toggling the cursor keys into > "shifted" state, because that's the "shifted" up arrow key. > > This only affects the arrow keys, and page up/page down (which are > toggled into scrolling). It seems like there's a bug somewhere > tracking the caps lock, since I seem to have correctly disabled caps > lock for number keys, but not arrows. Cygwin/XFree uses raw scancodes and uses XKB for symbol translation. Your tweaking will most likely break this conversion. I declare such a modification as unsupported. You may still ask for pointers to documentation but I (and most likely the other regulars too) am not willing to debug such strange modifications. bye ago -- Alexander.Gottwald@s1999.tu-chemnitz.de http://www.gotti.org ICQ: 126018723 From loucyphhre@libero.it Tue Nov 25 10:31:00 2003 From: loucyphhre@libero.it (Lou Cyphre) Date: Tue, 25 Nov 2003 10:31:00 -0000 Subject: Compiling SNNS (Stuttgart Neural Network Simulator) or using v.4.2 binaries Message-ID: <3FC32F7F.4070505@libero.it> Did anybody recompiled successfully SNNS 4.2 with Cygwin/X? Its home page is at http://www-ra.informatik.uni-tuebingen.de/SNNS/ I firstly tried using SNNS 4.2 binaries with latest Cygwin/X as X-server, but something wasn't working in the user interface (couldn't select some menu list entries), so I decided to get sources at http://www-ra.informatik.uni-tuebingen.de/downloads/SNNS/SNNSv4.2.tar.gz and try recompile them. Beside a few #define missing (that I properly fixed) seemed that the configure script was running fine, infact I can run the application, and now all the menu lists do work, but... when loading even an example configuration file I get syntax errors in file, and after some clicks, trying opening other windows, crashes. Note that I already used successfully on Linux some years ago, so not new to program usage. And yes, I know that JavaNNS does exist... Any help or hint would be greatly appreciated. Lou ----- Note: one 'h' is more than enough, in my e-mail address (spam prevention) From andrew.markebo@comhem.se Tue Nov 25 11:42:00 2003 From: andrew.markebo@comhem.se (Andrew Markebo) Date: Tue, 25 Nov 2003 11:42:00 -0000 Subject: startx problem on Win-XP In-Reply-To: <200311251057.11859.wolfgang.reichel@teepack.com> (Wolfgang Reichel's message of "Tue, 25 Nov 2003 10:57:11 +0100") References: <200311251057.11859.wolfgang.reichel@teepack.com> Message-ID: If you from a cmd window run startxwin.bat, what is printed out? If you run the startxwin.sh from a cygwin window, what is printed out? What does /tmp/XWin.log contain? /Andy / wolfgang.reichel@teepack.com (Reichel, Wolfgang ) wrote: | Harold , | |>>Reichel, Wolfgang wrote: |>>Hello ! |>>I have installed the newest cygwin-version |>>on my Win-XP box. |>>But i can't start the X-System. |>>It doesn't make any different how i try to start it. |>>I tried the following way... |>>startx 2>/tmp/mistlog | |> Use startxwin.bat instead: |> http://xfree86.cygwin.com/docs/ug/using.html#using-starting-bat |> Harold | | Thanks for your answer. But i tried all ways described in the | docs to start. Nothing works. | | The startxwin.bat runs but nothing happens. | | What can be the reason ? | | Wolfgang | -- The eye of the linker rests on the libs! From huntharo@msu.edu Tue Nov 25 14:15:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Tue, 25 Nov 2003 14:15:00 -0000 Subject: Compiling SNNS (Stuttgart Neural Network Simulator) or using v.4.2 binaries In-Reply-To: <3FC32F7F.4070505@libero.it> References: <3FC32F7F.4070505@libero.it> Message-ID: <3FC363F8.2010308@msu.edu> Lou, Lou Cyphre wrote: > Did anybody recompiled successfully SNNS 4.2 with Cygwin/X? > Its home page is at > http://www-ra.informatik.uni-tuebingen.de/SNNS/ > > I firstly tried using SNNS 4.2 binaries with latest Cygwin/X as > X-server, but something wasn't working in the user interface (couldn't > select some menu list entries), so I decided to get sources at > http://www-ra.informatik.uni-tuebingen.de/downloads/SNNS/SNNSv4.2.tar.gz > and try recompile them. > > Beside a few #define missing (that I properly fixed) seemed that the > configure > script was running fine, infact I can run the application, and now all the > menu lists do work, but... when loading even an example configuration > file I > get syntax errors in file, and after some clicks, trying opening other > windows, crashes. Are you running Cygwin with binary mode mounts or did you change the default to text? Send in the output of the "mount" command run in a Cygwin bash shell. I would suspect that SNNS expects UNIX-style end-of-line characters and would thus be confused by DOS-style end-of-line characters. Poor coding could lead to a crash as well. Harold From wolfgang.reichel@teepack.com Tue Nov 25 14:25:00 2003 From: wolfgang.reichel@teepack.com (Reichel, Wolfgang ) Date: Tue, 25 Nov 2003 14:25:00 -0000 Subject: startx problem on Win-XP Message-ID: <200311251638.34333.wolfgang.reichel@teepack.com> >If you from a cmd window run startxwin.bat, what is printed out? >If you run the startxwin.sh from a cygwin window, what is printed out? >What does /tmp/XWin.log contain? > /Andy Hello Andy! Thanks for you answer. When i run startxwin.bat only "startxwin.bat - Starting on Windows NT/2000/XP/2003" is printed out. When i run startxwin.sh also nothing is printed out. In /tmp/XWin.log i found a lot of messages. 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 0000001f 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 1024 1280 winAdjustForAutoHide - Taskbar is auto hide winAdjustForAutoHide - Found BOTTOM auto-hide taskbar winAdjustForAutoHide - Adjusted WorkArea: 0 0 1023 1280 winCreateBoundingWindowWindowed - WindowClient w 1280 h 1023 r 1280 l 0 b 1023 t 0 winCreateBoundingWindowWindowed - Returning winAllocateFBShadowGDI - Creating DIB with width: 1280 height: 1023 depth: 32 winAllocateFBShadowGDI - Dibsection width: 1280 height: 1023 depth: 32 size image: 5237760 winAllocateFBShadowGDI - Created shadow stride: 1280 winFinishScreenInitFB - Masks: 00ff0000 0000ff00 000000ff winInitVisualsShadowGDI - Masks 00ff0000 0000ff00 000000ff 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 winInitMultiWindowWM - Hello winInitMultiWindowWM - Calling pthread_mutex_lock () winMultiWindowXMsgProc - Hello winMultiWindowXMsgProc - Calling pthread_mutex_lock () InitOutput - Returning. MIT-SHM extension disabled due to lack of kernel support XFree86-Bigfont extension local-client optimization disabled due to lack of shared memory support in the kernel (==) winConfigKeyboard - Layout: "00000407" (00000407) (==) Using preset keyboard for "German (Germany)" (407), type "4" (EE) No primary keyboard configured (==) Using compiletime defaults for keyboard Rules = "xfree86" Model = "pc105" Layout = "de" Variant = "(null)" Options = "(null)" Could not init font path element /usr/X11R6/lib/X11/fonts/misc/, removing from list! Could not init font path element /usr/X11R6/lib/X11/fonts/Speedo/, removing from list! Could not init font path element /usr/X11R6/lib/X11/fonts/Type1/, removing from list! Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing from list! Could not init font path element /usr/X11R6/lib/X11/fonts/75dpi/, removing from list! Could not init font path element /usr/X11R6/lib/X11/fonts/100dpi/, removing from list! Fatal server error: could not open default font 'fixed' winDeinitClipboard - Noting shutdown in progress winDeinitMultiWindowWM - Noting shutdown in progress What do i have to do now ??? Wolfgang From bmj2001@bellsouth.net Tue Nov 25 14:29:00 2003 From: bmj2001@bellsouth.net (Robert McNulty Junior) Date: Tue, 25 Nov 2003 14:29:00 -0000 Subject: startx problem on Win-XP In-Reply-To: <200311251638.34333.wolfgang.reichel@teepack.com> Message-ID: You need to install the fonts. -----Original Message----- From: cygwin-xfree-owner@cygwin.com [mailto:cygwin-xfree-owner@cygwin.com]On Behalf Of Reichel, Wolfgang Sent: Tuesday, November 25, 2003 9:39 AM To: cygwin-xfree@cygwin.com Subject: Re: startx problem on Win-XP >If you from a cmd window run startxwin.bat, what is printed out? >If you run the startxwin.sh from a cygwin window, what is printed out? >What does /tmp/XWin.log contain? > /Andy Hello Andy! Thanks for you answer. When i run startxwin.bat only "startxwin.bat - Starting on Windows NT/2000/XP/2003" is printed out. When i run startxwin.sh also nothing is printed out. In /tmp/XWin.log i found a lot of messages. 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 0000001f 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 1024 1280 winAdjustForAutoHide - Taskbar is auto hide winAdjustForAutoHide - Found BOTTOM auto-hide taskbar winAdjustForAutoHide - Adjusted WorkArea: 0 0 1023 1280 winCreateBoundingWindowWindowed - WindowClient w 1280 h 1023 r 1280 l 0 b 1023 t 0 winCreateBoundingWindowWindowed - Returning winAllocateFBShadowGDI - Creating DIB with width: 1280 height: 1023 depth: 32 winAllocateFBShadowGDI - Dibsection width: 1280 height: 1023 depth: 32 size image: 5237760 winAllocateFBShadowGDI - Created shadow stride: 1280 winFinishScreenInitFB - Masks: 00ff0000 0000ff00 000000ff winInitVisualsShadowGDI - Masks 00ff0000 0000ff00 000000ff 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 winInitMultiWindowWM - Hello winInitMultiWindowWM - Calling pthread_mutex_lock () winMultiWindowXMsgProc - Hello winMultiWindowXMsgProc - Calling pthread_mutex_lock () InitOutput - Returning. MIT-SHM extension disabled due to lack of kernel support XFree86-Bigfont extension local-client optimization disabled due to lack of shared memory support in the kernel (==) winConfigKeyboard - Layout: "00000407" (00000407) (==) Using preset keyboard for "German (Germany)" (407), type "4" (EE) No primary keyboard configured (==) Using compiletime defaults for keyboard Rules = "xfree86" Model = "pc105" Layout = "de" Variant = "(null)" Options = "(null)" Could not init font path element /usr/X11R6/lib/X11/fonts/misc/, removing from list! Could not init font path element /usr/X11R6/lib/X11/fonts/Speedo/, removing from list! Could not init font path element /usr/X11R6/lib/X11/fonts/Type1/, removing from list! Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing from list! Could not init font path element /usr/X11R6/lib/X11/fonts/75dpi/, removing from list! Could not init font path element /usr/X11R6/lib/X11/fonts/100dpi/, removing from list! Fatal server error: could not open default font 'fixed' winDeinitClipboard - Noting shutdown in progress winDeinitMultiWindowWM - Noting shutdown in progress What do i have to do now ??? Wolfgang From huntharo@msu.edu Tue Nov 25 14:33:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Tue, 25 Nov 2003 14:33:00 -0000 Subject: startx problem on Win-XP In-Reply-To: <200311251638.34333.wolfgang.reichel@teepack.com> References: <200311251638.34333.wolfgang.reichel@teepack.com> Message-ID: <3FC36819.8050308@msu.edu> You either have no fonts or they got installed to a strange place. Look at the output of "mount" and see if that points to a valid path on your system. Then run "cygcheck -cd XFree86-fnts" and check that you have at least the XFree86-fnts package. Harold Reichel, Wolfgang wrote: >>If you from a cmd window run startxwin.bat, what is printed out? > > >>If you run the startxwin.sh from a cygwin window, what is printed out? >>What does /tmp/XWin.log contain? > > >> /Andy > > > Hello Andy! > > Thanks for you answer. > > When i run startxwin.bat only > "startxwin.bat - Starting on Windows NT/2000/XP/2003" > is printed out. > > When i run startxwin.sh also nothing is printed out. > > In /tmp/XWin.log i found a lot of messages. > > 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 0000001f > 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 1024 1280 > winAdjustForAutoHide - Taskbar is auto hide > winAdjustForAutoHide - Found BOTTOM auto-hide taskbar > winAdjustForAutoHide - Adjusted WorkArea: 0 0 1023 1280 > winCreateBoundingWindowWindowed - WindowClient w 1280 h 1023 r 1280 l 0 b 1023 > t 0 > winCreateBoundingWindowWindowed - Returning > winAllocateFBShadowGDI - Creating DIB with width: 1280 height: 1023 depth: 32 > winAllocateFBShadowGDI - Dibsection width: 1280 height: 1023 depth: 32 size > image: 5237760 > winAllocateFBShadowGDI - Created shadow stride: 1280 > winFinishScreenInitFB - Masks: 00ff0000 0000ff00 000000ff > winInitVisualsShadowGDI - Masks 00ff0000 0000ff00 000000ff 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 > winInitMultiWindowWM - Hello > winInitMultiWindowWM - Calling pthread_mutex_lock () > winMultiWindowXMsgProc - Hello > winMultiWindowXMsgProc - Calling pthread_mutex_lock () > InitOutput - Returning. > MIT-SHM extension disabled due to lack of kernel support > XFree86-Bigfont extension local-client optimization disabled due to lack of > shared memory support in the kernel > (==) winConfigKeyboard - Layout: "00000407" (00000407) > (==) Using preset keyboard for "German (Germany)" (407), type "4" > (EE) No primary keyboard configured > (==) Using compiletime defaults for keyboard > Rules = "xfree86" Model = "pc105" Layout = "de" Variant = "(null)" Options = > "(null)" > Could not init font path element /usr/X11R6/lib/X11/fonts/misc/, removing from > list! > Could not init font path element /usr/X11R6/lib/X11/fonts/Speedo/, removing > from list! > Could not init font path element /usr/X11R6/lib/X11/fonts/Type1/, removing > from list! > Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing from > list! > Could not init font path element /usr/X11R6/lib/X11/fonts/75dpi/, removing > from list! > Could not init font path element /usr/X11R6/lib/X11/fonts/100dpi/, removing > from list! > > Fatal server error: > could not open default font 'fixed' > winDeinitClipboard - Noting shutdown in progress > winDeinitMultiWindowWM - Noting shutdown in progress > > > What do i have to do now ??? > > Wolfgang > > From sb@dod.no Tue Nov 25 14:49:00 2003 From: sb@dod.no (Steinar Bang) Date: Tue, 25 Nov 2003 14:49:00 -0000 Subject: Alt key isn't Meta in Cygwin xterm (Norwegian keyboard) References: <87llqktqn1.fsf@home.lan> <87k75yt375.fsf@home.lan> <3FBA2442.8060206@juntadeandalucia.es> Message-ID: <87ekvw33nq.fsf@home.lan> >>>>> Hans Dekker : > Change to es file: > key { type[Group1]="TWO_LEVEL", > [ Mode_switch, Multi_key ] }; > modifier_map Mod5 { }; The no file looks like this: key { type[Group1]="TWO_LEVEL", [ ISO_Level3_Shift, Multi_key ] }; modifier_map Mod5 { }; But I'm not sure how this applies to the left Alt not being taken as meta in xterm? I'd guess it had something to do with keycaps rather than X keysym mappings, since Alt works fine as Meta in Emacs...? From jch@honig.net Tue Nov 25 15:18:00 2003 From: jch@honig.net (Jeffrey C Honig) Date: Tue, 25 Nov 2003 15:18:00 -0000 Subject: How to get my auto repeat back? In-Reply-To: Message from Jeffrey C Honig on Sun, 23 Nov 2003 12:57:50 -0500. Message-ID: <200311251518.hAPFIjD20749@escapade.honig.net> -25 has fixed autorepeat for me. Thanks to everyone! Thanks. Jeff -- Jeffrey C. Honig http://www.honig.net/jch GnuPG ID:14E29E13 From Ralf.Habacker@freenet.de Tue Nov 25 16:32:00 2003 From: Ralf.Habacker@freenet.de (Ralf Habacker) Date: Tue, 25 Nov 2003 16:32:00 -0000 Subject: QT 3.2.3 cygwin/XFree release available Message-ID: Hi all, today the cygwin/XFree port of the QT 3.2.3 X11 release based on the recent cygwin release is ready containing binary and source package. For further informations about this release see http://www.trolltech.com/newsroom/announcements/00000147.html For further informations about the cygwin/XFree port see http://kde-cygwin.sf.net/qt3/ Download Resources - binary package http://prdownloads.sourceforge.net/kde-cygwin/qt-3.2.3.tar.bz2?download - source package http://prdownloads.sourceforge.net/kde-cygwin/qt-3.2.3-src.tar.bz2?download Have fun The kde-cygwin team From loucyphhre@libero.it Tue Nov 25 17:22:00 2003 From: loucyphhre@libero.it (Lou Cyphre) Date: Tue, 25 Nov 2003 17:22:00 -0000 Subject: Compiling SNNS (Stuttgart Neural Network Simulator) or usingv.4.2 binaries Message-ID: <3FC38FE1.2050502@libero.it> Answering to Harold: my system is mounted in binary mode. Anyway that doesn't seem to be the cause for that crash: looks like that the first operation done in floating point (so I suspect) brings the application in an unstable state -- after reading the file that causes the syntax error I can still do other tasks in the user interface, "for a while". I'm sorry to be so approximative about this issue: the program itself is quite large, to investigate. What I hoped was to find someone who did it already, to "steal" his/her experience on this... while maybe I will have to manage it myself, unless not switching to the Java version of SNNS. Thanks again for reading and helping. Lou From huntharo@msu.edu Tue Nov 25 17:44:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Tue, 25 Nov 2003 17:44:00 -0000 Subject: Compiling SNNS (Stuttgart Neural Network Simulator) or usingv.4.2 binaries In-Reply-To: <3FC38FE1.2050502@libero.it> References: <3FC38FE1.2050502@libero.it> Message-ID: <3FC39502.7060901@msu.edu> Nevermind... that was a silly question. Harold Lou Cyphre wrote: > Answering to Harold: my system is mounted in binary mode. > Anyway that doesn't seem to be the cause for that crash: looks like that > the first operation done in floating point (so I suspect) brings the > application in an unstable state -- after reading the file that causes > the syntax error I can still do other tasks in the user interface, "for > a while". > > I'm sorry to be so approximative about this issue: the program itself is > quite large, to investigate. > What I hoped was to find someone who did it already, to "steal" his/her > experience on this... while maybe I will have to manage it myself, > unless not switching to the Java version of SNNS. > Thanks again for reading and helping. > > Lou > From huntharo@msu.edu Tue Nov 25 17:44:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Tue, 25 Nov 2003 17:44:00 -0000 Subject: Compiling SNNS (Stuttgart Neural Network Simulator) or usingv.4.2 binaries In-Reply-To: <3FC38FE1.2050502@libero.it> References: <3FC38FE1.2050502@libero.it> Message-ID: <3FC394EC.7020100@msu.edu> Is SNNS in anyway related to ns-2? Harold Lou Cyphre wrote: > Answering to Harold: my system is mounted in binary mode. > Anyway that doesn't seem to be the cause for that crash: looks like that > the first operation done in floating point (so I suspect) brings the > application in an unstable state -- after reading the file that causes > the syntax error I can still do other tasks in the user interface, "for > a while". > > I'm sorry to be so approximative about this issue: the program itself is > quite large, to investigate. > What I hoped was to find someone who did it already, to "steal" his/her > experience on this... while maybe I will have to manage it myself, > unless not switching to the Java version of SNNS. > Thanks again for reading and helping. > > Lou > From ford@vss.fsi.com Tue Nov 25 18:26:00 2003 From: ford@vss.fsi.com (Brian Ford) Date: Tue, 25 Nov 2003 18:26:00 -0000 Subject: DDD needs a porter [Was: DDD 3.3.8 segmentation error, related to Motif?] In-Reply-To: <3FC15FEC.10006@msu.edu> References: <3FC14C97.E9D22F22@doe.carleton.ca> <3FC15FEC.10006@msu.edu> Message-ID: I was going to try to look into this, but I stumbled early on and don't want to waste my time on known issues. Given that those involved in this thread seem to have gotten much further, I thought I'd ask if there is a known quick solution. Thanks. ddd-3.3.8: bash ./configure make gives: Making all in libiberty make[1]: *** No rule to make target `../include/xregex.h', needed by `regex.o'. Stop. -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444 From ats@acm.org Tue Nov 25 18:39:00 2003 From: ats@acm.org (Alan Shutko) Date: Tue, 25 Nov 2003 18:39:00 -0000 Subject: Problem with WinXP, XF86, Caps lock, xterm and cursor keys References: <874qwtilv2.fsf@wesley.springies.com> Message-ID: <873cccmrha.fsf@wesley.springies.com> Alexander Gottwald writes: > Cygwin/XFree uses raw scancodes and uses XKB for symbol translation. > Your tweaking will most likely break this conversion. I could understand that, if it were consistent. If Cygwin/XFree considered that key to still be caps lock, I could easily fix it with xmodmap. But it doesn't, xev sees it as control. Furthermore, why is it shifting arrow keys and page up/down but not anything else? Finally, why is caps lock affecting those keys at all? I haven't seen that on XFree86 on Linux, nor on any other X server I've tried. Personally, I suspect that some piece of code is handling things differently than the rest, so even the usual methods of fixing things (ie, xresources, xmodmap) may not fix things. (But I'll be giving it a try, since it's easy.) > I declare such a modification as unsupported. You may still ask for > pointers to documentation I'll take you up on that offer. Could you point me to some info on how Cygwin/XFree86 gets those scancodes and runs the conversion? Maybe I could put together a variant XKB layout without caps lock.... -- Alan Shutko - I am the rocks. St. Vidicon of Cathode, pray for us! From huntharo@msu.edu Tue Nov 25 18:45:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Tue, 25 Nov 2003 18:45:00 -0000 Subject: Problem with WinXP, XF86, Caps lock, xterm and cursor keys In-Reply-To: <873cccmrha.fsf@wesley.springies.com> References: <874qwtilv2.fsf@wesley.springies.com> <873cccmrha.fsf@wesley.springies.com> Message-ID: <3FC3A35E.9070909@msu.edu> The only special handling that I can think of is here: Look at the section after the following line (WIN_NEW_KEYBOARD_SUPPORT is set to NO): #else /* WIN_NEW_KEYBOARD_SUPPORT */ But that code just maps scan codes depending on whether or not the key is flagged as "extended", which sort of distinquishes the normal arrow keys from the keypad arrow keys, etc. You see, we don't do this sort of translation on our own. It may be that Windows is sending different codes when CapsLock is down, in which case we might want to translate those different codes to match the normal codes. Does that make sense? Harold Alan Shutko wrote: > Alexander Gottwald writes: > > >>Cygwin/XFree uses raw scancodes and uses XKB for symbol translation. >>Your tweaking will most likely break this conversion. > > > I could understand that, if it were consistent. If Cygwin/XFree > considered that key to still be caps lock, I could easily fix it with > xmodmap. But it doesn't, xev sees it as control. Furthermore, why is > it shifting arrow keys and page up/down but not anything else? > > Finally, why is caps lock affecting those keys at all? I haven't seen > that on XFree86 on Linux, nor on any other X server I've tried. > Personally, I suspect that some piece of code is handling things > differently than the rest, so even the usual methods of fixing things > (ie, xresources, xmodmap) may not fix things. (But I'll be giving it > a try, since it's easy.) > > >>I declare such a modification as unsupported. You may still ask for >>pointers to documentation > > > I'll take you up on that offer. Could you point me to some > info on how Cygwin/XFree86 gets those scancodes and runs the > conversion? Maybe I could put together a variant XKB layout without > caps lock.... > From ats@acm.org Tue Nov 25 18:55:00 2003 From: ats@acm.org (Alan Shutko) Date: Tue, 25 Nov 2003 18:55:00 -0000 Subject: Problem with WinXP, XF86, Caps lock, xterm and cursor keys References: <874qwtilv2.fsf@wesley.springies.com> <873cccmrha.fsf@wesley.springies.com> Message-ID: <877k1oi8ul.fsf@wesley.springies.com> Alan Shutko writes: > Personally, I suspect that some piece of code is handling things > differently than the rest, so even the usual methods of fixing things > (ie, xresources, xmodmap) may not fix things. (But I'll be giving it > a try, since it's easy.) I'm able to use X resources to have xterm treat Shift-cursor the same as (application) cursor keys. I also discovered that xev is showing a Shift_L keydown before hitting the affected keys. I haven't tried turning caps lock off with xkb yet. Is there a tool lower-level than xev which shows what XF86 is getting from Windows? -- Alan Shutko - I am the rocks. From huntharo@msu.edu Tue Nov 25 19:04:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Tue, 25 Nov 2003 19:04:00 -0000 Subject: Problem with WinXP, XF86, Caps lock, xterm and cursor keys In-Reply-To: <877k1oi8ul.fsf@wesley.springies.com> References: <874qwtilv2.fsf@wesley.springies.com> <873cccmrha.fsf@wesley.springies.com> <877k1oi8ul.fsf@wesley.springies.com> Message-ID: <3FC3A7CF.8010003@msu.edu> Have you got Spy++ from any version of Visual Studio? It will show you keyboard messages and you can check if the field that we check is changing depending on whether Caps Lock is down or not. Harold Alan Shutko wrote: > Alan Shutko writes: > > >>Personally, I suspect that some piece of code is handling things >>differently than the rest, so even the usual methods of fixing things >>(ie, xresources, xmodmap) may not fix things. (But I'll be giving it >>a try, since it's easy.) > > > I'm able to use X resources to have xterm treat Shift-cursor the same > as (application) cursor keys. I also discovered that xev is showing > a Shift_L keydown before hitting the affected keys. I haven't tried > turning caps lock off with xkb yet. > > Is there a tool lower-level than xev which shows what XF86 is getting > from Windows? > From ats@acm.org Tue Nov 25 21:10:00 2003 From: ats@acm.org (Alan Shutko) Date: Tue, 25 Nov 2003 21:10:00 -0000 Subject: Problem with WinXP, XF86, Caps lock, xterm and cursor keys References: <874qwtilv2.fsf@wesley.springies.com> <873cccmrha.fsf@wesley.springies.com> <3FC3A35E.9070909@msu.edu> Message-ID: <87d6bggom5.fsf@wesley.springies.com> Harold L Hunt II writes: > You see, we don't do this sort of translation on our own. It may be > that Windows is sending different codes when CapsLock is down, in > which case we might want to translate those different codes to match > the normal codes. Does that make sense? Makes sense. Unfortunately, I don't have Spy++, but I'll keep working on it.... -- Alan Shutko - I am the rocks. "Let the carnage begin!" - Larry From hzhou@lbl.gov Wed Nov 26 00:07:00 2003 From: hzhou@lbl.gov (Hong Zhou) Date: Wed, 26 Nov 2003 00:07:00 -0000 Subject: in xemacs or emacs the highlight disappeared, problems related to clipboard Message-ID: <3FC3EED3.1010503@lbl.gov> Dear All, I use cygwin/Xserver on my win2000 as multiwindow mode. It is a great work. I have two problems. 1. )It is good to copy between windows and X programs, so I start the Xserver with the parameter '-clipborad'. When press the left button of mouse to highlight a region and release the button the highlight disappeared automatically. And in the xemacs(emacs)mini window shows a message "mark set". The normal response should keep the highligh. Start the Xserver without the parameter '-clipboard', xemacs works normally. 2.)I have a dictionary program to pick up the words in the sreen. After I start local emacs in the cygwin shell , the program can't pick up any word.. I thought it was the clipboard 's bug, wasn't it? Thank you very much, Hong From huntharo@msu.edu Wed Nov 26 00:10:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Wed, 26 Nov 2003 00:10:00 -0000 Subject: in xemacs or emacs the highlight disappeared, problems related to clipboard In-Reply-To: <3FC3EED3.1010503@lbl.gov> References: <3FC3EED3.1010503@lbl.gov> Message-ID: <3FC3EF75.2080207@msu.edu> That is by design. Search the archives if you want to know why. Hong Zhou wrote: > Dear All, > > I use cygwin/Xserver on my win2000 as multiwindow mode. It is a great > work. I have two problems. > 1. )It is good to copy between windows and X programs, so I start the > Xserver with the parameter '-clipborad'. When press the left button of > mouse to highlight a region and release the button the highlight > disappeared automatically. And in the xemacs(emacs)mini window shows a > message "mark set". The normal response should keep the highligh. Start > the Xserver without the parameter '-clipboard', xemacs works normally. > 2.)I have a dictionary program to pick up the words in the sreen. After > I start local emacs in the cygwin shell , the program can't pick up any > word.. > > I thought it was the clipboard 's bug, wasn't it? > > Thank you very much, > Hong > From murakami@ipl.t.u-tokyo.ac.jp Wed Nov 26 04:21:00 2003 From: murakami@ipl.t.u-tokyo.ac.jp (Takuma Murakami) Date: Wed, 26 Nov 2003 04:21:00 -0000 Subject: Problem with WinXP, XF86, Caps lock, xterm and cursor keys In-Reply-To: <874qwtilv2.fsf@wesley.springies.com> References: <874qwtilv2.fsf@wesley.springies.com> Message-ID: <20031126125506.395D.MURAKAMI@ipl.t.u-tokyo.ac.jp> Alan Shutko wrote: > I've disabled my capslock key and turned it into a control key with > this registry hack: For your information, I am using the same scancode map on a system. The system is JP Windows, US keyboard, XKB enabled, no XF86Config file, and "setxkbmap -print" prints: xkb_keymap { xkb_keycodes { include "xfree86+aliases(qwerty)" }; xkb_types { include "complete" }; xkb_compat { include "complete" }; xkb_symbols { include "pc/pc(pc101)+pc/us" }; xkb_geometry { include "pc(pc101)" }; }; I can't reproduce your problems on this system. Ideally speaking, changes of Windows scancode mapper are invisible from Cygwin/X. Because scancodes are the only information Cygwin/X uses, your Caps Lock key and Control key should be completely equivalent for Cygwin/X. I hope you track down your problem. Takuma Murakami (murakami@ipl.t.u-tokyo.ac.jp) From Konrad.Bogner@lfw.bayern.de Wed Nov 26 10:02:00 2003 From: Konrad.Bogner@lfw.bayern.de (Bogner, Konrad) Date: Wed, 26 Nov 2003 10:02:00 -0000 Subject: Alt-Gr problem Message-ID: <939BA0DC181DD511AEA200E018CE50BE013F3BAB@s1470a08.lfw.umwelt.bayern.de> Hello, I've a big problem with my german keyboard setting. I'm using cygwin on an WinXP machine (Toshiba Satellite Notebook) and the Alt-Gr key doesnot work most of the time, although sometimes it works (that's the strange thing). I've tried all the advices that have been reported here, but I still didn't find a solution. When I start Cygwin without xfree the keyboard setting is o.k. But when I start a window manager (icewm, twm,..) the Alt-Gr key is not well defined. I've tried changes in the Xmodmap, XFConfig (xkb disabled) used xev, etc. ..Is this a problem of the Toshiba notebook? I've installed cygwin on different PC's with the german keyboard and with different Systems (Win NT, 2000, XP) and it worked quite well everywere else? Thank you very much for your advices! Konrad From skeeter_mon@yahoo.com Wed Nov 26 12:01:00 2003 From: skeeter_mon@yahoo.com (Skeeter) Date: Wed, 26 Nov 2003 12:01:00 -0000 Subject: Problem compiling Lesstif programs on latest Cygwin Message-ID: <20031126120122.102.qmail@web20813.mail.yahoo.com> Although I have been compiling and running Lesstif programs on Cygwin successfully for the past year, something in the latest Cygwin package seems to have broken my ability to compile/link(?) new programs. (I can still run previously compiled X/lestif programs.) The source code of some of my programs has not changed in years, and has compiled unchanged on many platforms, including, Sun, Linux, HP, SGI, and previous Cygwin distros, so I did not suspect a 'recent' bug on my part. At first I suspected Lesstif has become more strict or fragile to a possibly-bad or archaic construct that I use. However, I have now tested it on the simplest program fragments from my Motif text-book, and I realize that I cannot run any newly compiled X/lesstif program, no matter how simple. Below I show the error messages and include my simple test program. Any help/suggestions appreciated! Thanks --Skeet -------- $ gcc -I/usr/X11R6/include -L/usr/X11R6/lib memo_1.c -lXm -lXt -lX11 -o memo_1 Info: resolving _XtStrings by linking to __imp__XtStrings (auto-import) Info: resolving __XtInherit by linking to __imp___XtInherit (auto-import) Info: resolving __XtInheritTranslations by linking to __imp___XtInheritTranslations (auto-import) Info: resolving _XtShellStrings by linking to __imp__XtShellStrings (auto-import) ... Info: resolving _overrideShellClassRec by linking to __imp__overrideShellClassRec (auto-import) Info: resolving _transientShellClassRec by linking to __imp__transientShellClassRec (auto-import) $ memo_1 test Warning: XmPrimitive ClassInitialize: XmeTraitSet failed Error: attempt to add non-widget child "DropSiteManager" to parent "memo_1" which supports only widgets ------- Program Source: memo_1.c /* Memo.c - Display a message in an X window. */ #include #include #include #include main( int argc, char *argv[] ) { Widget toplevel, msg_widget; Arg wargs[10]; XmString message; /* Initialize the intrinsics. */ toplevel = XtInitialize(argv[0], "Memo", NULL, 0, &argc, argv); /* Create the Label Widget. */ message = XmStringCreate("Test Message", XmSTRING_DEFAULT_CHARSET); XtSetArg( wargs[0], XmNlabelString, message); msg_widget = XtCreateManagedWidget("msg", xmLabelWidgetClass, toplevel, wargs, 1); /* Realize the widgets and enter the event loop. */ XtRealizeWidget( toplevel ); XtMainLoop(); } ----- __________________________________ Do you Yahoo!? Protect your identity with Yahoo! Mail AddressGuard http://antispam.yahoo.com/whatsnewfree From skeeter_mon@yahoo.com Wed Nov 26 12:07:00 2003 From: skeeter_mon@yahoo.com (Skeeter) Date: Wed, 26 Nov 2003 12:07:00 -0000 Subject: Problem compiling Lesstif programs on latest Cygwin In-Reply-To: <20031126120122.102.qmail@web20813.mail.yahoo.com> Message-ID: <20031126120737.98354.qmail@web20801.mail.yahoo.com> PS - I also tried adding the -lSM and -lICE link options, and tried all suggested combinations of ordering them, but same run-time failure results. Example: $ gcc -I/usr/X11R6/include -L/usr/X11R6/lib memo_1.c \ -lXm -lXt -lX11 -lSM -lICE -o memo_1 Thanks, --Skeet --- Skeeter wrote: > Although I have been compiling and running Lesstif > programs on Cygwin successfully for the past year, > something in the latest Cygwin package seems to have > broken my ability to compile/link(?) new programs. > ... __________________________________ Do you Yahoo!? Free Pop-Up Blocker - Get it now http://companion.yahoo.com/ From V.Khamenia@biovision-discovery.de Wed Nov 26 12:52:00 2003 From: V.Khamenia@biovision-discovery.de (Khamenia, Valery) Date: Wed, 26 Nov 2003 12:52:00 -0000 Subject: problems with refresh rate of Xwin at win2000prof Message-ID: Hi Dear All, Problem 1: The refresh rate of my Xwin is too low. I run Xwin at my Win2000prof. The PC is good enough (Pentium 1.7GHz, 100Mbits/s Ethernet) I run kde remotely at PC with Linux and redirect displaying to my Win2000prof where Xwin is running. The refresh rate I get is about 1Hz :( Problem 2: Starting Xwin with "-refreshrate 25" (also with other integral parameters) causes Xwin to exit. Any hints? Thank you. P.S. RTFMed, STFWed, but maybe missed something P.P.S. Thanks in advance for Cc'ing answers directly to me! kind regards, Valery A.Khamenya --------------------------------------------------------------------------- Bioinformatics Department BioVisioN AG, Hannover From pavelr@coresma.com Wed Nov 26 13:17:00 2003 From: pavelr@coresma.com (Pavel Rosenboim) Date: Wed, 26 Nov 2003 13:17:00 -0000 Subject: problems with refresh rate of Xwin at win2000prof In-Reply-To: References: Message-ID: <3FC4A7C9.1070702@coresma.com> Khamenia, Valery wrote: > Hi Dear All, > > Problem 1: > The refresh rate of my Xwin is too low. > I run Xwin at my Win2000prof. > The PC is good enough (Pentium 1.7GHz, 100Mbits/s Ethernet) > I run kde remotely at PC with Linux and redirect displaying to > my Win2000prof where Xwin is running. > The refresh rate I get is about 1Hz :( How do you measure your refresh rate? I never seen a monitor that worked with vertical refresh rate of 1Hz. > > Problem 2: > Starting Xwin with "-refreshrate 25" (also with other integral > parameters) causes Xwin to exit. According to man XWin, the correct option is -refresh. Which is valid when you run in fullscreen mode with DirectDraw engine. You should try to run XWin -refresh xx -engine 4 -fullscreen. Also, I don't think 25Hz is a valid refresh rate for any monitor. Pavel. From V.Khamenia@biovision-discovery.de Wed Nov 26 13:30:00 2003 From: V.Khamenia@biovision-discovery.de (Khamenia, Valery) Date: Wed, 26 Nov 2003 13:30:00 -0000 Subject: problems with refresh rate of Xwin at win2000prof Message-ID: > How do you measure your refresh rate? 1Hz refresh rate one could measure by eye :) > I never seen a monitor that worked with vertical refresh rate of 1Hz. I do not speak about vertical refresh rate of monitor. I mean refresh rate of Xwin itself > According to man XWin, the correct option is -refresh. you are right. It was just a typo in my email. I've used "-refresh" of course. > Which is valid when you run in fullscreen mode with DirectDraw engine. I have used fullscreen mode. is DirectDraw specified by -engine 4? > You should try to run XWin -refresh xx -engine 4 -fullscreen. the same. Exited :( > Also, I don't think 25Hz is a valid refresh rate for any monitor. well I see, probably "-refresh" *does* have something to do with vertical refresh rate. Indeed, i've tried 75Hz and it doesn't exit! Then my questions are: 1. why repainting rate is so low? e.g., 2. how could I get quicker redraw of the window while dragging it? (I do not immediatelly believe that it is a Ethernet card latency problem) kind regards, Valery A.Khamenya --------------------------------------------------------------------------- Bioinformatics Department BioVisioN AG, Hannover From dirk.goethals@alcatel.be Wed Nov 26 13:46:00 2003 From: dirk.goethals@alcatel.be (dirk.goethals@alcatel.be) Date: Wed, 26 Nov 2003 13:46:00 -0000 Subject: DDD needs a porter [Was: DDD 3.3.8 segmentation error, relatedto Motif?] Message-ID: <3FC4AEA5.3030004@alcatel.be> At a certain point I had a simular problem and solved it as follow: - start Setup.exe (used a more up to date mirror: ftp://ftp.easynet.be/cygwin) - under all: select re-install - under dev: select gcc 3.2-3 - I removed my local copy of ddd.3.3.8 - unzipped everything form ddd.3.3.8 - under bash: ./configure - under bash: make - under bash: make check Result: still problems with Motif? bash-2.05b$ make check Making check in themes make[1]: Entering directory `/d/GnuTools/ddd-3.3.8/themes' make[1]: Nothing to be done for `check'. make[1]: Leaving directory `/d/GnuTools/ddd-3.3.8/themes' Making check in vsllib make[1]: Entering directory `/d/GnuTools/ddd-3.3.8/vsllib' make[1]: Nothing to be done for `check'. make[1]: Leaving directory `/d/GnuTools/ddd-3.3.8/vsllib' Making check in ddd make[1]: Entering directory `/d/GnuTools/ddd-3.3.8/ddd' MALLOC_CHECK_=2 \ DDD_HOME=./.. \ XUSERFILESEARCHPATH=%N XAPPLRESDIR=. \ ./ddd.exe cxxtest.exe Warning: This DDD requires a Motif 2.1 library (using Motif -1617156.-609) Continue at own risk. Warning: No type converter registered for 'String' to 'Orientation' conversion. Warning: No type converter registered for 'String' to 'Orientation' conversion. Warning: No type converter registered for 'String' to 'Orientation' conversion. Internal error (Segmentation fault). Oops! You have found a bug in DDD. If you can reproduce this bug, please send a bug report to , giving a subject like DDD 3.3.8 (i686-pc-cygwin) gets `Segmentation fault' signal To enable us to fix the bug, you should include the following information: * What you were doing to get this message. Report all the facts. * The contents of the `~/.ddd/log' file as generated by this session. Please read also the section "Reporting Bugs" in the DDD manual. We thank you for your support. make[1]: *** [check-now] Interrupt make: *** [check-recursive] Interrupt > Re: DDD needs a porter [Was: DDD 3.3.8 segmentation error, relatedto > Motif?] > > * From: Brian Ford > * To: cygwin-xfree at cygwin dot com > * Date: Tue, 25 Nov 2003 12:26:50 -0600 (CST) > * Subject: Re: DDD needs a porter [Was: DDD 3.3.8 segmentation > error, relatedto Motif?] > * References: <3FC14C97.E9D22F22@doe.carleton.ca > > > <3FC15FEC.10006@msu.edu > > > * Reply-to: cygwin-xfree at cygwin dot com > > ------------------------------------------------------------------------ > >I was going to try to look into this, but I stumbled early on and don't >want to waste my time on known issues. Given that those involved in this >thread seem to have gotten much further, I thought I'd ask if there is a >known quick solution. Thanks. > >ddd-3.3.8: >bash ./configure >make gives: > >Making all in libiberty >make[1]: *** No rule to make target `../include/xregex.h', needed by >`regex.o'. Stop. > >-- >Brian Ford >Senior Realtime Software Engineer >VITAL - Visual Simulation Systems >FlightSafety International >Phone: 314-551-8460 >Fax: 314-551-8444 > > From ford@vss.fsi.com Wed Nov 26 16:30:00 2003 From: ford@vss.fsi.com (Brian Ford) Date: Wed, 26 Nov 2003 16:30:00 -0000 Subject: Problem compiling Lesstif programs on latest Cygwin In-Reply-To: <20031126120122.102.qmail@web20813.mail.yahoo.com> References: <20031126120122.102.qmail@web20813.mail.yahoo.com> Message-ID: On Wed, 26 Nov 2003, Skeeter wrote: > Although I have been compiling and running Lesstif > programs on Cygwin successfully for the past year, > something in the latest Cygwin package seems to have > broken my ability to compile/link(?) new programs. > (I can still run previously compiled X/lestif > programs.) > Yes. It was the transition to a shared Xm/Xt, but you do NOT have the latest Cygwin packages of those if you are seeing the following error. You might need to choose a different mirror site. Please see this thread and search the archives before posting. Thanks. Additional comments follow. > $ gcc -I/usr/X11R6/include -L/usr/X11R6/lib memo_1.c > -lXm -lXt -lX11 -o memo_1 > Info: resolving _XtStrings by linking to > __imp__XtStrings (auto-import) > Info: resolving __XtInherit by linking to > __imp___XtInherit (auto-import) > Info: resolving __XtInheritTranslations by linking to > __imp___XtInheritTranslations (auto-import) > Info: resolving _XtShellStrings by linking to > __imp__XtShellStrings (auto-import) > ... > Info: resolving _overrideShellClassRec by linking to > __imp__overrideShellClassRec (auto-import) > Info: resolving _transientShellClassRec by linking to > __imp__transientShellClassRec (auto-import) > These are info messages, so they are not really errors. Can someone explain how we should fix these? I gather it is a mundane search and replace type task, but I haven't had time to look deeply at it. This is the error that indicates your lesstif/XFree86 packages are out of data: > $ memo_1 test > Warning: XmPrimitive ClassInitialize: XmeTraitSet > failed > Error: attempt to add non-widget child > "DropSiteManager" to parent "memo_1" which supports > only widgets > -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444 From ford@vss.fsi.com Wed Nov 26 16:35:00 2003 From: ford@vss.fsi.com (Brian Ford) Date: Wed, 26 Nov 2003 16:35:00 -0000 Subject: Problem compiling Lesstif programs on latest Cygwin In-Reply-To: References: <20031126120122.102.qmail@web20813.mail.yahoo.com> Message-ID: On Wed, 26 Nov 2003, Brian Ford wrote: > Please see this thread and search the archives before posting. Thanks. > Sorry, I forgot the thread reference. http://www.cygwin.com/ml/cygwin-xfree/2003-11/msg00219.html -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444 From ford@vss.fsi.com Wed Nov 26 16:55:00 2003 From: ford@vss.fsi.com (Brian Ford) Date: Wed, 26 Nov 2003 16:55:00 -0000 Subject: DDD needs a porter [Was: DDD 3.3.8 segmentation error, relatedto Motif?] In-Reply-To: <3FC4AEA5.3030004@alcatel.be> References: <3FC4AEA5.3030004@alcatel.be> Message-ID: On Wed, 26 Nov 2003 dirk.goethals@alcatel.be wrote: > At a certain point I had a simular problem and solved it as follow: > - start Setup.exe > (used a more up to date mirror: ftp://ftp.easynet.be/cygwin) > I do believe my mirror is fine, and I am up to date. > - under all: select re-install > - under dev: select gcc 3.2-3 > I will NOT revert my gcc to 3.2. If it can not be done with the current gcc, then it is not worth fixing. Also, this should have nothing to do with the error I received. > - I removed my local copy of ddd.3.3.8 > - unzipped everything form ddd.3.3.8 > - under bash: ./configure > - under bash: make > - under bash: make check > I have done this many times without a change in symptom. > Result: still problems with Motif? > I don't doubt it. You are using old buggy software to compile/link with. Either use current stuff, or don't expect support. I will get back to this if/when I have time. But to the casual glance, my problem appears to be missing include files for libiberty in ddd (ie, a ddd bug). -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444 From richard.campbell@air2web.com Wed Nov 26 17:00:00 2003 From: richard.campbell@air2web.com (Richard Campbell) Date: Wed, 26 Nov 2003 17:00:00 -0000 Subject: DDD needs a porter [Was: DDD 3.3.8 segmentation error, relate dto Motif?] Message-ID: >I will get back to this if/when I have time. But to the casual >glance, my problem appears to be missing include files for libiberty >in ddd (ie, a ddd bug). There is at least one other problem. I tried with ddd 3.3.8 (latest everything, as far as I can tell, certainly gcc 3.3), and got the same missing xregex include errors for libiberty. I tried with ddd 3.3.7, and got an ld error at the very end of the make routine. I'm going to look at it again, but I'm traveling until Monday. -Richard Campbell. From huntharo@msu.edu Wed Nov 26 21:26:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Wed, 26 Nov 2003 21:26:00 -0000 Subject: problems with refresh rate of Xwin at win2000prof In-Reply-To: References: Message-ID: <3FC51A67.3060104@msu.edu> The repainting might be slow for the two following reasons: 1) You have a video card that has a problem with its DirectDraw driver (e.g. ATI All-In-Wonder 8500 DV). Try using "-engine 1" to use the GDI driver and see if it is much faster. If it is, then you will have all sorts of fun testing the various drivers for your video card to see which one fixes the DirectDraw bug. Note that "-engine 4" is not required because the DirectDraw engine is the default engine if DirectDraw is supported by your system. You will only need "-engine 1" to force XWin.exe to use the GDI engine instead of the DirectDraw engine. 2) You have network latency issues. Sure, 100BaseT, yada yada yada, but if you have not tried another X Server on Windows then you have nothing to compare the performance of XWin.exe to and we cannot tell if your network is part of the problem or not. Hope that helps, Harold Khamenia, Valery wrote: >>How do you measure your refresh rate? > > > 1Hz refresh rate one could measure by eye :) > > >>I never seen a monitor that worked with vertical refresh rate of 1Hz. > > > I do not speak about vertical refresh rate of monitor. > I mean refresh rate of Xwin itself > > > >>According to man XWin, the correct option is -refresh. > > > you are right. It was just a typo in my email. > I've used "-refresh" of course. > > >>Which is valid when you run in fullscreen mode with DirectDraw engine. > > > I have used fullscreen mode. > > is DirectDraw specified by -engine 4? > > >>You should try to run XWin -refresh xx -engine 4 -fullscreen. > > > the same. Exited :( > > >>Also, I don't think 25Hz is a valid refresh rate for any monitor. > > > well I see, probably "-refresh" *does* have something to do with vertical > refresh rate. > > Indeed, i've tried 75Hz and it doesn't exit! > > Then my questions are: > > 1. why repainting rate is so low? > > e.g., > > 2. how could I get quicker redraw of the window while dragging it? > (I do not immediatelly believe that it is a Ethernet card latency problem) > > kind regards, > Valery A.Khamenya > --------------------------------------------------------------------------- > Bioinformatics Department > BioVisioN AG, Hannover > From huntharo@msu.edu Wed Nov 26 21:26:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Wed, 26 Nov 2003 21:26:00 -0000 Subject: problems with refresh rate of Xwin at win2000prof In-Reply-To: References: Message-ID: <3FC51A8B.1080306@msu.edu> Oh yeah, don't use "-refresh n", that has nothing to do with this problem and only confuses things further. Harold Khamenia, Valery wrote: > Hi Dear All, > > Problem 1: > The refresh rate of my Xwin is too low. > I run Xwin at my Win2000prof. > The PC is good enough (Pentium 1.7GHz, 100Mbits/s Ethernet) > I run kde remotely at PC with Linux and redirect displaying to > my Win2000prof where Xwin is running. > The refresh rate I get is about 1Hz :( > > Problem 2: > Starting Xwin with "-refreshrate 25" (also with other integral > parameters) causes Xwin to exit. > > Any hints? > > Thank you. > > P.S. RTFMed, STFWed, but maybe missed something > > P.P.S. Thanks in advance for Cc'ing answers directly to me! > > kind regards, > Valery A.Khamenya > --------------------------------------------------------------------------- > Bioinformatics Department > BioVisioN AG, Hannover > From the.unchallenged@gmx.de Wed Nov 26 21:41:00 2003 From: the.unchallenged@gmx.de (Oliver Brandt) Date: Wed, 26 Nov 2003 21:41:00 -0000 Subject: =?ISO-8859-1?Q?Can=B4t_open_remote-X-Apps_on_my_local_?= =?ISO-8859-1?Q?windows-machine_=3A-=28_?= Message-ID: <3FC51E82.8080707@gmx.de> Hi, I??ve tried anything :-( ... hope anybody could help because this is really urgent. I treid this: http://sources.redhat.com/ml/cygwin-xfree/2003-09/msg00008.html but it doesen??t work. Here is the complete session, started on a cygwin shell: oliver@windows ~ $ export DISPLAY=localhost:0.0 [1]+ Done X oliver@windows ~ $ X& [1] 544 oliver@windows ~ $ ssh -X -l oliver 192.168.0.3 oliver@192.168.0.3's password: Warning: No xauth data; using fake authentication data for X11 forwarding. Linux weapon-one 2.2.20-idepci #1 Sat Apr 20 12:45:19 EST 2002 i686 unknown Most of the programs included with the Debian GNU/Linux system are freely redistributable; the exact distribution terms for each program are described in the individual files in /usr/share/doc/*/copyright Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. Last login: Thu Nov 27 00:30:48 2003 from 192.168.0.2 oliver@linux:~$ xemacs & [1] 370 oliver@linux:~$ ... and nothing happend on my windows-box :-( Hope anybody could help, please. Regards Oliver -- icq: 172670232 homepage: http://www.the-unchallenged.de From ditasaka@silverbacksystems.com Thu Nov 27 01:18:00 2003 From: ditasaka@silverbacksystems.com (Dai Itasaka) Date: Thu, 27 Nov 2003 01:18:00 -0000 Subject: twm takes no control Message-ID: <018d01c3b484$4c11bee0$7b05000a@corp.silverbacksystems.com> ) > > It is obvious that it is not twm that is broken. ) > ) > So it is another little issue related to the shared Xt and Xaw ) > libraries. I did a search in the twm sources for "Vendor", "Shell", ) > "VendorShell", etc. but didn't find anything. I am sure that you can ) > probably find info on how the OS/2 guys handled this bug, but searching ) > for "OS2" turned up nothing in the twm sources either. ) > ) I don't think so, Harold. If this happens with twm run from other OSs, ) that eliminates twm itself and all its dlls, doesn't it? It must be ) internal to the Cygwin X server, or its dlls, right? ) ) Dai, could you test the inverse? Cygwin's twm controlling a RedHat or ) SuSE X server? I think that would definately rule out twm and its dlls. Cygwin's twm worked fine on a RedHat X Server. I think Brian is right. It must be the Cygwin X server. From V.Khamenia@biovision-discovery.de Thu Nov 27 08:41:00 2003 From: V.Khamenia@biovision-discovery.de (Khamenia, Valery) Date: Thu, 27 Nov 2003 08:41:00 -0000 Subject: AW: problems with refresh rate of Xwin at win2000prof Message-ID: Hi Harald, thank your for your answers, > The repainting might be slow for the two following reasons: > > 1) You have a video card that has a problem with its > DirectDraw driver (e.g. ATI All-In-Wonder 8500 DV). > Try using "-engine 1" to use the GDI driver and see if > it is much faster. If it is, then you will have all sorts of > fun testing the various drivers for your video card to see > which one fixes the DirectDraw bug. Note that "-engine 4" is not > required because the DirectDraw engine is the default engine if > DirectDraw is supported by your system. You will only need > "-engine 1" to force XWin.exe to use the GDI engine instead > of the DirectDraw engine. I've tried, the difference was a bit towards slowdown under "engine 1". > 2) You have network latency issues. Sure, 100BaseT, yada > yada yada, but if you have not tried another X Server on > Windows then you have nothing > to compare the performance of XWin.exe to and we cannot tell if your > network is part of the problem or not. Well, symbol echoing is quite fast, so I could live with that. Just wondering: is there any utility for estimating fps-performance for repainting abilities of X servers itselves?.. I mean, clients might be quite powerfull, but Xserver machine + network might introduce a slowdown, so it would be logical to have a simple tool revealing this issue. kind regards, Valery A.Khamenya --------------------------------------------------------------------------- Bioinformatics Department BioVisioN AG, Hannover From alexander.gottwald@s1999.tu-chemnitz.de Thu Nov 27 08:45:00 2003 From: alexander.gottwald@s1999.tu-chemnitz.de (Alexander Gottwald) Date: Thu, 27 Nov 2003 08:45:00 -0000 Subject: =?ISO-8859-1?Q?Can=B4t_open_remote-X-Apps_on_my_local_?= =?ISO-8859-1?Q?windows-machine_=3A-=28_?= In-Reply-To: <3FC51E82.8080707@gmx.de> References: <3FC51E82.8080707@gmx.de> Message-ID: On Wed, 26 Nov 2003, Oliver Brandt wrote: > oliver@windows ~ > $ export DISPLAY=localhost:0.0 > [1]+ Done X > > oliver@windows ~ > $ X& > [1] 544 > > oliver@windows ~ > $ ssh -X -l oliver 192.168.0.3 > oliver@192.168.0.3's password: > Warning: No xauth data; using fake authentication data for X11 forwarding. > oliver@linux:~$ xemacs & > [1] 370 have you tried starting xemacs without "&"? > ... and nothing happend on my windows-box :-( What does xemacs print out? > Hope anybody could help, please. http://xfree86.cygwin.com/docs/faq/cygwin-xfree-faq.html#q-ssh-no-x11forwarding bye ago -- Alexander.Gottwald@s1999.tu-chemnitz.de http://www.gotti.org ICQ: 126018723 From alexander.gottwald@s1999.tu-chemnitz.de Thu Nov 27 16:06:00 2003 From: alexander.gottwald@s1999.tu-chemnitz.de (Alexander Gottwald) Date: Thu, 27 Nov 2003 16:06:00 -0000 Subject: Disabling mousecursor Message-ID: Hi, I'm currently using x2x to use an external X display as second monitor (mainly to write mail and read news *g*). x2x forwards the input from windows (mouse and keyboard) to the xserver and allows easy sharing between the two displays. If the cursor leaves the windows display, the windows cursor is switched off (replace by an empty image). But Xwin does not honour this. It still displays its cursor. Normally we could switch off the cursor after receiving WM_MOUSELEAVE and enable it again after WM_MOUSEENTER. I've searched in the miDC code for an easy way to switch off rendering the software cursor but haven't found one. Am I blind or is the only way to hide the software cursor an empty image as cursorshape? bye ago -- Alexander.Gottwald@s1999.tu-chemnitz.de http://www.gotti.org ICQ: 126018723 From the.unchallenged@gmx.de Thu Nov 27 18:47:00 2003 From: the.unchallenged@gmx.de (Oliver Brandt) Date: Thu, 27 Nov 2003 18:47:00 -0000 Subject: =?ISO-8859-1?Q?Can=B4t_open_remote-X-Apps_on_my_lo?= =?ISO-8859-1?Q?cal_windows-machine_=3A-=28?= In-Reply-To: References: <3FC51E82.8080707@gmx.de> Message-ID: <3FC64746.4060701@gmx.de> Hi Alexander, > http://xfree86.cygwin.com/docs/faq/cygwin-xfree-faq.html#q-ssh-no-x11forwarding thanx for this link :-) anything works fine .... but there is another problem: Always when I try to start wmaker on my windows box (X is running, startet with X & in a cygwin -shell) I get an error like this: wmaker warning: /home/Oliver Brandt/GNUstep/Defaults/ directory created with def ault configuration. TIFFReadDirectory: Warning, /usr/X11R6/share/WINGs/Images.tiff: unknown field wi th tag 317 (0x13d) encountered. wmsetbg warning: could not open domain file /home/Oliver Brandt/GNUstep/Defaults /WindowMaker wmsetbg warning: could not open domain file /home/Oliver Brandt/GNUstep/Defaults /WindowMaker wmaker fatal error: got signal 11 TIFFReadDirectory: Warning, /usr/X11R6/share/WINGs/Images.tiff: unknown field wi th tag 317 (0x13d) encountered. Perhaps you can help me again :-) Because, if I don??t have a windowmaker, I can??t resize my X-applications and I can??t move them in my X-window on my windows- box :-( Regards Olli -- icq: 172670232 homepage: http://www.the-unchallenged.de From andreas.schildbach@friendscout24.de Fri Nov 28 13:23:00 2003 From: andreas.schildbach@friendscout24.de (Andreas Schildbach) Date: Fri, 28 Nov 2003 13:23:00 -0000 Subject: Strange Keyboard Problem Message-ID: <3FC74E31.8040407@friendscout24.de> Hello everyone, I've got a strange problem with Cygwin/X 4.2.99.903(174) (just installed with setup.exe): The keyboard works fine with small programs like xterm or xcalc. As soon as I start KDE or Eclipse from remote using Cygwin as display, the keyboard does not accept any keys at all. Even the xterm does not accept keys any more. The mouse works fine, as well as cut & paste. What am I doing wrong? Regards, Andreas From Alexander.Gottwald@s1999.tu-chemnitz.de Fri Nov 28 14:37:00 2003 From: Alexander.Gottwald@s1999.tu-chemnitz.de (Alexander Gottwald) Date: Fri, 28 Nov 2003 14:37:00 -0000 Subject: =?ISO-8859-1?Q?Can=B4t_open_remote-X-Apps_on_my_lo?= =?ISO-8859-1?Q?cal_windows-machine_=3A-=28?= In-Reply-To: <3FC64746.4060701@gmx.de> References: <3FC51E82.8080707@gmx.de> <3FC64746.4060701@gmx.de> Message-ID: Oliver Brandt wrote: > wmaker warning: /home/Oliver Brandt/GNUstep/Defaults/ directory created > with def > ault configuration. > TIFFReadDirectory: Warning, /usr/X11R6/share/WINGs/Images.tiff: unknown > field wi > th tag 317 (0x13d) encountered. > wmsetbg warning: could not open domain file /home/Oliver > Brandt/GNUstep/Defaults > /WindowMaker > wmsetbg warning: could not open domain file /home/Oliver > Brandt/GNUstep/Defaults > /WindowMaker > wmaker fatal error: got signal 11 Two problems: - Space in user name. - broken TIFF support in libtiff both questions have been discussed last week on the mailinglist so the archives may help you. bye ago -- Alexander.Gottwald@informatik.tu-chemnitz.de http://www.gotti.org ICQ: 126018723 From pechtcha@cs.nyu.edu Sat Nov 29 18:57:00 2003 From: pechtcha@cs.nyu.edu (Igor Pechtchanski) Date: Sat, 29 Nov 2003 18:57:00 -0000 Subject: Cygwin XFree86 startx Problem In-Reply-To: <3FBFACC6.80305@msu.edu> References: <20031121192050.14367.qmail@web60304.mail.yahoo.com> <3FBE6FCF.6090002@msu.edu> <3FBFACC6.80305@msu.edu> Message-ID: 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/ |\ _,,,---,,_ pechtcha@cs.nyu.edu ZZZzz /,`.-'`' -. ;-;;,_ igor@watson.ibm.com |,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 From andrew.leung@utoronto.ca Sun Nov 30 04:13:00 2003 From: andrew.leung@utoronto.ca (Andrew Leung) Date: Sun, 30 Nov 2003 04:13:00 -0000 Subject: xwin on cygwin - cannot connect Message-ID: <071B78D196015846A511D2EA6540766D0209E3@commandcenter.dijitalconceptions.com> Hey list, I'm new subscriber, but have been reading the threads - let me say that there's been a lot of helpful tips towards the a problem I'm having - I've gotten further but not quite there.. so I'm askin for some help. Apologies if this has already been covered.. I've got cygwin on winxp machine - can't connect to the X server. When using xwin.exe :0 -query the checkered screen quickly comes up and then disappears.. Anyone know whats happening? Also I remember someone mentioning that X shouldn't be running on the linux box when trying to connect. How do I stop this as the login screen loads up everytime I boot up? The machine is running slackware. I'm pretty sure there's communication since tcpdumps show some responsive port 117 traffic.. Any help is appreciated, I'm new to linux so I'm not sure what to look for.. Thanks in advance. From huntharo@msu.edu Sun Nov 30 06:08:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Sun, 30 Nov 2003 06:08:00 -0000 Subject: xwin on cygwin - cannot connect In-Reply-To: <071B78D196015846A511D2EA6540766D0209E3@commandcenter.dijitalconceptions.com> References: <071B78D196015846A511D2EA6540766D0209E3@commandcenter.dijitalconceptions.com> Message-ID: <3FC98961.3030400@msu.edu> Andrew, Andrew Leung wrote: > I've got cygwin on winxp machine - can't connect to the X server. When > using xwin.exe :0 -query the checkered screen quickly comes up > and then disappears.. Anyone know whats happening? Also I remember > someone mentioning that X shouldn't be running on the linux box when > trying to connect. How do I stop this as the login screen loads up > everytime I boot up? The machine is running slackware. I'm pretty sure > there's communication since tcpdumps show some responsive port 117 > traffic.. Any help is appreciated, I'm new to linux so I'm not sure > what to look for.. Thanks in advance. Sounds like you have a font problem on your Windows machine. Please send in the contents of /tmp/XWin.log after a failed attempt to connect. Harold From andrew.leung@utoronto.ca Sun Nov 30 06:14:00 2003 From: andrew.leung@utoronto.ca (Andrew Leung) Date: Sun, 30 Nov 2003 06:14:00 -0000 Subject: xwin on cygwin - cannot connect Message-ID: <071B78D196015846A511D2EA6540766D0209E4@commandcenter.dijitalconceptions.com> Thanks for the reply, here it is, This was my latest attempt, but now it seems the checkered screen stays.. but with no change. It does not disappear on me at this point. ddxProcessArgument - Initializing default screens winInitializeDefaultScreens - w 1024 h 768 winInitializeDefaultScreens - Returning OsVendorInit - Creating bogus screen 0 _XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root (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 0000001f InitOutput - g_iNumScreens: 1 iMaxConsecutiveScreen: 1 winSetEngine - Using Shadow DirectDraw NonLocking winAdjustVideoModeShadowDDNL - Using Windows display depth of 32 bits per pixel winCreateBoundingWindowWindowed - User w: 1024 h: 768 winCreateBoundingWindowWindowed - Current w: 1024 h: 768 winAdjustForAutoHide - Original WorkArea: 0 100 718 1024 winAdjustForAutoHide - Adjusted WorkArea: 0 100 718 1024 winCreateBoundingWindowWindowed - WindowClient w 918 h 693 r 918 l 0 b 693 t 0 winCreateBoundingWindowWindowed - Returning winCreatePrimarySurfaceShadowDDNL - Creating primary surface winCreatePrimarySurfaceShadowDDNL - Created primary surface winCreatePrimarySurfaceShadowDDNL - Attached clipper to primary surface winAllocateFBShadowDDNL - lPitch: 3672 winAllocateFBShadowDDNL - Created shadow pitch: 3672 winAllocateFBShadowDDNL - Created shadow stride: 918 winFinishScreenInitFB - Masks: 00ff0000 0000ff00 000000ff winInitVisualsShadowDDNL - Masks 00ff0000 0000ff00 000000ff BPRGB 8 d 24 bpp 32 winCreateDefColormap - Deferring to fbCreateDefColormap () winFinishScreenInitFB - returning winScreenInit - returning InitOutput - Returning. MIT-SHM extension disabled due to lack of kernel support XFree86-Bigfont extension local-client optimization disabled due to lack of shared memory support in the kernel (==) winConfigKeyboard - Layout: "00000409" (00000409) (EE) No primary keyboard configured (==) Using compiletime defaults for keyboard Rules = "xfree86" Model = "pc101" Layout = "us" Variant = "(null)" Options = "(null)" winPointerWarpCursor - Discarding first warp: 459 346 winBlockHandler - Releasing pmServerStarted winBlockHandler - pthread_mutex_unlock () returned -----Original Message----- From: cygwin-xfree-owner@cygwin.com [mailto:cygwin-xfree-owner@cygwin.com] On Behalf Of Harold L Hunt II Sent: Sunday, November 30, 2003 1:09 AM To: cygwin-xfree@cygwin.com Subject: Re: xwin on cygwin - cannot connect Andrew, Andrew Leung wrote: > I've got cygwin on winxp machine - can't connect to the X server. When > using xwin.exe :0 -query the checkered screen quickly comes up > and then disappears.. Anyone know whats happening? Also I remember > someone mentioning that X shouldn't be running on the linux box when > trying to connect. How do I stop this as the login screen loads up > everytime I boot up? The machine is running slackware. I'm pretty sure > there's communication since tcpdumps show some responsive port 117 > traffic.. Any help is appreciated, I'm new to linux so I'm not sure > what to look for.. Thanks in advance. Sounds like you have a font problem on your Windows machine. Please send in the contents of /tmp/XWin.log after a failed attempt to connect. Harold From huntharo@msu.edu Sun Nov 30 06:26:00 2003 From: huntharo@msu.edu (Harold L Hunt II) Date: Sun, 30 Nov 2003 06:26:00 -0000 Subject: xwin on cygwin - cannot connect In-Reply-To: <071B78D196015846A511D2EA6540766D0209E4@commandcenter.dijitalconceptions.com> References: <071B78D196015846A511D2EA6540766D0209E4@commandcenter.dijitalconceptions.com> Message-ID: <3FC98D9D.1010704@msu.edu> Andrew, Hmm... the log file looks okay, you did try a failed connection, then send in that XWin.log, right? I'm going to bed. Maybe someone else can help. Harold Andrew Leung wrote: > Thanks for the reply, here it is, This was my latest attempt, but now > it seems the checkered screen stays.. but with no change. It does not > disappear on me at this point. > > ddxProcessArgument - Initializing default screens > winInitializeDefaultScreens - w 1024 h 768 > winInitializeDefaultScreens - Returning > OsVendorInit - Creating bogus screen 0 > _XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root > (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 0000001f > InitOutput - g_iNumScreens: 1 iMaxConsecutiveScreen: 1 > winSetEngine - Using Shadow DirectDraw NonLocking > winAdjustVideoModeShadowDDNL - Using Windows display depth of 32 bits > per pixel > winCreateBoundingWindowWindowed - User w: 1024 h: 768 > winCreateBoundingWindowWindowed - Current w: 1024 h: 768 > winAdjustForAutoHide - Original WorkArea: 0 100 718 1024 > winAdjustForAutoHide - Adjusted WorkArea: 0 100 718 1024 > winCreateBoundingWindowWindowed - WindowClient w 918 h 693 r 918 l 0 b > 693 t 0 > winCreateBoundingWindowWindowed - Returning > winCreatePrimarySurfaceShadowDDNL - Creating primary surface > winCreatePrimarySurfaceShadowDDNL - Created primary surface > winCreatePrimarySurfaceShadowDDNL - Attached clipper to primary surface > winAllocateFBShadowDDNL - lPitch: 3672 > winAllocateFBShadowDDNL - Created shadow pitch: 3672 > winAllocateFBShadowDDNL - Created shadow stride: 918 > winFinishScreenInitFB - Masks: 00ff0000 0000ff00 000000ff > winInitVisualsShadowDDNL - Masks 00ff0000 0000ff00 000000ff BPRGB 8 d 24 > bpp 32 > winCreateDefColormap - Deferring to fbCreateDefColormap () > winFinishScreenInitFB - returning > winScreenInit - returning > InitOutput - Returning. > MIT-SHM extension disabled due to lack of kernel support > XFree86-Bigfont extension local-client optimization disabled due to lack > of shared memory support in the kernel > (==) winConfigKeyboard - Layout: "00000409" (00000409) > (EE) No primary keyboard configured > (==) Using compiletime defaults for keyboard > Rules = "xfree86" Model = "pc101" Layout = "us" Variant = "(null)" > Options = "(null)" > winPointerWarpCursor - Discarding first warp: 459 346 > winBlockHandler - Releasing pmServerStarted > winBlockHandler - pthread_mutex_unlock () returned > > > -----Original Message----- > From: cygwin-xfree-owner@cygwin.com > [mailto:cygwin-xfree-owner@cygwin.com] On Behalf Of Harold L Hunt II > Sent: Sunday, November 30, 2003 1:09 AM > To: cygwin-xfree@cygwin.com > Subject: Re: xwin on cygwin - cannot connect > > Andrew, > > Andrew Leung wrote: > >>I've got cygwin on winxp machine - can't connect to the X server. > > When > >>using xwin.exe :0 -query the checkered screen quickly comes up >>and then disappears.. Anyone know whats happening? Also I remember >>someone mentioning that X shouldn't be running on the linux box when >>trying to connect. How do I stop this as the login screen loads up >>everytime I boot up? The machine is running slackware. I'm pretty > > sure > >>there's communication since tcpdumps show some responsive port 117 >>traffic.. Any help is appreciated, I'm new to linux so I'm not sure >>what to look for.. Thanks in advance. > > > Sounds like you have a font problem on your Windows machine. Please > send in the contents of /tmp/XWin.log after a failed attempt to connect. > > Harold > > > > > From the.unchallenged@gmx.de Sun Nov 30 21:22:00 2003 From: the.unchallenged@gmx.de (Oliver Brandt) Date: Sun, 30 Nov 2003 21:22:00 -0000 Subject: keyboard mapping does not work Message-ID: <3FCA6022.7090208@gmx.de> Hi all, wmaker an X works fine until I want to enable F1, F2, F3 etc. to switch my workspace. I used the wmaker-configuration tool. As I tried to capture my keyboard entries, everytime I capture F2 or F3 etc, I realized that Mod1 + F1 is captured but I only press F1! I can??t find Mod1 on my keyboard. F11 and F12 is preconfigured and works! Very odd :-) If I try to change the entry manually the configuration doesn??t work, too. I downloaded the XF86Config from here: http://www-user.tu-chemnitz.de/~goal/index.php3?jump=xfree but this changed nothing. Normally I??ve got problems with | @ and ~ (on my debian) but never with F1 - F12. Could someone tell me how to configure the keyboardmapping correctly? Perhaps how to configure the keys manually? Regards Olli -- icq: 172670232 homepage: http://www.the-unchallenged.de From the.unchallenged@gmx.de Sun Nov 30 23:00:00 2003 From: the.unchallenged@gmx.de (Oliver Brandt) Date: Sun, 30 Nov 2003 23:00:00 -0000 Subject: keyboard mapping does not work In-Reply-To: <3FCA6022.7090208@gmx.de> References: <3FCA6022.7090208@gmx.de> Message-ID: <3FCA770E.4090606@gmx.de> Problem is solved :-) Olli > Hi all, > > wmaker an X works fine until I want to enable F1, F2, F3 etc. > to switch my workspace. I used the wmaker-configuration tool. > As I tried to capture my keyboard entries, everytime I capture > F2 or F3 etc, I realized that Mod1 + F1 is captured but I only > press F1! I can??t find Mod1 on my keyboard. F11 and F12 is > preconfigured and works! Very odd :-) > If I try to change the entry manually the configuration doesn??t > work, too. > > I downloaded the XF86Config from here: > http://www-user.tu-chemnitz.de/~goal/index.php3?jump=xfree > but this changed nothing. Normally I??ve got problems with | @ > and ~ (on my debian) but never with F1 - F12. Could someone > tell me how to configure the keyboardmapping correctly? Perhaps > how to configure the keys manually? > > Regards Olli > -- icq: 172670232 homepage: http://www.the-unchallenged.de From andrew.leung@utoronto.ca Sun Nov 30 23:53:00 2003 From: andrew.leung@utoronto.ca (Andrew Leung) Date: Sun, 30 Nov 2003 23:53:00 -0000 Subject: xwin on cygwin - cannot connect Message-ID: <071B78D196015846A511D2EA6540766D0209E5@commandcenter.dijitalconceptions.com> Harold, Yes that's the latest XWin.log off the cygwin installation. Then I suppose it's something on the linux box. Are there logs on there that would shed some light? I see that gdm is running from top command: PID USER PRI NI SIZE RSS SHARE STAT %CPU %MEM TIME CPU COMMAND 2089 root 14 0 936 900 752 R 2.1 3.0 0:02 0 top 2092 root 11 0 10372 5276 1500 S 1.3 17.9 0:16 0 X 2060 root 11 0 896 740 660 S 0.7 2.5 0:00 0 sshd 6 root 10 0 0 0 0 SW 0.1 0.0 0:15 0 kupdated 2101 gdm 9 0 10968 10M 6736 S 0.1 37.3 0:26 0 gdmgreeter 1 root 9 0 80 52 44 S 0.0 0.1 0:04 0 init 2 root 9 0 0 0 0 SW 0.0 0.0 0:00 0 keventd 3 root 19 19 0 0 0 SWN 0.0 0.0 0:00 0 ksoftirqd_CPU 4 root 9 0 0 0 0 SW 0.0 0.0 0:33 0 kswapd Login screen prompt is on the box. Am I in the right direction or something missing? -----Original Message----- From: cygwin-xfree-owner@cygwin.com [mailto:cygwin-xfree-owner@cygwin.com] On Behalf Of Harold L Hunt II Sent: Sunday, November 30, 2003 1:27 AM To: cygwin-xfree@cygwin.com Subject: Re: xwin on cygwin - cannot connect Andrew, Hmm... the log file looks okay, you did try a failed connection, then send in that XWin.log, right? I'm going to bed. Maybe someone else can help. Harold Andrew Leung wrote: > Thanks for the reply, here it is, This was my latest attempt, but now > it seems the checkered screen stays.. but with no change. It does not > disappear on me at this point. > > ddxProcessArgument - Initializing default screens > winInitializeDefaultScreens - w 1024 h 768 > winInitializeDefaultScreens - Returning > OsVendorInit - Creating bogus screen 0 > _XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root > (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 0000001f > InitOutput - g_iNumScreens: 1 iMaxConsecutiveScreen: 1 > winSetEngine - Using Shadow DirectDraw NonLocking > winAdjustVideoModeShadowDDNL - Using Windows display depth of 32 bits > per pixel > winCreateBoundingWindowWindowed - User w: 1024 h: 768 > winCreateBoundingWindowWindowed - Current w: 1024 h: 768 > winAdjustForAutoHide - Original WorkArea: 0 100 718 1024 > winAdjustForAutoHide - Adjusted WorkArea: 0 100 718 1024 > winCreateBoundingWindowWindowed - WindowClient w 918 h 693 r 918 l 0 b > 693 t 0 > winCreateBoundingWindowWindowed - Returning > winCreatePrimarySurfaceShadowDDNL - Creating primary surface > winCreatePrimarySurfaceShadowDDNL - Created primary surface > winCreatePrimarySurfaceShadowDDNL - Attached clipper to primary surface > winAllocateFBShadowDDNL - lPitch: 3672 > winAllocateFBShadowDDNL - Created shadow pitch: 3672 > winAllocateFBShadowDDNL - Created shadow stride: 918 > winFinishScreenInitFB - Masks: 00ff0000 0000ff00 000000ff > winInitVisualsShadowDDNL - Masks 00ff0000 0000ff00 000000ff BPRGB 8 d 24 > bpp 32 > winCreateDefColormap - Deferring to fbCreateDefColormap () > winFinishScreenInitFB - returning > winScreenInit - returning > InitOutput - Returning. > MIT-SHM extension disabled due to lack of kernel support > XFree86-Bigfont extension local-client optimization disabled due to lack > of shared memory support in the kernel > (==) winConfigKeyboard - Layout: "00000409" (00000409) > (EE) No primary keyboard configured > (==) Using compiletime defaults for keyboard > Rules = "xfree86" Model = "pc101" Layout = "us" Variant = "(null)" > Options = "(null)" > winPointerWarpCursor - Discarding first warp: 459 346 > winBlockHandler - Releasing pmServerStarted > winBlockHandler - pthread_mutex_unlock () returned > > > -----Original Message----- > From: cygwin-xfree-owner@cygwin.com > [mailto:cygwin-xfree-owner@cygwin.com] On Behalf Of Harold L Hunt II > Sent: Sunday, November 30, 2003 1:09 AM > To: cygwin-xfree@cygwin.com > Subject: Re: xwin on cygwin - cannot connect > > Andrew, > > Andrew Leung wrote: > >>I've got cygwin on winxp machine - can't connect to the X server. > > When > >>using xwin.exe :0 -query the checkered screen quickly comes up >>and then disappears.. Anyone know whats happening? Also I remember >>someone mentioning that X shouldn't be running on the linux box when >>trying to connect. How do I stop this as the login screen loads up >>everytime I boot up? The machine is running slackware. I'm pretty > > sure > >>there's communication since tcpdumps show some responsive port 117 >>traffic.. Any help is appreciated, I'm new to linux so I'm not sure >>what to look for.. Thanks in advance. > > > Sounds like you have a font problem on your Windows machine. Please > send in the contents of /tmp/XWin.log after a failed attempt to connect. > > Harold > > > > >