> Do you know what change could have introduced this vmwgfx/wayland interaction problem inside mutter in the first place ?
Technically it was a whole point release. The trigger could be any change that went into mutter 3.28.4 as well as any Ubuntu patch. As mentioned in comment #31, my suspicion is this specific change: https://gitlab.gnome.org/GNOME/mutter/commit/e9e4b2b72 > Just to look at our option (since a kernel fix might be not end up being trivial) does a revert of the change could be a possibility here ? If the issue turns out to be commit e9e4b2b72 above then no. Because too many people benefit vs the possible number of people affected by this bug. But we also aren't completely sure that's the relevant mutter commit. If only I could reproduce this bug I could probably write a workaround (or fix) for it in mutter. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832138 Title: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832138/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
