Copilot dissapeared while working in two terminals, now won't run, says it is not installed. Ubuntu 24.04 LTS Guake and Terminal.
- Lenguaje dominante
- Shell
- Estrellas
- 11.2k
- Forks
- 1.9k
- Merge medio
- 14 h 16 min
- PR fusionados (30 d)
- 6
Descripción
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.
Guía de contribución
Línea de trabajo
El informe menciona Ubuntu 24.04, Guake y Terminal, la instalación de curl y un flujo de auth-code, pero no menciona archivos del repositorio ni ninguna prueba que falle. Empieza reproduciendo la desaparición y los errores “not installed” o de cuenta en esa configuración; se considerará terminado cuando se haya identificado una causa fiable y documentado una ruta de recuperación.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- github, shell, ubuntu
- Área
- authentication, cli
- Tipo de issue
- Error
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Estado de actividad
- Tranquilo
- Claridad
- Necesita aclaración
- Aptitud para principiantes
- 25/100