Can't Sign-In to Zed: HTTP error: 400 Bad Request (KDE)

[fornellas-maze]

Summary

I'm unable to sign-in, meaning I'm unable to use GH Copilot.

Steps to trigger the problem:

1. Open zed
2. Click "Sign in"

Actual Behavior:

I get this error:

Expected Behavior:

for it to... sign in.

The issue seems to be here:

2025-02-26T14:25:12.583853248Z [INFO] connected to rpc endpoint https://collab.zed.dev/rpc
2025-02-26T14:25:12.930474442Z [INFO] set status on client 304613: ConnectionError
2025-02-26T14:25:12.930750137Z [ERROR] HTTP error: 400 Bad Request

Caused by:
    HTTP error: 400 Bad Request

Full log: Zed.log

Zed Version and System Specs

Zed: v0.174.8 (Zed)
OS: Linux Wayland neon 24.04
Memory: 30.7 GiB
Architecture: x86_64
GPU: AMD Radeon 780M (RADV GFX1103_R1) || radv || Mesa 24.2.8-1ubuntu1~24.04.1

[notpeter]

Is this happening when you are attempting to:

1. login into Zed (upper right hand corner)
2. GitHub Copilot (copilot icon -> sign in)
3. GitHub Copilot (Assistant->Configuration->Copilot Chat->Sign In)

Logging into Zed is with your GitHub login is distinct from authorizing Zed as a device for Copilot. They are entirely distinct authorization flows (e.g they can be logged into distinct accounts and have independent login/logout state)

[sakloui]

I can confirm this is happening to me as well on v0.174.6 and v0.175.5. This is at least for me specifically for logging into Zed. I have not tried logging into Github Copilot.

This is on fedora 41, KDE Plasma 6.3.1

Building v0.173.11 right now, will update below.
Update: Seems v0.173.11 also is not working. Going further back just in case.
Update 2: v0.168.3 also has the issue

screenshots

[sakloui]

Alright did some more testing, this seems to be an issue in oo7/Kwallet. I haven't been able to figure out which of the two.

Check KWalletManager and check if there's a key under Secret Service > Binary Data > zed-github-account

Like so

If it isn't there you can try the following:

• Close Zed
• Go to settings > KDE Wallet and untick "Use KWallet for the Secret Service interface"
• Kill kwalletd6
• Start Zed, the Sign in button should no longer have the disconnected icon to the left of it
• Click Sign in and go through the log in process
• Close Zed
• Re-enable "Use KWallet for the Secret Service interface"
• Kill kwalletd6 again
• Start KWalletManager and open the wallet
• If you start Zed, it should shown the same Sign in button as before
• Do the log in process again
• It should hopefully have now added the key to the keychain, restarting Zed should automatically log in.

This worked for me at least, YMMV.

[fornellas-maze]

@notpeter

Is this happening when you are attempting to:

This: login into Zed (upper right hand corner)

@sakloui

Check KWalletManager and check if there's a key under Secret Service > Binary Data > zed-github-account

No key there:

It should hopefully have now added the key to the keychain, restarting Zed should automatically log in.

Everything worked until the previous step, but no key added at this point, and Zed asks to login every time it is open.

If I leave "Use KWallet for the Secret Service interface" unset, zed login survives a restart, so... "fixed".

[sakloui]

If you disable KWallet's SS interface it won't write a permanent key for login, so it's a solution. Though any other application won't be able to use KWallet either, so it's not a perfect solution.

After re-enabling the "Use KWallet for the Secret Service interface" setting, could you also enable "Prompt when an application accesses a wallet" under the Access Control tab. Then kill KWallet6d again and follow the steps after re-enabling the setting? It should prompt you for access when opening the keyring with KWalletManager and Zed.

[sakloui]

This is definitely a KWallet issue it seems.