http://bugzilla.suse.com/show_bug.cgi?id=1142492 http://bugzilla.suse.com/show_bug.cgi?id=1142492#c1 Franck Bui changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fbui@suse.com Assignee|systemd-maintainers@suse.de |fabian@ritter-vogt.de --- Comment #1 from Franck Bui --- (In reply to Jiri Slaby from comment #0)

Or is this a bug in /usr/lib/X11/display-manager script of xdm?

I am using sddm as display manager.

sddm.service has: [Service] ... Restart=always so it's expected that systemd tries to restart it. Perhaps "always" is not the best choice and another value might be more appropriate (see systemd.service(5)). Now systemd also offers some protections against such restart infinite loop through the StartLimitIntervalSec= and StartLimitBurst= options (systemd.unit(5)) but in this specific case the default values for these options (10s / 5) are not appropriate as restarting sddm takes at least 2 seconds. So yes sddm.service should be improved to handle gracefully such cases, therefore reassigning to sddm maintainer. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1142492 http://bugzilla.suse.com/show_bug.cgi?id=1142492#c3 Jiri Slaby changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(jslaby@suse.com) | --- Comment #3 from Jiri Slaby --- (In reply to Fabian Vogt from comment #2)

(In reply to Franck Bui from comment #1)

...

So yes sddm.service should be improved to handle gracefully such cases, therefore reassigning to sddm maintainer.

I opened a PR upstream: https://github.com/sddm/sddm/pull/1184

However, in openSUSE sddm.service is not used by default, as we have display-manager.service. Which one is used here?

● display-manager.service - X Display Manager Loaded: loaded (/usr/lib/systemd/system/display-manager.service; enabled; vendor preset: enabled) ● sddm.service - Simple Desktop Display Manager Loaded: loaded (/usr/lib/systemd/system/sddm.service; disabled; vendor preset: disabled) So the former. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1142492 http://bugzilla.suse.com/show_bug.cgi?id=1142492#c5 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium Status|NEW |IN_PROGRESS --- Comment #5 from Stefan Dirsch --- Ok. Just to give you some background. Once upon a time code was added to xdm not to try more often than 3 times to start an Xserver and fail completely otherwise, so the Linux console got accessible again. This code has been extracted and adjusted/added to kdm and gdm. Not sure about other displaymanagers at this point. I thought it would exist also in sddm. Maybe it has been removed for some reason. Anyway, using StartLimitIntervalSec=30 StartLimitBurst=2 in [Unit] section of systemd service file looks promising to me. Let's give it a try. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1142492 http://bugzilla.suse.com/show_bug.cgi?id=1142492#c7 --- Comment #7 from Stefan Dirsch --- @Jiry ping! -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1142492 http://bugzilla.suse.com/show_bug.cgi?id=1142492#c9 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- Component|X.Org |KDE Workspace (Plasma) Summary|display-manager is |Xserver is restarted like |restarted like mad on crash |mad on crash by sddm QA Contact|xorg-maintainer-bugs@forge. |qa-bugs@suse.de |provo.novell.com | --- Comment #9 from Stefan Dirsch --- Ok. As I already expected in comment #6. sddm isn't failing, it's the start of the Xserver, which fails. Therefore it doesn't help to limit the times sddm is failing. This needs to be fixed inside sddm. My guess is, that it has never been implemented. I know it was in kdm and gdm. Back to KDE component. Jiry, as workaround you can use another displaymanager, which still supports this feature. xdm and possbily also still gdm. And maybe also others ... -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1142492 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sndirsch@suse.com -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1142492 http://bugzilla.suse.com/show_bug.cgi?id=1142492#c11 --- Comment #11 from Stefan Dirsch --- Hmm. Which intel GPU are you using? xf86-video-intel may still be the right/recommended driver, if it's rather old. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1142492 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- CC|sndirsch@suse.com | -- You are receiving this mail because: You are on the CC list for the bug.