HD Install :: .xinitrc not running script

After starting X, press Ctrl+Alt+F1 (Alt+ one of the other F keys depending on your setup to return to X) and look to see if there are any error messages listed from the xinit script. You can use Alt+PageUp if you need to scroll up.

I think it's very strange that you can run cron_start_frame.sh from a terminal window, but the very same command doesn't work from .xinitrc

I tried the alt-ctr-f1 and all I see is a bright blue screen???

alt-ctrl-f2 brings me back to my desktop, all the other combinatoins (f3,f4...) are blue screens.

I am thinking maybe I need to reinstall DSL, but I am so close to being done, I hate to start over again, but then, I too don't understand why the script runs from a shell but not from .xinitrc

Quote (mikshaw @ Oct. 28 2007,15:49)

Any other way to scroll up? (page up, arrows, etc., don't work)

I'm still curious whether it's the particular script or something about cron that doesn't work from .xinitrc (if nobody else has cron loaded, I could experiment when I have time).

Edit: oh....just saw the script; I thought this was related to cron...guess not.. The problem is probably that your app, FEH (or components), isn't loaded correctly prior to running the script; so just run the script after the desktop is fully loaded...no problem.

Quote (jpeters @ Oct. 28 2007,23:14)

Edit: oh....just saw the script; I thought this was related to cron...guess not.. The problem is probably that your app, FEH (or components), isn't loaded correctly prior to running the script; so just run the script after the desktop is fully loaded...no problem.

I thought of that also... I did put a & at the end of the fluxbox and put flid=$!

on the next line I put a wait $flid

then put the lines in to run the script.

No change.

Quote

Any other way to scroll up? (page up, arrows, etc., don't work)

My bad. I said Alt+PageUp, but it's Shift+PageUp. In either case, though, it hadn't occured to me that this doesn't work when there is an application currently running in the tty. Maybe there is another way, but I don't know it.
Personally I redirect output to a file and tail it, so any error messages appear in aterm after X has started (if successful, otherwise I look in the log file).

I still don't have a good idea, but I stress the importance of finding specific error messages. Until you know the source of the problem, you won't be able to find a solution.

Next Page...
original here.