#Linux xscreensaver strange install#
#Linux xscreensaver strange full#
#Linux xscreensaver strange windows#

These keystrokes will switch to a different virtual console, while leaving the console that X11 is running on locked. To disable this keystroke globally and permanently, you need to set the DontZap flag in your nf or XF86Config or XF86Config-4 file, depending which is in use on your system. If the user launched X11 manually, that text console will still be logged in. This keystroke kills the X server, and on some systems, leaves you at a text console. If you care about keeping your screen locked, this is a big problem. The XFree86 X server and the Linux kernel both trap certain magic keystrokes before X11 client programs ever see them. (It doesn’t even need to be fast 3D hardware: the problem will be fixed if there is any 3D hardware at all.) With all of these changes in place, we're ready to start using our new setup.Your options are: don’t use the OpenGL display modes or, collect the spare change hidden under the cushions of your couch, and use it to buy a video card manufactured after 1998. Alternatively, we could simply stop the script from writing anything on stdout, but it's sometimes useful for debugging. We can silence the script's output by piping it into /dev/null.

#Linux xscreensaver strange windows#

# Create an array of windows by setting IFS to the list separation value: The basic idea of our script will be to get a hold of the properties of each active window, and see if any of them include the full-screen state, _NET_WM_STATE_FULLSCREEN: #!/bin/bash

#Linux xscreensaver strange full#

Let's write a little script that detects full screen, and prevents the problem! Many default Linux set ups won't take this into account, and so enable power-saving strategies when you don't want them to. While watching a full-screen youtube video, you don't usually type things or move the mouse. The assumption here is that quite often full-screen apps will be things that aren't accompanied by user interaction.

To configure xscreensaver, you can run the following in a terminal to open the setting/configuration window: $ xscreensaver-demoĬhanging any settings will create a configuration file at ~/.xscreensaver. Add something like the following to your i3 config: bindsym $mod+Control+l exec xscreensaver-command -lock I like CRTL + ALT + L for this, but you can set to to whatever you'd like by substituting other keys in the pattern. While we're at it, why don't we also set up a key combination to lock the screen. Add the following like to your i3 config, which by default is at ~/.config/i3/config, to silently start it in the background: exec -no-startup-id xscreensaver -no-splash In order for to start xscreensaver when i3 loads, we need to add an invocation to i3's config.

#Linux xscreensaver strange install#

To start, we'll need to install it: $ sudo apt update In this tutorial we'll install a screensaver/locker called xscreensaver, and write a small script to detect full screen and prevent your screen from going dark! We'll improve our security and our general computing experience at the same time! Setting Up xscreensaver: It's also quite possible you've discovered that during some activities, like watching full-screen videos, your screen dims, or goes to sleep. Initially after installing i3, there's no screen locker set up (though i3 does ship with such software). To that end, it's a good idea to have a screensaver/locker! For a variety of reasons, many of which are not directly a result of security-mindedness, we resist providing information to strangers. We divulge enough information as it is and there's no need to make it any easier for a would-be attacker or opportunist of fortune. Operational security rule 1 - and probably 2, 3 and then some - is to say nothing.