Jason Gauci
@jubalh https://github.com/MisterTea/EternalTerminal/pull/470
@jubalh is sentry going to accept your patch?
It's more common that people need to run et on a different port since 2022 is not standard. What if we added another argument for the ssh port?
That's pretty unorthodox, but as long as we also have the --ssh-port argument, I'm fine with it. Please let me know if you have any issues writing the PR.
Does updating vcpkg fix it? On Sun, Mar 6, 2022, 7:46 AM Yonle ***@***.***> wrote: > Reproduceable as in Debian Bullseye amd64 > > — > Reply to this email...
Instead of rebooting the server, just restart the et service? We did fix a number of issues recently in 6.0.10 that could be the cause of this.
I think a brew upgrade changed your protobuf library. Reinstalling et should fix it.
Sorry, I wasn't clear. You should reinstall eternal terminal since your version of protobuf has changed. On Tue, Sep 14, 2021, 1:45 PM Demyx ***@***.***> wrote: > Ran brew reinstall...
try manually deleting /usr/local/bin/etterminal and then reinstalling et
What about building it from source?