Hi all! I try to get a transparent background with conky, but somehow I need dirty tricks to make it going: When I start conky from .xinitrc ("sleep 15; conky -d"), the background is blue and stays blue when TDE is running. Conky writes text on that blue background, but never erases it, so it gets unreadable after some time. Switching to another desktop and back again does not change this. The behaviour is the same without delay, so that TDE starts in parallel and twin comes up after conky. When I start conky from .trinity/Autostart/<something>.desktop - which calls only "sleep 15; conky -d", then the background is black and stays black, conky erases it before writing. Switching to another desktop and back again gives a pseudo-transparent background in conky. When twin comes up after conky, then the background of conky is as above (blue without erase). I have put the second way including switching desktops into a file that's called from TDE autostart, so things basicly work. But what I do not understand: what is the difference from calling conky from .xinitrc to calling it from .trinity/Autostart? And what chages, if twin comes up before/after conky? I'm quite sure that this is TDE specific, 'cause when running fvwm I do not observe this. And it looks like it is OS agnostic, I see the same thing happen on FreeBSD, too. Nik -- Please do not email me anything that you are not comfortable also sharing with the NSA, CIA ...