I am aware this is upstream problem, but maybe somebody has better solution than what I am doing.
I am using conky to output some stuff on screen even if I am using tiling WM under wayland (hyprland) and it worked well until several months ago. I am aware conky has experimental wayland support but every conky simply breaks on start many versions back. As a temporary solution I keep conky-1.20.2-2-x86_64.pkg.tar.zst which is the last version that works well. Of course this can break at any moment as system upgrades.
Any suggestion what to do except to submit ticket to upstream? I am skeptical they can do anything meaningful since their wayland related responses are very unsatisfactory.
If it does break due to mismatched libraries building the conky-1.20.2-2 package locally will fix that most of the time, as it will be compiled against the libs on your system.
Other than that I have no idea especially with the lack of any error messages posted.
I quickly installed latest conky to provide errors:
$ conky -c ~/bin/conky/conkyrc-cal
conky: FOUND: console
conky: FOUND: ncurses
conky: FOUND: file
conky: FOUND: x11
conky: FOUND: wayland
conky: '(null)' wayland session running 'Hyprland' desktop
Basically everything later than 1.20.2-2 just flashes content on screen and turns off. Latest version keeps running conky but without output to screen past the initial flash, previous versions actually quit after the last "null" line, message didn't change between the versions.
Last related conky ticked doesn't sound optimistic:
https://github.com/brndnmtthws/conky/issues/1898
Good tip about compiling myself, I'd like to avoid that but if nothing else works it will do.
Just to be clear I mean building the package locally with makepkg NOT just compiling the conky source.
It's a fairly simple process.
Yeah, got it, I am dev myself so no sweat. Just not liking to have to build but there's nothing we can do.
Conky on Wayland indeed still has many bugs.
A possible workaround is to set :
out_to_wayland = false,
artist