+++ This bug was initially created as a clone of Bug #842204 +++ NEW UPDATE FOR F18 -- It is now MUCH worse in that the system fails to login as a user every time... have not had a successful login under release F18. previous workaround under f16 of alt-F4 to close the message window, no longer works. KDE session works. Version information update - Gnome shell 3.6.2.6.fc18 Can the severity be updated to severe ? =================================== Description of problem: After a reboot there is a 5 minute delay before a user can successfully login. Attempting to do so before this gets an "Oh no! Something has gone wrong." error Version-Release number of selected component (if applicable): gnome-shell x86_64 3.2.2.1-1.fc16 (I think) How reproducible: Every time a reboot occurs, the first two(sometime three) logins will produce the error... Steps to Reproduce: 1. reboot machine (from initially windows or from linux) 2. login immediately (twice) 3. Third time (usually) normal login occurs. (Normal login occurs is the machine is left for about 5-10 minutes) So this is something time based that fixes it self !!! Actual results: <delay> <screen blink then goes black with....> "Oh no! Something has gone wrong. A problem has occurred and the system can't recover. Please log out and try again." Click OK/button <flash screen black> <flash see the title bar of normal login> <flash screen black> back to normal login Expected results: Normal Gnome 3 desktop after login Additional info: From google and bugzilla searching found a number of occurrences that had been fixed by various means. None worked here. These machines are installs of f16 not upgrades. Caribou not i686 Alt F4 didn't have any effect to make the error go away. Don't have selinux enabled. We use ldap authentication for login... but a root login(locally authenticated) also has the same problem. The root login is a new account and default creation for F16..(so no messy old dot files around) This started sometime through F16 in 2012-- but unknown as to when it was noticed. Have tried to track it but not sure what or where... "Something has gone wrong" is not very informative --- Additional comment from Fedora End Of Life on 2013-01-16 12:28:52 EST --- This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. 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 WONTFIX if it remains open with a Fedora 'version' of '16'. 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 prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 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 to click on "Clone This Bug" and open it against that version of Fedora. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
A followup to this error with further information... We can't get a "normal" user to login. "root" can login --even though it gets the error. I tried a normal user with a completely clean dotfile setup (rm -rf .??*) and the error still occurs. The .xsession-errors of the normal user is attached.
Created attachment 684654 [details] .xsession-errors showing critical errors on login attempts
My problem is almost similar to that of the OP but I have am unable to log in after multiple tries and my .xsession-errors remains 0 bytes. Is there anything you want me to post to help figure out the problem? As a workaround, I can start a KDE session.
Some additional info: I upgraded from FC17 to FC18 via FedUp (detailed in http://fedoraproject.org/wiki/FedUp using the network preparation (section 4.1.1)) In FC17, my Gnome session was working fine. After the first failure in FC18, I removed ALL gnome-shell extensions, to no avail.
My colleague here has found our cause(by numerous reinstalls til we got the lines that caused it). We have kept the post install configuration from year to year. Historically we replaced the /tmp directory with a symlink to /var/tmp (to keep all the files in one area.) ie in %post we had rm -rf /tmp ln -sf /var/tmp /tmp In F18 that causes a chain of events that produces the "Oh No" problem. If we remove that change to /tmp ..All works.. If we have that change, all user logins always fail.
(In reply to comment #5) > My colleague here has found our cause(by numerous reinstalls til we got the > lines that caused it). We have kept the post install configuration from year > to year. Historically we replaced the /tmp directory with a symlink to > /var/tmp Unfortunately this doesn't work for me since my /tmp is not a symlink to /var/tmp. They are 2 separate directories.
Here is some additional information I was able to gather: Each time, after I try to login to a Gnome GUI that fails and I log into a KDE GUI, abrt shows me a couple of failures: * tracker (killed by signal 6, SIGABRT) * nepomuk-core (killed by signal 11, SIGSEGV) * xorg-x11-server (killed by signal 11, SIGSEGV) * kernel (Unfortunately, kernel is tainted due to VirtualBox and NVidia driver) Can someone please let me know what information I should collect to post here in order to help out and see if anything can be found to solve this issue?
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora 'version' of '18'. 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 prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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 to Fedora 18's end of life. 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 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.