From: William L. T. Jr. <wl...@ob...> - 2018-05-18 14:16:18
|
On Fri, 18 May 2018 13:51:31 +0900 Carsten Haitzler (The Rasterman) <ra...@ra...> wrote: > > > http://dev.o-sinc.com/wayland_session2.log > > > > Specifically > > ESTART: 0.09551 [0.00002] - Compositor Init > > <<<< Enlightenment Error >>>> > > Enlightenment cannot initialize Ecore_X! > > > > LOAD WL_WL MODULE > > ERR<3640>:ecore_evas > > modules/ecore_evas/engines/wayland/ecore_evas_wayland_common.c:2340 > > _ecore_evas_wl_common_new_internal() Failed to connect to Wayland > > Display (null) > > > > Could not create wayland canvasLOAD WL_X11 MODULE > > X11 connect failed! > > LOAD WL_DRM MODULE > > > > Then at the bottom > > i explained this whole sequence in a fairly short paragraph in my > prior mail. :) Sure just trying to understand what failed per that output and what is working. Seems like its all working. Not sure why those modules like WL_WL failed to load. > > LOAD XWAYLAND MODULE > > XWayland Listening on display: :0 > > > > > so you're in wayland. some windows are wayland clients doing CSD, > > > some are wayland clients doing SSD (e's own internal dialogs) and > > > some are X clients via Xwayand doing SSD too. > > > > Ok so I am in Wayland something. Hard to tell as the output makes it > > seem like Wayland failed. Maybe everything is running under > > Xwayland? > > > it didn't fail - these are normal as it's first trying to see if > > > it can be an X WM, if that fails try and by an X client app (think > > > Xnest.Xephyr - Xserver in a window), where it runs a desktop in a > > > window, it also tries to be a waland client too this way (wayland > > > in wayland nested), and finally tried to be a console (drm/kms) > > > full screen compositor at the end. the fact you get something on > > > screen says that this works. :) > > > > That makes sense, but I think everything is running in Xwayland. I > > could be wrong, but not seeing anything to make me thing Wayland > > started successfully. Other than lack of X process beyond > > Xwayland. > > no. it isn't. the borders prove that. and it won't be everything - > it'll be client windows only because its rootless (like i explained > with apple and their x compat) :) Ok just confirming, so which one is using the default theme CSD or SSD? > nothing is wrong with what you have... it's seemingly working. the > different borders are a result of SSD vs CSD etc. :) That is good to know. Making some progress towards wayland and via elogind without systemd. So I do have Wayland and XWayland going. Is there any way to get all borders and such to be the same? EFL, E, or theme issue? Assuming still a theme issue. -- William L. Thomson Jr. |