On Jan 5, 2017 10:24 PM, "Greg Woods" <woods@xxxxxxxx> wrote:
On Thu, Jan 5, 2017 at 3:46 PM, stan <stanl-fedorauser@xxxxxxxxxxx> wrote:
It sounds like a race condition. Does it occur intermittently? That
is, if it happens and you hit the hard reset button, does it
then sometimes boot correctly and sometimes not?I confess that I have not tried rapid and repeated reboots. However, my wife's laptop had the issue for enough times that I finally had to set it to boot to command line, and remind her to log in and run startx (most of the time she just suspends it, so she often forgets that she has to do this, which is why I would like to fix it).Ed Greshko ed.greshko@xxxxxxxxxxx via lists.fedoraproject.org:[root@worldsys system]# ll default.targetlrwxrwxrwx. 1 root root 36 Oct 26 2013 default.target -> /lib/systemd/system/graphical.target [root@worldsys system]# ll display-manager.servicelrwxrwxrwx. 1 root root 35 Oct 26 2013 display-manager.service -> /usr/lib/systemd/system/gdm.service Since I use GNOME, this is what I would expect.> Have you modified the grub lines at all? Try removing "quiet" and "rhgb" from the kernel command line and you will get more info about what's happening.That's about the first thing I do when installing any Red Hat system. In this case, what I see is a lot of "OK" lines, no visible errors, then something like "running a start job for Waiting for Plymouth Screen to Quit" with the counter that never stops.This thread does make me think about checking out what the plymouth-quit service is actually supposed to be doing. I have a pretty busy weekend coming up, so it probably won't be until sometime next week that I have time to look at this. Thanks for the suggestions.--Greg
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@lists.fedoraproject.org
The last line in one console isn't necessarily the problem. If the system boots to multi-user but doesn't show the display manager in the default target, I would suspect the display managed. Look at `journalctl -u gdm -r`. I *suspect* disabling wayland in /etc/gdm/custom.conf will help, often that will work around graphics issues that hurt gdm.
--Pete
_______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
