github / github/copilot-cli

Copilot dissapeared while working in two terminals, now won't run, says it is not installed. Ubuntu 24.04 LTS Guake and Terminal.

Ouverte
#3,967 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub
area:installation area:platform-linux
Langage dominant
Shell
Étoiles
11.2k
Forks
1.9k
Merge moyen
14 h 16 min
PR mergées (30 j)
6

Description

On my first try of copilot, I was thrilled by its performance. It made a gist for me containing commands etc. I made a macro for me to invoke it with one word. It was great. Then it dissapeared, never to return.

**What happened:**
Using Guake, it was making a gist with keyboard commands, help tips, often used routines etc, and made it availble in Terminal.
Then copilot dissapeared from Guake as I was using it. My hands were on my keyboard a the time, its not impossible I inadvertently touch the q ket, or it crashed - I can't be sure.

_Side note_ - Copilot had said I must log in and out of Gnome desktop to make permanent some edits it made. I said no as I have an open project in use.ai in Chrome that was paused for 24 hours because of use,ai's unbeleivable nasty token cutoff nonsense. I need to continue that this afternoon.

Ater it dissapeared, on trying to reload it in Guake, it said it copilot was not installed, install it with snap.
I have never used snap, I installed it with curl, and I still use apt-install for installs on Ubuntu.
So I double clicked the app instead, it gave an auth code, the code was accepted, but still no copilot. That happened a few times, now it tells me I need an account, which I have. Stuck.
Copilot's online help ai tells me it is too scared to help.

Copilot had been joyfully rewiring stuff under the hood, but the session is no longer available, I can't track what it did to undo it.
Any ideas?
Bear in mind I've only used copilot for a couple of hours, not exactly familiar with it.

Guide de contribution

Ouvrir le guide de contribution

Piste de recherche

Le rapport mentionne Ubuntu 24.04, Guake et Terminal, l’installation de curl ainsi qu’un flux auth-code, mais aucun fichier du dépôt ni aucun test en échec. Commencez par reproduire la disparition et les erreurs « not installed » ou de compte dans cette configuration ; le travail sera terminé lorsqu’une cause fiable aura été identifiée et qu’une procédure de récupération aura été documentée.

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

Évaluation

Stack technique
github, shell, ubuntu
Domaine
authentication, cli
Type d'issue
Bug
Difficulté
4/5
Temps estimé
3-5 jours
Activité
Calme
Clarté
À clarifier
Accessibilité débutants
25/100

Recevez les nouvelles issues par e-mail

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