Can't sign in with GitHub.

[0x6e7a6f]

Check for existing issues

• [X] Completed

Describe the bug / provide steps to reproduce it

When I click on "Sign In", I can link my GitHub account. But after that, I get an error like the screen below. I have the same problem on my laptop (running the same OS but with a different desktop). Same problem when installing Zed from the AUR or from the command line given on the Zed website.

Environment

Zed: v0.144.3 (Zed) OS: Arch Linux (Linux 6.9.9-arch1-1) Desktop: XFCE4 & KDE Plasma 6.1 (Wayland)

If applicable, add mockups / screenshots to help explain present your vision of the feature

If applicable, attach your Zed.log file to this issue.

Zed.log

2024-07-19T00:21:36.887058984+02:00 [INFO] set status on client 0: Authenticating
2024-07-19T00:21:36.887857482+02:00 [INFO] perform;
2024-07-19T00:21:36.887917198+02:00 [INFO] read_command;
2024-07-19T00:21:36.88795186+02:00 [INFO] read_command;
2024-07-19T00:21:36.888212933+02:00 [INFO] socket reader;
2024-07-19T00:21:36.911492836+02:00 [INFO] new;
2024-07-19T00:21:36.911967304+02:00 [INFO] keep_updated;
2024-07-19T00:21:36.911991656+02:00 [INFO] new;
2024-07-19T00:21:38.012516605+02:00 [INFO] Using surface present mode MAILBOX
2024-07-19T00:21:38.012562947+02:00 [WARN] Unable to forbid exclusive full screen
2024-07-19T00:23:16.918935262+02:00 [INFO] set status on client 0: ConnectionError
2024-07-19T00:23:16.919017238+02:00 [ERROR] didn't receive login redirect
2024-07-19T00:23:16.927403765+02:00 [INFO] Creating a descriptor pool for at most 16 sets
2024-07-19T00:23:16.929998349+02:00 [INFO] Creating a descriptor pool for at most 16 sets
2024-07-19T00:23:16.938924791+02:00 [INFO] Creating a descriptor pool for at most 256 sets
2024-07-19T00:23:16.94462997+02:00 [INFO] Creating a descriptor pool for at most 256 sets
2024-07-19T00:23:54.356398966+02:00 [ERROR] window not found
2024-07-19T00:23:54.356430796+02:00 [ERROR] window not found

[jibanes]

maybe xdg/dbus needs a fallback (token or else)

[notpeter]

Following up, are you still seeing this?

[0x6e7a6f]

Following up, are you still seeing this?

Hello ! Yes, I'm still experiencing this issue.