I should probably explain:
Weston is a Wayland compositor, but it appears Conky's error message is
about wanting an X11 compositor feature that it thinks is missing. In a
Wayland session, X11 composition is provided by 'Xwayland'. So this bug
is somewhere between Conky and Xwayland.
This is only
Weston is a compositor, and it is the reference compositor for Wayland.
The problem you describe in Weston sounds to me like Conky is using X11
and complaining about the Xwayland layer it is communicating through. So
this might be a bug in Xwayland or Conky. Either way it appears to
already have a
Yesterday evening I upgraded my laptop to Ubuntu 20.10, so today I tried
the same on my HP Elitebook 8460p laptop based on an i5-2520M and there
conky displayed as I expected. Also I had no flickering of top-bar and
Ubuntu dock with VMs or videos in full screen.
By the way that flickering also occ
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
You can try:
sudo apt install weston
and then log into Weston instead of GNOME. If it works in Weston then we
have a GNOME bug, otherwise it is a Conky bug.
** Changed in: conky (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
I do not expect the error is in conky:
1. The error does not appear, when I login with xorg. The error did not appear
in 21.04.
2. The conky window is of course somewhat outside of the standard application
windows; It has no windows boundaries, the background of the window is
transparent and it
