Linux first-run: atlas off PATH (bash), desktop not installed, AppImage blank window (EGL)
Mantenedores costumam responder em até 1 dia
Ninguém assumiu esta issue ainda.
Avaliação
- Dificuldade
- 5/5
- Tempo estimado
- Mais de uma semana
- Facilidade para iniciantes
- 22/100
- Tipo de issue
- Bug
- Clareza
- Razoavelmente clara
- Status de atividade
- Ativa
- Domínio
- desktop-dev, release, tooling
Direção de pesquisa
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.
Escrita pelo modelo de indexação a partir do texto da issue.
Descrição
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
- Linguagem predominante
- Rust
- Estrelas
- 3
- Forks
- 1
- Merge médio
- 9h 51min
- PRs com merge (30d)
- 310
Preparar o ambiente
- Sem Dockerfile nem arquivo Docker Compose
- Tem um modelo de pull request
- Ler o guia de contribuição
Primeiros passos
- Leia a issue inteira e depois o guia de contribuição do projeto.
- Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
- Faça um fork do repositório e trabalhe em uma branch.
- Abra um pull request que referencie o número da issue.
Mais de codeatlasdev/atlas
-
type: bug
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 75/100
codeatlasdev/atlas#597 ·
Mantenedores costumam responder em até 1 dia
-
area: ci os: linux type: bug
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 78/100
codeatlasdev/atlas#496 ·
Mantenedores costumam responder em até 1 dia
-
area: ci type: bug
Dificuldade 3/5 1-2 dias Facilidade para iniciantes 68/100
codeatlasdev/atlas#596 ·
Mantenedores costumam responder em até 1 dia
-
os: linux type: bug
Dificuldade 3/5 1-2 dias Facilidade para iniciantes 68/100
codeatlasdev/atlas#591 ·
Mantenedores costumam responder em até 1 dia
-
flaky: Windows scripts job hits test timeouts (check-dco, i18n runner/translate, check-changed)Abertaarea: ci os: windows type: bug
Dificuldade 3/5 1-2 dias Facilidade para iniciantes 56/100
codeatlasdev/atlas#550 · 1 comentário ·
Mantenedores costumam responder em até 1 dia
Todas as issues de codeatlasdev/atlas
Issues semelhantes
-
marketing
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 76/100
Mantenedores costumam responder em até 1 dia
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 74/100
kinqsradio/orbyn-engineering#729 ·
-
Plans page scenario races Shift+Tab against the plan list being drawn again in Firefox and WebKitAbertabug
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 83/100
nledford/Ladderback#1091 ·
Mantenedores costumam responder em até 1 dia
-
bug fix packaging ui user-sprint
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 78/100
Vondor/KassenSturz#1197 ·
Mantenedores costumam responder em até 1 dia
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 82/100
Mantenedores costumam responder em até 1 dia