Dear Jon (et al.) -- Perhaps this problem report was
buried in the discussion of the taskbar appearance
issue and was therefore overlooked
When I start XWin using xlaunch, trying to the start
programs from the .XWinrc popup menu (right-click on
the X icon, left-click on the program's entry i
On 11/04/2012 11:23, Eliot Moss wrote:
> When I start XWin using xlaunch, trying to the start
> programs from the .XWinrc popup menu (right-click on
> the X icon, left-click on the program's entry in the
> menu), programs do not start. I get only those programs
> started by my script that I told x
On 4/23/2012 9:51 AM, Jon TURNEY wrote:
> On 11/04/2012 11:23, Eliot Moss wrote:
>> When I start XWin using xlaunch, trying to the start
>> programs from the .XWinrc popup menu (right-click on
>> the X icon, left-click on the program's entry in the
>> menu), programs do not start. I get only those
Ok -- by perusing the log I figured it out ...
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 attac
On 4/23/2012 12:41 PM, Eliot Moss wrote:
Ok -- by perusing the log I figured it out ...
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
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: xt
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 prob
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.xl
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 ad
