Hi Adam,
I have see the tutorial of system debugging, when I was stuck in the boot, I press Ctrl-Alt-F2 to another terminal,
in the second terminal,  I use the command
dmesg
to get the debug information of system
I think the problem may be in the gnome stuff because when I check the last part of the debug log(I guess it is where things got stuck), it seems to be related to GNOME-shell and GNOME-session. Remember I sent to this mailing list couple days ago that I can not update these packages because the DNF said that there is some broken dependencies, so DNF just skip those packages. So I still use the old version of GNOME-session and GNOME-shell since maybe 10 days ago.
Can I get the broken dependencies fixed? I guess that my laptop will work if I can get those dependencies fixed.

Bowen

On Sat, Dec 3, 2016 at 9:14 AM, Adam Williamson <adamwill@fedoraproject.org> wrote:
On Sat, 2016-12-03 at 03:59 -0600, Bowen Wang wrote:
> Hi everyone,
> I just run the command
> dnf upgrade --refresh
> to update to the 20161202.n.2 build
> but after I updated the system, it cannot be boot up, it will be stuck in
> the boot process
> there will 3 places that the boot process can be stuck in
> 1. the output
> started gnome display rook ... service some_other_stuff
> 2. the output
> started virtualization daemon hook... service some_other_stuff
> 3 the output
> install ABRT coredump ...some_other_stuff

This doesn't mean much, as the boot process is parallel. You have to at
least follow the steps at:

https://freedesktop.org/wiki/Software/systemd/Debugging/

to figure out where it's really getting stuck. It's most likely just
failing when it tries to start the login screen.
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
_______________________________________________
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-leave@lists.fedoraproject.org