Comment 5 for bug 1947185

The Weston try out is irrelevant. In Weston Conky refuses to start and gives an error message about the display and it does it all the time. I use transparency and for that, conky requires a compositor, see the following text about that setting:

own_window_argb_visual
    ARGB can be used for real transparency, note that a composite manager is required for real transparency.

Weston does not have a compositor, so it does not run at all.

I run Ubuntu 21.10 also in a Virtualbox VM since 5 months and there Conky displays normally. Everything displays fine.

Yesterday evening I upgraded my laptop to Ubuntu 21.10, so today I tried the same on my HP Elitebook 8460p laptop based on an i5-2520M and there conky displayed as on the Ryzen desktop. It only displays, when started for the second time.

What is the difference between conky on real hardware and conky in a VM?

The reporting of conky after the starts is different.
On the real hardware it starts the first time as:
- conky: desktop window (b4) is root window
On the VMs and
on the real hardware after the second time it starts as:
- conky: desktop window (800014) is subwindow of root window (b4)

The root window is not displayed on the desktop and that subwindow is displayed