search

warpdotdev / Warp

Warp is a modern, Rust-based terminal with AI built in so you and your team can build great software, faster.
https://warp.dev
Other
20.21k stars 334 forks source link

linux: xdg-open does not open url #4501

Open jxn opened 3 months ago

jxn commented 3 months ago

Discord username (optional)

No response

Describe the bug

Any command that seems to use xdg-open to launch a browser from the terminal interface seems to be broken. Examples include things like az login for azure-cli and aws sso login for AWS CLI. You can also trigger the issue by using xdg-open directly to launch a command.

To reproduce

Open warp terminal, enter xdg-open http://example.org

Observe that no browser window launches and the output spawns with a seemingly infinite stream of "Warning: ConnectToCompositor() try again : Connection refused" lines. I see no other errors or information. CPU also seems to spike, but maybe that's just from warp processing a huge number of lines in the output.

Since the compositor is mentioned, perhaps this issue is only on wayland? I'm using Ubuntu mantic with a gnome-wayland or ubuntu-wayland session.

Note that the error does not appear and the browser launches correctly in gnome-terminal, terminator, etc.

Expected behavior

A browser window should open at example.org

Screenshots

No response

Operating system

Linux

Operating system and version

Ubuntu 23.10

Shell Version

5.2.15(1)

Current Warp version

v0.2024.03.05.08.02.stable_00

Regression

No, this bug or issue has existed throughout my experience using Warp

Recent working Warp date

No response

Additional context

Ubuntu linux with gnome-wayland session

Does this block you from using Warp daily?

Yes, this issue prevents me from using Warp daily.

Is this a Warp specific issue? (i.e. does it happen in Terminal, iTerm, Kitty, etc.)

Yes, this I confirmed this only happens in Warp, not other terminals.

Warp Internal (ignore): linear-label:b9d78064-c89e-4973-b153-5178a31ee54e

None

alokedesai commented 3 months ago

@jxn Are you using Firefox as your default browser by chance?

jxn commented 3 months ago

@alokedesai I am. I just tested and it works with chromium, though I'd ditch warp if I had to choose between firefox and warp.

Is this a warp problem or do you think the issue is with another project?

jxn commented 3 months ago

I did try with xdg-open and firefox nightly (125.0a125.0a1 (2024-03-06)) as the default browser works fine, so it's either the official snap from ubuntu or just a particular set of firefox versions that do not work?

Note I have tested 4 other terminals, 5 if you count the VS Code terminal, and they all work fine with the current ubuntu snap firefox version, so it seems to be limited to warp?

jxn commented 3 months ago

Just returning to note that indeed the xdg-open process spawned from warp keeps running and takes up 100% CPU until manually killed. I also cannot reproduce this behavior in other terminals.