# Mojo LSP Failing to read SDK on Kali Linux(Debian based) **URL:** \ **Category:** LSP\ **Created:** [September 24, 2026, 12:09pm UTC](https://forum.modular.com/t/mojo-lsp-failing-to-read-sdk-on-kali-linux-debian-based/3525 "2026-09-24T12:09:46Z")\ **Posts on this page:** 15\ **Page:** 1
**Author:** ![Autark\_pseudo](https://sea1.discourse-cdn.com/flex001/user_avatar/forum.modular.com/autark_pseudo/32/1297_2.png) [@Autark\_pseudo](https://forum.modular.com/u/Autark_pseudo)\ **Post date:** [September 24, 2026, 12:09pm UTC](https://forum.modular.com/t/mojo-lsp-failing-to-read-sdk-on-kali-linux-debian-based/3525/1 "2026-09-24T12:09:46Z")
Mojo fails to install directly on Kali Linux and requires ‘UV venv’ on UV installation which is not listed in the official page installation guide-yet after succesfull installation the VS Code IDE Mojo package allows code to be typed but fails to run it as “No SDK” yet the UV virtual environment for Mojo,Mojo and MAX have all successfully installed. Pixi also fails in a direct installation. And the compiler fails to list the errors in the code(which i deliberately wrote them on this second screenshot at runtime and on the first displays UV failing to install. Do any folks have solutions for this?? ![Screenshot From 2026-09-23 02-17-18](https://us1.discourse-cdn.com/flex001/uploads/modular/original/2X/3/316d0b0e2c9a33af0c35917420a53efebb23bea4.jpeg) ![Screenshot From 2026-09-24 07-18-04](https://us1.discourse-cdn.com/flex001/uploads/modular/original/2X/9/9585a6b427fd51f1e18d75b83e34bf7de3016ff0.jpeg) ---
**Author:** ![derickdowney](https://sea1.discourse-cdn.com/flex001/user_avatar/forum.modular.com/derickdowney/32/1287_2.png) [@derickdowney](https://forum.modular.com/u/derickdowney)\ **Post date:** [September 24, 2026, 12:47pm UTC](https://forum.modular.com/t/mojo-lsp-failing-to-read-sdk-on-kali-linux-debian-based/3525/2 "2026-09-24T12:47:50Z")
I could be wrong but it looks like in your first pixi attempt you called “sh~” instead of just “sh”. I wonder if you try again with just “sh” if the pixi will work for you! ---
**Author:** ![Autark\_pseudo](https://sea1.discourse-cdn.com/flex001/user_avatar/forum.modular.com/autark_pseudo/32/1297_2.png) [@Autark\_pseudo](https://forum.modular.com/u/Autark_pseudo)\ **Post date:** [September 24, 2026, 1:09pm UTC](https://forum.modular.com/t/mojo-lsp-failing-to-read-sdk-on-kali-linux-debian-based/3525/3 "2026-09-24T13:09:52Z")
Do you perhaps mean UV? Pixi didn’t work but UV did work . The real problem is on the SDK. ---
**Author:** ![Autark\_pseudo](https://sea1.discourse-cdn.com/flex001/user_avatar/forum.modular.com/autark_pseudo/32/1297_2.png) [@Autark\_pseudo](https://forum.modular.com/u/Autark_pseudo)\ **Post date:** [September 24, 2026, 1:20pm UTC](https://forum.modular.com/t/mojo-lsp-failing-to-read-sdk-on-kali-linux-debian-based/3525/4 "2026-09-24T13:20:46Z")
The Major reason i prefer Kali linux is measly because I’m handling some really awesome CyberSecurity projects on Adversarial Machine Learning. Yet i think Mojo is pretty good for this. ---
**Author:** ![derickdowney](https://sea1.discourse-cdn.com/flex001/user_avatar/forum.modular.com/derickdowney/32/1287_2.png) [@derickdowney](https://forum.modular.com/u/derickdowney)\ **Post date:** [September 24, 2026, 1:24pm UTC](https://forum.modular.com/t/mojo-lsp-failing-to-read-sdk-on-kali-linux-debian-based/3525/5 "2026-09-24T13:24:35Z")
@Autark_pseudo I mean that in your screenshot it looks like you may have accidentally typed `sh~` instead of `sh`. See screenshot. If you type “sh” instead, pixi may still work for you? I’m not totally sure though, just a guess. ![Screenshot 2026-09-24 at 8.22.03 AM](https://us1.discourse-cdn.com/flex001/uploads/modular/original/2X/e/e2ad21ff43301cb993cc17121a00a5d1d73dec3d.jpeg) ---
**Author:** ![Autark\_pseudo](https://sea1.discourse-cdn.com/flex001/user_avatar/forum.modular.com/autark_pseudo/32/1297_2.png) [@Autark\_pseudo](https://forum.modular.com/u/Autark_pseudo)\ **Post date:** [September 24, 2026, 1:36pm UTC](https://forum.modular.com/t/mojo-lsp-failing-to-read-sdk-on-kali-linux-debian-based/3525/6 "2026-09-24T13:36:53Z")
Since this environment worked i dont need Pixi: fixing Pixi now wont solve it but the real thing is on the LSP on VS Code: ![Screenshot From 2026-09-24 09-33-52](https://us1.discourse-cdn.com/flex001/uploads/modular/original/2X/4/47f598a2802c6132c75f8a814bb1679235102314.png) ---
**Author:** ![derickdowney](https://sea1.discourse-cdn.com/flex001/user_avatar/forum.modular.com/derickdowney/32/1287_2.png) [@derickdowney](https://forum.modular.com/u/derickdowney)\ **Post date:** [September 24, 2026, 2:13pm UTC](https://forum.modular.com/t/mojo-lsp-failing-to-read-sdk-on-kali-linux-debian-based/3525/7 "2026-09-24T14:13:21Z")
Unfortunately I haven’t worked with “uv” just “pixi”… but when I work with pixi, I need to: - Create the virtual pixi environment (using `pixi init`) - Then activate the virual pixi environment (using `pixi shell`) - Then add the mojo package (using `pixi add mojo`) Since the “mojo” compiler and “mojo-lsp-server” binaries get loaded into `"/.pixi/envs/default/bin/mojo-lsp-server`", then the LSP won’t work unless I activate the virtual environment with “pixi shell”, because doing that adds the “.pixi/envs/default/bin” directory into my path. These errors in your first message make it sound like your “uv” environment is not activated, so $PATH has not been updated to include your virtual environment’s “mojo-lsp-server” binary. Have activated the “uv” environment? ![Screenshot 2026-09-24 at 9.11.29 AM](https://us1.discourse-cdn.com/flex001/uploads/modular/original/2X/6/67e0c56edb0791b327a5c1e866ba961e34fb1eb4.png) ---
**Author:** ![Autark\_pseudo](https://sea1.discourse-cdn.com/flex001/user_avatar/forum.modular.com/autark_pseudo/32/1297_2.png) [@Autark\_pseudo](https://forum.modular.com/u/Autark_pseudo)\ **Post date:** [September 25, 2026, 5:38am UTC](https://forum.modular.com/t/mojo-lsp-failing-to-read-sdk-on-kali-linux-debian-based/3525/8 "2026-09-25T05:38:04Z")
Do any folks in the community have a way to activate UV environment. I was wondering why this was never added to the official page installation guide. Since the $PATH setup for the SDK is the root cause there should be a way to setup a perfect environment on my Kali machine? ---
**Author:** ![Autark\_pseudo](https://sea1.discourse-cdn.com/flex001/user_avatar/forum.modular.com/autark_pseudo/32/1297_2.png) [@Autark\_pseudo](https://forum.modular.com/u/Autark_pseudo)\ **Post date:** [September 25, 2026, 10:20am UTC](https://forum.modular.com/t/mojo-lsp-failing-to-read-sdk-on-kali-linux-debian-based/3525/9 "2026-09-25T10:20:39Z")
Previous citings on UV Installation do not seem like much in both the Discourse Forum and Github. but i found a relevant post that might touch on UV Installation. > [@LSP server with uv and vim](https://forum.modular.com/t/lsp-server-with-uv-and-vim/2285): > > I have a Mojo repository with uv: [GitHub - gonsolo/mojo\_gpu\_raytracer](https://github.com/gonsolo/mojo_gpu_raytracer) To edit: “uv run vim file.mojo” In ~/.vimrc: if executable(‘uv’) au User lsp\_setup call lsp#register\_server({ \ ‘name’: ‘Mojo Language Server’, \ ‘cmd’: {server\_info → [‘uv’, ‘run’, ‘–’, ‘.venv/lib/python3.13/site-packages/max/bin/mojo-lsp-server’, ‘-I’, ‘.venv/lib/python3.13/site-packages/max/lib/mojo’]}, \ ‘whitelist’: [‘mojo’], \ }) endif autocmd FileType mojo nnoremap \ :LspDefinition autocmd FileType… I wonder if folks like @owenhilyard who have worked on Ubuntu before can give a solid answer to this? ---
**Author:** ![ahajha](https://avatars.discourse-cdn.com/v4/letter/a/cdc98d/32.png) [@ahajha](https://forum.modular.com/u/ahajha)\ **Post date:** [September 26, 2026, 4:13am UTC](https://forum.modular.com/t/mojo-lsp-failing-to-read-sdk-on-kali-linux-debian-based/3525/10 "2026-09-26T04:13:01Z")
We should add this to the docs, but the minimum steps should be ```auto uv venv source .venv/bin/activate uv pip install mojo ``` This makes sure you (a) have the venv active, (b) that Mojo gets installed to said venv, and (c) the LSP gets detected. One key difference between `uv` and `pixi` is that `uv` defaults to a global install, but seems to still warn you. `pixi` defaults to a local install, but you can do a global install if you want (though I don’t know if the VSCode extension will work with it, would have to check). ---
**Author:** ![Autark\_pseudo](https://sea1.discourse-cdn.com/flex001/user_avatar/forum.modular.com/autark_pseudo/32/1297_2.png) [@Autark\_pseudo](https://forum.modular.com/u/Autark_pseudo)\ **Post date:** [September 28, 2026, 6:54am UTC](https://forum.modular.com/t/mojo-lsp-failing-to-read-sdk-on-kali-linux-debian-based/3525/11 "2026-09-28T06:54:18Z")
Well it should have been expected to work perfectly but the VS code extension still says the `No SDK`thing. ```auto Using CPython 3.14.7 interpreter at: /usr/bin/python Creating virtual environment at: .venv ✔ A virtual environment already exists at `.venv`. Do you want to replace it? · yes Activate with: source .venv/bin/activate Resolved 9 packages in 1.55s Prepared 1 package in 126ms Installed 9 packages in 66ms + click==8.5.0 + mblack==26.6.0 + mojo==1.1.0 + mojo-compiler==1.1.0 + mojo-compiler-mojo-libs==1.1.0 + mojo-lldb-libs==1.1.0 + mypy-extensions==1.1.0 + pathspec==1.1.1 + platformdirs==4.12.1 ``` This is the ouput . ---
**Author:** ![ahajha](https://avatars.discourse-cdn.com/v4/letter/a/cdc98d/32.png) [@ahajha](https://forum.modular.com/u/ahajha)\ **Post date:** [September 28, 2026, 10:55am UTC](https://forum.modular.com/t/mojo-lsp-failing-to-read-sdk-on-kali-linux-debian-based/3525/12 "2026-09-28T10:55:18Z")
I don’t know the inner workings of the VSCode extensions super well, but I think you’ll want to double check that 1. You have the venv selected in the Python extension. 2. The file `.venv/bin/mojo-lsp-server` exists If those are true, you might just need to restart the extension. Let me know if that works. ---
**Author:** ![Autark\_pseudo](https://sea1.discourse-cdn.com/flex001/user_avatar/forum.modular.com/autark_pseudo/32/1297_2.png) [@Autark\_pseudo](https://forum.modular.com/u/Autark_pseudo)\ **Post date:** [September 28, 2026, 1:32pm UTC](https://forum.modular.com/t/mojo-lsp-failing-to-read-sdk-on-kali-linux-debian-based/3525/13 "2026-09-28T13:32:09Z")
@ahajha Everything should be working out well as of now-based on this screenshot: ![Screenshot From 2026-09-28 09-25-59](https://us1.discourse-cdn.com/flex001/uploads/modular/original/2X/e/e17f3d9cb511fcedfb3e931419b9b7b12e94c78b.png) Since VS code can now read the LSP. The major problem was on the VS code extension restrictions however the LSP is working abit too slow compared to normal speeds in Debian. However if you see any problem just point it out. ---
**Author:** ![Autark\_pseudo](https://sea1.discourse-cdn.com/flex001/user_avatar/forum.modular.com/autark_pseudo/32/1297_2.png) [@Autark\_pseudo](https://forum.modular.com/u/Autark_pseudo)\ **Post date:** [September 28, 2026, 1:36pm UTC](https://forum.modular.com/t/mojo-lsp-failing-to-read-sdk-on-kali-linux-debian-based/3525/14 "2026-09-28T13:36:24Z")
> [@ahajha](#): > > 1. .venv/bin/mojo-lsp-server I think this file already exists. It shouldn’t be part of the `uv install packages` should it? ---
**Author:** ![ahajha](https://avatars.discourse-cdn.com/v4/letter/a/cdc98d/32.png) [@ahajha](https://forum.modular.com/u/ahajha)\ **Post date:** [September 28, 2026, 3:48pm UTC](https://forum.modular.com/t/mojo-lsp-failing-to-read-sdk-on-kali-linux-debian-based/3525/15 "2026-09-28T15:48:54Z")
I don’t know of any reason why the LSP would be slower on Kali than on any other distro. mojo-lsp-server is installed in your case via the `mojo` package, not sure what you mean by “already exists”.