Created attachment 801459 [details] journalctl --since="2013-09-23" /usr/bin/gnome-session --no-pager | egrep "NetworkManager/Active" > gnome-session-NM.log Description of problem: After I enter my password and click login, gdm tends to freeze. It does nothing. At this time, I can't even access a virtual terminal to gather some data. All the virtual terminal gives me is a blinking cursor. journalctl is spewed with errors related to gnome-session/NetworkManager Version-Release number of selected component (if applicable): [asinha@ankur ~]$ rpm -qa | egrep "Network|gdm|gnome-session" NetworkManager-openconnect-0.9.8.0-2.fc20.x86_64 NetworkManager-openvpn-0.9.8.2-3.fc20.x86_64 NetworkManager-l2tp-0.9.8-2.fc20.x86_64 gnome-session-xsession-3.9.92-1.fc20.x86_64 NetworkManager-0.9.9.0-12.git20130913.fc20.x86_64 pulseaudio-gdm-hooks-4.0-3.gitbf9b3.fc20.x86_64 NetworkManager-vpnc-0.9.8.2-2.fc20.x86_64 NetworkManager-pptp-0.9.8.2-3.fc20.x86_64 gdm-libs-3.9.90-1.fc20.x86_64 NetworkManager-glib-0.9.9.0-12.git20130913.fc20.x86_64 gdm-3.9.90-1.fc20.x86_64 gnome-session-3.9.92-1.fc20.x86_64 [asinha@ankur ~]$ How reproducible: Always Steps to Reproduce: 1.Boot 2.Enter password at gdm 3. Actual results: gdm hangs. Does not login. I've waited a few minutes at times. I can't cancel or use a virtual terminal either. Expected results: Should login quickly, as expected. Additional info: It seems to be something related to NM. If I disable the NM service, it lets me login. I'm using this as a workaround: - disable nm service - boot, login - run nm service manually journalctl is full of messages related to gnome-session and NM (attached).
Created attachment 801460 [details] journalctl --since="2013-09-23" /usr/sbin/gdm --no-pager > gdm-complete.log
Created attachment 801461 [details] journalctl --since="2013-09-23" /usr/bin/gnome-session --no-pager > gnome-session-complete.log
Complete journalctl log: http://ankursinha.fedorapeople.org/F20-alpha-debug/journalctl-complete.log (To large to upload to bugzilla)
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.