A JavaScript error occurred in the main process（help me

[theCatBoyL]

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

1. Download the original version of lens （latest）
2. A JavaScript error occurred in the main process
3. There is no this file/Users/climber /. K8slens/cli. The sock
4. See error
   Uncaught Exception:
   Error: listen EACCES: permission denied /Users/climber/.k8slens/cli.sock
   at Server.setupListenHandle [as _listen2] (node:net:1882:21)
   at listenInCluster (node:net:1961:12)
   at Server.listen (node:net:2080:5)
   at /Applications/Lens 2.app/Contents/Resources/app.asar/node_modules/@hapi/hapi/lib/core.js:336:31
   at new Promise ()
   at module.exports.internals.Core._listen (/Applications/Lens 2.app/Contents/Resources/app.asar/node_modules/@hapi/hapi/lib/core.js:313:16)
   at module.exports.internals.Core._start (/Applications/Lens 2.app/Contents/Resources/app.asar/node_modules/@hapi/hapi/lib/core.js:287:24)
   at async run (/Applications/Lens 2.app/Contents/Resources/app.asar/node_modules/@lensapp/cli-lens-extension/dist/main.js:317:17)
   at async instantiate (/Applications/Lens 2.app/Contents/Resources/app.asar/node_modules/@lensapp/run-many/dist/index.js:131:5)
   at async Promise.all (index 6)

Environment (please complete the following information):

• Lens Version: Lens: 2024.9.300059-latest
  Electron: 31.6.0
  Chrome: 126.0.6478.234
  Node: 20.17.0
  © 2024 Mirantis, Inc.
• OS:mac os 2 GHz 四核Intel Core i5
• Installation method (e.g. snap or AppImage in Linux):

[sangbui1211]

the same issue on my screen

[theCatBoyL]

the same issue on my screen

bro，how to fix this problem,do you have other suitable version ?

[theCatBoyL]

ok，i had fixed this err, just give the enough authority (sudo chmod 777 /Users/xxx), try create the dictory by yourself(mkdir -p /Users/xxx/.k8slens) ,and (chmod 755 /Users/xxx/.k8slens), then restart the app, that's ok !!!

[clrothmann]

Thank you all for your feedback. We are aware of this issue, and it will be addressed in an upcoming patch release. @theCatBoyL's workaround perfectly outlines the root cause, and in the meantime, you can use it as a temporary solution until the fix is available. We appreciate your patience!

[theCatBoyL]

Thank you all for your feedback. We are aware of this issue, and it will be addressed in an upcoming patch release. @youDoned's workaround perfectly outlines the root cause, and in the meantime, you can use it as a temporary solution until the fix is available. We appreciate your patience!

it’s my honor, i love the app!

[sangbui1211]

Alternatively, you can use the following command for the terminal:
kubectl exec -it {pod-name} -n {namespace} -- /bin/sh