Yes, I saved them. Did not help.
Anyway, in the meanwhile I added GPIO buttons with SqeezeButtonPi to the
player, and, interestingly, the screensaver shows up if the power
command is triggered by the physical button, but it does not if the
power command is done over touch screen. And yes, I
Well I just cant seem to get this done.
I uninstalled and started a fresh compilation. Not being sure of how
change the permissions for user "ronnie" I googled a bit and ended up
with "sudo chown -R ronnie /opt"
That changed /opt from root to ronnie. Groups was still root so I
changed that to
I've got:
Code:
Logitech Media Server (v7.9.2, 1576909043, Sat Dec 21 07:49:57 CET 2019)
perl 5.030001 - aarch64-linux-thread-multi
Running on a Raspberry Pi 4 with Alpine Linux 3.11.2:
Code:
Linux rpi4 5.4.6-0-rpi4
Just make sure you backup changes when you make themeither from the
pCP web pages, or the piCorePlayer Applet in jivelite.
piCorePlayer a small player for the Raspberry Pi in RAM.
Homepage: https://www.picoreplayer.org
Please 'donate'
firedog wrote:
> Sorry if this has been answered, but I couldn't find any recent posts on
> the issue.
>
> Installed a clean install of v 5.0 today.
> I configured the screensaver settings to show the clock "when stopped"
> or off.
>
> But the clock never appears. The device reverts to the
Sorry if this has been answered, but I couldn't find any recent posts on
the issue.
Installed a clean install of v 5.0 today.
I configured the screensaver settings to show the clock "when stopped"
or off.
But the clock never appears. The device reverts to the homepage and also
boots up into
Man in a van wrote:
>
> decide to build as root, removed the previously built, download and
> untarred files from the home directory, did a sudo su and away we go.
> The files built as root and are in /opt
>
Building as root is never a good idea (since you could damage your
system if
Rnee wrote:
>
> Just by creating a Linux user with same name/password as the Windows
> user of my desktop, I thought of making it simple/easier.
>
As I said, I think it muddies the waters - e.g. people tend to assume
it's the "same user" when it is not, and both have the same properties
(e.g.
