From 6260d28b8a002a401eab7511f96fd62f471dccdb Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Marco=20Trevisan=20=28Trevi=C3=B1o=29?= Date: Thu, 1 Nov 2018 03:04:50 +0100 Subject: [PATCH] login: Don't mark framebuffer devices as master-of-seat devices Currently we consider any framebuffer device as enough to have a valid graphical session, but this might lead to many false postives like in the case of framebuffer devices that have a linked drm card which is still in the process of being added, or for vesa fb, and so it doesn't ensure us that we can have a proper graphical session. Since these days we normally don't consider anything without a DRM card able to provide a full graphical session, let's not set this at this level. Drivers which can provide a graphical session with the sole fb are still free to mark any device as `master-of-seat` Fixes #10435 --- src/login/71-seat.rules.in | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/login/71-seat.rules.in b/src/login/71-seat.rules.in index 0db46adc84..1f30900392 100644 --- a/src/login/71-seat.rules.in +++ b/src/login/71-seat.rules.in @@ -12,7 +12,7 @@ ACTION=="remove", GOTO="seat_end" TAG=="uaccess", SUBSYSTEM!="sound", TAG+="seat" SUBSYSTEM=="sound", KERNEL=="card*", TAG+="seat" SUBSYSTEM=="input", KERNEL=="input*", TAG+="seat" -SUBSYSTEM=="graphics", KERNEL=="fb[0-9]*", TAG+="seat", TAG+="master-of-seat" +SUBSYSTEM=="graphics", KERNEL=="fb[0-9]*", TAG+="seat" SUBSYSTEM=="drm", KERNEL=="card[0-9]*", TAG+="seat", TAG+="master-of-seat" SUBSYSTEM=="usb", ATTR{bDeviceClass}=="09", TAG+="seat"