Description of problem:
When booting current Fedora 26 as a virtual guest in gnome-boxes, the system does not reach GDM. It gets stuck during the graphical boot procedure. After removing boot option "rhgb", the system gets frozen after attempting to launch the graphical login manager GDM.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Boot current Fedora 26 virtual guest in gnome-boxes.
System gets stuck during the graphical boot procedure.
System launches GDM successfully.
- After adding boot option "nomodeset", the system launches GDM on Xorg successfully.
- After changing the video device from "qxl" to "virtio", the system launches GDM on Wayland successfully.
Probably the same as Rawhide bug 1465148
Try removing "rhgb" from the normal boot options, see if it works without disabling modeset. You may not get past the login screen though.
As reported in bug 1464780 for the Fedora development tree, removing "rhgb" allows the system to launch GDM, albeit unsuccessfully: the screen gets frozen. Moreover, after booting into runlevel 3 without option "rhgb", startx launches a GNOME on Xorg session successfully while using the QXL video driver.
(In reply to Chuck Ebbert from comment #1)
This situation was already addressed in the initial report.
With kernel-4.12.12-300.fc26, the system still hangs at the graphical boot screen. After removing kernel option "rhgb", the system now launches the graphical login manager successfully. However, the screen exhibits a strong flicker.
We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. The kernel moves very fast so bugs may get fixed as part of a kernel update. Due to this, we are doing a mass bug update across all of the Fedora 26 kernel bugs.
Fedora 26 has now been rebased to 4.15.4-200.fc26. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.
If you have moved on to Fedora 27, and are still experiencing this issue, please change the version to Fedora 27.
If you experience different issues, please open a new bug report for those.