In my experience with using Conky w/compositing, you need to have a delay in your Conky startup script to give the compositor time to get up and running; here's my Conky startup script:
- Code: Select all
#!/bin/sh
# click to start, click to stop
if pidof conky | grep [0-9] > /dev/null
then
exec killall conky
else
sleep 18
exec conky -c ~/Scripts/conkyrc.time &
exec conky -c ~/Scripts/conkyrc.weather &
exec conky -c ~/Scripts/conkyrc.system &
exec conky -c ~/Scripts/conkyrc.wireless &
exec conky -c ~/Scripts/conkyrc.keys
fi
Note the "sleep 18"; this makes Conky wait 18 seconds after login to launch, (which is not very long, a bit after the desktop and panel are up). You can play w/this number to suit your needs.
BTW, you can remove the sleep command and use this script for a Conky start/stop switch, either as a desktop/panel launcher, or assign a key command to it...
Edit: if you're using Nautilus, Nautilus may be drawing a desktop on top of everything; in that case, I'd disable the Nautilus desktop. I don't remember how off hand, but I'm sure Google will have plenty of how-tos.
If you're NOT using Nautilus, but are using DropBox, (I'm not), see
this thread...