http://bugzilla.opensuse.org/show_bug.cgi?id=1158543 http://bugzilla.opensuse.org/show_bug.cgi?id=1158543#c1 Dr. Werner Fink changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|opensuse-kde-bugs@opensuse. |fabian@ritter-vogt.de |org | --- Comment #1 from Dr. Werner Fink --- The dbus people want that all applications using dbus should work and therefore all errors are fatal. Therefore pelase fix sddm to enable all users to lock their screens and enable othe users to open a new session -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1158543 http://bugzilla.opensuse.org/show_bug.cgi?id=1158543#c3 Dr. Werner Fink changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |DUPLICATE Flags|needinfo?(werner@suse.com) | --- Comment #3 from Dr. Werner Fink --- OK then this is more a dupliate of boo#1151290 *** This bug has been marked as a duplicate of bug 1151290 *** -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1158543 http://bugzilla.opensuse.org/show_bug.cgi?id=1158543#c5 Dr. Werner Fink changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|DUPLICATE |--- --- Comment #5 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 -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1158543 http://bugzilla.opensuse.org/show_bug.cgi?id=1158543#c6 Fabian Vogt changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution|--- |UPSTREAM --- Comment #6 from Fabian Vogt --- (In reply to Dr. Werner Fink from comment #5)

One problem seems to remain: libdbus1 aborts sddm if an second X server (which crahses) started over display-manager service.

Why do you think that's libdbus1? sddm has:

// start display server if (!m_displayServer->start()) { qFatal("Display server failed to start. Exiting"); }

By default, qFatal calls abort() after logging. Feel free to open an issue upstream (https://github.com/sddm/sddm). -- You are receiving this mail because: You are on the CC list for the bug.