DioxusLabs/dioxus · error · anyhow::Error
AppImage was not created. Expected at: {} linuxdeploy stdout
Error message
AppImage was not created. Expected at: {}
linuxdeploy stdout:
{}
linuxdeploy stderr:
{} What it means
After linuxdeploy ran, neither the expected AppImage path nor any discoverable AppImage output existed in the output directory. The tool reported success or was relocated, so the fallback search failed and the bundler bails with the expected path and tool logs.
Source
Thrown at packages/cli/src/bundler/linux.rs:112
);
}
if !appimage_path.exists() {
let found = find_appimage_output(&output_dir, &name)?;
if let Some(found_path) = found {
if found_path != appimage_path {
fs::rename(&found_path, &appimage_path).with_context(|| {
format!(
"Failed to rename {} to {}",
found_path.display(),
appimage_path.display()
)
})?;
}
} else {
let stdout = String::from_utf8_lossy(&output.stdout);
let stderr = String::from_utf8_lossy(&output.stderr);
bail!(
"AppImage was not created. Expected at: {}\nlinuxdeploy stdout:\n{}\nlinuxdeploy stderr:\n{}",
appimage_path.display(),
stdout.trim(),
stderr.trim()
);
}
}
let _ = fs::remove_dir_all(&appdir);
tracing::info!("Created AppImage: {}", appimage_path.display());
Ok(vec![appimage_path])
}
/// Build a Debian `.deb` package entirely in Rust.
///
/// The Debian bundler does not shell out to `dpkg-deb`. Instead it assembles the
/// archive directly from its three standard members:View on GitHub (pinned to 24f6a829df)
Solutions
- linuxdeploy did not produce the AppImage. Check its stdout and stderr output and ensure it completed without errors.
Defensive patterns
Strategy: fallback
When it happens
Trigger: Thrown at packages/cli/src/bundler/linux.rs:112 when the library encounters an invalid state.
Common situations: See trigger scenarios.
AI-assisted analysis of DioxusLabs/dioxus@24f6a829df (2026-08-23).
Data as JSON: /api/errors/55fc3a9fda28444d.
Report an issue: GitHub.