Simon Ser 21e1953b61 backend/drm: don't modeset with a NULL mode after TTY switch ... This fixes a segfault in drm_connector_set_mode (mode = NULL). This happens because we set wlr_output.enabled to true if the connector is attached to the CRTC. When the user disables an output in the wlroots-based compositor, switches to another VT (enabling the output), then switches back, wlroots sets wlr_output.enabled to true but wlr_output.current_mode is NULL. We should consider not reading properties from KMS after a TTY switch, disabling all connectors. However this may result in flickering (outputs being disabled then re-enabled). Closes: https://github.com/swaywm/wlroots/issues/1874		2019-12-30 14:32:37 -07:00
..
drm	backend/drm: don't modeset with a NULL mode after TTY switch	2019-12-30 14:32:37 -07:00
headless	output: re-introduce atomic mode, enabled, scale and transform	2019-12-30 11:21:11 -07:00
libinput	meson: Various improvements	2019-12-23 07:48:29 -05:00
multi	meson: Various improvements	2019-12-23 07:48:29 -05:00
noop	output: re-introduce atomic mode, enabled, scale and transform	2019-12-30 11:21:11 -07:00
rdp	output: re-introduce atomic mode, enabled, scale and transform	2019-12-30 11:21:11 -07:00
session	meson: Various improvements	2019-12-23 07:48:29 -05:00
wayland	output: re-introduce atomic mode, enabled, scale and transform	2019-12-30 11:21:11 -07:00
x11	output: re-introduce atomic mode, enabled, scale and transform	2019-12-30 11:21:11 -07:00
backend.c	backend: Do not attempt DRM on X11/WL failure	2019-11-18 11:53:17 +01:00
meson.build	meson: Various improvements	2019-12-23 07:48:29 -05:00