diff options
| author | Marco Trevisan (Treviño) <mail@3v1n0.net> | 2018-11-01 03:04:50 +0100 |
|---|---|---|
| committer | Lennart Poettering <lennart@poettering.net> | 2018-11-06 20:02:26 +0300 |
| commit | 6260d28b8a002a401eab7511f96fd62f471dccdb (patch) | |
| tree | 5aaae0b16e131de91371d142d491d23f1d0736e8 | |
| parent | 39adc474953e84d121ef98e6cbf24da9d593d67f (diff) | |
| download | systemd-6260d28b8a002a401eab7511f96fd62f471dccdb.tar.gz systemd-6260d28b8a002a401eab7511f96fd62f471dccdb.tar.bz2 systemd-6260d28b8a002a401eab7511f96fd62f471dccdb.zip | |
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
| -rw-r--r-- | src/login/71-seat.rules.in | 2 |
1 files changed, 1 insertions, 1 deletions
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" |