I have Waldorf 64bit installed on a Dell Precision M6600 and am mostly happy with it. However I have one problem. Conky fails to start on booting. This is random behaver, many time it will start but many more times it does not. Sometimes it will start for a string of boots, then suddenly it will not start. On the whole, it fails to start more than it succeeds.
Can someone give me idears as to where to look and also how to start conky if it does not start. Lastly my conky is the standard one and is not modified or changed in anyway.
Last edited by Sailorxyz (2013-02-14 19:05:58)
What is the syntax in autostart for starting conky. Do you have a delay before it starts.
Maybe write a simple script to run / start conky and call that from autostart.
grill it | the rocky path may just be the best path
Let's assume you have just rebooted (or switched on) your computer. You log in, and #! shows up.
1) First step: open terminal and execute:
$ ps ax | grep conky | grep -v grep
(it will show if conky is running or not). Show us your output.
2) Then, if conky is running, I would kill all conkies with:
$ killall conky
3) And finally, start fresh conky in terminal:
$ conky -c <your conky config>
Perhaps, it will spill some errors or useful comments out. Show us the output.
4) As a last resort, show us your .conkyrc ...
Postpone all your duties; if you die, you won't have to do them ..
my guess would be that, for some reason, it needs some delay upon startup...
if also your ~/.config/openbox/autostart file is untouched, it should have such a part
## Group start: ## 1. nitrogen - restores wallpaper ## 2. compositor ## 3. sleep - give compositor time to start ## 4. conky ## 5. tint2 panel (\ dispup && \ nitrogen --restore && \ cb-compositor --start && \ sleep 2s && \ conky -q && \ tint2 \ ) &
try commenting out the line which launches conky and add a delayed start for it...
## Group start: ## 1. nitrogen - restores wallpaper ## 2. compositor ## 3. sleep - give compositor time to start ## 4. conky ## 5. tint2 panel (\ dispup && \ nitrogen --restore && \ cb-compositor --start && \ sleep 2s && \ #conky -q && \ tint2 \ ) & ## delayed conky start (sleep 30s && conky -q) &
Thank you to everyone who replied. #! Junkie's recomendation was spot on, insert a delay into the startup script. Did not need as much as 30 seconds though, 10 was ample.
Interseting that this problem never occured while I was useing a conventional hard drive. It only happened after I changed to an SSD.
Thanks once again for all the suggestions.