APatch
APatch copied to clipboard
Unable to use Sandbox in chroot
Please check before submitting an issue/在提交 issue 前请检查
- [X] I have searched the issues and haven't found anything relevant/我已经搜索了 issues 列表,没有发现于本问题相关内容
- [X] If patch failed, root failed, or device unable to boot after flashing the new boot.img. Please goto KernelPatch/修复失败或刷入修补后镜像不能启动,请前往 KernelPatch 提问
- [X] I will upload bugreport file in APatch Manager - Settings - Report log/我会上传 bureport 文件从 APatch 管理器 - 设置 - 发送日志
- [X] I know how to reproduce the issue which may not be specific to my device/我知道如何重新复现这个问题
Version requirement/版本要求
- [X] I am using latest CI version of APatch/我正在使用最新 CI 版本
Describe the bug/描述 bug
unable to use sandbox in chroot while open chromium,
but if i root with magisk it will work, means it use sandbox in chroot. i can run chromium without --no-sandbox
with magisk
Reproduce method/复现方法
Install Linuxdeploy termux-x11 for gui (grant root permission from apatch)
install debian then chromium browser
open it.
it will crash
but if run with --no-sandbox
flag it can run.
Expected behavior/预期行为
chromium should run without --no-sandbox
flag
Actual behaviour /实际行为
through Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: Connection refused
Screenshots/截图
No response
Logs/日志
No response
Device Name/设备名称
Mi 11 Lite 4G
OS Version/系统版本
13
APatch Version/APatch 版本
10657 github action
Kernel Version/内核版本
4.14.190-perf-g019d15b3d168
KernelPatch Version/KernelPatch 版本
0.10.6-dev
Additional context/其他信息
chromium log from apatch apatch_chromium.txt
from magisk magisk_chromium.txt
Did you try whether working on SELinux Permissive
Status? I don't thought this is a bug that APatch should fix.
Did you try whether working on
SELinux Permissive
Status? I don't thought this is a bug that APatch should fix.
i tried with both, it is working with magisk(or magisk delta), so ya, there is problem in APatch
also i check with KernelSu , it is working but still not working with APatch.
same problem in chroot firefox
I have the same problem in chroot, with both chromium and firefox.