Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Created attachment 1198792 [details] System journal file
Description of problem: When running current Fedora 25 in a virtual box by means of GNOME Boxes, Xorg is used by the graphical login manager GDM and also after a GNOME on Wayland session has been initiated. Version-Release number of selected component (if applicable): xorg-x11-server-Xwayland-1.18.4-5.fc25 How reproducible: Always Steps to Reproduce: 1. Launch a Fedora 25 guest session in GNOME Boxes. Actual results: Xorg is used by the graphical login manager GDM and also by a GNOME on Wayland session. Expected results: Xwayland is used instead of Xorg. Additional info: Things used to work as expected until recently.
Live image Fedora-Workstation-Live-x86_64-25-20160904.n.0 was not affected by this issue yet.
gdm decides/choose which session (x11/Wayland) to run, not the X server. => Moving to gdm
we don't offer a GNOME on Wayland session in Fedora 25. Are you sure you see it? In F25, the two options are "GNOME" and "GNOME on Xorg". The former is either wayland or xorg depending on if WaylandEnable=true or WaylandEnable=false in /etc/gdm/custom.config. There is also some fail safe logic to make that option pick Xorg if wayland doesn't seem to work for the login screen.
(In reply to Ray Strode [halfline] from comment #5) I had written "GNOME on Wayland" session without explicitly referring to the session denomination used by GDM. The corresponding session type in Fedora 25 is "GNOME". As mentioned above, the issue becomes apparent already when GDM appears on the screen: because of bug 1266484, GDM used to show heavy flicker when running in a virtual machine, e.g. try booting from live image Fedora-Workstation-Live-x86_64-25-20160904.n.0. Switching to a virtual console and checking the relevant processes for later live images confirmed that a process Xorg was running instead of the expected process Xwayland. Finally, I had provided attachment 1198792 [details] for a reason, namely, it exhibits a number of error messages, e.g.: "(EE) failed to dispatch Wayland events: Connection reset by peer".
Too bad I upgraded my host system from Fedora 24 to Fedora 25 yesterday; right now, both of Fedora-Workstation-Live-x86_64-25-20160904.n.0 and Fedora-Workstation-Live-x86_64-25-20160907.n.0 do boot into the default "GNOME" session running Xwayland (the comment about GDM referred to fresh system installed using the corresponding live media). Nevertheless, I will leave this bug report open until I have the opportunity to recheck against a Fedora 24 host system.
This regression has been introduced by upgrading mutter-3.21.90-3.fc25 to mutter-3.21.91-1.fc25. This can be verified by updating mutter after booting from a recent live image. Downgrading mutter restores correct behaviour; on a fully updated Fedora 25 system this requires to also downgrade gnome-shell plus extensions.
There a now two live images available which include different versions of package mutter and exhibit the issue without any further action by merely booting from the latter in gnome-boxes: 1. Fedora-Workstation-Live-x86_64-25-20160907.n.0 (mutter-3.21.90-3.fc25): Xwayland session. 2. Fedora-Workstation-Live-x86_64-25-20160910.n.0 (mutter-3.21.91-1.fc25): Xorg session.
mutter-3.21.92-1.fc25 is not pushed yet: https://bodhi.fedoraproject.org/updates/FEDORA-2016-78efe5595f
(In reply to Kamil Páral from comment #10) This bug is not subject to https://bodhi.fedoraproject.org/updates/FEDORA-2016-78efe5595f which does not even mention bug 1374028. As a consequence, no bodhi notification was added to this bug report.
This seems to be resolved with Fedora-Workstation-Live-x86_64-25-20160925.n.0.iso. Boots into Wayland in Boxes and virt-manager.