[Bug 939571] New: gdm can't show up after logout
http://bugzilla.opensuse.org/show_bug.cgi?id=939571 Bug ID: 939571 Summary: gdm can't show up after logout Classification: openSUSE Product: openSUSE Distribution Version: 42.1 Milestone 1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X.Org Assignee: xorg-maintainer-bugs@forge.provo.novell.com Reporter: tiwai@suse.com QA Contact: xorg-maintainer-bugs@forge.provo.novell.com Found By: --- Blocker: --- After logout from GNOME or XFCE session, the screen remains blank without showing the login screen. Restarting via rcxdm doesn't work, as it can't take VT7. The same problem is seen also with lightdm. In the case of lightdm, lightdm process itself aborts. Meanwhile xdm seems working, it can relogin. However, "loginctl list-sessions" shows zombie user sessions. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=939571
http://bugzilla.opensuse.org/show_bug.cgi?id=939571#c1
Stefan Dirsch
http://bugzilla.opensuse.org/show_bug.cgi?id=939571
Stefan Dirsch
http://bugzilla.opensuse.org/show_bug.cgi?id=939571
http://bugzilla.opensuse.org/show_bug.cgi?id=939571#c2
Takashi Iwai
http://bugzilla.opensuse.org/show_bug.cgi?id=939571
http://bugzilla.opensuse.org/show_bug.cgi?id=939571#c3
--- Comment #3 from Takashi Iwai
http://bugzilla.opensuse.org/show_bug.cgi?id=939571
http://bugzilla.opensuse.org/show_bug.cgi?id=939571#c4
--- Comment #4 from Takashi Iwai
The problem of lightdm looks different. It's a problem that was seen on FACTORY once, the empty lightdm-default-greeter.desktop. It seems that something is incompatible regarding update-alternative. Let's track the lightdm issue in another bug entry.
lightdm problem is tracked on bug 939693. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=939571
http://bugzilla.opensuse.org/show_bug.cgi?id=939571#c5
--- Comment #5 from Takashi Iwai
http://bugzilla.opensuse.org/show_bug.cgi?id=939571
http://bugzilla.opensuse.org/show_bug.cgi?id=939571#c6
--- Comment #6 from Egbert Eich
http://bugzilla.opensuse.org/show_bug.cgi?id=939571
http://bugzilla.opensuse.org/show_bug.cgi?id=939571#c7
--- Comment #7 from Egbert Eich
http://bugzilla.opensuse.org/show_bug.cgi?id=939571
http://bugzilla.opensuse.org/show_bug.cgi?id=939571#c8
--- Comment #8 from Takashi Iwai
This could be a dupe of boo#939594.
Frankly, I don't see how this is a problem of the X Window System. IHMO, this is a gdm issue.
Yes, we can change the component to GNOME. I firstly thought it being a generic X and systemd issue because both gdm and lightdm don't work. But it turned out that the problem of lightdm is its own. And the gdm problem is its own as well. Though, a problem with xdm and loginctl still remains. (Just check loginctl output after login twice via xdm. You'll see two assigned seats.) But this can be tracked in another bug. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=939571
http://bugzilla.opensuse.org/show_bug.cgi?id=939571#c10
--- Comment #10 from Takashi Iwai
This could be a dupe of boo#939594.
Looks so. FWIW, it happens only with autologin. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=939571
http://bugzilla.opensuse.org/show_bug.cgi?id=939571#c11
--- Comment #11 from Dominique Leuenberger
http://bugzilla.opensuse.org/show_bug.cgi?id=939571
http://bugzilla.opensuse.org/show_bug.cgi?id=939571#c12
--- Comment #12 from Egbert Eich
http://bugzilla.opensuse.org/show_bug.cgi?id=939571
http://bugzilla.opensuse.org/show_bug.cgi?id=939571#c13
--- Comment #13 from Takashi Iwai
Or a DUP of bug 936028
OK, then this looks like a problem of the latest GNOME. Actually, I could reproduce the problem on Tumbleweed, too. A fresh installation of the latest Tumbleweed on KVM showed the very same buggy behavior. Also, I tested to install systemd-219 on Leap, and the problem was still present. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=939571
http://bugzilla.opensuse.org/show_bug.cgi?id=939571#c14
--- Comment #14 from Takashi Iwai
http://bugzilla.opensuse.org/show_bug.cgi?id=939571
http://bugzilla.opensuse.org/show_bug.cgi?id=939571#c15
--- Comment #15 from Egbert Eich
http://bugzilla.opensuse.org/show_bug.cgi?id=939571
http://bugzilla.opensuse.org/show_bug.cgi?id=939571#c16
Egbert Eich
http://bugzilla.opensuse.org/show_bug.cgi?id=939571
http://bugzilla.opensuse.org/show_bug.cgi?id=939571#c18
Takashi Iwai
http://bugzilla.opensuse.org/show_bug.cgi?id=939571
http://bugzilla.opensuse.org/show_bug.cgi?id=939571#c20
--- Comment #20 from Takashi Iwai
(In reply to Takashi Iwai from comment #18)
Does this also happen with original SLES-12 kernel?
The gdm problem appears with SLE12 kernel, yes.
Why it is not possible to close a duplicated file descriptor of an already open descriptor of /dev/input/event3
I haven't checked the problem of X manual start with SLE12 kernel yet, though. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=939571
http://bugzilla.opensuse.org/show_bug.cgi?id=939571#c21
Takashi Iwai
I can reproduce your problem by a manual start of X. But gdm issue is a bit different. The similar log is found in Olaf's bug entry. (there is no X log but included in journal).
To be clear: systemd-logind crash doesn't happen via gdm. I see it only with the manual start of X. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=939571
http://bugzilla.opensuse.org/show_bug.cgi?id=939571#c26
--- Comment #26 from Egbert Eich
(In reply to Takashi Iwai from comment #21)
Does this mean that this might destroy/disable the device below /dev/input/event3?
I doubt this. The Xserver dies however when the systemd-logind which has opened a device is gone. The Xserver starts if systemd-logind fails on all instances (or all but the last) as then the fallback is used all the time (or in the latter case systemd-logind isn't killed on a consecutive device open operation). (In reply to Dr. Werner Fink from comment #24)
I'd like to see a backtrace of this SIGABRT to be able to identify the function where the close_nointr_nofail() function has been called
Will see if I can attack gdb. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=939571
http://bugzilla.opensuse.org/show_bug.cgi?id=939571#c28
--- Comment #28 from Egbert Eich
Will see if I can attach gdb.
It works however the output is pretty useless due to: # zypper install systemd-logind-debug [..] Repository 'openSUSE-Leap-Debug' is invalid. [repo-debug|http://download.opensuse.org/debug/distribution/leap/42.1/repo/oss/] Valid metadata not found at specified URL therefore I won't bother to attach it. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=939571
http://bugzilla.opensuse.org/show_bug.cgi?id=939571#c30
--- Comment #30 from Takashi Iwai
http://bugzilla.opensuse.org/show_bug.cgi?id=939571
http://bugzilla.opensuse.org/show_bug.cgi?id=939571#c65
Dominique Leuenberger
http://bugzilla.opensuse.org/show_bug.cgi?id=939571
http://bugzilla.opensuse.org/show_bug.cgi?id=939571#c66
Dominique Leuenberger
participants (1)
-
bugzilla_noreply@novell.com