Environment variables probably

Discord username (optional)

No response

Describe the bug

If I run 'flatpak run com.moonlight_stream.Moonlight' from a normal terminal when I open moonlight and connect to another computer everything works, but if I run the command 'flatpak run com.moon....' from the Warp terminal when I connect to a computer the screen goes black, I suspect it's a problem with environment variables not set or not exported by warp.
It may not be a bug but rather how Warp works, but I would expect it to work as it does in a normal terminal, so I wouldn't have to open it while using Warp.

To reproduce

explanation above

Expected behavior

No response

Screenshots

No response

Operating system

Linux

Operating system and version

6.6.10-1-MANJARO

Shell Version

bash 5.2.21

Current Warp version

v0.2024.03.19.08.01.stable_01

Regression

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

Recent working Warp date

No response

Additional context

No response

Does this block you from using Warp daily?

No

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

The report names no source files or tests. Reproduce flatpak run com.moonlight_stream.Moonlight in Warp and a normal terminal, then compare their exported environment variables; done means connecting to another computer no longer produces a black screen in Warp.