To do a manual authentication

1. run 'zed --foreground'
2. copy the failed to open url ''https://zed.dev/native_app_signin..."
3. paste it in your browser

zed will pick it up from there.

There is no failed to open url ''https://zed.dev/native_app_signin..." log for me.

There is no failed to open url ''https://zed.dev/native_app_signin..." log for me.

Is zed able to access internet ? Can you share logs

i am not able to find any log related to failed to open url

[2024-07-12T18:02:30 02:00 ERROR client] DBus error service error org.freedesktop.zbus.Error: The name org.freedesktop.secrets was not provided by any .service files
[2024-07-12T18:02:30 02:00 ERROR gpui] Zbus(MethodError(OwnedErrorName("org.freedesktop.DBus.Error.UnknownMethod"), Some("No such interface “org.freedesktop.portal.OpenURI” on object at path /org/freedesktop/portal/desktop"), Msg { type: Error, sender: UniqueName(":1.4"), reply-serial: 30, body: Signature("s"), fds: [] }))

This is what I'm getting when running with --foreground flag on Void Linux, running DWM. I'm running Zed through flatpak, with flatseal allowing DBUS access.

I am on Arch XMonad. Same error as described above by @lalishansh including steps of reproduction. The relevant output after running `zen --foreground`` and then clicking on the "Sign in" button is:

[2024-07-12T23:03:25 02:00 ERROR client] DBus error service error org.freedesktop.zbus.Error: The name is not activatable
[2024-07-12T23:03:25 02:00 ERROR gpui] Zbus(MethodError(OwnedErrorName("org.freedesktop.DBus.Error.ServiceUnknown"), Some("The name is not activatable"), Msg { type: Error, sender: UniqueName("org.freedesktop.DBus"), reply-serial: 30, body: Signature("s"), fds: [] }))

Got a similar output as @joeyjooste , but the message is different. It says: The name is not activatable. I also do NOT get any links in the logs which I can use to sign in.

I am on Arch XMonad. Same error as described above by @lalishansh including steps of reproduction. The relevant output after running `zen --foreground`` and then clicking on the "Sign in" button is:

[2024-07-12T23:03:25 02:00 ERROR client] DBus error service error org.freedesktop.zbus.Error: The name is not activatable
[2024-07-12T23:03:25 02:00 ERROR gpui] Zbus(MethodError(OwnedErrorName("org.freedesktop.DBus.Error.ServiceUnknown"), Some("The name is not activatable"), Msg { type: Error, sender: UniqueName("org.freedesktop.DBus"), reply-serial: 30, body: Signature("s"), fds: [] }))

Got a similar output as @joeyjooste , but the message is different. It says: The name is not activatable. I also do NOT get any links in the logs which I can use to sign in.

HI, I had the same problem on archlinux, the gnome-keyring-daemon -r -d did the magic, once the keyring restarted and entered in Zed all the git/authentication related things worked

HI, I had the same problem on archlinux, the gnome-keyring-daemon -r -d did the magic, once the keyring restarted and entered in Zed all the git/authentication related things worked

I am not running gnome, and don't think I have any keyrings otherwise installed. Also, what did you mean by "entered in Zed"? Do we need to manually add Zed to the keyring?

UPDATE: I installed gnome-keyring and ran gnome-keyring-daemon -r -d but it did not change anything.

I ran gnome-keyring-daemon -r -d
Then when opening zed, gnome keyring opens and prompts me for a login password for zed. (this seems to be a keyring specific thing not the actual zed login) then after entering a password it goes away and zed behaves the same as before. Where it gives an error when clicking the Sign-In button.

I ran gnome-keyring-daemon -r -d Then when opening zed, gnome keyring opens and prompts me for a login password for zed. (this seems to be a keyring specific thing not the actual zed login) then after entering a password it goes away and zed behaves the same as before. Where it gives an error when clicking the Sign-In button.

I have also received this error on several occasions, but I am not sure what the steps to reproduce in my case are. Simply opening the app does not do it for me. I cannot reproduce it consistently, but click the buttons and close it enough times, and I do get it.

I am able to resolve the issue with switching to gnome-keyring (😑) for secrets and encryption. gnome-keyring-daemon -r -d is required after login (for my setup) because this service depends on graphical-session-pre.target and graphical-session.target.
And for my minimal set it doesn't launch. (Using greetd-tuigreet, dwl (to keep user session WM separate, will do somthing about it))

I was also getting extension error not being able to execute. Fixed it with nix-ld as just like flatpaks, nix packages are sandboxed but need FHS compliance, so instead we make necessary deps available. Src https://nixos.wiki/wiki/Jetbrains_Tools

Current tree for my dotfiles

I am able to resolve the issue with switching to gnome-keyring (😑) for secrets and encryption. gnome-keyring-daemon -r -d is required after login (for my setup) because this service depends on graphical-session-pre.target and graphical-session.target. And for my minimal set it doesn't launch. (Using greetd-tuigreet, dwl (to keep user session WM separate, will do somthing about it))

I was also getting extension error not being able to execute. Fixed it with nix-ld as just like flatpaks, nix packages are sandboxed but need FHS compliance, so instead we make necessary deps available. Src https://nixos.wiki/wiki/Jetbrains_Tools

Current tree for my dotfiles

After installing gnome-keyring and running the command, did you do anything special for Zed?

Essentially, after doing the gnome-keyring/dbus config, Zed sign in prompts me to create a new keychain, and I enter the password and press continue. But then, I again get the error:

[2024-07-14T22:44:26 02:00 ERROR gpui] Zbus(MethodError(OwnedErrorName("org.freedesktop.DBus.Error.ServiceUnknown"), Some("The name is not activatable"), Msg { type: Error, sender: UniqueName("org.freedesktop.DBus"), reply-serial: 40, body: Signature("s"), fds: [] }))

Fix was installing GTK properly and then using gnome-keyring. Apparently my GTK paths were broken.

Fix was installing GTK properly and then using gnome-keyring. Apparently my GTK paths were broken.

How did you fix the issue ? I ran gnome-keyring-daemon -r -d but nothing happens

Fix was installing GTK properly and then using gnome-keyring. Apparently my GTK paths were broken.

How did you fix the issue ? I ran gnome-keyring-daemon -r -d but nothing happen.

1. (Re)Install xdg-desktop-portal-impl and xdg-desktop-portal. (or equivalent on your distro)
2. The file /usr/share/xdg-desktop-portal/portals/gnome-keyring.portal should be:

[portal]
DBusName=org.freedesktop.secrets
Interfaces=org.freedesktop.impl.portal.Secret
UseIn=gnome;gtk;

3. Run the commands:
   1. dbus-update-activation-environment --all
   2. dbus-update-activation-environment DISPLAY XAUTHORITY
   3. gnome-keyring-daemon -r -d

I do not know which of these was the actual fix, or whether all of them were needed. But, running all of them did work...

PS: Make sure you have GTK.