I, too, have forsaken the startxwin.bat startup script in favor of a home-grown script much like the one you've shown below. However, initially I ran into problems similar to what you describe. I attributed it to the fact that you can't count on the "sleep 2" command to be long enough for XWin to start. I then found that the xinit command has a way of determining that XWin is up and running before trying to launch any xclients. To use it, move most of the commands into the file ~/.xinitrc. For instance:
xwinclip & python /home/geek/bin/workspace_indicator --size 200 & xv -root -maxpect -quit $HOME/images/gazebo.jpg xrdb -merge $HOME/.config/Xresources pwm Note that I left out the stuff that sets the DISPLAY to :0, xinit takes care of that for you. Also note how I moved "pwm" to the end and left it in the foreground, as per the recommendations in the xinit documentation. To run it, use this command-line: xinit -- -fullscreen -once -terminate -nowinkill -unixkill \ -auth $HOME/.Xauthority Hope this helps. >From: "Brian Gallew" <[EMAIL PROTECTED]> >To: <[EMAIL PROTECTED]> >Subject: XWin doesn't always start "right"' >Date: Thu, 16 May 2002 07:24:07 -0400 (EDT) > >I'm running cygiwn/xfree on a ThinkPad under XP. Generally speaking, >the first time that I start X after booting, the window doesn't get >drawn. So, I kill it and restart X and then it works. I'm very >confused about why it behaves this way. If it matters, here's the >script I'm using to start X: >#! /bin/bash >cd /home/geek >export DISPLAY=:0 >/bin/rm -rf /tmp/.X11-unix > >run XWin -fullscreen -once -terminate -nowinkill -unixkill -auth >$HOME/.Xauthority :0sleep 2 >run xwinclip >run pwm >export DISPLAY=:0.0 >run python /home/geek/bin/workspace_indicator --size 200 >sleep 2 >xv -root -maxpect -quit $HOME/images/gazebo.jpg >xrdb -merge $HOME/.config/Xresources _________________________________________________________________ Send and receive Hotmail on your mobile device: http://mobile.msn.com
