Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

Error when starting Atom from terminal

Ouverte
  • Quelque chose ne va pas ?
#189 1 commentaire 0 réactions 0 personnes assignées Voir sur GitHub

Personne n'a encore pris cette issue.

Évaluation

Difficulté
3/5
Temps estimé
1-2 jours
Accessibilité débutants
25/100
Type d'issue
Bug
Clarté
À clarifier
Activité
À l'abandon
Stack technique
javascript, python
Domaine
devtools

Piste de recherche

Reproduisez l’échec en lançant Atom avec atom ., puis examinez les entrées de la pile ide-python autour de python/lib/utils.js et python/lib/main.js, en particulier detectPipEnv. Comparez les environnements de lancement du terminal et du bureau ; le travail est terminé lorsque le démarrage depuis le terminal ne produit plus spawn ENOTDIR et que les packages des environnements virtuels restent disponibles.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

Hey,
I have the follow error when opening atom from the terminal with atom .
Once atom is opened, every time a open a python module I get the error.

internal/child_process.js:358 Uncaught (in promise) Error: spawn ENOTDIR
    at ChildProcess.spawn (internal/child_process.js:358)
    at Object.spawn (child_process.js:543)
    at resolve (/home/somnium/.atom/…thon/lib/utils.js:9)
    at new Promise (<anonymous>)
    at detectPipEnv (/home/somnium/.atom/…thon/lib/utils.js:8)
    at PythonLanguageClient.startServerProcess (/home/somnium/.atom/…thon/lib/main.js:50)
    at PythonLanguageClient.<anonymous> (auto-languageclient.ts:298)
    at Generator.next (<anonymous>)
    at /home/somnium/.atom/…languageclient.js:7
    at new Promise (<anonymous>)
    at __awaiter (/home/somnium/.atom/…languageclient.js:3)
    at process.reportBusyWhile (auto-languageclient.ts:298)
    at AtomIdeProvider.<anonymous> (atom-ide-provider.js? [sm]:7)
    at Generator.next (<anonymous>)
    at step (/home/somnium/.atom/…m-ide-provider.js:9)
    at /home/somnium/.atom/…m-ide-provider.js:9
    at new Promise (<anonymous>)
    at AtomIdeProvider.<anonymous> (/home/somnium/.atom/…m-ide-provider.js:9)
    at Object.reportBusyWhile (index.js? [sm]:33)
    at PythonLanguageClient.<anonymous> (auto-languageclient.ts:798)
    at Generator.next (<anonymous>)
    at /home/somnium/.atom/…languageclient.js:7
    at new Promise (<anonymous>)
    at __awaiter (/home/somnium/.atom/…languageclient.js:3)
    at PythonLanguageClient.AutoLanguageClient.reportBusyWhile (auto-languageclient.ts:796)
    at PythonLanguageClient.<anonymous> (auto-languageclient.ts:296)
    at Generator.next (<anonymous>)
    at /home/somnium/.atom/…languageclient.js:7
    at new Promise (<anonymous>)
    at __awaiter (/home/somnium/.atom/…languageclient.js:3)
    at PythonLanguageClient.startServer (auto-languageclient.ts:295)
    at ServerManager._serverManager.server_manager_js_1.ServerManager [as _startServer] (auto-languageclient.ts:253)
    at ServerManager.<anonymous> (server-manager.ts:155)
    at Generator.next (<anonymous>)
    at /home/somnium/.atom/…server-manager.js:7
    at new Promise (<anonymous>)
internal/child_process.js:358 Uncaught (in promise) Error: spawn ENOTDIR
    at ChildProcess.spawn (internal/child_process.js:358)
    at Object.spawn (child_process.js:543)
    at resolve (/home/somnium/.atom/…thon/lib/utils.js:9)
    at new Promise (<anonymous>)
    at detectPipEnv (/home/somnium/.atom/…thon/lib/utils.js:8)
    at PythonLanguageClient.startServerProcess (/home/somnium/.atom/…thon/lib/main.js:50)
    at PythonLanguageClient.<anonymous> (auto-languageclient.ts:298)
    at Generator.next (<anonymous>)
    at /home/somnium/.atom/…languageclient.js:7
    at new Promise (<anonymous>)
    at __awaiter (/home/somnium/.atom/…languageclient.js:3)
    at process.reportBusyWhile (auto-languageclient.ts:298)
    at AtomIdeProvider.<anonymous> (atom-ide-provider.js? [sm]:7)
    at Generator.next (<anonymous>)
    at step (/home/somnium/.atom/…m-ide-provider.js:9)
    at /home/somnium/.atom/…m-ide-provider.js:9
    at new Promise (<anonymous>)
    at AtomIdeProvider.<anonymous> (/home/somnium/.atom/…m-ide-provider.js:9)
    at Object.reportBusyWhile (index.js? [sm]:33)
    at PythonLanguageClient.<anonymous> (auto-languageclient.ts:798)
    at Generator.next (<anonymous>)
    at /home/somnium/.atom/…languageclient.js:7
    at new Promise (<anonymous>)
    at __awaiter (/home/somnium/.atom/…languageclient.js:3)
    at PythonLanguageClient.AutoLanguageClient.reportBusyWhile (auto-languageclient.ts:796)
    at PythonLanguageClient.<anonymous> (auto-languageclient.ts:296)
    at Generator.next (<anonymous>)
    at /home/somnium/.atom/…languageclient.js:7
    at new Promise (<anonymous>)
    at __awaiter (/home/somnium/.atom/…languageclient.js:3)
    at PythonLanguageClient.startServer (auto-languageclient.ts:295)
    at ServerManager._serverManager.server_manager_js_1.ServerManager [as _startServer] (auto-languageclient.ts:253)
    at ServerManager.<anonymous> (server-manager.ts:155)
    at Generator.next (<anonymous>)
    at /home/somnium/.atom/…server-manager.js:7
    at new Promise (<anonymous>)

Everything works if I'm starting Atom from desktop icon, however I need to be able to running it from the terminal.
When running sudo atom . it works, but I don't get my virtual env installed packages available which makes it impossible to use some other atom plugins features.

My setup:
OS: Ubuntu 18
Atom: 1.42
ide-python: 1.5.0

Any help is welcome.
Thanks

Langage dominant
JavaScript
Étoiles
238
Forks
41
Aucune PR mergée en 30 j

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de atom-community/ide-python

Toutes les issues de atom-community/ide-python

Issues similaires

Plus d'issues JavaScript

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.