On 2019-04-07 14:02:14 Dr. Nikolaus Klepp wrote:
> Anno domini 2019 Sun, 7 Apr 13:08:49 -0400
>
>  E. Liddell scripsit:
> > On Sun, 7 Apr 2019 15:26:26 +0200
> >
> > "Dr. Nikolaus Klepp" <office@...> wrote:
> > > 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.
> >
> > Hmmm.  Probably either something to do with the compositor not being up
> > or the root window not being available for it to draw on.  I've never had
> > any problems with conky and transparency that weren't traceable either to
> > my fiddling with compositors, or the video card on the ten-year-old
> > laptop I use as a secondary machine being poorly behaved.
> >
> > A comparison of our configs turns up some slight differences, but the
> > only one that looks at all relevant is the fact that I have
> > "own_window_argb_visual = true" set.
> >
> > E. Liddell
>
> Hi!
>
> Ok, tried "own_window_argb_visual = true", but it changes nothing.
> Compositor sounds like a good thing to blame, I'll try to figure that out.
>
> Nik
>
	My guess is that when started from .xinitrc, something in Trinity that it
needs hasn't started yet.

Leslie