zed-industries/zed · error
{message}: {error_details}
Error message
{message}: {error_details} What it means
Startup failure report in zed/src/main.rs: files that must be created before launch were not created; {message} describes what failed and {error_details} carries the underlying error. Shown in a critical prompt, after which the app exits.
Source
Thrown at crates/zed/src/main.rs:148
window
.update(cx, |_, window, cx| {
let response = window.prompt(
gpui::PromptLevel::Critical,
message,
Some(&error_details),
&["Exit"],
cx,
);
cx.spawn_in(window, async move |_, cx| {
response.await?;
cx.update(|_, cx| cx.quit())
})
.detach_and_log_err(cx);
})
.log_err();
} else {
fail_to_open_window(anyhow::anyhow!("{message}: {error_details}"), cx)
}
})
}
fn fail_to_open_window_async(e: anyhow::Error, cx: &mut AsyncApp) {
cx.update(|cx| fail_to_open_window(e, cx));
}
fn fail_to_open_window(e: anyhow::Error, _cx: &mut App) {
eprintln!(
"Zed failed to open a window: {e:?}. See https://zed.dev/docs/linux for troubleshooting steps."
);
#[cfg(not(any(target_os = "linux", target_os = "freebsd")))]
{
process::exit(1);
}
// Maybe unify this with gpui::platform::linux::platform::ResultExt::notify_err(..)?View on GitHub (pinned to 9d272b0363)
Solutions
- Check disk space and permissions on the config/data directories
- Remove conflicting files at the reported paths
- Run with appropriate privileges if needed
Defensive patterns
Strategy: try-catch
When it happens
Trigger: Thrown at crates/zed/src/main.rs:147 when the library encounters an invalid state.
Common situations: See trigger scenarios.
AI-assisted analysis of zed-industries/zed@9d272b0363 (2026-08-20).
Data as JSON: /api/errors/f2a5d3b3f6fd61b0.
Report an issue: GitHub.