Fedora Account System
Red Hat Associate
Red Hat Customer
Created attachment 614402 [details] /var/log/messages for failing session Description of problem: Apologies if I've guessed the wrong component. Please redirect if so. Version-Release number of selected component (if applicable): 3.4.1 How reproducible: 100% Steps to Reproduce: 1. Boot Machine (F17) and wait for login screen Actual results: "Oh no! Something has gone wrong..." Expected results: Machine boots. Additional info: I'm familiar with similar problems on other machines, but they are all either old hardware, or virtual machines, and probably really do fail to complete gdm initialisation within 60 seconds. This machine is a reasonably high-end server (maybe 3 years old), so that's unlikely to be the problem (plus it only started happening in the last week). I'm attaching /var/log/messages with gdm debugging turned on; I can't see anything useful, but perhaps you will. It's a full boot trace; gdm logging starts at 18:40:59, and by 18:41:41, gdm was displaying the "Oh no" message. I actually use lxde for terminal sessions on this machine (but presumably, the login manager doesn't know that, so it shouldn't affect anything). The machine runs OK in runlevel 3 (and I can login via nx and get a perfectly good lxde session). The problem seems to be limited to the gdm greeter.
I have a similar problem, just the "Oh no" screen appears after I press enter (when my login name is preselected) to get the password prompt. "init 3; xdm" works for me on my F17 laptop. (A side note: the stupidity of the "oh no" screen itself is colossal: gdm clearly knows _what_ has gone wrong, and still decides to display a "pretty" picture instead of the exact reason of the failure. This is not what I can count as "usability".)
it happens also sometimes (a month ago, this morning) and after many reboots I can get into the machine. No idea how to debug any related issue,
Created attachment 673081 [details] var/log/messages in the offending situation (I hope) This might be the var/log/messages file related to teh situation
Created attachment 676572 [details] var/log/messages with debug gdm activated Today I experienced this issue again: I cannot get any useful information from this messages file...
it happened also in F18, so I suggest to change version of Fedora
I erased fprintd and I am checking if this solves the problem. Anyway, it is silly that we cannot debug the problem and we have no clue apart from the stupid message : Oh no something has gone wrong" !!!
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. 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 '17'. 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 17'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 17 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 17'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 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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. Thank you for reporting this bug and we are sorry it could not be fixed.
Reopening and changing to F18, as requested in comment #5.
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.
please reopen this and assign it to fedora 21. it happens always after latest set of updates. it also happened from time to time on fedora 18, 19 and 20. # rpm -q gdm gdm-3.12.2-5.fc21.i686 # rpm -qa | grep gnome | grep 3.13 gnome-color-manager-3.13.90-1.fc21.i686 gnome-shell-extension-launch-new-instance-3.13.90-1.fc21.noarch gnome-packagekit-3.13.90-1.fc21.i686 gnome-weather-3.13.90-1.fc21.i686 gnome-maps-3.13.4-2.fc21.i686 gnome-online-miners-3.13.3-2.fc21.i686 gnome-initial-setup-3.13.4-3.fc21.i686 gnome-shell-extension-alternate-tab-3.13.90-1.fc21.noarch gnome-user-docs-3.13.4-1.fc21.noarch gnome-desktop3-3.13.4-2.fc21.i686 gnome-user-share-3.13.2-2.fc21.i686 gnome-session-3.13.3-2.fc21.i686 gnome-settings-daemon-3.13.90-1.fc21.i686 gnome-classic-session-3.13.90-1.fc21.noarch gnome-logs-3.13.90-1.fc21.i686 gnome-calculator-3.13.90-1.fc21.i686 gnome-photos-3.13.4-2.fc21.i686 gnome-shell-extension-window-list-3.13.90-1.fc21.noarch gnome-online-accounts-3.13.90-1.fc21.i686 gnome-bluetooth-3.13.90-1.fc21.i686 gnome-shell-extension-apps-menu-3.13.90-1.fc21.noarch gnome-clocks-3.13.2-1.fc21.i686 gnome-getting-started-docs-3.13.90-1.fc21.noarch gnome-shell-extension-places-menu-3.13.90-1.fc21.noarch gnome-boxes-3.13.4-2.fc21.i686 gnome-backgrounds-3.13.90-1.fc21.noarch gnome-shell-extension-common-3.13.90-1.fc21.noarch gnome-software-3.13.90-1.fc21.i686 gnome-system-monitor-3.13.90-1.fc21.i686 gnome-documents-3.13.4-3.fc21.i686 gnome-themes-standard-3.13.4-3.fc21.i686 gnome-shell-3.13.90-1.fc21.i686 gnome-menus-3.13.3-2.fc21.i686 gnome-sound-recorder-3.13.4-1.fc21.noarch gnome-bluetooth-libs-3.13.90-1.fc21.i686 gnome-contacts-3.13.90-1.fc21.i686 gnome-session-xsession-3.13.3-2.fc21.i686 gnome-terminal-3.13.90-1.fc21.i686 Please provide a mean to investigate this.
just fyi, i've rebooted into an older kernel twice, and it worked every time. then i've rebooted the newer kernel (once) and it also worked. i'm confused. $ rpm -qa kernel-PAE-core kernel-PAE-core-3.16.1-300.fc21.i686 kernel-PAE-core-3.16.0-0.rc6.git2.1.fc21.i686 kernel-PAE-core-3.16.0-1.fc21.i686