Comment # 5 on bug 1158543 from Dr. Werner Fink

One problem seems to remain: libdbus1 aborts sddm if an second X server (which
crahses) started over display-manager service.  And this, IMHO, should not
happen due to a failed X server start triggered over dbus.  I've no idea how to
avoid this ... maybe in display-manager service the environment variable
DBUS_FATAL_WARNINGS should be set to true aka 1, then sddm and all other DM
survive the broken dbus-a API


��� display-manager.service - X Display Manager
   Loaded: loaded (/etc/systemd/system/display-manager.service; enabled; vendor
preset: enabled)
   Active: failed (Result: core-dump) since Thu 2019-12-05 14:34:51 CET; 5h
34min ago
 Main PID: 5042 (code=dumped, signal=ABRT)
    Tasks: 4 (limit: 4915)
   CGroup: /system.slice/display-manager.service
           ������17056 /usr/bin/X -reset -nolisten tcp -auth
/run/sddm/{2a148eb5-b5af-4ca6-b2af-c4d27e5f1302} -background none -noreset
-displayfd 19 -seat seat0 vt7