search

project-repo / cagebreak

Cagebreak: A Wayland Tiling Compositor Inspired by Ratpoison
MIT License
286 stars 19 forks source link

waitpid for Xwayland fork failed: No child processes #23

Closed jbeich closed 2 years ago

jbeich commented 2 years ago

Similar to https://github.com/djpohly/dwl/issues/177. Xwayland works fine elsewhere: cage, hikari, kwinft, labwc, phoc, river, sway, wayfire.

$ cagebreak
[...]
00:00:00.085 [xwayland/server.c:92] Starting Xwayland on :0
00:00:00.116 [render/swapchain.c:105] Allocating new swapchain buffer
00:00:00.118 [render/allocator/gbm.c:142] Allocated 1280x720 GBM buffer (format 0x34325258, modifier 0x100000000000004)
00:00:00.118 [render/gles2/renderer.c:143] Created GL FBO for buffer 1280x720
00:00:00.160 [types/wlr_surface.c:748] New wlr_surface 0x880d81f80 (res 0x86f22d380)
00:00:00.165 [xwayland/server.c:243] waitpid for Xwayland fork failed: No child processes
(EE) failed to read Wayland events: Broken pipe
xterm: Xt error: Can't open display: :0

$ cc --version
FreeBSD clang version 11.0.1 (git@github.com:llvm/llvm-project.git llvmorg-11.0.1-0-g43ff75f2c3fe)
Target: x86_64-unknown-freebsd13.0
Thread model: posix
InstalledDir: /usr/bin

$ pkg info -x cagebreak wayland wlroots
cagebreak-1.8.3
wayland-1.20.0
wayland-protocols-1.25
xwayland-devel-21.0.99.1.171
wlroots-0.15.1
project-repo commented 2 years ago

Thanks for the bug report! I'm not quite sure what is causing this atm... My best guess is that this is due to a version discrepancy somewhere, seeing as the xwayland initialization code in cagebreak v1.8.3 and cage v0.1.4 is pretty much identical as much as I can tell. What version of cage are you using? cheers project-repo

jbeich commented 2 years ago

What version of cage are you using?

Patched to fix some bugs + wlroots 0.15 compat:

cage v0.1.4-36-gf71844a unmodified also works fine.

sevz17 commented 2 years ago

See https://github.com/djpohly/dwl/issues/177#issuecomment-1081241033

project-repo commented 2 years ago

Thanks for reporting this @jbeich and for providing a solution @Sevz17! This should be fixed in release 1.9.0 so I'm closing this for now. Feel free to reopen if the bug persists though. Cheers project-repo