shadowsocksrr / electron-ssr

Shadowsocksr client using electron
MIT License
1.73k stars 510 forks source link

deepin v20 beta 运行appimage版本无任何响应 #80

Open ziggy1030 opened 4 years ago

ziggy1030 commented 4 years ago

Your os

Linux deepin v20 beta

The version of electron-ssr

0.3.0-alpha.5

What's the problem

运行appimage后没有任何反应,也没有进程打开

App log here

LittleTurtle2333 commented 4 years ago

对0.2.7没有问题

xVanTuring commented 4 years ago

@AppJ-GS Is there any output in log file(located in ~/.config/electron-ssr/logs)

ziggy1030 commented 4 years ago

@AppJ-GS Is there any output in log file(located in ~/.config/electron-ssr/logs)

No,I couldn't the app,so there is no log file.

zty199 commented 4 years ago

Actually, if you run Appimage in deepin-terminal, you will get this info:

[15634:0604/224100.928277:FATAL:setuid_sandbox_host.cc(157)] The SUID sandbox helper binary was found, but is not configured correctly. Rather than run without sandboxing I'm aborting now. You need to make sure that /tmp/.mount_electrMJ20lJ/chrome-sandbox is owned by root and has mode 4755.

But you can install the app with deb, and run "sudo chmod 4755 /opt/electron-ssr/chrome-sandbox" to fix this problem. This solution is metioned in issue #85 .

ziggy1030 commented 4 years ago

Actually, if you run Appimage in deepin-terminal, you will get this info:

[15634:0604/224100.928277:FATAL:setuid_sandbox_host.cc(157)] The SUID sandbox helper binary was found, but is not configured correctly. Rather than run without sandboxing I'm aborting now. You need to make sure that /tmp/.mount_electrMJ20lJ/chrome-sandbox is owned by root and has mode 4755.

But if you can install the app with deb, and run "sudo chmod 4755 /opt/electron-ssr/chrome-sandbox" to fix this problem. This resolution is metioned in issue #85 .

Thanks,I'll try later

zty199 commented 4 years ago

See this: https://bbs.deepin.org/forum.php?mod=viewthread&tid=195642&extra=

Seems that this problem happens in Debian 10, which Deepin V20 is based on. You can edit /etc/sysctl.conf and add args as follows:

kernel.unprivileged_userns_clone=1

Then reboot your system and problem might be solved.