Warp
Warp copied to clipboard
warpdotdev
Warp fails to render a visible window when starting on Ubuntu Linux - libEGL error
Discord username (optional)
No response
Describe the bug
"Tell us what you see" - Nothing. Literally, nothing.
I downloaded and installed Warp from the .deb file. Installed fine. Tried to run it from the dash - it launched and nothing happened. Hmmmm. Tried to run it from the terminal; it launched and there were logs with some warnings; again nothing happened.
What's interesting is it appears to have created an invisible window - I can Alt-Tab to it, and clicking on where it apparently is makes things appear in the log. BUT there is literally nothing to see! So no screenshot possible...
Here are the lines of log output when starting:
stdout is a tty true, in CI false. using logfile: false
02:51:15 [INFO] Spawning terminal server process...
02:51:15 [INFO] Running terminal server...
02:51:15 [WARN] Failed to load font Some("/usr/share/fonts/X11/Type1/D050000L.pfb"): InvalidFontFormat("Type 1")
02:51:15 [WARN] Failed to load font Some("/usr/share/fonts/X11/Type1/NimbusMonoPS-Regular.pfb"): InvalidFontFormat("Type 1")
02:51:15 [WARN] Failed to load font Some("/usr/share/fonts/X11/Type1/StandardSymbolsPS.pfb"): InvalidFontFormat("Type 1")
02:51:15 [WARN] Failed to load font: Hack due to error Font family Hack does not contain any valid fonts
02:51:15 [INFO] Failed to read User from secure storage NotFound
02:51:15 [INFO] Initializing crash reporting Some("stable_release") with tag "v0.2024.02.20.08.01.stable_02"...
02:51:15 [INFO] Starting warp with channel state ChannelState { channel: Stable, app_id: AppId { qualifier: "dev", organization: "warp", application_name: "Warp" }, additional_features: {}, firebase_api_key: "AIzaSyBdy3O3S9hrdayLJxJ7mriBR4qgUaUygAs", server_root_url: "https://app.warp.dev", ws_server_url: "wss://rtc.app.warp.dev/graphql", session_sharing_server_url: Some("wss://session-sharing-server-o3mgmiurkq-uk.a.run.app"), segment_write_key: "sTT9ZajzIaQ0phzLFOnqZ6VOqplJTlaJ", segment_root_url: "https://api.segment.io", releases_base_url: "https://releases.warp.dev", sentry_url: "https://[email protected]/5658526", logfile_name: "warp.log", show_autoupdate_menu_items: true, skip_login: false } and version Some("v0.2024.02.20.08.01.stable_02")
02:51:15 [INFO] Performance metrics collector started
02:51:15 [INFO] Start to flush telemetry events to Segment
02:51:15 [INFO] Initializing app services
02:51:15 [INFO] Start to flush telemetry events to Segment
libEGL warning: egl: failed to create dri2 screen
02:51:15 [WARN] No config found!
02:51:15 [WARN] No config found!
02:51:15 [INFO] Connecting to SQLite database
02:51:15 [INFO] fetching team tester status
02:51:15 [INFO] Checking for update on channel stable_release. Update id is uDt83wk
02:51:15 [INFO] Fetching channel versions (without changelogs) from Warp server
02:51:15 [INFO] dispatching global action for root_view:open_from_restored
02:51:15 [INFO] dispatching global action for root_view:open_new
02:51:15 [WARN] Failed to load font Some("/usr/share/fonts/X11/Type1/D050000L.pfb"): InvalidFontFormat("Type 1")
02:51:15 [WARN] Failed to load font Some("/usr/share/fonts/X11/Type1/NimbusMonoPS-Regular.pfb"): InvalidFontFormat("Type 1")
02:51:15 [WARN] Failed to load font Some("/usr/share/fonts/X11/Type1/StandardSymbolsPS.pfb"): InvalidFontFormat("Type 1")
02:51:15 [WARN] error getting team tester status: Failed to get access token for GraphQL request. Falling back to in-memory state.
02:51:15 [INFO] Guessed window scale factor: 2
libEGL warning: egl: failed to create dri2 screen
02:51:15 [WARN] No config found!
02:51:15 [WARN] No config found!
02:51:15 [INFO] Enabled wgpu backends: Backends(VULKAN | GL | METAL | DX12 | DX11 | BROWSER_WEBGPU)
02:51:15 [INFO] Available wgpu adapters:
02:51:15 [INFO] Cpu: llvmpipe (LLVM 15.0.7, 256 bits)
02:51:15 [INFO] Driver: llvmpipe (Mesa 23.2.1-1ubuntu3.1 (LLVM 15.0.7))
02:51:15 [INFO] Cpu: llvmpipe (LLVM 15.0.7, 256 bits)
02:51:15 [INFO] Driver: Unknown
02:51:15 [INFO] Using Cpu (llvmpipe (LLVM 15.0.7, 256 bits)) for rendering new window.
02:51:15 [WARN] Failed to load font Some("/usr/share/fonts/X11/Type1/C059-Bold.pfb"): InvalidFontFormat("Type 1")
02:51:15 [INFO] Received channel versions from Warp server: dev: ChannelVersion { version_info: VersionInfo { version: "v0.2024.02.23.08.02.dev_00", update_by: None, soft_cutoff: Some("v0.2023.05.12.08.03.dev_00") }, overrides: [] }; preview: ChannelVersion { version_info: VersionInfo { version: "v0.2024.02.23.08.02.preview_00", update_by: None, soft_cutoff: None }, overrides: [] }; canary: ChannelVersion { version_info: VersionInfo { version: "v0.2022.09.29.08.08.canary_00", update_by: None, soft_cutoff: None }, overrides: [] }; beta: ChannelVersion { version_info: VersionInfo { version: "v0.2024.02.20.08.02.beta_00", update_by: None, soft_cutoff: None }, overrides: [] }; stable: ChannelVersion { version_info: VersionInfo { version: "v0.2024.02.13.08.02.stable_00", update_by: None, soft_cutoff: Some("v0.2023.12.19.08.02.stable_00") }, overrides: [VersionOverride { predicate: TargetOS(Linux), version_info: VersionInfo { version: "v0.2024.02.20.08.01.stable_02", update_by: None, soft_cutoff: None } }] }
02:51:15 [WARN] redraw_frame was called 3 times before the frame was drawn
02:51:15 [INFO] No update available
02:51:15 [INFO] active window changed: Some(WindowId(0))
02:51:15 [INFO] dispatching global action for root_view:update_quake_mode_state
02:51:15 [INFO] dispatching global action for workspace:save_app
02:51:16 [INFO] Successfully flushed events to segment from disk
02:51:16 [INFO] Flushed telemetry events.
02:51:41 [INFO] active window changed: None
02:51:41 [INFO] dispatching global action for root_view:update_quake_mode_state
02:51:41 [INFO] dispatching global action for workspace:save_app
02:51:42 [INFO] active window changed: Some(WindowId(0))
02:51:42 [INFO] dispatching global action for root_view:update_quake_mode_state
02:51:42 [INFO] dispatching global action for workspace:save_app
02:51:46 [INFO] Start to flush telemetry events to Segment
02:51:46 [INFO] Dropping empty telemetry batch
02:51:46 [INFO] Flushed telemetry events.
And here are some more showing what happens when I click around or Alt-Tab:
02:51:52 [INFO] active window changed: None
02:51:52 [INFO] dispatching global action for root_view:update_quake_mode_state
02:51:52 [INFO] dispatching global action for workspace:save_app
02:51:57 [INFO] active window changed: Some(WindowId(0))
02:51:57 [INFO] dispatching global action for root_view:update_quake_mode_state
02:51:57 [INFO] dispatching global action for workspace:save_app
02:52:00 [INFO] active window changed: None
02:52:00 [INFO] dispatching global action for root_view:update_quake_mode_state
02:52:00 [INFO] dispatching global action for workspace:save_app
02:52:11 [INFO] active window changed: Some(WindowId(0))
02:52:11 [INFO] dispatching global action for root_view:update_quake_mode_state
02:52:11 [INFO] dispatching global action for workspace:save_app
Truly bizarre.
As well as some messages about failing to load fonts, there's also a libEGL warning that it failed to create a screen - I'm guessing that is the root cause...?
To reproduce
- Use Ubuntu
- Download and install Warp
- Run...
Expected behavior
I'd expect to see something 🙂
Screenshots
No response
Operating system
Linux
Operating system and version
Ubuntu 23.10
Shell Version
Bash 5.2.15
Current Warp version
warp-terminal_0.2024.02.20.08.01.stable.02_amd64.deb
Regression
No, this bug or issue has existed throughout my experience using Warp
Recent working Warp date
N/A - first try
Additional context
Not sure if this is relevant, but my Ubuntu system is a VM running on a KVM setup. I guess it's possible that Warp is expecting a physical GPU and there isn't one - but there is the virtual hardware, and I don't have issues with other applications rendering.
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
I had same issue, took a good 5+ minutes (20 thread 12th gen Intel laptop). Once you get past that they want you to have email access on same computer as your shell to log in because they copy a link to your clipboard without showing you a code to type for mandatory 2FA (at least to sign up). Worst new user experience I've seen on Linux in a long time.
Once it came up by laptop didn't work right, kill -9 even didn't stop warp process. A reboot resulted in a few boot loops then finally got it removed.
@bitshop wow. That's... insane... 🤯
Perhaps I didn't leave it long enough... I left it a good couple of minutes and nothing seemed to be happening. What on earth is it doing in that case?! The mind boggles!
The sign-up process sounds very off-putting too. Like you, I don't have my email on the same machine.
I don't think I'll bother trying again until this start-up problem is fixed at the very least. A great shame, as I have been excitedly awaiting the Linux release for at least a year. Sigh...
Hey folks! Thanks for your patience while trying Warp. Could you download the latest version of Warp at https://www.warp.dev/linux-terminal ?
If using Wayland, you can enable Wayland support by setting the WARP_ENABLE_WAYLAND envar (e.gWARP_ENABLE_WAYLAND=1 warp-terminal).
Unfortunately, no. Same issue remains, except the launch window from console (Konsole) now renders as a split screen, displaying logging output in both. The warp-terminal window displays for a split second and then dies.
Same here. Tried on Linux Mint and Ubuntu. Trying Warp for the first time. Can't find any info on extra steps/config to do after installing the deb file.
@dannyneira thank you - I am very pleased (and a little surprised, based on the other comments above) to report that that updated Debian package did work 🙂
I downloaded and installed it as normal, and then ran it with the Wayland support flag you mentioned, as I am on Wayland in Ubuntu 23.10 with Gnome. It came up with the Warp window right away, and I was able to sign up successfully, and the Warp terminal is running.
This seems to have resolved my problem - although it seems not for others. The only thing I would observe is that after the original attempt, I removed all of the Warp config files that had been created. I don't know if that mattered, but it meant that my attempt today was in a pristine environment.
Thank you again!
...out of interest, running without the Wayland support flag doesn't work, and has the same problem as originally reported.
@bazziebaz @roscom Are you two able to repro on the latest version of Warp? We believe we've fixed this, but it would be useful if you could confirm. Thank you!
@bazziebaz @roscom Are you two able to repro on the latest version of Warp? We believe we've fixed this, but it would be useful if you could confirm. Thank you!
Had trouble on 3 environments:
- Ubuntu VM, now fixed
- Linux Mint VM, now fixed
- Linux Mint laptop, unable to test, gave the laptop away