Hi,

I'm not quite sure what to make of this bug; I don't know of any
specific changes between conky 1.7 and 1.8 that could have possibly
caused this bug, and the fact that this bug can't be reproduced
reliably makes it even harder to pinpoint the cause.

However, as a workaround, can you try introducing a delay before
starting conky? For example, in ~/.xsession:

sleep 15 && conky

Besides that, I don't have any other suggestions. If delaying conky's
startup doesn't fix this, let me know and I'll file a bug report
upstream.

Kind regards,
- Vincent



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to