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
..
atomic.c	Add -Wmissing-prototypes	2019-11-20 02:05:03 +00:00
backend.c	backend/drm: don't modeset with a NULL mode after TTY switch	2019-12-30 14:32:37 -07:00
cvt.c	backend/drm: add support for custom modes	2019-10-27 10:46:47 -04:00
drm.c	backend/drm: don't modeset with a NULL mode after TTY switch	2019-12-30 14:32:37 -07:00
legacy.c	Add -Wmissing-prototypes	2019-11-20 02:05:03 +00:00
meson.build	meson: Various improvements	2019-12-23 07:48:29 -05:00
properties.c	backend/drm: check format when scanning out DMA-BUF	2019-06-07 09:06:11 -04:00
renderer.c	Refactor EGL/GL API loading	2019-12-20 01:03:34 +00:00
util.c	backend/drm: add BenQ to manufacturer list	2019-12-11 08:18:45 -05:00