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.

オープン
#3,967 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る
area:installation area:platform-linux
主要言語
Shell
スター
11.2k
フォーク
1.9k
平均マージ
14時間 16分
マージ済み PR(30日)
6

説明

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.

コントリビューションガイド

コントリビューションガイドを開く

調査の方向性

このレポートでは Ubuntu 24.04、Guake、Terminal、curl のインストール、auth-code フローについて述べられていますが、リポジトリのファイルや失敗するテストは示されていません。まず、その環境で消失と「not installed」またはアカウント関連のエラーを再現してください。信頼できる原因を特定し、復旧手順を文書化できれば完了です。

索引モデルが issue の本文から書いたものです。

評価

技術スタック
github, shell, ubuntu
領域
authentication, cli
issue の種類
バグ
難易度
4/5
見積もり時間
3〜5日
活発さ
静か
明瞭さ
説明が足りない
初心者へのやさしさ
25/100

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。