|Project Name||Stars||Downloads||Repos Using This||Packages Using This||Most Recent Commit||Total Releases||Latest Release||Open Issues||License||Language|
|Autorandr||2,166||1||6 days ago||16||December 22, 2021||110||Python|
|Auto-detect the connected display hardware and load the appropriate X11 setup using xrandr|
|Lanta||40||4 years ago||12||mit||Rust|
|Experiments in creating a tiling X11 window manager in Rust.|
|Shift Shift||14||2 months ago||May 27, 2021||gpl-3.0||Go|
|Xorg keyboard switcher for two dedicated keys. LShift for Group1. RShift for Group2.|
|Nvidia Prime Switch Sddm||10||4 years ago||mit||Python|
|Draco||8||3 years ago||21||C++|
|Draco Desktop Environment|
|Appmodmap||7||3 years ago||1||C|
|Stronger Command, finer Control, more Option (and Shifty author).|
|Nvidia Prime Switch Lightdm||7||4 years ago||mit||Python|
|Nvidia Prime Switch||3||4 years ago||mit||Python|
|Linux Window Switcher||2||6 months ago||gpl-3.0||Python|
|A Python script that enables one to switch to an arbitrary window through a key shortcut. Based on xdotool X11 utility in Linux.|
Automatically select a display configuration based on connected devices
This is a compatible Python rewrite of wertarbyte/autorandr. Contributions for bash-completion, fd.o/XDG autostart, Nitrogen, pm-utils, and systemd can be found under contrib.
The original wertarbyte/autorandr
tree is unmaintained, with lots of open pull requests and issues. I forked it
and merged what I thought were the most important changes. If you are searching
for that version, see the
Note that the Python version is better suited for non-standard configurations,
like if you use
--reflect. If you use
have to use the bash version, as there is no disper support in the Python
version (yet). Both versions use a compatible configuration file format, so
you can, to some extent, switch between them. I will maintain the
branch until @wertarbyte finds the time to maintain his branch again.
If you are interested in why there are two versions around, see #7, #8 and especially #12 if you are unhappy with this version and would like to contribute to the bash version.
autorandr is available under the terms of the GNU General Public License (version 3).
Contributors to this version of autorandr are:
You can use the
autorandr.py script as a stand-alone binary. If you'd like to
install it as a system-wide application, there is a Makefile included that also
places some configuration files in appropriate directories such that autorandr
is invoked automatically when a monitor is connected or removed, the system
wakes up from suspend, or a user logs into an X11 session. Run
as root to install it.
If you prefer to have a system wide install managed by your package manager, you can
We appreciate packaging scripts for other distributions, please file a pull request if you write one.
If you prefer
pip over your package manager, you can install autorandr with:
sudo pip install "git+http://github.com/phillipberndt/autorandr#egg=autorandr"
sudo pip install autorandr
if you prefer to use a stable version.
Save your current display configuration and setup with:
autorandr --save mobile
Connect an additional display, configure your setup and save it:
autorandr --save docked
Now autorandr can detect which hardware setup is active:
$ autorandr mobile docked (detected)
To automatically reload your setup:
$ autorandr --change
To manually load a profile:
$ autorandr --load <profile>
$ autorandr <profile>
autorandr tries to avoid reloading an identical configuration. To force the (re)configuration:
$ autorandr --load <profile> --force
To prevent a profile from being loaded, place a script call block in its directory. The script is evaluated before the screen setup is inspected, and in case of it returning a value of 0 the profile is skipped. This can be used to query the status of a docking station you are about to leave.
If no suitable profile can be identified, the current configuration is kept.
To change this behaviour and switch to a fallback configuration, specify
--default <profile>. The system-wide installation of autorandr by default
calls autorandr with a parameter
--default default. There are three special,
virtual configurations called
automatically generate a configuration that incorporates all screens
connected to the computer. You can symlink
default to one of these
names in your configuration directory to have autorandr use any of them
as the default configuration without you having to change the system-wide
You can store default values for any option in an INI-file located at
~/.config/autorandr/settings.ini. In a
config section, you may place any
default values in the form
A common and effective use of this is to specify default
instance skipping the
gamma setting if using
redshift as a daemon. To implement
the equivalent of
--skip-options gamma, your
settings.ini file should look
Three more scripts can be placed in the configuration directory
(as defined by the XDG spec,
~/.autorandr if you have an old installation
for user configuration and
/etc/xdg/autorandr for system wide configuration):
postswitchis executed after a mode switch has taken place. This can be used to notify window managers or other applications about the switch.
preswitchis executed before a mode switch takes place.
postsaveis executed after a profile was stored or altered.
predetectis executed before autorandr attempts to run xrandr.
These scripts must be executable and can be placed directly in the configuration directory, where they will always be executed, or in the profile subdirectories, where they will only be executed on changes regarding that specific profile.
Instead (or in addition) to these scripts, you can also place as many executable
files as you like in subdirectories called
The order of execution of scripts in these directories is by file name, you can
force a certain ordering by naming them
If a script with the same name occurs multiple times, user configuration takes precedence over system configuration (as specified by the XDG spec) and profile configuration over general configuration.
As a concrete example, suppose you have the files
and switch from
~/.config/autorandr/docked/postswitch is executed, since the profile specific
configuration takes precedence, and
~/.config/autorandr/postswitch.d/notify-herbstluftwm is executed, since
it has a unique name.
If you switch back from
is executed instead of the
If you experience issues with xrandr being executed too early after connecting
a new monitor, then you can use a
predetect script to delay the execution.
sleep 1 into that file to make autorandr wait a second before
Some of autorandr's state is exposed as environment variables
AUTORANDR_, such as:
with the intention that they can be used within the hook scripts.
For instance, you might display which profile has just been activated by
including the following in a
notify-send -i display "Display profile" "$AUTORANDR_CURRENT_PROFILE"
The one kink is that during
reporting the upcoming profile rather than the current one.
The EDID strings in the
~/.config/autorandr/*/setup files may contain an
asterisk to enable wildcard matching: Such EDIDs are matched against connected
monitors using the usual file name globbing rules. This can be used to create
profiles matching multiple (or any) monitors.
In order for
udev to detect
drm events from the native NVidia driver, the
nvidia-drm.modeset must be set to 1. For example, add a file
options nvidia_drm modeset=1
Before running autorandr will check the environment for the
variable to check if the program is running in a Wayland session. This is to
avoid issues between usage of xrandr in Wayland environments.
If you need to run autorandr in a Wayland environment, one workaround is to
WAYLAND_DISPLAY variable before running the program, such as:
--skip-options setto skip setting properties
--listto list all profiles
--cycleto cycle all detected profiles
AUTORANDR_MONITORSvariable to hooks (by @bricewge, #106)
off, which disables all screens
--batchmode (See #87)
--panningunless it is required (See #72)
--no-blockfrom udev rule (See #61)
#) in config/setup files