Re: problem with startxwin.exe and a possible solution
On 21/01/2010 23:13, Marco Atzeri wrote: Hi, after the transition from startxwin.bat to startxwin.exe, I had the Xwin Server menu pratically unusable. The server start but the xterm usually don't show up while ps reports it running. Running a second xterm could appear but most of the time as if the window manager is absent: no border, no possibility to move the program and similar. The Xserver is also unstable, the icon on the toolbar usually disappear and to terminate the server I really need to kill it with Process Explorer. I can reproduce this if I have CYGWIN=tty (which I note in your cygcheck.out) in my Windows environment. Without that it seems to work fine. I'm not sure that I believe that this is the underlying cause of the problem, and if it is, I have no idea how it could make difference or why it wasn't a problem previously. -- 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: problem with startxwin.exe and a possible solution
I posted a related problem a month ago (CYGWIN=tty). In my case, when starting the server, I could not start an Xterm, nor could I start one from the system tray icon. I could start one from a shortcut icon on my desktop, however. This is the first time that anyone else on this list has confirmed it. - Jim On Wed, Feb 3, 2010 at 2:09 PM, Jon TURNEY jon.tur...@dronecode.org.uk wrote: On 21/01/2010 23:13, Marco Atzeri wrote: Hi, after the transition from startxwin.bat to startxwin.exe, I had the Xwin Server menu pratically unusable. The server start but the xterm usually don't show up while ps reports it running. Running a second xterm could appear but most of the time as if the window manager is absent: no border, no possibility to move the program and similar. The Xserver is also unstable, the icon on the toolbar usually disappear and to terminate the server I really need to kill it with Process Explorer. I can reproduce this if I have CYGWIN=tty (which I note in your cygcheck.out) in my Windows environment. Without that it seems to work fine. I'm not sure that I believe that this is the underlying cause of the problem, and if it is, I have no idea how it could make difference or why it wasn't a problem previously. -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- Jim Reisert AD1C, jjreis...@alum.mit.edu, http://www.ad1c.us -- 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: problem with startxwin.exe and a possible solution
2010.02.03.16:43:56 EST Hi Jim and cygwin-xfree folks, I had the same problem that Jim was experiencing. I had started with cygwin-1.7 back in August, and over the course of the autumn months had my difficulties with startxwin.bat. Among the things that I did to make startxwin.bat work was to have the environment variable CYGWIN set to: CYGWIN = tty notitle glob When I stepped up to startxwin.exe in late December/early January, it would start the Xwin server, but my xterm would always hang. I retained startxwin.bat for a few weeks while I scanned the postings for information. Jim Reisert's hint, about removing the tty setting from the CYGWIN environment variable, was what got the startxwin.exe going for me. Now that my variable states only CYGWIN = notitle glob the xterm starts up nicely within a few seconds after Xwin.exe is initialized. Mucho gracias, Jim! George gbarr...@walsh.edu -- 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: problem with startxwin.exe and a possible solution
Marco Atzeri wrote: Today I start some experiments and I have found that changing the menu target from C:\cygwin2\bin\run.exe /usr/bin/bash.exe -l -c /usr/bin/startxwin.exe to C:\cygwin2\bin\run.exe -p /usr/bin /usr/bin/startxwin.exe all the problems seem gone. The Xserver is stable and all the Xterms run smoothly. I suppose that my login shell redefine some parameters that startxwin.exe needs, while a much simpler run.exe -p /usr/bin is what is really needed. The real issue, I think, is that your mechanism doesn't allow you to set OTHER environment variables that might need to be defined before launching XWin, such as LC_ALL etc -- which would get set by the original formula, since 'bash -l' reads your startup files like ~/.bash_profile where they might get set. Another (untested!) possibility is to use run2.exe (which is kinda wierd: use a launcher to start a launcher that starts X...) == startxwin.xml === ?xml version=1.0 encoding=us-ascii? Run2Config xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:noNamespaceSchemaLocation=run2.xsd Global Environment !-- set environment variables here -- Append var=PATH value=/usr/bin/ Set var=LC_ALL value=en_US.UTF-8/ /Environment Target filename=/usr/bin/startxwin.exe startin=~ /Target /Global /Run2Config Shortcut target: C:/cygwin/bin/run2.exe --notty /usr/bin/startxwin.xml -- Chuck -- 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/
