开云体育

I'm trying to fix a fix for the problem, not a workaround that I already know about! :-)
Simply rerunning conky, using the method you mentioned, will run a separate instance of conky which will not fix the problem. You have to restart it - or kill it and start it, but simply restarting it as I mentioned in the original post, is simpler.

This is a known issue that I don't have a good answer for at this time. I am working on BAP 3.0.8 but a fix for Conky will probably not make it into the next release. You are correct that it will start a second instance. A simple script ran at boot could kill/restart Conky but that is only another workaround. I would prefer an actual fix. If you find a solution, please post. I would love to get this resolved.

https://github.com/km4ack/pi-build/issues/213
--