Hide Forgot
Description of problem: when loading Fedora 19 (with updates from @updates-testing) system cannot be started. I get a message like: Failed to start GNOME Display Manager See 'systemctl status gdm.service' for details. Well, if the system doesn't start, I don't know how to check this details. Also the Sendmail Mail Transport Agent and Client seem to fail to start properly, altought I don't get a failed message (only start and stop messages(. Version-Release number of selected component (if applicable): Well, I cannot check this (I'm writing from a live version of Crunchbang). The version must be the latest one for Fedora 19 as released yesterday. How reproducible: Start Fedora. Steps to Reproduce: 1. Simply wait. 2. GDM won't load. 3. System isn't loaded, so there is nothing to do with the computer Actual results: See above. Expected results: I need to use the computer. Additional info: How could I at least check the command 'systemctl status gdm.service'? I login to a classic session. I don't know whether this may be relevant.
I have the same problem since yesterday. systemctl status gdm.service : nov. 11 05:39:30 gedoc04 systemd[1]: Unit gdm.service entered failed state. nov. 11 05:39:30 gedoc04 systemd[1]: gdm.service holdoff time over, scheduling restart. nov. 11 05:39:30 gedoc04 systemd[1]: Stopping GNOME Display Manager... nov. 11 05:39:30 gedoc04 systemd[1]: Starting GNOME Display Manager... nov. 11 05:41:00 gedoc04 systemd[1]: gdm.service operation timed out. Terminating. nov. 11 05:41:00 gedoc04 systemd[1]: Failed to start GNOME Display Manager. nov. 11 05:41:00 gedoc04 systemd[1]: Unit gdm.service entered failed state. nov. 11 05:41:00 gedoc04 systemd[1]: gdm.service holdoff time over, scheduling restart. nov. 11 05:41:00 gedoc04 systemd[1]: Stopping GNOME Display Manager... nov. 11 05:41:00 gedoc04 systemd[1]: Starting GNOME Display Manager... The boot process seems to loop at this stage, trying to launch gdm again and again. I can boot into runlevel 3, then startx to get a usable desktop.
Thanks for your reply, GeH. I was able to boot in runlevel 3, but startx gives the following error: Oh no! Something has gone wrong. A problem has ocurred and the system can[t recover. Please log out and try again. Now I have to find out what causes the error.
Created attachment 824075 [details] Xorg.0.log from today
Created attachment 824078 [details] last 200 lines from "journalctl -a" Just in case it might help to solve the bug, I attach a copy Xorg.O.log, the last 200 lines from "journalctl -a". A log from GDM is not available from today.
No more problem today, after last update. Maybe solved by last selinux-policy update : selinux-policy-3.12.1-74.13
After being able to update the packages, everything works fine now. Closing the bug myself as errata.
Well, it seems that it is broken again in Fedora 20. I'm experiencing another issue. When I run "startx", it starts a GNOME 3.10 session, which doesn't work for me. Is there a way to invoke startx so it starts a classic session? Many thanks for your help.
Well, closing the report myself, since nobody replied to my question.