Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[coc.nvim] Server TexLab failed to start: spawn ETXTBSY

See original GitHub issue

Hi. i have void-linux and install latex like this: https://en.wikibooks.org/wiki/LaTeX/Installation#Custom_installation_with_TeX_Live And after that try to install coc-texlab via neovim: :CocInstall coc-texlab When i hit the enter, i see this:

[coc.nvim] TexLab Server is not found, downloading…

And after a while:

[coc.nvim] Server TexLab failed to start: spawn ETXTBSY

Every time i open an .tex file:

[coc.nvim] Error output from texlab: /home/linarcx/.config/coc/extensions/coc-texlab-data/texlab exited with code: null

Tip: I also notice that it downloads a file called: texlab and put it in: /home/linarcx/.config/coc/extensions/coc-texlab-data/texlab

And this is the output of :CocInfo:

## versions

vim version: NVIM v0.3.8
node version: v11.14.0
coc.nvim version: 0.0.71-fa429d0bbc
term: xterm-kitty
platform: linux

## Messages
[coc.nvim] Error output from texlab: /home/linarcx/.config/coc/extensions/coc-texlab-data/texlab exited with code: 127
[coc.nvim] Error output from texlab: Connection to server is erroring. Shutting down server.
[coc.nvim] Error output from texlab: Connection to server is erroring. Shutting down server.
[coc.nvim] Error output from texlab: Connection to server is erroring. Shutting down server.
[coc.nvim] Error output from texlab: /home/linarcx/.config/coc/extensions/coc-texlab-data/texlab exited with code: 127
## Output channel: TexLab

[Error  - 6:14:15 PM] Connection to server is erroring. Shutting down server.
[Error  - 6:14:15 PM] Connection to server is erroring. Shutting down server.
/home/linarcx/.config/coc/extensions/coc-texlab-data/texlab: error while loading shared libraries: libssl.so.1.1: cannot open shared object file: No such file or directory
[Error  - 6:14:15 PM] /home/linarcx/.config/coc/extensions/coc-texlab-data/texlab exited with code: 127

Issue Analytics

State:
Created 4 years ago
Comments:5 (2 by maintainers)

Top GitHub Comments

1reaction

LinArcXcommented, Jul 27, 2019

I find the solution. i build texlab from source and put it’s binary in /home/linarcx/.config/coc/extensions/coc-texlab-data/texlab Now everything works like charm. But should i do everytime build it from source? There is no better way to handle these situations?

0reactions

fannheywardcommented, Jul 27, 2019

You don’t need to build the server every time. After texlab new version released, you can upgrade it from vim by :CocCommand latex.UpdateLanguageServer.

Top Results From Across the Web

neoclide/coc.nvim - Gitter

[coc.nvim] We encountered an issue extracting the Language Server. ... [coc.nvim] Command error: Error: ETXTBSY: text file is busy, open ...

Serverless framework: Chrome "Error: spawn ETXTBSY"

However when I run: $ sls invoke -f hello. I get: { "errorType": "Error", "errorMessage": "spawn ETXTBSY", "trace": [ "Error: spawn ETXTBSY" ...

coc-texlab - npm

Start using coc-texlab in your project by running `npm i coc-texlab`. ... for LaTeX documents, powered by the TexLab language server.

`UnhandledRejection: spawn ETXTBSY` - Fannheyward/Coc-Texlab

[coc.nvim]: UnhandledRejection: spawn ETXTBSY Error: spawn ETXTBSY at ChildProcess.spawn ... The newly downloaded server works ok after restarting coc.

Texlab LSP server crashes on launch : r/neovim - Reddit

Hiya, not super used to posting threads like this so excuse my etiquette if it's a bit wonky, wasn't sure which github repo...