fix(webui): force headless ozone backend on linux#1973
Merged
piorpua merged 4 commits intoiOfficeAI:mainfrom Mar 31, 2026
Merged
fix(webui): force headless ozone backend on linux#1973piorpua merged 4 commits intoiOfficeAI:mainfrom
piorpua merged 4 commits intoiOfficeAI:mainfrom
Conversation
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
yejiming
force-pushed
the
jimmy/2026-03-31-03-19-38
branch
from
39a4d00 to
198248b
Compare
Contributor
Code Review：fix(webui): force headless ozone backend on linux (#1973)变更概述本 PR 修改了 方案评估结论：✅ 方案合理 方案正确解决了 PR 描述的问题——在某些 Linux 环境（如 Termux/proot）中， 问题清单
汇总
结论
本报告由本地 CONCLUSION: APPROVED |
Contributor
|
✅ 已自动 review，无阻塞性问题，正在触发自动合并。 |
piorpua
added
bot:done
|
Hello, thanks for your prompt edit. root@localhost:~# dpkg -P AionUi
(Reading database ... 87204 files and directories currently installed.)
Removing aionui (1.9.4) ...
update-alternatives: warning: alternative /opt/AionUi/AionUi (part of link group AionUi) doesn't exist; removing from list of alternatives
update-alternatives: warning: /etc/alternatives/AionUi is dangling; it will be updated with best choice
Purging configuration files for aionui (1.9.4) ...
Processing triggers for hicolor-icon-theme (0.18-2) ...
root@localhost:~# apt purge --autoremove
Summary:
Upgrading: 0, Installing: 0, Removing: 0, Not Upgrading: 81
root@localhost:~# dpkg -i AionUi-1.9.4-linux-arm64.deb
Selecting previously unselected package aionui.
(Reading database ... 86627 files and directories currently installed.)
Preparing to unpack AionUi-1.9.4-linux-arm64.deb ...
Unpacking aionui (1.9.4) ...
Setting up aionui (1.9.4) ...
update-alternatives: using /opt/AionUi/AionUi to provide /usr/bin/AionUi (AionUi) in auto mode
Processing triggers for hicolor-icon-theme (0.18-2) ...
root@localhost:~# AionUi --no-sandbox --webui
[10861:0331/174501.584677:ERROR:dbus/bus.cc:408] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
build.buildStorage global
build.buildStorage system
build.buildStorage agent.chat
build.buildStorage agent.chat.message
build.buildStorage agent.config
build.buildStorage agent.env
[CDP] Chrome DevTools Protocol disabled
17:45:11.676 › [security] Generated random CSRF secret for this session
17:45:11.710 › [ChannelBridge] Initializing...
17:45:11.715 › [ChannelBridge] Initialized
17:45:17.500 › [ShellEnv-Diag] platform=linux, arch=arm64, node=v22.21.1
17:45:17.509 › [ShellEnv-Diag] process.env.PATH (first 300): /opt/AionUi:/root/.cargo/bin:/root/.bun/bin:/root/.local/bin:/root/.nvm/versions/node/v24.11.1/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/local/games:/usr/games:/data/data/com.termux/files/usr/bin:/system/bin:/system/xbin:/root/.dotnet/tools
17:45:18.376 › [Database] Schema initialized successfully
[10861:0331/174518.420317:ERROR:ui/ozone/platform/x11/ozone_platform_x11.cc:250] Missing X server or $DISPLAY
[10861:0331/174518.420535:ERROR:ui/aura/env.cc:257] The platform failed to initialize. Exiting.
Segmentation fault |
Contributor
Author
Let me double-check this. |
|
Currently doing this works: root@localhost:~# xvfb-run --auto-servernum --server-args="-screen 0 1920x1080x24" AionUi --webui --no-sandbox
[6605:0401/111629.521961:ERROR:dbus/bus.cc:408] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
build.buildStorage global
build.buildStorage system
build.buildStorage agent.chat
build.buildStorage agent.chat.message
build.buildStorage agent.config
build.buildStorage agent.env
[CDP] Chrome DevTools Protocol disabled
11:16:39.692 › [security] Generated random CSRF secret for this session
11:16:39.719 › [ChannelBridge] Initializing...
11:16:39.722 › [ChannelBridge] Initialized
11:16:45.672 › [ShellEnv-Diag] platform=linux, arch=arm64, node=v22.21.1
11:16:45.675 › [ShellEnv-Diag] process.env.PATH (first 300): /opt/AionUi:/root/.cargo/bin:/root/.bun/bin:/root/.local/bin:/root/.nvm/versions/node/v24.11.1/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/local/games:/usr/games:/data/data/com.termux/files/usr/bin:/system/bin:/system/xbin:/root/.dotnet/tools
11:16:46.465 › [Database] Schema initialized successfully
[6605:0401/111647.640399:ERROR:dbus/bus.cc:408] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
[6605:0401/111647.642002:ERROR:dbus/bus.cc:408] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
[6605:0401/111647.700441:ERROR:dbus/bus.cc:408] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[6605:0401/111647.700776:ERROR:dbus/bus.cc:408] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[6605:0401/111647.700912:ERROR:dbus/bus.cc:408] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[6605:0401/111647.701231:ERROR:dbus/bus.cc:408] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[6605:0401/111647.703045:ERROR:dbus/object_proxy.cc:590] Failed to call method: org.freedesktop.DBus.NameHasOwner: object_path= /org/freedesktop/DBus: unknown error type:
[6605:0401/111647.767525:ERROR:content/browser/zygote_host/zygote_host_impl_linux.cc:283] Failed to adjust OOM score of renderer with pid 6902: Permission denied (13)
[6605:0401/111647.790382:ERROR:device/udev_linux/udev_watcher.cc:51] Failed to initialize a udev monitor.
11:16:49.143 › [AionUi:ready] start +0ms
11:16:49.155 › [AionUi:init] start +0ms
11:16:49.163 › [AionUi:init] 1. migrateLegacyData +9ms
11:16:49.177 › [AionUi:init] 3. storage interceptors +22ms
11:16:49.291 › [AionUi:init] 4. MCP config +137ms
11:16:56.436 › [AionUi:init] 5.1 initBuiltinAssistantRules +7281ms
11:16:56.527 › [AionUi:init] 5.2 assistant config + migrations +7372ms
11:16:56.543 › [AionUi:init] 6. database +7389ms
11:16:56.550 › [AionUi:init] done +7395ms
11:16:56.556 › [AionUi:process] initStorage +7403ms
11:16:56.568 › [Extensions] Initializing extension registry...
11:16:56.619 › [Extensions] Registry initialized in 42ms: 0 extension(s), 0 adapter(s), 0 MCP server(s), 0 assistant(s), 0 agent(s), 0 skill(s), 0 theme(s), 0 channel plugin(s), 0 webui contribution(s), 0 settings tab(s), 0 model provider(s), 0 i18n locale(s)
11:16:56.622 › [AionUi:process] ExtensionRegistry +7470ms
11:16:56.626 › [ChannelManager] Initializing...
11:16:56.634 › [ChannelManager] Initialized successfully
11:16:56.635 › [AionUi:process] ChannelManager +7483ms
11:16:56.636 › [AionUi:ready] initializeProcess +7493ms
11:16:56.648 › [AionUi:ready] initializeZoomFactor +7505ms
11:16:56.662 › [WebUI] Serving renderer from: /opt/AionUi/resources/app.asar/out/renderer
11:16:56.678 ›
🚀 WebUI started / WebUI 已启动: http://localhost:25808
11:16:56.679 › [WebSocketManager] Initialized
11:16:56.680 › [ACP] Starting agent detection...
11:17:01.701 › [ShellEnv] Failed to load shell environment: spawnSync /bin/bash ETIMEDOUT
11:17:03.888 › [ACP] Detection completed in 7207ms, found 14 agents
[6605:0401/111703.900048:ERROR:dbus/bus.cc:408] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
[6605:0401/111703.902815:ERROR:dbus/bus.cc:408] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
[6605:0401/111703.905218:ERROR:dbus/bus.cc:408] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directoryWorkaround resource usage: root@localhost:~# top -b | grep -E 'xvfb-run|Xvfb'
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
6551 root 10 -10 2404 1528 1408 S 0.0 0.0 0:00.04 xvfb-run
6600 root 10 -10 182900 64376 45700 S 0.0 1.1 0:00.35 Xvfb |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Pull Request
Description
This PR fixes a startup crash in Linux headless environments (e.g., Termux/proot) when launching AionUi with
--webui.Previously, headless Ozone flags were only applied when
DISPLAYwas missing. In some environments,DISPLAYmay be present but unusable, causing Electron to still initialize the X11 platform and crash with:Missing X server or $DISPLAYThe platform failed to initialize. Exiting.Segmentation faultWhat changed
src/process/utils/configureChromium.ts, for Linux in--webuiand--resetpassmodes, always force:--ozone-platform=headless--disable-gpu--disable-software-rasterizerThis ensures WebUI/reset-password flows do not depend on X11/Wayland availability.
Related Issues
Type of Change
Testing
Screenshots
N/A (no UI visual change).
Additional Context
This change intentionally scopes to WebUI/reset-password startup paths and does not affect normal desktop window mode.