#cli #xrandr #gnome #wayland #displays

bin+lib gnome-randr

A reimplementation of xrandr for Gnome on Wayland

2 releases

0.1.1 Oct 26, 2021
0.1.0 Oct 26, 2021

#538 in Configuration

Download history 48/week @ 2023-08-09 46/week @ 2023-08-16 49/week @ 2023-08-23 24/week @ 2023-08-30 159/week @ 2023-09-06 103/week @ 2023-09-13 82/week @ 2023-09-20 34/week @ 2023-09-27 13/week @ 2023-10-04 43/week @ 2023-10-11 18/week @ 2023-10-18 26/week @ 2023-10-25 27/week @ 2023-11-01 20/week @ 2023-11-08 25/week @ 2023-11-15 63/week @ 2023-11-22

141 downloads per month

MIT license

1.5K SLoC


A reimplementation of xrandr for Gnome on Wayland, especially for systems that don't support wlr-output-management-unstable-v1 (e.g. Manjaro). Written ground-up in rust for performance. This is also my first project in rust, so any suggestions are welcome!


gnome-randr-rust uses the dbus object org.gnome.Mutter.DisplayConfig. See https://wiki.gnome.org/Initiatives/Wayland/Gaps/DisplayConfig for the original proposal, although the specification listed there is somewhat out of date (checked via dbus introspect on Gnome shell 40.5). A better (commented) XML file is listed in the gnome-monitor-config project here.

The GetCurrentState method is used to list information about the displays, while ApplyMonitorsConfig is used to modify the current configuration.


This project was heavily inspired by xrandr (obviously) and also gnome-randr. Sadly, gnome-randr.py appears to be broken as of my gnome version (40.5) when trying to modify display configurations.

gnome-randr.py is also slower than my rust reimplementation: querying the python script takes about 30ms on my 3-monitor system, while the rust implementation takes about 3ms (xrandr takes about 1.5ms, but is also displaying different information due to limitations in xrandr's bridge.)


~160K SLoC