I ran the latest update after not having yet run the update from 14 May, so effectively ran them both at the same time. I updated from a tty using $ yay -Syu. There were no obvious problems during the update. But after a restart, conky did not appear on the desktop.
Sometimes this happens, so I opened the “Choose Conky” dialog, where nothing was checked, chose my conkies, and clicked “Apply”. Still no conky.
I checked ~/.config/conky-session.desktop and ~./config/conky/conky-sessionfile. They were both there and looked reasonably ok, so I tried starting conky from the terminal using the mb-conky-session command:
$ mb-conky-session
conky: error while loading shared libraries: libxml2.so.2: cannot open shared object file: No such file or directory
Ok. Where is libxml2.so.2? Or any libxml2?
$ ls -l /usr/lib/libxml2.so.2
ls: cannot access '/usr/lib/libxml2.so.2': No such file or directory
$ ls -l /usr/lib/libxml2*
lrwxrwxrwx 1 root root 13 May 13 08:31 /usr/lib/libxml2.so -> libxml2.so.16
lrwxrwxrwx 1 root root 17 May 13 08:31 /usr/lib/libxml2.so.16 -> libxml2.so.16.0.3
-rwxr-xr-x 1 root root 1297360 May 13 08:31 /usr/lib/libxml2.so.16.0.3
This was starting to look particularly mysterious! I recalled reading something about libxml2 in the 14 May Manjaro update forum announcement comments, so searched the thread and found this: a response to someone running a different package that was throwing the same error. It suggests installing extra/libxml-legacy, which supplies libxml2.so.2.13.8.
Thus:
$ yay -S libxml-legacy
$ ls -l /usr/lib/libxml2.so.2
lrwxrwxrwx 1 root root 17 May 1 18:42 /usr/lib/libxml2.so.2 -> libxml2.so.2.13.8
$ mb-conky-session
Success: conky starts now, but I am wondering why there is a libxml2 version mismatch–at least on my installation–and whether anyone else has encountered this yet.