-
Notifications
You must be signed in to change notification settings - Fork 27
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
skate link freezes #60
Comments
What version of skate are you using? Are you still encountering this issue? |
Hey @174n is this still a problem for you? |
Hey @bashbunni, it is for me. I am using skate version |
We had another user in our Discord mentioning some issues with Arch and Skate. I believe there might be more to troubleshoot here with Arch and Skate... I wasn't able to reproduce this issue linking between Pop_OS! and macOS. I'll see about getting an Arch VM going to try and reproduce. |
I'm experiencing this and I think the issue is iTerm2 or tmux.
I experienced this and believe I isolated it to iterm2. I experienced the hanging behavior in every situation except: comp 1 used terminal (not iterm2) as the initiation. When I select and enter on Yes the prompt clears and messages me that I have been linked. So I would experience the stuck prompt on any laptop using iTerm2 as the initiation. |
@TravisSpangle are you linking a macOS machine to an arch machine? |
both are macOS machines. Have I stumbled into the wrong tooling? |
@TravisSpangle No, I just thought the issue was possibly arch-related since I wasn't able to reproduce. Thanks! I can try this on my end as well and see if I can reproduce. Thank you so much for the additional info |
After I type skate link on one device and the code on another device I get "Link request from:" dialog with yes and no buttons. I can switch between them by using arrow keys. Enter to select didn't work, but after I pressed Y the bash got frozen, arrow keys no longer work and even Ctrl+C doesn't have any effect.
On one device I have raspbian and on another arch.
The text was updated successfully, but these errors were encountered: