search

conservationtechlab / dencam

Polar bear maternal den observation system.
MIT License
5 stars 2 forks source link

Screensaver on a fresh install of Raspian is on and we need it off #18

Closed icr-ctl closed 2 years ago

icr-ctl commented 3 years ago

A fresh Raspian install includes a screensaver which is on by default. It is easy to disable the screensaver through the desktop environment but we would really prefer to be able to integrate disabling the screensaver into a primary setup script (that we don't yet have) along with all/any other such steps so that a person setting up a DenCam never has to interact with the desktop environment and setup can be done by invoking one script. Also would allow us to avoid having to add instructions for disabling the screensaver via the desktop environment into the README.

The question becomes how does one disable the screensaver using the CLI?

iamgarcia commented 2 years ago

I looked into this matter and found a method that works. I tested the method on my Raspberry Pi and I can vouch that it does disable the screensaver and screen blanking permanently. Having said that, I should note that the GUI preferences menu doesn't reflect the changes made in regards to the disabled screensaver and screen blanking. If this method doesn't work on another Raspberry Pi for whatever reason, then I think it's worth taking another look at the alternative method below.

Link to method: https://raspberrypi.stackexchange.com/questions/2059/disable-screen-blanking-in-x-windows-on-raspbian#2079

Link to alternate method but in the form of a script that runs at startup: https://livingthelinuxlifestyle.wordpress.com/2019/08/19/disable-screen-blanking-in-linux/

iamgarcia commented 2 years ago

I noticed in the readme file that there are different usages of the pip and python command (ex. pip or pip3, python or python3). Which version should I stick to when writing the terminal commands for the install.sh script?

icr-ctl commented 2 years ago

Within the virtual environments we recommend (and explain the setup of) we're assuming python3 so sticking within pip and python should be fine if the user is currently within the VE but it may be better to be explicit with pip3 and python3.

Note: README also calls for python setup.py install but this is deprecated now so we should use pip install for this, too.