[Bug 262695] x11/gnome under wayland startup stuck in gdm

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262695

--- Comment #1 from Jan Beich <jbeich@FreeBSD.org> ---
(In reply to ykla from comment #0)
> It works fine with gnome 3.3x

GNOME/Wayland was never supported, see bug 249882, bug 258042. Maybe before
ports a69eab30db5a GDM forced Xorg session. Some GNOME components and many
GNOME applications do support Wayland but those need to be running under
non-GNOME compositor or a GNOME compositor based on wlroots like x11-wm/phoc.
Besides, regular applications can use Xwayland if native Wayland support is
broken or missing.

> (EE) open /dev/dri/card0: No such file or directory
> (EE) vmware(0): Failed to open drm.
> (WW) vmware(0): Disabling 3D support.
> (WW) vmware(0): Disabling Render Acceleration.
> (WW) vmware(0): Disabling RandR12+ support.
> (II) AIGLX: Screen 0 is not DRI2 capable
> (II) IGLX: Loaded and initialized swrast
> (II) GLX: Initialized DRISWRAST GL provider for screen 0

DRM is "de facto" required under Wayland. Without it the compositor has to use
legacy framebuffer a la xf86-video-vesa or xf86-video-scfb e.g.,
https://github.com/swaywm/wlroots/pull/2410

drm-kmod currently lacks vmwgfx.ko, so you're constrained by software
rendering. Running Wayland compositor on top of Xorg or in headless mode should
still work.

-- 
You are receiving this mail because:
You are the assignee for the bug.