Re: [gerardin@fr.ibm.com: unable to get French keyboard with twm (Xfree)]
Did you try setxkbmap fr ? - Forwarded message from Pierre Gerardin [EMAIL PROTECTED] - Date: Fri, 30 Aug 2002 20:58:19 GMT From: Pierre Gerardin [EMAIL PROTECTED] Subject: unable to get French keyboard with twm (Xfree) To: [EMAIL PROTECTED] Running cygwin Xfree86, I tried twm, fvwm2, mwm ... I am not able to get the French keyboard in an xterm... Only the US one. Any idea ? Thanks. I also have messagestwm : invalid color name ... -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/ - End forwarded message - -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:[EMAIL PROTECTED] Red Hat, Inc. ___ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com
Re: xwinclip re selection polling
Harold L Hunt II said: I have searched for months and months for a way to receive a definite signal that the X server is about to shutdown. There is a hook provided by most window managers to indicate that the display is closeing, but it has so far given mixed results. The last idea I saw was in the x2x (I think) source code, which interfaces with the raw Xlib, just like xwinclip. It looked like x2x was watching for a move message for the mouse to (0, 0) (or some other special point) and it took this as a signal to close the X client connection. Please correct me if I'm wrong, but isn't it the case that you merely need to be able to gracefully handle the X server is dead case rather than knowing the X server is about to exit? If so, perhaps this (grotty kludge) is what you want. During initialization, after the initial connection to the X server is made (using the appropriate X library funtions), MANUALLY create another connection to the X server (e.g. open a socket and send some messages). Then, before any X operations, try accessing the manual socket to make sure X is still up (e.g. ping the server). If the ping fails, then you can un-hook your event gracefully. Yes, there's still a window where you ping, the server goes down, and then you try your operation, but I doubt you really want to do it all by hand. The ping will be painful enough. This idea has come to me through the python-xlib project, which basically implements libX11 in pure python code (except for the socket layer, of course). My understanding is that the fundamental problem is that the X11 functions generally force an application exit when they fail to do server absence.
X windows display problem
Hi I have found some related posts in the archives, but nothing that seems to solve my problem, which is: I start startxwin.sh from my client (which runs windows2000) (I have tried both cygwin shell and cmd) then i open up an ssh connection (ssh -X -l username hostname) to my host computer which is running red hat 7.3. The sshd config file has X11Forwarding turned on when i try to open xterm, xeyes, anything - i get the following error: xterm Xt error: Can't open display: this happens no matter which window i am sshing from - cmd, cygwin, xwindows. and /tmp/XWin.log displays no error messages Any suggestions? Thanks, Meredith -- Open WebMail Project (http://openwebmail.org)
Re: X windows display problem
What is the value of the DISPLAY environment variable on the remote machine after running ssh? It should have a value of remotehostname:10.0, or something similar. If it's empty, or the value looks like remotehostname:0.0, localhostname:0.0, or simply :0, then there is a problem with the X forwarding. Note that the ssh daemon on the remote machine has to be explicitly told to enable X forwarding. This might be to blame. I've also seen the existance of the .Xauthority file in the home directory on the local Cygwin host cause problems. From: Meredith Finkelstein [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] To: [EMAIL PROTECTED] [EMAIL PROTECTED] Subject: X windows display problem Date: Fri, 30 Aug 2002 15:41:41 -0400 Hi I have found some related posts in the archives, but nothing that seems to solve my problem, which is: I start startxwin.sh from my client (which runs windows2000) (I have tried both cygwin shell and cmd) then i open up an ssh connection (ssh -X -l username hostname) to my host computer which is running red hat 7.3. The sshd config file has X11Forwarding turned on when i try to open xterm, xeyes, anything - i get the following error: xterm Xt error: Can't open display: this happens no matter which window i am sshing from - cmd, cygwin, xwindows. and /tmp/XWin.log displays no error messages Any suggestions? Thanks, Meredith -- Open WebMail Project (http://openwebmail.org) _ Chat with friends online, try MSN Messenger: http://messenger.msn.com
Re: X windows display problem
Doh. One more thing. Be sure to run the ssh command from an xterm within XWin. If you're running ssh from the same Cygwin prompt from which you issued startxwin.sh, then that is very likely the source of your problem. From: Thomas Chadwick [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] To: [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: Re: X windows display problem Date: Fri, 30 Aug 2002 16:17:29 -0400 I guess I should have read your message a little more carefully before replying. You said that sshd has been configure with X11Forwarding turned on. Give the following a try: 1) On the local system, before running ssh, echo the value of DISPLAY. It should have a value of localhost:0.0 or something similar. If it doesn't, manually set it to the correct value. Verify its value by running a simple xclient like xeyes. 2) Run your ssh -X command. 3) On the remote system, echo the value of DISPLAY. It should have a value of remotesystem:10.0 or something similar. If it doesn't have the right value, try setting it manually. If that doesn't work, then I'm stumped. From: Thomas Chadwick [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] To: [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: Re: X windows display problem Date: Fri, 30 Aug 2002 16:07:13 -0400 What is the value of the DISPLAY environment variable on the remote machine after running ssh? It should have a value of remotehostname:10.0, or something similar. If it's empty, or the value looks like remotehostname:0.0, localhostname:0.0, or simply :0, then there is a problem with the X forwarding. Note that the ssh daemon on the remote machine has to be explicitly told to enable X forwarding. This might be to blame. I've also seen the existance of the .Xauthority file in the home directory on the local Cygwin host cause problems. From: Meredith Finkelstein [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] To: [EMAIL PROTECTED] [EMAIL PROTECTED] Subject: X windows display problem Date: Fri, 30 Aug 2002 15:41:41 -0400 Hi I have found some related posts in the archives, but nothing that seems to solve my problem, which is: I start startxwin.sh from my client (which runs windows2000) (I have tried both cygwin shell and cmd) then i open up an ssh connection (ssh -X -l username hostname) to my host computer which is running red hat 7.3. The sshd config file has X11Forwarding turned on when i try to open xterm, xeyes, anything - i get the following error: xterm Xt error: Can't open display: this happens no matter which window i am sshing from - cmd, cygwin, xwindows. and /tmp/XWin.log displays no error messages Any suggestions? Thanks, Meredith -- Open WebMail Project (http://openwebmail.org) _ Chat with friends online, try MSN Messenger: http://messenger.msn.com _ Join the worlds largest e-mail service with MSN Hotmail. http://www.hotmail.com _ Join the worlds largest e-mail service with MSN Hotmail. http://www.hotmail.com
Re: xwinclip re selection polling
I can't tell if you have enough of an understanding of X11 to write a proposed solution that actually makes sense. At least, I can't make any sense out of your proposal. I understand what he's saying but XLib seems quite against the idea : XSetIOErrorHandler is the first thing and the last thing that happens. Automagically unfortunately so it can't be recovered from. What I'm confused about is what does this matter? For me it's a great place to close the hook (stops the hook from not working the next time xwinclip is started). In fact the only thing for me now is to try and get a proper close notification when xwinclip is closed by the user. Ctrl-c doesn't cut it. As an aside it comes back to the Windoze window being visible again (could put a button on it to disable xwinclip's activities, god knows why you'd want to though - as appose to just killing it then resarting it?-). Do you want this information because having a client that is within the x server could cause a big problem when the server disconnects? Personally I think we'd be better off keeping it out of XWin anyway, possibly have it start it but it really is a seperate tool KISS and all that. Why do we need to know when the server is about to close? Chris _ MSN Photos is the easiest way to share and print your photos: http://photos.msn.com/support/worldwide.aspx
Re: xwinclip re selection polling
Harold, As an aside this link explains that the only way is to longjmp/setjmp. http://www.faqs.org/faqs/Xt-FAQ/section-19.html If the intention is to fully integrate xwinclip into XWin then this would be unwanted to say the least. Given XWin would close anyway you'd still want xwinclip to close with it. Chris _ Join the worlds largest e-mail service with MSN Hotmail. http://www.hotmail.com
Re: xwinclip re selection polling
Chris, Excellent detective work. It looks like longjmp setjmp is the way to go. I will give it a try someday, unless you want to do it first. The reason that catching a server reset is so important is that we should not be killed when the server resets and we should try to connect to the server again if it resets. Part of this makes it easy to stay connected when a user is using XDMCP to connect to a remote machine. Also, we can never integrate clipboard support into XWin.exe until we can be assured that the server will not be killed when it resets. Later, Harold Chris Twiner wrote: Harold, As an aside this link explains that the only way is to longjmp/setjmp. http://www.faqs.org/faqs/Xt-FAQ/section-19.html If the intention is to fully integrate xwinclip into XWin then this would be unwanted to say the least. Given XWin would close anyway you'd still want xwinclip to close with it. Chris _ Join the worlds largest e-mail service with MSN Hotmail. http://www.hotmail.com
