[Bug 1003822] New: GNOME desktop login fails
http://bugzilla.opensuse.org/show_bug.cgi?id=1003822 Bug ID: 1003822 Summary: GNOME desktop login fails Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome@forge.provo.novell.com Reporter: seroton10@gmail.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:48.0) Gecko/20100101 Firefox/48.0 Build Identifier: I upgraded my Leap 42.1 server/workstation to 42.2 Beta 2 using the DVD image, and it worked very well - all functionality I care about worked just like before, or better. When 42.2 Beta 3 came out, I upgraded using "zypper dup", and then graphical login to the GNOME desktop stopped working. The login screen does appear, as usual, but after I enter my password, the screen just goes black, flickers a couple of times, and then the graphical login screen reappears. Reproducible: Always -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1003822
http://bugzilla.opensuse.org/show_bug.cgi?id=1003822#c1
--- Comment #1 from Olav Reinert
http://bugzilla.opensuse.org/show_bug.cgi?id=1003822
http://bugzilla.opensuse.org/show_bug.cgi?id=1003822#c2
Dominique Leuenberger
http://bugzilla.opensuse.org/show_bug.cgi?id=1003822
http://bugzilla.opensuse.org/show_bug.cgi?id=1003822#c3
Olav Reinert
http://bugzilla.opensuse.org/show_bug.cgi?id=1003822
http://bugzilla.opensuse.org/show_bug.cgi?id=1003822#c4
Dominique Leuenberger
Created attachment 697076 [details] Journal of a GNOME login attempt
Thanks for the log; that seems to help more.
From what I gather, shell dies because one of its mandatory panel items (shell-calendar) is not coming up properly
from what I gather, you can try: rm -rf /home/olav/.cache/evolution (It's cache data, so will be re-constructed; feel free to make a backup though) If that helps, then we have some lead at least; of course this should not stop shell from working though -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1003822
http://bugzilla.opensuse.org/show_bug.cgi?id=1003822#c5
Olav Reinert
(In reply to Olav Reinert from comment #3) From what I gather, shell dies because one of its mandatory panel items (shell-calendar) is not coming up properly
from what I gather, you can try:
rm -rf /home/olav/.cache/evolution
Doing this makes no difference - behavior at login remains unchanged. Perhaps increasing the log level of GNOME would be informative? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1003822
http://bugzilla.opensuse.org/show_bug.cgi?id=1003822#c6
--- Comment #6 from Olav Reinert
http://bugzilla.opensuse.org/show_bug.cgi?id=1003822
Olav Reinert
http://bugzilla.opensuse.org/show_bug.cgi?id=1003822
http://bugzilla.opensuse.org/show_bug.cgi?id=1003822#c7
Olav Reinert
http://bugzilla.opensuse.org/show_bug.cgi?id=1003822
http://bugzilla.opensuse.org/show_bug.cgi?id=1003822#c8
--- Comment #8 from Olav Reinert
http://bugzilla.opensuse.org/show_bug.cgi?id=1003822
http://bugzilla.opensuse.org/show_bug.cgi?id=1003822#c9
Dominique Leuenberger
http://bugzilla.opensuse.org/show_bug.cgi?id=1003822
http://bugzilla.opensuse.org/show_bug.cgi?id=1003822#c10
--- Comment #10 from Dominique Leuenberger
http://bugzilla.opensuse.org/show_bug.cgi?id=1003822
http://bugzilla.opensuse.org/show_bug.cgi?id=1003822#c11
--- Comment #11 from Dominique Leuenberger
http://bugzilla.opensuse.org/show_bug.cgi?id=1003822
http://bugzilla.opensuse.org/show_bug.cgi?id=1003822#c12
--- Comment #12 from Olav Reinert
Also for completeness: does coredumpctl report any crashes at that time?
Yes, it reports that plymouthd core-dumped (see attachments). -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1003822
http://bugzilla.opensuse.org/show_bug.cgi?id=1003822#c13
--- Comment #13 from Olav Reinert
http://bugzilla.opensuse.org/show_bug.cgi?id=1003822
http://bugzilla.opensuse.org/show_bug.cgi?id=1003822#c14
--- Comment #14 from Olav Reinert
http://bugzilla.opensuse.org/show_bug.cgi?id=1003822
http://bugzilla.opensuse.org/show_bug.cgi?id=1003822#c15
--- Comment #15 from Olav Reinert
http://bugzilla.opensuse.org/show_bug.cgi?id=1003822
http://bugzilla.opensuse.org/show_bug.cgi?id=1003822#c16
Olav Reinert
http://bugzilla.opensuse.org/show_bug.cgi?id=1003822
http://bugzilla.opensuse.org/show_bug.cgi?id=1003822#c17
--- Comment #17 from Olav Reinert
http://bugzilla.opensuse.org/show_bug.cgi?id=1003822
http://bugzilla.opensuse.org/show_bug.cgi?id=1003822#c18
Dominique Leuenberger
http://bugzilla.opensuse.org/show_bug.cgi?id=1003822
http://bugzilla.opensuse.org/show_bug.cgi?id=1003822#c19
Olav Reinert
If this is indeed the case here, then RC2 comes with the cure for this issue
I'm having a hard time providing any useful information about this bug, because it is coming and going. * Even with RC1, it disappeared after a while, and login started working. * When RC2 came out, it returned (I upgraded on the day it came out). * Shortly after the RC2 release, some Gnome packages were updated, and from then on login has worked fine. So right now there is no issue. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1003822
http://bugzilla.opensuse.org/show_bug.cgi?id=1003822#c20
--- Comment #20 from Olav Reinert
http://bugzilla.opensuse.org/show_bug.cgi?id=1003822
http://bugzilla.opensuse.org/show_bug.cgi?id=1003822#c21
Dominique Leuenberger
The release version of 42.2 does not exhibit this issue - I would close the bug as resolved.
Agreed - there have been many things hinting in the direction of one of our GNOME-Shell patches (for SLE Classic) to cause this kind of issues and we should have fixed them before release (around RC2 time, as stated in comment 18) Assuming this was indeed resolved by the same patches - as the reporter could no longer reproduce it beyond that point. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com