Linux first-run: atlas off PATH (bash), desktop not installed, AppImage blank window (EGL)
Maintainer antworten meist innerhalb von 1 Tag
Dieses Issue hat noch niemand übernommen.
Bewertung
- Schwierigkeit
- 5/5
- Geschätzter Aufwand
- Über eine Woche
- Anfängerfreundlichkeit
- 22/100
- Issue-Typ
- Bug
- Klarheit
- Größtenteils klar
- Aktivitätsstatus
- Aktiv
- Bereich
- desktop-dev, release, tooling
Rechercherichtung
This is a multi-bug tracking issue, not a single edit. Start with bug 1: run the already-written failing test shellrc::tests::bash_file_on_linux_is_bashrc_even_with_a_login_file and read ShellEnv::bash_file to see where the bash PATH target is chosen. Bugs 2-4 involve install.sh, tauri.linux.conf.json and the AppImage bundle step, and need maintainer decisions plus hand testing on Debian/Ubuntu/Fedora before anything is startable. Do not pick this up as a first contribution without scoping one sub-issue first.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Beschreibung
Hand-tested on Omarchy (Arch, Hyprland/Wayland, AMD Radeon 680M, Mesa 26.2.5, host webkit2gtk-4.1 2.54.1), fresh curl … install.sh | sh of 1.5.0-alpha.25. Tracking issue: the Linux first-run path breaks in several places. Debian/Ubuntu/Fedora still need the same hand test.
Reproduced
1. atlas: command not found after install (bash)
ShellEnv::bash_filepicks the first of.bash_profile/.bash_login/.bashrcthat exists. Omarchy ships~/.bash_profile, so the PATH line went there.- Linux terminals start non-login bash, which reads only
~/.bashrc. Result:atlasis missing in every new terminal, even though the installer printed✓ Added to PATH [bash ~/.bash_profile]. - The macOS rule (Terminal.app starts login shells) is wrong on Linux. On Linux the line belongs in
~/.bashrc, created if missing. - A regression test is written and fails as expected:
shellrc::tests::bash_file_on_linux_is_bashrc_even_with_a_login_file.
2. The installer does not install the desktop app; it only prints a hint
install.shends with "Next: atlas desktop". Because of bug 1, the user can't even run that command.- Running
~/.atlas/bin/atlas desktopby hand works: it downloads the AppImage to~/.local/bin/atlas-desktopin about 7s, writes a.desktopentry and an icon, and the app shows up in the launcher. - Decide: should install.sh offer or install the desktop app on Linux when a graphical session is present?
3. The AppImage opens a blank window: WebKitWebProcess crashes (EGL)
- stderr:
Could not create default EGL display: EGL_BAD_PARAMETER. Aborting...(×3), then a "Process crashed: WebKitWebProcess" toast over an empty dark window. WEBKIT_DISABLE_DMABUF_RENDERER=1does not fix it.- The AppImage bundles the build distro's
libwayland-client/egl/cursor/server, and those conflict with the host Mesa. Deletingusr/lib/libwayland-*from the extracted AppImage makes the app render (the Welcome screen loads). This is a known class of Tauri/linuxdeploy problem with AppImages on rolling distros. - Fix options:
- strip the bundled libwayland in the bundle step;
- on Arch, prefer the native package (
packaging/arch) or the .deb/.rpm over the AppImage; - have
atlas desktoppick the package format per distro.
4. WebKitNetworkProcess crash and missing GStreamer after the fix in bug 3
GStreamer element appsrc not found+ GStreamer CRITICALs; a "Process crashed: WebKitNetworkProcess" toast is still shown.bundleMediaFramework: falseintauri.linux.conf.json, while the bundled WebKit expects GStreamer plugins.
5. Smaller things
- There is no
atlas doctor, so nothing checks PATH, the desktop install, WebKitGTK/GStreamer, or the session type for the user. Gtk-CRITICAL gtk_distribute_natural_allocationspam at startup (cosmetic).- The "Process crashed… Click to diagnose with AI" toasts are the only signal on a blank window; the CLI exits 0.
Still to test by hand
- Ubuntu 24.04 / Debian 12 / Fedora (VM): install.sh, PATH, AppImage vs .deb/.rpm
- zsh and fish users on Linux (
.zshenv,conf.d) - X11 session
- NVIDIA (EGL/DMABUF)
-
atlas updatesyncing the AppImage;atlas uninstallcleaning the.desktopentry, icon and PATH lines - Onboarding past Welcome: open a project, terminals (xterm.js), services, hostd
- Arch package from
packaging/arch
- Vorherrschende Sprache
- Rust
- Sterne
- 3
- Forks
- 1
- Ø Merge
- 9 Std. 51 Min.
- Gemergte PRs (30 T.)
- 310
Entwicklungsumgebung
- Kein Dockerfile und keine Docker-Compose-Datei
- Hat eine Pull-Request-Vorlage
- Beitragsleitfaden lesen
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Mehr aus codeatlasdev/atlas
-
type: bug
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 75/100
codeatlasdev/atlas#597 ·
Maintainer antworten meist innerhalb von 1 Tag
-
area: ci os: linux type: bug
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 78/100
codeatlasdev/atlas#496 ·
Maintainer antworten meist innerhalb von 1 Tag
-
area: ci type: bug
Schwierigkeit 3/5 1-2 Tage Anfängerfreundlichkeit 68/100
codeatlasdev/atlas#596 ·
Maintainer antworten meist innerhalb von 1 Tag
-
os: linux type: bug
Schwierigkeit 3/5 1-2 Tage Anfängerfreundlichkeit 68/100
codeatlasdev/atlas#591 ·
Maintainer antworten meist innerhalb von 1 Tag
-
flaky: Windows scripts job hits test timeouts (check-dco, i18n runner/translate, check-changed)Offenarea: ci os: windows type: bug
Schwierigkeit 3/5 1-2 Tage Anfängerfreundlichkeit 56/100
codeatlasdev/atlas#550 · 1 Kommentar ·
Maintainer antworten meist innerhalb von 1 Tag
Alle Issues in codeatlasdev/atlas
Ähnliche Issues
-
marketing
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 76/100
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 74/100
kinqsradio/orbyn-engineering#729 ·
-
Plans page scenario races Shift+Tab against the plan list being drawn again in Firefox and WebKitOffenbug
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 83/100
nledford/Ladderback#1091 ·
Maintainer antworten meist innerhalb von 1 Tag
-
bug fix packaging ui user-sprint
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 78/100
Vondor/KassenSturz#1197 ·
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 82/100
Maintainer antworten meist innerhalb von 1 Tag