![]() The only way to power that stuff back up, though, is to cycle the main power to the board or reset the SOC (or PMIC for later models). A sub-process is launched for each one running a graphics demo, pointed at the appropriate window. xscreensaver & xscreensaver-settings HOW IT WORKS When it is time to activate the screensaver, a full-screen black window is created that covers each monitor. This is what happens when the OS is shutdown properly (eg. You configure it with the xscreensaver-settings (1) program. Not 100% true, since all models can have the SoC or significant parts thereof powered off, in which case the "power state" of the device could be said to have changed.Also, I have it on a 3.8A hub and the only thing plugged directly into the pi's usb is a "nano"-size wifi dongle. Screen Saver: prefer blanking: yes allow exposures: yes timeout: 0 cycle: 600. However, I make pretty light use of it too, maybe occasionally there is a big download, etc., but not constant traffic (the more it's accessed the more opportunities there are for something to fail, so I can't say how reliable it would be serving a cafe full of people all day). 1 Answer Sorted by: 4 I'm playing in the same corner right now but I want to turn off the blank during the day and let it happend off working hour so I have the info on hand, here it is. I use this methodology to ensure the connection stays up peeking at the current log, it's had to reconnect itself only twice in the past 48 hours. If it's any consolation, I use the pi headless on a WLAN and don't turn it off very often, and it's been pretty flawless. You'd see lots of evidence that in /var/log/syslog or /var/log/messages. You may want to look at your logs to see if anything else has been going on during the network downtime - eg, (I'm speculating), if you have stuff attached to the usb ports that is near the limits of the pi's 150 mA output, that thing may intermittently fail, and if it's a wifi dongle, the system will then have to wait until the interface reappears. So whatever your problem is, that is not it. However, the "power state" of the hardware is still the same (because it only has one state, on). When you shutdown the system, the software stops, meaning there is now no way to get it to do anything again. There's either power (plugged in), or there isn't (not plugged in). It does not have a sleep or suspend mode. Logout or reboot for all changes to take effect.The raspberry pi hardware has no power management capability. If you want to manually lock the screen with the keyboard combination CTRL+ ALT+ L then you will need to run the following to repoint the old gnome-screensaver lock to xscreensaver sudo ln -s /usr/bin/xscreensaver-command /usr/bin/gnome-screensaver-command Now to start the xscreensaver daemon on login you need to search in Dash for startup applicationsĬreate a new entry running the command xscreensaver -nosplash Now start the xscreensaver configuration tool - from a terminal: xscreensaver-demoĬlick OK to both prompts asking to turn-off Gnome Daemon and to start xscreensaver-daemon respectively. Now remove gnome-screensaver sudo apt-get remove gnome-screensaver Potential workaround - installing xscreensaver sudo apt-get install xscreensaver xscreensaver-gl-extra xscreensaver-data-extra ![]() However, at the time of writing, no implementation has been started. The Canonical Devs thought it was a useful idea to continue and raised a blue-print for implementation in Oneiric.Ī few ideas were raised such as a Compiz specific implementation or reusing a Lubuntu/Xubuntu screensaver implementation. The replacement screensaver is just a blank screen. The Gnome 3 Devs dumped the old gnome-screensaver.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |