Gnome login hangs F20 after fedup upgrade

[David Highley]

"Mateusz Marzantowicz wrote:"
> 
> On 22.12.2013 22:49, David Highley wrote:
> > "David Highley wrote:"
> >>
> >> "Mateusz Marzantowicz wrote:"
> >>>
> >>> On 21.12.2013 20:40, David Highley wrote:
> >>>> We upgraded a test system to Fedora 20 using the fedup process. There
> >>>> were 60 packages that were left from Fedora 19 after the upgrade that
> >>>> were subsequently fixed by doing a yum distro-sync. Since the upgrade we
> >>>> are not able to login into a Gnome session. We select the user in the
> >>>> greater and it prompts for the pass word. After that it goes to the
> >>>> grayed background and hangs leaving the user session in a hung state
> >>>> where you have cursor control but the session setup does not get to the
> >>>> point where you can select anything.
> >>>>
> >>>> We have checked the logs and see nothing in the logs that indicate an
> >>>> issue. The other change noticed is the monitor never goes to sleep when
> >>>> the greater screen is active.
> >>>>
> >>>
> >>> Does systemctl restart gdm.service from text shell help you restore
> >>> system responsiveness? It might be some problem with gnome-shell or
> >>> Xorg, I'm facing similar behavior from time to time on fresh installation.
> >>
> >> Same recovery as doing init 3 init 5 you get back to the Gnome greater
> >> screen with the session ended. We have looked at the Xorg log files and
> >> see nothing wrong in them. Our case is not intermittent. We have tried
> >> both VGA and HDMI connections and get the same results. We have also
> >> reviewed dmesg and the /var/log/message log files. Nothing seems to get
> >> logged. We have checked for selinux avc issues and tried login in
> >> selinux Permissive mode. Second check just now indicates that a
> >> systemctl restart gdm.service gets us back to the Gnome greater screen
> >> but then we were not able to select a user for login.
> >>
> > 
> > We see by using journalctl -f | less
> > That the shell fails to register before a timeout occurs and that there
> > is a kernal pool segfault and a core dump. We have not been able to
> > determine if they are all related. Except they happen close together.
> > 
> 
> It might be coincidence but it's worth investigating it. I don't
> experience any core dumps when having issues with gnome-shell but who
> knows how it's in your case.

Since we saw the complaint about a timeout we changed the nsswitch.conf
file to look at files before dns and stopped autofs and hardmounted the
home directories. We have now upgraded a second system which has the
same issue. Yet no fix found.

> 
> 
> 
> Mateusz Marzantowicz
> -- 
> users mailing list
> users at lists.fedoraproject.org
> To unsubscribe or change subscription options:
> https://admin.fedoraproject.org/mailman/listinfo/users
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
> Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
> Have a question? Ask away: http://ask.fedoraproject.org
>