Great! Looks good to me. Now I just need to get rid of the second [✓] Root user check passed 
I’ll test that tomorrow morning as I need some zzzzz
No worries. Thanks for all the help/testing as usual!
I did the update today. It left the wfpiconsole folder owner and group as root. I changed them back mto PI and everything worked again. Just an fyi
Same thing here I think. I installed the update and the autostart feature doesn’t work now. I checked the permissions on the wfpiconsole folder and it’s showing root, not pi. Unfortunately, I’m not smart enough with ubuntu to know how to change the owners 
go to the location where the wfpifolder is and just issue these 2 commands, one line at each time
chown -fR pi wfpiconsole
chgrp -fR pi wfpiconsole
Sorry @chuckmc and @quarkie! This shouldn’t happen again and thanks @eric for providing the fix.
Can I check whether you updated using:
wfpiconsole update
or the complete install command?:
curl -sSL https://peted-davis.github.io/wfpiconsole | bash
If you access via the console (ssh) you have to put “sudo” in front of the commands, otherwise you do not have the necessary rights…
Hi @peter i have used the complete install command and then the user pi had no access rights to the folder “wfpiconsole”
After executing @eric 's advice everything works perfectly
Hmmmmm that’s annoying… The complete install command shouldn’t be causing this issue. Can you do me a favour? Make sure the version number in your .ini file is set back to v2.15 and try to update using the complete install command again. Do you see the same behaviour with root taking ownership of the wfpiconsole directory?
I did everything just like you asked.
The permissions on the folder haven’t changed…
Is it possible the error is related to the dist-upgrade command I performed earlier?
Thanks peter. I used wfpiconsole update.
Thanks to both of you! That solved the issue and it’s launching appropriately again.
No I don’t think so. I think the error is caused by changes I made to the install script designed to make sure the console is installed at a local level rather than at a root level. The interwebs suggest this is better practice security wise. Once I made this change I thought using wfpiconsole update would cause the error you’ve seen, while using the complete install command would avoid it. It looks like using the complete install command also causes the error though, and I cannot work out why.
On the plus side though, the fact it didn’t happen second time around is encouraging. Hopefully it will be a one time error that won’t appear again.
If you don’t mind doing one last favour, can you set the version back to v2.15 in your .ini file and run wfpiconsole update this time? Do the permissions on the wfpiconsole folder remain unchanged after the update to v2.16?
Thanks for confirming @quarkie and sorry for the issue. Hopefully you won’t see it again. I should be releasing Version 3 of the console very soon, so keep an eye out for that
No worries at all! I appreciate everything you do…you put out a great product!
I’ve done everything you asked, the permissions haven’t changed.
Great! Thanks for doing all these tests. It looks like it’s just a temporary bug, which can be easily fixed with Eric’s solution
No worries - thanks for the heads-up. Work has been crazy but just got a chance to do it, worked like a charm and I’m back up and running!
1 Like
so just to be clear “wfpiconsole update” should still be used to update?
Just getting a bit confused, with the threaded discussions on the subject. Right now I don’t think I’m going to anyway, as it appears most of all modifications relate to the rpi4 platform.
However, I wanted to know going forward.
Thanks in advance.