Tmux can't working on wayfire

[SLin0218]

Describe the bug tmux can't work option xwayland = false

To Reproduce Steps to reproduce the behavior:

1. open tmux

Expected behavior A clear and concise description of what you expected to happen.

Screenshots or stacktrace

plugins = \
  alpha \
  autostart \
  command \
  cube \
  expo \
  fast-switcher \
  grid \
  idle \
  move \
  oswitch \
  place \
  preserve-output \
  resize \
  scale \
  scale-title-filter \
  switcher \
  vswitch \
  window-rules \
  wm-actions \
  wobbly \
  wrot \
  zoom \
  pixdecor \
  ipc ipc-rules \
  foreign-toplevel shortcuts-inhibit input-method-v1 \
  showrepaint follow-focus \
  session-lock

EE 21-10-24 23:40:05.788 - [wf-config-0.9.0/src/compound-option.cpp:86] The option command/repeatable_binding_slurp is neither specified nor has a default value
EE 21-10-24 23:40:05.788 - [wf-config-0.9.0/src/compound-option.cpp:86] The option command/repeatable_binding_terminal is neither specified nor has a default value
II 21-10-24 23:40:05.788 - [backend/headless/backend.c:67] Creating headless backend
II 21-10-24 23:40:05.788 - [backend/headless/backend.c:17] Starting headless backend
EE 21-10-24 23:40:05.788 - [wayfire-0.9.0/src/core/core.cpp:130] Failed to create wlr_drm_lease_device_v1; VR will not be available!
II 21-10-24 23:40:05.789 - [wayland] unable to lock lockfile /run/user/1000/wayland-1.lock, maybe another compositor is running
II 21-10-24 23:40:05.789 - [wayland] unable to lock lockfile /run/user/1000/wayland-2.lock, maybe another compositor is running
II 21-10-24 23:40:05.789 - [wayland] unable to lock lockfile /run/user/1000/wayland-3.lock, maybe another compositor is running
II 21-10-24 23:40:05.789 - [wayland] unable to lock lockfile /run/user/1000/wayland-4.lock, maybe another compositor is running
II 21-10-24 23:40:05.789 - [wayland] unable to lock lockfile /run/user/1000/wayland-5.lock, maybe another compositor is running
II 21-10-24 23:40:05.789 - [wayland] unable to lock lockfile /run/user/1000/wayland-6.lock, maybe another compositor is running
II 21-10-24 23:40:05.789 - [wayland] unable to lock lockfile /run/user/1000/wayland-7.lock, maybe another compositor is running
II 21-10-24 23:40:05.789 - [wayland] unable to lock lockfile /run/user/1000/wayland-8.lock, maybe another compositor is running
II 21-10-24 23:40:05.789 - [wayfire-0.9.0/src/main.cpp:435] Using socket name wayland-9
II 21-10-24 23:40:05.789 - [backend/wayland/backend.c:436] Starting Wayland backend
II 21-10-24 23:40:05.789 - [wayfire-0.9.0/src/core/seat/input-manager.cpp:47] handle new input: wayland-keyboard-default, default mapping: wayland-keyboard-default
II 21-10-24 23:40:05.791 - [wayfire-0.9.0/src/core/output-layout.cpp:1177] new output: WL-1 ("(null) (null) (null)")
II 21-10-24 23:40:05.791 - [wayfire-0.9.0/src/core/output-layout.cpp:460] loaded mode auto
II 21-10-24 23:40:05.792 - [wayfire-0.9.0/src/core/output-layout.cpp:634] Couldn't find matching mode 1280x720@0 for output WL-1. Trying to use custom mode(might not work)
EE 21-10-24 23:40:05.794 - [wayfire-0.9.0/src/core/output-layout.cpp:655] Failed to change adaptive sync on output: WL-1
II 21-10-24 23:40:05.794 - [wayfire-0.9.0/src/core/seat/input-manager.cpp:47] handle new input: wayland-pointer-default, default mapping: wayland-pointer-default
false
false
false
false
EE 21-10-24 23:40:05.832 - [types/wlr_cursor.c:1174] Cannot map device "wayland-keyboard-default" to output (not found in this cursor)

Wayfire version 0.9.0

[ammen99]

Does it work with xwayland=true?

[SLin0218]

Does it work with xwayland=true?

can work

[ammen99]

Sorry for the late response, but that sounds like a bug in tmux, not in Wayfire. Maybe tmux wants to connect to Xwayland (something in your initialization, maybe?) and fails.