Script builds great! But Xwayland not working when invoked with /opt/wayfire/bin/startwayfire about wf-install

[soreau]

Ok, thanks for reporting your findings. I'm not sure what the problem could be exactly but I'm guessing it has something to do with the environment setup. You could try commenting out one line at a time for the environment variables startwayfire script sets, to try and narrow it down. XDG_DATA_DIRS, LD_LIBRARY_PATH or PATH (or some combination) but since I cannot reproduce, you would have to debug it.

[clort81]

It is likely some mess I created due to old builds. If I find what causes it I will append the answer.
It is wonderful that wayfire runs again here. So much nicer than Xorg. You're the best!

[soreau]

The features are correct in meson.build, those are merely initial values. If you have the dependencies installed for xwayland, wlroots should show true for xwayland when running wf-install. Specifically, you need to have the packages installed that provide these files with .pc extension appended.

[soreau]

The issue is most likely missing dependencies for xwayland when building (wlroots). See https://github.com/WayfireWM/wayfire#xwayland-support-optional

[clort81]

the build log seems to indicate xwayland enabled.

----------------
wayfire 0.8.0

system wfconfig: false
 system wlroots: false
       xwayland: true
    x11-backend: true
        imageio: true
         gles32: true
    print trace: true
     unit tests: true
----------------

Build targets in project: 138
NOTICE: Future-deprecated features used:
 * 0.56.0: {'dependency.get_pkgconfig_variable', 'meson.source_root'}

wlroots 0.10.0

    systemd    : 0
    elogind    : 1
    xwayland   : 1
    x11_backend: 1
    xcb-icccm  : 1
    xcb-errors : 0

wayfire 0.8.0

  Subprojects
    wf-config: YES
    wf-touch : YES
    wf-utils : YES 1 warnings
    wlroots  : YES 1 warnings                                                                                                                                                         

  User defined options
    backend  : ninja

During install, I kept my old ~/.config/wayfire.ini which may be the cause of the problem? In [core] i added

xwayland = true
Xwayland = true

I've tried setting $DISPLAY to :0 and :1
No ideas what might be wrong

$ xeyes
Error: Can't open display: :0

The wlroots meson build log might be informative:

Determining dependency 'xwayland' with pkg-config executable '/usr/bin/pkg-config'
env[PKG_CONFIG_PATH]: 
Called `/usr/bin/pkg-config --modversion xwayland` -> 1

CMake binary for 1 is not cached
CMake binary missing from cross or native file, or env var undefined.
Trying a default CMake fallback at cmake
Found CMake: /usr/bin/cmake (3.23.2)
Extracting basic cmake information
CMake Toolchain: Calling CMake once to generate the compiler state
Calling CMake (['/usr/bin/cmake']) in /media/sd/Projects/System/wayland/wlroots/build/meson-private/__CMake_compiler_info__ with:
  - "--trace-expand"
  - "--trace-format=json-v1"
  - "--no-warn-unused-cli"
  - "--trace-redirect=cmake_trace.txt"
  - "-G"
  - "Ninja"
  - "-DCMAKE_TOOLCHAIN_FILE=/media/sd/Projects/System/wayland/wlroots/build/meson-private/__CMake_compiler_info__/CMakeMesonTempToolchainFile.cmake"
  - "."
Try CMake generator: auto
Calling CMake (['/usr/bin/cmake']) in /media/sd/Projects/System/wayland/wlroots/build/meson-private/cmake_xwayland with:
  - "--trace-expand"
  - "--trace-format=json-v1"
  - "--no-warn-unused-cli"
  - "--trace-redirect=cmake_trace.txt"
  - "-DCMAKE_TOOLCHAIN_FILE=/media/sd/Projects/System/wayland/wlroots/build/meson-private/cmake_xwayland/CMakeMesonToolchainFile.cmake"
  - "."
  -- Module search paths:    ['/', '/opt', '/usr', '/usr/local']
  -- CMake root:             /usr/share/cmake-3.23
  -- CMake architectures:    ['aarch64-linux-gnu', 'arm-linux-gnueabihf', 'x86_64-linux-gnu', 'x86_64-linux-gnux32']
  -- CMake lib search paths: ['lib', 'lib32', 'lib64', 'libx32', 'share', 'lib/aarch64-linux-gnu', 'lib/arm-linux-gnueabihf', 'lib/x86_64-linux-gnu', 'lib/x86_64-linux-gnux32']
Preliminary CMake check failed. Aborting.
Run-time dependency xwayland found: NO (tried pkgconfig and cmake)
Program Xwayland found: YES (/usr/bin/Xwayland)
Dependency xcb found: YES 1.14 (cached)
Pkg-config binary for 1 is cached.
Determining dependency 'xcb-composite' with p

[soreau]

Silly question, but have you installed xwayland? If so, please upload wayfire log somewhere and post the link here.

[clort81]

which Xwayland shows /usr/bin/Xwayland
but

pkg-config --modversion xwayland
Package xwayland was not found in the pkg-config search path.
Perhaps you should add the directory containing `xwayland.pc'
to the PKG_CONFIG_PATH environment variable
No package 'xwayland' found

[soreau]

which Xwayland shows /usr/bin/Xwayland but

pkg-config --modversion xwayland
Package xwayland was not found in the pkg-config search path.
Perhaps you should add the directory containing `xwayland.pc'
to the PKG_CONFIG_PATH environment variable
No package 'xwayland' found

This is not a problem, please upload the full wayfire log.

[clort81]

I have not found where wayfire puts the log yet. What is filename?

[soreau]

It is the stdout of wayfire. You can redirect it to a file with wayfire &> /tmp/wayfire/log for example.

[clort81]

wayfire.log

[soreau]

I don't see where it prints the starting xwayland message from wlroots.. can you repost the log when running wayfire -d to enable debugging output?

[clort81]

When I run wayfire -d > ~/wayfire2.log, i get X apps running fine!
when i started with /opt/wayfire/bin/startwayfire i got no X apps.
wayfire2log.txt

[soreau]

That's strange, the -d option should only enable additional debugging messages.

[clort81]

Also works without the -d option.
The issue occurs when i start with /opt/wayfire/bin/startwayfire.

I also notice when I invoke with startwayfire, I cannot drag window corners to resize - I need to use mod+rightlcick to resize windows.

Starting wayfire just with "wayfire", I can resize windows by click-dragging corners of windows.

[EDIT] Starting with 'wayfire' solves my issue. Can I help provide more info / context about the startwayfire problem?

[soreau]

When you run startwayfire, it should tell you where it's outputting the log. Can you post it as well?

[clort81]

The startwayfire log was wayfire.log posted above. It got written to ~/.local/share/wayfire

[clort81]

Ok I had working X11 apps when i didn't set the PATH to prepend /opt/wayfire, which means I was running something from an old install.
I purged the wayfire stuff in /usr/local/bin, and now i REALLY can't get any X11 apps to run.
Then I reinstalled from install script with no apparent errors, chose to overwrite my wayfire.ini with the new default.
Still after invoking with /opt/wayfire/bin/startwayfire I get

$ xclock
Error: Can't open display:

What's running?
ps aux |grep wf-
returns wf-panel and wf-background (only)

I have a working panel and i see the wayfire-config app in it, and it runs.

wayfire.log
wayfire.ini.txt

1) Why can't I start any X app?
2) How can I begin to diagnose the problem?

I'll invoke startwayfire script and with -d and append a debug startup in a couple of minutes.

Cheers! :)
[edit]Also I can't resize windows by the frame if i use server side decorations... but i used to be able to.
DEBUG LOG
wayfire.log

[EDIT2]Invoking X11 apps doesn't send anything to wayfire log. I just get:

15:57:22-Kornho@Desktop:/pr/System/wayland/wf-install$ xterm
xterm: Xt error: Can't open display: 
xterm: DISPLAY is not set
15:57:25-Kornho@Desktop:/pr/System/wayland/wf-install$ export DISPLAY=:0
15:57:33-Kornho@Desktop:/pr/System/wayland/wf-install$ xterm
xterm: Xt error: Can't open display: :0
15:57:34-Kornho@Desktop:/pr/System/wayland/wf-install$ export DISPLAY=:1
15:57:36-Kornho@Desktop:/pr/System/wayland/wf-install$ xterm
xterm: Xt error: Can't open display: :1

[EDIT3]I can run Xwayland from within a foot terminal but that gets me a black window.

[EDIT4] Maybe these old wlroots are conflicting?

ldconfig -p |grep wlroots
	libwlroots.so.7 (libc6,AArch64) => /usr/local/lib/aarch64-linux-gnu/libwlroots.so.7
	libwlroots.so.6 (libc6,AArch64) => /lib/aarch64-linux-gnu/libwlroots.so.6
	libwlroots.so (libc6,AArch64) => /usr/local/lib/aarch64-linux-gnu/libwlroots.so

[EDIT5]Cleared out the old libwl cruft from /lib and /usr/local/lib, still no solution
More info:

• from within foot terminal, check what $LD_LIBRARY PATH is...

pr/System/wayland/wf-install$ echo $LD_LIBRARY_PATH
/opt/wayfire/lib/aarch64-linux-gnu:

• is any of that /opt/wayfire/lib in linker path? Shouldn't need to be if the install script explicitly told where to find them during compilation.

# ldconfig -p |grep opt
	libpopt.so.0 (libc6,AArch64) => /lib/aarch64-linux-gnu/libpopt.so.0
	libosdGPU.so.3.1.1 (libc6,AArch64) => /opt/lib/osd/lib/libosdGPU.so.3.1.1
	libosdGPU.so (libc6,AArch64) => /opt/lib/osd/lib/libosdGPU.so
	libosdCPU.so.3.1.1 (libc6,AArch64) => /opt/lib/osd/lib/libosdCPU.so.3.1.1
	libosdCPU.so (libc6,AArch64) => /opt/lib/osd/lib/libosdCPU.so
	libboost_program_options.so.1.74.0 (libc6,AArch64) => /lib/aarch64-linux-gnu/libboost_program_options.so.1.74.0
	libboost_program_options.so (libc6,AArch64) => /lib/aarch64-linux-gnu/libboost_program_options.so
	libabsl_bad_optional_access.so.20210324 (libc6,AArch64) => /lib/aarch64-linux-gnu/libabsl_bad_optional_access.so.20210324
	libabsl_bad_optional_access.so.20200923 (libc6,AArch64) => /lib/aarch64-linux-gnu/libabsl_bad_optional_access.so.20200923
	libAlembic.so (libc6,AArch64) => /opt/lib/alembic/lib/libAlembic.so

• is /opt/wayfire/bin/wayfire really the new version I built?

-rwxr-xr-x 1 Kornho Kornho 28897112 Jul  9 15:02 /opt/wayfire/bin/wayfire

Ok, yes..

• what's it linked to?

 ldd /opt/wayfire/bin/wayfire 
	linux-vdso.so.1 (0x0000ffff96404000)
	**### libwlroots.so.10 => not found**
	libwf-config.so.1 => /usr/local/lib/aarch64-linux-gnu/libwf-config.so.1 (0x0000ffff9610c000)
	libwf-utils.so.0 => /usr/local/lib/aarch64-linux-gnu/libwf-utils.so.0 (0x0000ffff9606a000)
	libdl.so.2 => /lib/aarch64-linux-gnu/libdl.so.2 (0x0000ffff96056000)
	libwayland-server.so.0 => /usr/local/lib/aarch64-linux-gnu/libwayland-server.so.0 (0x0000ffff96032000)
	libxkbcommon.so.0 => /lib/aarch64-linux-gnu/libxkbcommon.so.0 (0x0000ffff95fdf000)
	libpixman-1.so.0 => /lib/aarch64-linux-gnu/libpixman-1.so.0 (0x0000ffff95f6c000)
	libGLESv2.so.2 => /usr/local/lib/aarch64-linux-gnu/libGLESv2.so.2 (0x0000ffff95f50000)
	libinput.so.10 => /lib/aarch64-linux-gnu/libinput.so.10 (0x0000ffff95eef000)
	libjpeg.so.62 => /lib/aarch64-linux-gnu/libjpeg.so.62 (0x0000ffff95e94000)
	libpng16.so.16 => /lib/aarch64-linux-gnu/libpng16.so.16 (0x0000ffff95e4d000)
	libstdc++.so.6 => /lib/aarch64-linux-gnu/libstdc++.so.6 (0x0000ffff95c30000)
	libm.so.6 => /lib/aarch64-linux-gnu/libm.so.6 (0x0000ffff95b85000)
	libgcc_s.so.1 => /lib/aarch64-linux-gnu/libgcc_s.so.1 (0x0000ffff95b60000)
	libc.so.6 => /lib/aarch64-linux-gnu/libc.so.6 (0x0000ffff959e4000)
	libevdev.so.2 => /lib/aarch64-linux-gnu/libevdev.so.2 (0x0000ffff959b8000)
	libxml2.so.2 => /lib/aarch64-linux-gnu/libxml2.so.2 (0x0000ffff95806000)
	/lib/ld-linux-aarch64.so.1 (0x0000ffff963d1000)
	libffi.so.7 => /lib/aarch64-linux-gnu/libffi.so.7 (0x0000ffff957ed000)
	libpthread.so.0 => /lib/aarch64-linux-gnu/libpthread.so.0 (0x0000ffff957bd000)
	libglapi.so.0 => /usr/local/lib/aarch64-linux-gnu/libglapi.so.0 (0x0000ffff95740000)
	libmtdev.so.1 => /lib/aarch64-linux-gnu/libmtdev.so.1 (0x0000ffff9572a000)
	libudev.so.1 => /lib/aarch64-linux-gnu/libudev.so.1 (0x0000ffff956f0000)
	libwacom.so.9 => /lib/aarch64-linux-gnu/libwacom.so.9 (0x0000ffff956d4000)
	libz.so.1 => /lib/aarch64-linux-gnu/libz.so.1 (0x0000ffff956aa000)
	libicuuc.so.71 => /lib/aarch64-linux-gnu/libicuuc.so.71 (0x0000ffff954a4000)
	liblzma.so.5 => /lib/aarch64-linux-gnu/liblzma.so.5 (0x0000ffff9546e000)
	libgudev-1.0.so.0 => /lib/aarch64-linux-gnu/libgudev-1.0.so.0 (0x0000ffff95452000)
	libgobject-2.0.so.0 => /lib/aarch64-linux-gnu/libgobject-2.0.so.0 (0x0000ffff953e4000)
	libglib-2.0.so.0 => /lib/aarch64-linux-gnu/libglib-2.0.so.0 (0x0000ffff9529c000)
	libicudata.so.71 => /lib/aarch64-linux-gnu/libicudata.so.71 (0x0000ffff93588000)
	libffi.so.8 => /lib/aarch64-linux-gnu/libffi.so.8 (0x0000ffff9356e000)
	libpcre.so.3 => /lib/aarch64-linux-gnu/libpcre.so.3 (0x0000ffff934f8000)

HEY!

$locate libwlroots.so.10
/opt/wayfire/lib/aarch64-linux-gnu/libwlroots.so.10

??!?!

[clort81]

Alright this i'm sure is not how things should be:

1. wayfire seems to not have libwlroots.so.10 linked in from proper location (?)
   ... but it's looking like a new, shiny valid shared object

# file /opt/wayfire/lib/aarch64-linux-gnu/libwlroots.so.10
/opt/wayfire/lib/aarch64-linux-gnu/libwlroots.so.10: ELF 64-bit LSB shared object, ARM aarch64, version 1 (SYSV), dynamically linked, BuildID[sha1]=dfee7fd79ec9d4131dfdae49b78e5355916b9e06, with debug_info, not stripped

built just today...
2) is libwlroots supposed to link to some xwayland.so? cause all i got is...

$ locate -i xwayland |grep \\.so
/usr/lib/aarch64-linux-gnu/libweston-9/xwayland.so

and libwlroots isn't linked to any kind of xwayland shared object

# ldd /opt/wayfire/lib/aarch64-linux-gnu/libwlroots.so.10
	linux-vdso.so.1 (0x0000ffff8f97c000)
	libwayland-server.so.0 => /usr/local/lib/aarch64-linux-gnu/libwayland-server.so.0 (0x0000ffff8f81c000)
	libdrm.so.2 => /lib/aarch64-linux-gnu/libdrm.so.2 (0x0000ffff8f7f6000)
	libgbm.so.1 => /usr/local/lib/aarch64-linux-gnu/libgbm.so.1 (0x0000ffff8f7d6000)
	libxkbcommon.so.0 => /lib/aarch64-linux-gnu/libxkbcommon.so.0 (0x0000ffff8f783000)
	libudev.so.1 => /lib/aarch64-linux-gnu/libudev.so.1 (0x0000ffff8f749000)
	libpixman-1.so.0 => /lib/aarch64-linux-gnu/libpixman-1.so.0 (0x0000ffff8f6d6000)
	libm.so.6 => /lib/aarch64-linux-gnu/libm.so.6 (0x0000ffff8f62b000)
	librt.so.1 => /lib/aarch64-linux-gnu/librt.so.1 (0x0000ffff8f613000)
	libEGL.so.1 => /usr/local/lib/aarch64-linux-gnu/libEGL.so.1 (0x0000ffff8f5c2000)
	libGLESv2.so.2 => /usr/local/lib/aarch64-linux-gnu/libGLESv2.so.2 (0x0000ffff8f5a6000)
	libvulkan.so.1 => /lib/aarch64-linux-gnu/libvulkan.so.1 (0x0000ffff8f537000)
	libinput.so.10 => /lib/aarch64-linux-gnu/libinput.so.10 (0x0000ffff8f4d6000)
	libxcb.so.1 => /lib/aarch64-linux-gnu/libxcb.so.1 (0x0000ffff8f49e000)
	libxcb-dri3.so.0 => /lib/aarch64-linux-gnu/libxcb-dri3.so.0 (0x0000ffff8f48a000)
	libxcb-present.so.0 => /lib/aarch64-linux-gnu/libxcb-present.so.0 (0x0000ffff8f477000)
	libxcb-render.so.0 => /lib/aarch64-linux-gnu/libxcb-render.so.0 (0x0000ffff8f45a000)
	libxcb-render-util.so.0 => /lib/aarch64-linux-gnu/libxcb-render-util.so.0 (0x0000ffff8f446000)
	libxcb-shm.so.0 => /lib/aarch64-linux-gnu/libxcb-shm.so.0 (0x0000ffff8f432000)
	libxcb-xfixes.so.0 => /lib/aarch64-linux-gnu/libxcb-xfixes.so.0 (0x0000ffff8f41a000)
	libxcb-xinput.so.0 => /lib/aarch64-linux-gnu/libxcb-xinput.so.0 (0x0000ffff8f3e8000)
	libwayland-client.so.0 => /usr/local/lib/aarch64-linux-gnu/libwayland-client.so.0 (0x0000ffff8f3c8000)
	libseat.so.1 => /lib/aarch64-linux-gnu/libseat.so.1 (0x0000ffff8f3a7000)
	libc.so.6 => /lib/aarch64-linux-gnu/libc.so.6 (0x0000ffff8f22b000)
	libffi.so.7 => /lib/aarch64-linux-gnu/libffi.so.7 (0x0000ffff8f212000)
	libpthread.so.0 => /lib/aarch64-linux-gnu/libpthread.so.0 (0x0000ffff8f1e2000)
	/lib/ld-linux-aarch64.so.1 (0x0000ffff8f949000)
	libdl.so.2 => /lib/aarch64-linux-gnu/libdl.so.2 (0x0000ffff8f1ce000)
	libexpat.so.1 => /lib/aarch64-linux-gnu/libexpat.so.1 (0x0000ffff8f196000)
	libstdc++.so.6 => /lib/aarch64-linux-gnu/libstdc++.so.6 (0x0000ffff8ef79000)
	libglapi.so.0 => /usr/local/lib/aarch64-linux-gnu/libglapi.so.0 (0x0000ffff8eefc000)
	libX11-xcb.so.1 => /lib/aarch64-linux-gnu/libX11-xcb.so.1 (0x0000ffff8eeea000)
	libxcb-dri2.so.0 => /lib/aarch64-linux-gnu/libxcb-dri2.so.0 (0x0000ffff8eed5000)
	libxcb-sync.so.1 => /lib/aarch64-linux-gnu/libxcb-sync.so.1 (0x0000ffff8eebe000)
	libxshmfence.so.1 => /lib/aarch64-linux-gnu/libxshmfence.so.1 (0x0000ffff8eeab000)
	libmtdev.so.1 => /lib/aarch64-linux-gnu/libmtdev.so.1 (0x0000ffff8ee95000)
	libevdev.so.2 => /lib/aarch64-linux-gnu/libevdev.so.2 (0x0000ffff8ee67000)
	libwacom.so.9 => /lib/aarch64-linux-gnu/libwacom.so.9 (0x0000ffff8ee4b000)
	libXau.so.6 => /lib/aarch64-linux-gnu/libXau.so.6 (0x0000ffff8ee37000)
	libXdmcp.so.6 => /lib/aarch64-linux-gnu/libXdmcp.so.6 (0x0000ffff8ee21000)
	libsystemd.so.0 => /lib/aarch64-linux-gnu/libsystemd.so.0 (0x0000ffff8ed65000)
	libgcc_s.so.1 => /lib/aarch64-linux-gnu/libgcc_s.so.1 (0x0000ffff8ed3e000)
	libgudev-1.0.so.0 => /lib/aarch64-linux-gnu/libgudev-1.0.so.0 (0x0000ffff8ed22000)
	libgobject-2.0.so.0 => /lib/aarch64-linux-gnu/libgobject-2.0.so.0 (0x0000ffff8ecb4000)
	libglib-2.0.so.0 => /lib/aarch64-linux-gnu/libglib-2.0.so.0 (0x0000ffff8eb6c000)
	libbsd.so.0 => /lib/aarch64-linux-gnu/libbsd.so.0 (0x0000ffff8eb47000)
	liblzma.so.5 => /lib/aarch64-linux-gnu/liblzma.so.5 (0x0000ffff8eb0f000)
	liblz4.so.1 => /lib/aarch64-linux-gnu/liblz4.so.1 (0x0000ffff8eae0000)
	libgcrypt.so.20 => /lib/aarch64-linux-gnu/libgcrypt.so.20 (0x0000ffff8e9e6000)
	libffi.so.8 => /lib/aarch64-linux-gnu/libffi.so.8 (0x0000ffff8e9cc000)
	libpcre.so.3 => /lib/aarch64-linux-gnu/libpcre.so.3 (0x0000ffff8e956000)
	libmd.so.0 => /lib/aarch64-linux-gnu/libmd.so.0 (0x0000ffff8e938000)
	libgpg-error.so.0 => /lib/aarch64-linux-gnu/libgpg-error.so.0 (0x0000ffff8e904000)

[clort81]

This may be informative
swaywm/wlroots#2773
I've got lots of diverse wlroots.pc files! Is that not a strength?

$ locate wlroots.pc
/media/sd/Projects/System/wayland/wayfire/build/meson-private/wlroots.pc
/media/sd/Projects/System/wayland/wf-install/wayfire/build/meson-private/wlroots.pc
/media/sd/Projects/System/wayland/wlroots/build/meson-private/wlroots.pc
/media/sd/Projects/System/wayland/wlroots2/wlroots/build/meson-private/wlroots.pc
/opt/wayfire/lib/aarch64-linux-gnu/pkgconfig/wlroots.pc
/opt/wayland/lib/aarch64-linux-gnu/pkgconfig/wlroots.pc
/usr/local/lib/aarch64-linux-gnu/pkgconfig/wlroots.pc

Hey! wf-install's wlroots.pc has have_xwayland=false!

have_drm_backend=true
have_x11_backend=true
have_libinput_backend=true
have_xwayland=false
have_gles2_renderer=true
have_vulkan_renderer=true

ok restarting with --clean now

/install.sh --prefix /opt/wayfire --stream 0.7.x --clean

And there it is!

wlroots| Run-time dependency xwayland found: NO (tried pkgconfig and cmake)

[EDIT1] Removing the cruft of wlroots.pc elsewhere on system didn't help - still xwayland found: NO

/media/sd/Projects/System/wayland/wf-install/wayfire/subprojects/wlroots$ vi meson.build

features = {
        'drm-backend': false,
        'x11-backend': false,
        'libinput-backend': false,
        'xwayland': false,
        'gles2-renderer': false,
        'vulkan-renderer': false,
}

That's wrong, isn't it?

[clort81]

It was my #@$%!^ ccache >_<
Clearing ccache got me Xwayland detected by the wlroots build.
Thanks for the help!