I am working on a project similar to the one at http://www.instructables.com/id/Raspberry-Pi-Wall-Mounted-Google-Calendar/?ALLSTEPS
Similarly, I need my pi to stay on constantly. I have the regular Raspbian OS installed and I am using Iceweasel browser to run a web application all day.
I have tried every single one of these suggestions from this link http://www.bitpi.co/2015/02/14/prevent-raspberry-pi-from-sleeping/
Yet the pi fails to stay on longer than 10 minutes. Any help would be greatly appreciated.
I installed xscreensaver
sudo apt-get install xscreensaver
Once installed, go to Rpi's desktop "Menu" (left top corner)
Go to preference --> screensaver.
You will see a screen saver main menu. In the mode drop-down menu, select "disable screensaver" then close the window.
Reboot the Raspberry PI.
It should work now.
You don't need to install lib, just edit lightdm
1 - Open lightdm using your prefer text editor, eg using default editor(nano).:
sudo nano /etc/lightdm/lightdm.conf
2 - Add this line
xserver-command=X -s 0 -p 0 -dpms
I recently installed Raspian Buster with Desktop (circa 2019-September) - the smaller install with the Desktop, but without the "recommended software". I found there are two settings that have to be changed as either one of them will blank the screen in ten minutes under the default settings.
set screen saver timeout to zero:
xset s 0
and set dpms (EnergyStar) to disabled:
xset -dpms
This way I haven't needed to install anything (no screensaver). It was confusing because I'd tried both items, but it wasn't until I learned they both were blanking the screen at ten minutes that I saw what was going on. As this has tested out OK, the next step for me is to put them into an autostart routine.
ps Verify your settings with
xset q
Without installing anything, official Raspberry Pi doc:
On the Console
If you are using the Raspberry Pi solely on the console (no desktop GUI), you need to set the console blanking. The current setting, in seconds, can be displayed using
cat /sys/module/kernel/parameters/consoleblank
Here, consoleblank is a kernel parameter. In order to be permanently set, it needs to be defined on the kernel command line.
sudo nano /boot/cmdline.txt
Add consoleblank=0 to turn screen blanking off completely, or edit it to set the number of seconds of inactivity before the console will blank. Note the kernel command line must be a single line of text.
https://www.raspberrypi.org/documentation/configuration/screensaver.md
Simply enter the config with sudo raspi-config and disable screen blanking in the display settings.
I've created a picture frame with a pi 3 and want to stop the screen going blank. I installed xscreensaver as in answer 22 and it's working a treat:
sudo apt-get install xscreensaver
After install, went to Rpi's desktop "Menu" (left top corner)
Went to preference ---> screensaver.
Then In mode : section, selected "disable screensaver" and closed.
Rebooted Rpi.
I had the same issue with Raspbian OS that was installed on raspberry Pi device. I just installed xscreensaver by using the following command in default Command panel.
sudo apt-get install xscreensaver
After installation is completed, Go to the menu in the left corner and select preference. First time you will see a pop up to enable xscreensaver on your screen. Just accept it. After that you can disable the screensaver.
Related
I am trying to make my raspberry pi open a set of page's automatically when i start it up in the morning but unfortunately i can't get it to work
i already have the links in chromium so if chromium can start automatically and get to the full screen mode it is solved
so the only thing that needs to happen is to automatically start up chromium
i tried to use Kiosk for it but it gave me a lot of trouble
this is the code i have right now
#chromium-browser --kiosk
If u want to start your browser in fullscreen mode at boot use the following line in terminal to edit the startup file. (if you're already in root then u dont have to use sudo)
sudo nano /home/pi/.config/lxsession/LXDE-pi/autostart
Then add the following to the startup file.
For using chromium
#chromium-browser --start-fullscreen
It is basically the same as pressing f11 but then automatically.
If u want to add an URL to this u can do that in-between the command and the argument like this.
#chromium-browser http://localhost --start-fullscreen
This will launch the browser in fullscreen in the requested URL.
I am producing a software product which runs on Raspberry Pi.
My users won't have mouse and keyboard connected to Pi.
I want to be able to upgrade the os with cli scripts by using apt-get update and apt-get dist-upgrade consecutively.
I can do that now but the problem is, after the upgrade is done. It shows this dialog box to user. I want to disable this or be able to click the ok button from the cli with a command. Do you know how can I do that? Or as a solution maybe, I can close/kill all os realted windows/dialog boxes/pop-ups. Do you know a command for this?
Thanks this is the dialog box shown after dist-upgrade is done
I have installed, on my rpi , the Operating System Raspian and when i try raspi-config boot throught the autologin-desktop start LXDE.
I would like starting the desktop of OPENBOX and uninstall the desktop of raspian.
How can be done?Thank you
I get the feeling you don't fully understand the difference between services like Openbox and Xorg.
Openbox is a window manager (much like LXDE, which is built on top of Openbox itself), so you can just apt-get install it. Whereas startx is a command from the Xorg package.
If you want to use Openbox instead of LXDE, you need to edit your .xinitrc file, located in your user folder, or edit the global xinitrc file, located at /etc/X11/xinit/xinitrc.
You'll need to replace exec startlxde with exec openbox-session.
Cursor of mouse disappear(at last pixels of screen).
For example. Now all ok.
And if I move mouse to the top of the monitor it disappear.
But at the same time I can click on buttons on top panel.
Any ideas how to fix it?
Verbatim copy (Mint commented by me) of Heath Jones (hjones014) post on launchpad which solved the issue:
I finally remedied the problem, using the xorg-edgers ppa. This is what I did -
sudo apt-add-repository ppa:xorg-edgers/ppa
sudo apt-get update
goto additional drivers (driver manager on Linux Mint) and select driver 349.16 (at the moment of writing is 355)
reboot
goto software/updates (Software Sources->PPAs on Mint) and goto the "Other Software" tab and UNCHECK the xorg-edgers ppa. I DID NOT PURGE THIS PPA.
The reason why I nixed this ppa is because after selecting driver 349, the software updater would try to pull in other updates from the xorg-edgers ppa which kept crashing my system. This allowed me to keep the driver 349 and not pull in any other updates. If you do a ppa-purge, it will also nix the driver, hence why i just unchecked it in the sources tab.
Adding the option
Option "hw_cursor" "off"
on the Device section of /etc/X11/xorg.conf solves this issue but creates other (more annoying) issues. [Disclaimer] messing with the xorg.conf can screw up your graphics and you'd be unable to log in. Proceed with caution, backup your xorg.conf and know how to log in to your system with a live CD/usb or drop to a shell that doesn't need the X server.
Also, switching to the nouveau driver solves it too.
None of the aforementioned solutions are acceptable for me. I'll keep digging and update the answer.
Yesterday I installed Teamviewer 7 on my Centos 5.8 desktop. After a reboot, am not able to see the login screen. Only a blue color screen is visible.
I read https://superuser.com/questions/403548/os-x-stuck-at-blue-screen-after-installing-teamviewer-host-and-rebooting?rq=1
But how do I do that on Centos?
I know that to login to Single User Mode, we need to press a key while the os boots up. And then type single in the cmd. And then?
Once in Single User Mode, you can try to remove TeamViewer from your system.
For example, if you have installed TeamViewer by running the rpm -ivh teamviewer_linux.rpm command, you can run the rpm -e teamviewer_linux command to uninstall it.
I don't think that the Mac OS link you've referred to can be very useful in your case.
If you peek into the teamviewer_linux.rpm (for example by running the command rpm -qpl teamviewer_linux.rpm) you won't find any "Launch Agents and Daemons", since on CentOS TeamViewer is wrapped around a Windows Emulator (wine).
By default the TeamViewer files gets installed in the /opt/teamviewer folder; the only exception is the startup script /usr/bin/teamviewer7.
Finally, the rpm post-installation script does nothing more and nothing less than create a desktop icon and add a menu entry, so I can't really understand how the TeamViewer installation could have broken your system.