Please, can anyone tell us the recommended way for doing the update?
Click on my Avatar
Not very helpful the answer.
How can i do the update to 2.x without a fresh volumio install?
Uninstall existing peppymeter plugin 1.5 from gui is not working.
I usually use filezilla to delete the following folders :
/data/INTERNAL/peppy_screensaver
/data/plugins/user_interface/peppy_screensaver
/home/volumio/peppy_screensaver
after reboot it will clean uninstall the old peppymeter,
then you can install the new vsesion as guide.
1 Like
@dewen: This works perfectly! Updated now to 2.2.1
Thank you
this cannot be removed. There are only skins there
REMEMBER You need to install the fresh version!! What you’re doing isn’t helping. You will still have the old version of pygame
Your pygame version is still 1.94. You must have version 2.6
you do not believe? Check pygame version
First, the plugin seems to work porperly. The screensaver starts fine and the animation works as expected.
@Gelo5: I do not want upgrage from a previous version < 1.5.0, but my version = 1.50
So wthat i have to do, if i have version 1.5.0 and not below?
How to update from pygame 1.9.4 to 2.6.0?
Only fresh installation.
First check pygame ver. via SSH (write):
python3
Click ENTER and next write
import pygame
Click ENTER
Seems ok
What i did to install pygame 2.6.0:
cd /home/volumio/peppy_screensaver/dependencies
sudo tar -xzf pygame2.tar.gz -C /usr
reboot
I saw the tar file (pygame2.tar.gz) also in version 1.5. I did a fresh install with version 1.5 some weeks ago. So it was already present. So the way with deleting the folders, reboot and install peppymeter 2.2.1 the normal way was successful.
the command is correct.
@2aCD advises to do this:
1.uninstall the old version of peppy screensaver
2.remove the old pygame folder from here: /usr/local/lib/python3.7/dist-packages/pygame…
3.install new peppy screen saver
That’s the best way without factory reset.
Uninstall from the plugin screen was the first try before i did any other things, but it has never worked
only for version less than 2.0. Now everything works properly
Good news, Thank you, i will test it if a version > 2.2.1 is avaiable