Re: startx with different displays
Larry Hall (Cygwin-X) wrote: Get rid of the real dups. You only need the one in /usr/bin. I don't know how they got there. They are not in my normal path. Somehow my procedure to run cygcheck must have injected them. I add them in neither .bash_profile nor .bashrc. Marc -- View this message in context: http://old.nabble.com/startx-with-different-displays-tp33702991p33737835.html Sent from the cygwin-xfree mailing list archive at Nabble.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: Issue with XWin under xlaunch
On 23/04/2012 17:41, Eliot Moss wrote: Ok -- by perusing the log I figured it out ... [727848.279] executing 'xterm -display :0.0 -ls -title swarm -bg rgbi:.0/.20/.0 -geometry 120x47+0+0 -e /usr/bin/ssh m...@swarm.cs.umass.edu', pid 13748 [727848.311] (pid 13748 stderr) /bin/sh: xterm: command not found In the past, .XWinrc names of files such as xterm worked just fine. Apparently something changed about the PATH used, and xterm was not being found. When I write /usr/bin/xterm, it starts up. You can see the first case and the second in the attached log file. So, I think xlaunch is ok, but this was a surprising difference :-) ... This is not intentional. I can't reproduce this, so I'm not quite sure what is causing this. What I am expecting to happen is that xlaunch is invoked via the start menu shortcut which it's package creates, which runs bash -l -c xlaunch, which reads /etc/profile, which sets PATH to include /usr/bin, which should be inherited by XWin and used when it execs /bin/sh -c 'your xterm command'. We try to create the login environment as far up the process hierarchy as possible, rather than starting the processes from the notification area menu with bash -l -c, as creating the login environment can be expensive. -- 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: Issue with XWin under xlaunch
On 23/04/2012 16:04, Ken Brown wrote: I've added some code to capture stdout and stderr from these subprocesses to the X server log, and to more clearly diagnose problems which could occur while fork/exec-ing them. Would it be possible for you to also add some code for diagnosing problems with processes started from .startxwinrc? I'm hoping it might help with the problem I reported in http://cygwin.com/ml/cygwin-xfree/2012-04/msg00050.html Hmm.. not sure code is really needed. You can see the output from startxwin by running it from a terminal, or capture it by changing the shortcut which runs it to something like the following (perhaps we should do that by default) C:\cygwin\bin\run.exe /usr/bin/bash.exe -l -c '/usr/bin/startxwin.exe /var/log/xwin/startxwin.log 21' -- 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: Issue with XWin under xlaunch
Ok, I can see that perhaps in some ways I was being foolish and could have figured out more of this myself. But here's something interesting. I tried this: - Pin to Start Menu of the supplied XLaunch short cut - Edit to change the command to: /usr/bin/xlaunch.exe -run /home/Eliot/config.xlaunch (since I want to start things, not build/edit a config file) The full line in the shortcut is: C:\cygwin\bin\run.exe /usr/bin/bash.exe -l -c /usr/bin/xlaunch.exe -run /home/Eliot/config.xlaunch This works, without putting in the explicit /usr/bin/ everywhere in the .XWinrc file. BUT: I get the extra icon I don't want, this time for XLaunch rather than for StartXWin. So the extra icon seems to have to do with the bash that run.exe is starting and the fact that the bash is still there as parent to the still-running XLaunch (or StartXWin). Perhaps it is because the bash does not start the program under it in the same way that run.exe does? Regards -- EM -- 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: Issue with XWin under xlaunch
On 4/24/2012 7:54 AM, Jon TURNEY wrote: On 23/04/2012 16:04, Ken Brown wrote: I've added some code to capture stdout and stderr from these subprocesses to the X server log, and to more clearly diagnose problems which could occur while fork/exec-ing them. Would it be possible for you to also add some code for diagnosing problems with processes started from .startxwinrc? I'm hoping it might help with the problem I reported in http://cygwin.com/ml/cygwin-xfree/2012-04/msg00050.html Hmm.. not sure code is really needed. You can see the output from startxwin by running it from a terminal, or capture it by changing the shortcut which runs it to something like the following (perhaps we should do that by default) C:\cygwin\bin\run.exe /usr/bin/bash.exe -l -c '/usr/bin/startxwin.exe /var/log/xwin/startxwin.log 21' That doesn't help, but I'll reply to my original thread to explain why. I shouldn't have interjected my question into this thread. Ken -- 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: dbus-launch --exit-with-session fails when run from .startxwinrc
On 4/16/2012 9:50 AM, Ken Brown wrote: On 4/16/2012 9:44 AM, Ken Brown wrote: The following problem occurs on my 64-bit Windows 7 system but not on my XP system. I start the X server using the Start Menu shortcut [modified to add -emulate3buttons] and a .startxwinrc with the following contents: eval `dbus-launch --sh-syntax --exit-with-session` xterm Running ps in the resulting xterm window shows no dbus-launch or dbus-daemon process. But I can give the same dbus-launch command in the xterm window, and the processes start as expected. I'm attaching cygcheck output and the XWin log. My hope in reporting this is that the problem I'm seeing (and the difference between XP and Win7) is somehow related to the emacs problem I've been trying to solve: http://cygwin.com/ml/cygwin-xfree/2012-04/msg00048.html Ken P.S. You'll see in the cygcheck output that I'm running a Cygwin snapshot; but nothing changes if I revert to cygwin-1.7.13-1. I forgot to say that if I remove --exit-with-session from the command line in my .startxwinrc, then a dbus-daemon process does start. I tried modifying the X server shortcut to read C:\cygwin\bin\run.exe /usr/bin/bash.exe -l -c '/usr/bin/startxwin.exe /var/log/xwin/startxwin.log 21' as suggested in a different thread, but that provides no information. The resulting startxwin.log is virtually identical (with minor differences) to XWin.0.log. In particular, there's no indication of what's happening when .startxwinrc is processed. For starters, it would really be helpful if someone could try to reproduce my problem on a 64-bit Windows 7 system. At the moment, I don't even know if there is a bug somewhere or simply a problem with my own system. Here's the recipe: 1. Create a .startxwinrc file with the following contents: eval `dbus-launch --sh-syntax --exit-with-session` xterm 2. Start the X server using the Start Menu shortcut. 3. In the resulting xterm window, give the ps command. If things are working right, the output from ps should show a dbus-launch process and a dbus-daemon process. These processes do appear on my XP system but not on my Windows 7 system. Ken -- 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: startx with different displays
On 4/24/2012 2:58 AM, Marc Girod wrote: Larry Hall (Cygwin-X) wrote: Get rid of the real dups. You only need the one in /usr/bin. I don't know how they got there. They are not in my normal path. Somehow my procedure to run cygcheck must have injected them. I add them in neither .bash_profile nor .bashrc. Don't worry about the duplicated paths. I'm saying get rid of the actual duplicated DLLs. -- Larry _ A: Yes. Q: Are you sure? A: Because it reverses the logical flow of conversation. Q: Why is top posting annoying in email? -- 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: startx with different displays
Larry Hall (Cygwin-X) wrote: Don't worry about the duplicated paths. I'm saying get rid of the actual duplicated DLLs. Sorry, but I have none. My understanding is that the report was only the result of the duplicated paths. Running cygcheck again doesn't find duplicated DLLs. Marc -- View this message in context: http://old.nabble.com/startx-with-different-displays-tp33702991p33741843.html Sent from the cygwin-xfree mailing list archive at Nabble.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: startx with different displays
On 4/24/2012 5:12 PM, Marc Girod wrote: Larry Hall (Cygwin-X) wrote: Don't worry about the duplicated paths. I'm saying get rid of the actual duplicated DLLs. Sorry, but I have none. My understanding is that the report was only the result of the duplicated paths. Running cygcheck again doesn't find duplicated DLLs. OK, good. -- Larry _ A: Yes. Q: Are you sure? A: Because it reverses the logical flow of conversation. Q: Why is top posting annoying in email? -- 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/
