Re: xterm no longer accepts keyboard input
On Mon, Mar 15, 2010 at 10:44 AM, Jon TURNEY wrote: > > No. startx and startxwin are different tools to solve different problems. > > I keep adding more text to [1] to clarify this, but this doesn't appear to > help, perhaps because nobody actually reads it... > > [1] http://x.cygwin.com/docs/ug/using.html#using-starting > I read it. I just don't agree with it. These appear to be the reasons: 1) "startxwin supplies the -multiwindow option to XWin.exe" So does startx if you put that in the shortcut. 2) "It uses a different script to start clients (~/.startxwinrc rather than ~/.xinitrc), because ~/.xinitrc will normally end by starting a window manager, which would be incorrect for ~/.startxwinrc (as it would discover the internal window manager is already running and exit immediately)." In my opinion, it doesn't really matter with .xinitrc normally ends with. We can end it with anything that we want. It sounds like you can get the startxwin behavior (if that's what you really want) from startx if you put "sh ~/.startxwinrc& while : ; do sleep 1000; done" in your .xinitrc. 3) "startxwin exits after ~/.startxwinrc has completed and leaves XWin.exe running, whereas startx waits until ~/.xinitrc exits (which is usually waiting for the window manager started by it to exit) and then kills XWin.exe." If you don't like the behavior of startx exiting after the .xinitrc is complete, then why not write your .xinitrc so that it doesn't exit? Is it really worth maintaining another program when you can get the same behavior out of existing programs through config changes? Additionally, the startxwin.exe program is missing the security feature of creating a .Xauthority file. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: Incorrect Cygwin/X behavior leads to .X0-lock related fatal error
On 12/03/2010 02:31, Ken Klein wrote: Here is tool behavior that seems like a bug in 1.7.1 related to the Cygwin/X FAQ item 3.4 (A2)called "Fatal server error: Can't read lock file /tmp/.X0-lock." I am posting this, because the faq item states that the buggy behavior happens "For reasons which are not well understood at present." This post presents what I consider to be incorrect behavior that leads to this error. If I log on as a user without admin rights (on Windows XP), and I start Cygwin/X using the XWin Server program shortcut, the referenced lock file gets created and gives me read/write access. The Everyone user just has read access. When I then close my XWin session, the lock file remains. I log out of Windows, then someone else logs on (also without admin rights), and they get the fatal error as described in the FAQ item, since they do not have write access to the lock file. If, however, I had originally started Cygwin/X by opening a Cygwin window then entering startx, when I eventually end my Cygwin session, the lock file gets deleted. So in this scenario, the next person to log on will not get the fatal error, since Cygwin didn't leave the lock file behind. My opinion is that the startx scenario behaves correctly, and the XWin Server shortcut scenario presents a bug, namely, it leaves behind the lock file after the session is ended. Thanks for the detailed bug report. In fact that FAQ is slightly out of date and we do now understand that the problem is shown when running XWin as both Administrator and non-Adminstrator users as you describe. I'm not able to reproduce the difference in behaviour you describe (of leaving the log file behind) between running startx (which then starts XWin) and directly starting XWin when running as a non-administrator user. Can you be specific about how you are exiting XWin which causes it to leave the lock file behind? This shouldn't happen, and is the cause of the problem. -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: xterm no longer accepts keyboard input
On 3/15/2010 1:35 PM, Jon TURNEY wrote: ... I'm not sure if the difficulties starting a server mean you have some other problem as well. Thanks for your response, Jon. As you'll see from a more recent post, I was able to solve both problems by going back to using a script instead of the compiled binary for startxwin. -- Bob Kline http://www.rksystems.com mailto:bkl...@rksystems.com -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: xterm no longer accepts keyboard input
On 15/03/2010 05:42, David Barr wrote: On Sun, Mar 14, 2010 at 7:17 AM, Jeff Spirko wrote: The icon runs from the Windows environment, so the run.exe and bash.exe wrapper programs are needed to set up the proper cygwin environment. Once you're in a cygwin shell, you already have the cygwin environment set up. That's why you don't need to type them in from the command line. So, they really should be equivalent. I've probably missed a prior discussion, but if "startxwin.exe" doesn't set up the Cygwin environment, then what good is it? I thought that this was about the only advantage that "startxwin.bat" had over "startx". No. startx and startxwin are different tools to solve different problems. I keep adding more text to [1] to clarify this, but this doesn't appear to help, perhaps because nobody actually reads it... [1] http://x.cygwin.com/docs/ug/using.html#using-starting > Considering that "startx" also sets up the .Xauthority file and startxwin.exe doesn't, I see absolutely no reason to use startxwin.exe instead of startx. -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: xterm no longer accepts keyboard input
On 13/03/2010 21:47, Bob Kline wrote: On 3/13/2010 1:05 PM, Bob Kline wrote: I have used X under Cygwin successfully for years. Yesterday I did an upgrade of my Cygwin installation and X stopped working. After struggling to get things working again, I decided to just install Cygwin fresh and start over. Now I can get the X server started (following the instructions in the Cygwin/X User's Guide, running /usr/bin/startxwin from a Cygwin shell), but xterm windows that I open do not respond to keyboard input. I looked at the FAQ and found the entry (3.2 I upgraded my X server and now I can't type anything into any X application) which warns against using any older scripts to launch X, but as noted above, I'm invoking the startxwin binary directly. Any thoughts as to what could be going wrong, given that this is an installation of Cygwin and X from scratch? looking at your cygcheck.out, you have the following variables in your environment XKEYSYMDB = '/usr/X11R6/lib/X11/XKeysymDB' XAPPLRESDIR = '/usr/X11R6/lib/X11/app-defaults' XCMSDB = '/usr/X11R6/lib/X11/Xcms.txt' XNLSPATH = '/usr/X11R6/lib/X11/locale' These have probably been set by Microsoft Services for Unix, and as the FAQ tries to make clear, at least XKEYSYMDB must be unset for keyboard input to XWin to work correctly (FAQ 3.2 refers to FAQ 8.8) We used to have something in startxwin.bat to unset this, so I guess it is a regression that we don't do that anymore. Following up on my earlier post, I see that although I am able to start the X server if I invoke /usr/bin/startxwin directly from a Cygwin shell, that's not *exactly* what the FAQ was suggesting. I'm not sure if the difficulties starting a server mean you have some other problem as well. -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Deixe todos verem seu site.
- Você possui um site ou blog? Mostre ele a todos. ---Use: www.gooto.com.br --- - - Seu concorrente pode estar aqui, venha também! - - - -- Totalmente gratuito, Sem pagamento de cliques, Anuidades, Mensalidades, etc. -- -- Localize novos fornecedores, locais de compras, etc. -- >http://www.gooto.com.br < Retorne este email com o tílulo de Assunto: REMOVER, para não receber nossos emails. Removerá também sua URL das pesquisas. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
