Troubleshooting

Logs Tell You Everything

The logs contain initial state and configuration. All activity is logged from any source: CLI, hotplug, cfg.yaml changes etc.

It's best practice to direct logs to a file on startup e.g.

way-displays > /tmp/way-displays.${XDG_VTNR}.${USER}.log 2>&1

Please enable debug logging when raising an issue:

way-displays --log-threshold debug ...

Known Issues with Workarounds

Laptop Lid Not Detected - Permission Denied

W [10:09:44.542] WARNING: open '/dev/input/event0' failed 13: 'Permission denied'

User must be in the input group to monitor libinput events.

sudo usermod -a -G input "${USER}"

Laptop Lid Not Closed At Startup

Fixed in libinput 1.21.0.

Unusable Displays Following MODE

One or many displays may be rendered unusable after setting a MODE. This has occurred when a higher resolution/refresh than the preferred has been selected, particularly when using a HDMI cable.

It may be possible to work around this by setting WLR_DRM_NO_MODIFIERS=1. See wlroots documentation for details.

Directly

You can set it when directly starting your compositor e.g.

WLR_DRM_NO_MODIFIERS=1 river ...

Display Manager

If you use a display manager, you will need to export it from your non-login shell environment e.g. .zshenv

export WLR_DRM_NO_MODIFIERS=1

systemd Service

Set the variable directly in the appropriate environment file e.g. ~/.config/sway/env

WLR_DRM_NO_MODIFIERS=1

See (unofficial) sway documentation for more information about using sway as a systemd user service.