… conky is displayed in Arch again, just after login as expected:
I don’t actually know what happened, and what’s the cause that by now I don’t have to restart conky to be displayed (I used Brenden Matthews’ recommended one-liner ‘killall -SIGUSR1 conky’ to do just that until now). And I have to admit that even after all those years in Linux, I still don’t exactly understand Gnome’s initialisation process, with its ‘mutter’ (Gnome’s implementation of the Wayland display server) and so on. What I noticed was that I’ve got extension updates in Gnome, both in Debian as well as in Arch, but that was for the GSConnect extension, which shouldn’t have much to do with how the screen is rendered in my opinion – but as I said, what do I know?
Okay, time to re-edit my (closed by others) bug in Arch which I mentioned in my August post, and to also tell Brenden via Element/Matrix. I’m glad that it works now, even if I still don’t understand why.
And like always, thanks for reading.
P.S.: Update, from less than half an hour later: after a few reboots and re-logins into Gnome on Arch, the behaviour is back to what it was before – meaning that conky is running (I see it with ‘ps waux | grep conky’, but I have to restart it with ‘killall -SIGUSR1 conky’ to have it displayed. Weird (as in fishes)…
And another update, from 2 days later: it worked again for the last two days, and I have no idea why (yet). But whenever I log into Arch, conky is there – displayed as it’s ought to be, like in the picture above. So this will be my last addendum on this case, except if I find out what caused all of this. So, like two days ago:
Thanks for reading.