-
Notifications
You must be signed in to change notification settings - Fork 435
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TPM causes my AppImage build to hang on start if no server is running #189
TPM causes my AppImage build to hang on start if no server is running #189
Comments
Client log:
|
Server log :
|
Actually it breaks in the same way even for https://github.com/nelsonenzo/tmux-appimage |
This is a successful log from my system installation of tmux 2.3.
|
Well it turns out it has nothing to do with AppImage, it breaks for all vesion >= 3.1, even for my non-appimage binary. I will look if there are some bugs preventing from working. |
working server log at 3.0a You may want to do a tmux split for both less It looks like There is a server_client_push_stderr in https://github.com/tmux/tmux/blob/3.0a/server-client.c#L2049 but not https://github.com/tmux/tmux/blob/3.1/server-client.c, looks like changed in tmux/tmux@7922f4e#diff-ea06b9ec74ec81be7b034016d6c272203a36aeee30300b9865170429a9d5b999L2075, which looks like from ThomasAdam/tmux@c284ebe, tmux/tmux@c284ebe Some notes: |
Full logs for both working 3.0a and broken 3.1: working 3.0a: broken 3.1, which is killed with SIGTERM: broken 3.1 with the inner tmux logged in -vv, killed with SIGTERM: working 3.0a with the inner tmux logged in -vv: All these logs are produced in my Google Cloud Shell instance, 3.0a logs are produced with my working 3.0a AppImage, 3.1 logs are produced with 3.1b AppImage here https://github.com/nelsonenzo/tmux-appimage/releases/tag/tmux3.1b |
After one Sunday of debug now I understand this problem now. When I start an AppImage instance of tmux (3.1b), it uses the newer file-based protocol that uses MSG_WRITE suite of commands to communicate with the client, which the system version of old tmux (2.3 in this case) will not understand. In What can we do to resolve this problem:
@bruno- can you have a look at this? I can help landing a PR if you can think of how should we work this out. |
Steps to reproduce:
The text was updated successfully, but these errors were encountered: