Gnome-screensaver uses standard desktop entry (.desktop) files to define the screensaver themes. How come my xscreensaver "hacks" don't show up in the gnome-screensaver configuration tool? Any screensaver theme engines that support using the environment variable XSCREENSAVER_WINDOW should work without modification.Īctually, that seems to no longer be the case in GNOME3, after commit 76d2c9ff6acf4a98bfa1569a62fafe14e89f413e gnome-screensaver only seems to support blanking.
#Xscreensaver command code#
The actual code paths through these libraries are quite small and very well tested.Ĭan I use xscreensaver "hacks" with gnome-screensaver? These libraries are a result of using DBUS, GTK+, and GConf. gnome-screensaver links to many more libraries than does xscreensaver. The screensaver daemon is currently using the GTK+ implementation of the XEmbed protocol. This way there is no transfer of grabs to cause a race condition. It maintains a keyboard grab on the toplevel window at all times.
#Xscreensaver command password#
gnome-screensaver runs the screen lock password dialog in a separate process and embeds the interface using XEmbed. translation into many languages by the GNOME Translation Project.
a secure separation of user input processing and authentication from the screen locking window.allowing a system administrator to set a mandatory policy for any setting.switching users directly from the unlock dialog.
#Xscreensaver command install#
Is there a way that I can disable the screensaver?