AUR (en) - clash-for-windows-electron-bin

Search Criteria

Enter search criteria

Search by

Keywords

Out of Date

Sort by

Sort order

Per page

Package Details: clash-for-windows-electron-bin 0.20.39-1

Package Actions

Git Clone URL:	https://aur.archlinux.org/clash-for-windows-electron-bin.git (read-only, click to copy)
Package Base:	clash-for-windows-electron-bin
Description:	A Windows/macOS/Linux GUI based on Clash and Electron. Using system clash and electron
Upstream URL:	https://github.com/Fndroid/clash_for_windows_pkg
Keywords:	clash4windows
Licenses:	unknown
Conflicts:	clash-for-windows, clash-for-windows-bin
Provides:	clash-for-windows, clash-for-windows-electron
Submitter:	sukanka
Maintainer:	None
Last Packager:	sukanka
Votes:	9
Popularity:	0.055807
First Submitted:	2022-02-26 17:04 (UTC)
Last Updated:	2023-10-20 12:05 (UTC)

Dependencies (8)

clash-geoip^AUR
electron (electron13-bin^AUR, electron16-bin^AUR, electron15-bin^AUR, electron14-bin^AUR, electron17-bin^AUR, electron18-bin^AUR, electron19-bin^AUR, electron21-bin^AUR, electron20-bin^AUR, electron22-bin^AUR, electron9-bin^AUR, electron10-bin^AUR, electron11-bin^AUR, electron12-bin^AUR, electron2-bin^AUR, electron23-bin^AUR, electron24-bin^AUR, electron25-bin^AUR, electron26-bin^AUR, electron27-bin^AUR, electron28-bin^AUR)
asar (make)
npm (nodejs6-bin^AUR, nodejs-nightly^AUR, corepacker^AUR) (make)
clash-meta^AUR (clash-meta-bin^AUR) (optional) – clash core
clash-premium-bin (optional) – clash core
iproute2 (iproute2-git^AUR, busybox-coreutils^AUR, iproute2-selinux^AUR) (optional) – TUN mode required.
nftables (nftables-git^AUR, nftables-fullcone^AUR) (optional) – TUN mode required.

Required by (0)

Sources (6)

Pinned Comments

sukanka commented on 2022-09-05 08:46 (UTC) (edited on 2022-09-25 02:04 (UTC) by sukanka)

要使用 clash-meta 请在安装和更新后执行 (x64 根据情况替换成 arm64)

sudo ln -sf /usr/bin/clash-meta /opt/clash-for-windows/static/files/linux/x64/clash-linux

然后再

sudo systemctl restart clash-core-service@$USER

已知问题：service mode 不会亮，但是不影响使用。同时轻量模式不可使用（由于 service mode 检测为 inactive)

sukanka commented on 2022-02-26 17:07 (UTC) (edited on 2022-09-18 09:00 (UTC) by sukanka)

这个软件包尽量使用系统的组件，如果要使用 TUN 模式，务必记得安装所有可选依赖（clash-core 选一个你喜欢的就行）并

sudo systemctl start clash-core-service@$USER
sudo systemctl enable clash-core-service@$USER

在更新后记得

sudo systemctl restart clash-core-service@$USER

Latest Comments

1 2 Next › Last »

sukanka commented on 2023-06-22 05:29 (UTC)

@Brainos, 现在本软件包实际上依赖 electron25 而不是 electron22，所以无需修改。

Brainos commented on 2023-06-22 05:11 (UTC)

Arch Repo的electron现在是指向electron稳定版本的meta包，不再和其他版本的electron冲突，可以考虑把依赖的electron换成electron22。

diff --git a/PKGBUILD b/PKGBUILD
index b614482..6d74215 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -10,7 +10,7 @@ url="https://github.com/Fndroid/clash_for_windows_pkg"
 install=clash-for-windows-bin.install
 provides=('clash-for-windows' ${_pkgname})
 conflicts=('clash-for-windows' 'clash-for-windows-bin')
-depends=('electron'
+depends=('electron22'
 'clash-geoip'
 )
 optdepends=(
@@ -28,7 +28,7 @@ source=(
     "cfw-start-pre.sh"
     "clash-core-service@.service")
 sha256sums=('9a84b05b718913d3d1fbe462a2da671abff2cb94bb2ded75a3af12204cebe32f'
-            'db2e160e5d5cf82ed69d0926ac51c0eccb9efc541f89be3bb467d85be509f735'
+            '3d636a66fc582afe663ad6716ec95e42bf2f24d3eca319229afc51576f8bc44c'
             '4bea2fe6e8580a4316451ca5c8b921bd908422d839f8bd9ceaddd709f9178153'
             'd55c2f4088505116a5bad6d09f5ebe232e7c6a269ea6bf46daada02bc3a9f961')
 sha256sums_x86_64=('deadc2a21223e0169e747471e9c0cfa95bbf9645bd6534f287342aa050b853d1')
diff --git a/cfw b/cfw
index 70b654a..533285a 100644
--- a/cfw
+++ b/cfw
@@ -1,3 +1,3 @@
 #!/bin/sh
 cd /opt/clash-for-windows
-electron app.asar "$@"
+electron22 app.asar "$@"

W47MPUSv commented on 2023-01-30 05:44 (UTC)

@sukanka ok, 我自己改下PKGBUILD好了

sukanka commented on 2023-01-29 02:03 (UTC)

@W47MPUSv 这个问题我也遇到了，但是不影响使用我就没管。我目前只有 electron 跟 electron19, 所以不是很想把这个改成 electron20.

W47MPUSv commented on 2023-01-28 18:09 (UTC)

现在上游electron版本更新到了22，在我的机器上会出现启动cfw不能创建tray图标的问题。使用electron20是正常的。不知是否需要指定electron版本。

谢谢

wordlesswind commented on 2023-01-17 04:31 (UTC)

似乎启用通知后，每次通知都会“假死”一段时间。

Kimiblock commented on 2022-11-15 11:44 (UTC) (edited on 2022-11-15 13:16 (UTC) by Kimiblock)

近期 Arch 频繁死机, 似乎和 cfw 的 service 有关, 经常晚上锁屏(未睡眠)早上起来发现电脑卡死, 切换 TTY 没反应. 重启后 journalctl -b-1 输出了几万行和 unit=clash-core-service@kimiblockzhou 有关的信息截图

11月 15 06:27:30 kimiblock-archlinux-zenbook audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=clash-core-service@kimiblockzhou comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
11月 15 06:27:30 kimiblock-archlinux-zenbook systemd[1]: Stopped Clash core service created by Clash for Windows for normal user..
11月 15 06:27:30 kimiblock-archlinux-zenbook systemd[1]: Starting Clash core service created by Clash for Windows for normal user....
11月 15 06:27:30 kimiblock-archlinux-zenbook systemd[1]: Started Clash core service created by Clash for Windows for normal user..
11月 15 06:27:30 kimiblock-archlinux-zenbook audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=clash-core-service@kimiblockzhou comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
11月 15 06:27:30 kimiblock-archlinux-zenbook kernel: audit: type=1130 audit(1668464850.112:782): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=clash-core-service@kimiblockzhou comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
11月 15 06:27:30 kimiblock-archlinux-zenbook clash-core-service[6585]: listen fail with error: listen tcp 127.0.0.1:53000: bind: address already in use
11月 15 06:27:30 kimiblock-archlinux-zenbook systemd[1]: clash-core-service@kimiblockzhou.service: Deactivated successfully.
11月 15 06:27:30 kimiblock-archlinux-zenbook audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=clash-core-service@kimiblockzhou comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
11月 15 06:27:30 kimiblock-archlinux-zenbook kernel: audit: type=1131 audit(1668464850.116:783): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=clash-core-service@kimiblockzhou comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
11月 15 06:27:32 kimiblock-archlinux-zenbook CROND[2038]: (root) CMDOUT (  0.00% complete (??? remaining)  0.00% complete (??? remaining)  0.00% complete (??? remaining)                                                                                Removed '2022-11-15_06-23-15')
11月 15 06:27:32 kimiblock-archlinux-zenbook CROND[2038]: (root) CMDOUT (------------------------------------------------------------------------------)
11月 15 06:27:32 kimiblock-archlinux-zenbook crontab[6595]: (root) LIST (root)
11月 15 06:27:32 kimiblock-archlinux-zenbook crontab[6596]: (root) LIST (root)
11月 15 06:27:32 kimiblock-archlinux-zenbook systemd[1]: run-timeshift-2041-backup.mount: Deactivated successfully.
11月 15 06:27:35 kimiblock-archlinux-zenbook systemd[1]: clash-core-service@kimiblockzhou.service: Scheduled restart job, restart counter is at 164.
11月 15 06:27:35 kimiblock-archlinux-zenbook audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=clash-core-service@kimiblockzhou comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
11月 15 06:27:35 kimiblock-archlinux-zenbook audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=clash-core-service@kimiblockzhou comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
11月 15 06:27:35 kimiblock-archlinux-zenbook kernel: audit: type=1130 audit(1668464855.299:784): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=clash-core-service@kimiblockzhou comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
11月 15 06:27:35 kimiblock-archlinux-zenbook kernel: audit: type=1131 audit(1668464855.299:785): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=clash-core-service@kimiblockzhou comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
11月 15 06:27:35 kimiblock-archlinux-zenbook systemd[1]: Stopped Clash core service created by Clash for Windows for normal user..
11月 15 06:27:35 kimiblock-archlinux-zenbook systemd[1]: Starting Clash core service created by Clash for Windows for normal user....
11月 15 06:27:35 kimiblock-archlinux-zenbook systemd[1]: Started Clash core service created by Clash for Windows for normal user..
11月 15 06:27:35 kimiblock-archlinux-zenbook audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=clash-core-service@kimiblockzhou comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
11月 15 06:27:35 kimiblock-archlinux-zenbook kernel: audit: type=1130 audit(1668464855.352:786): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=clash-core-service@kimiblockzhou comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
11月 15 06:27:35 kimiblock-archlinux-zenbook clash-core-service[6614]: listen fail with error: listen tcp 127.0.0.1:53000: bind: address already in use
11月 15 06:27:35 kimiblock-archlinux-zenbook systemd[1]: clash-core-service@kimiblockzhou.service: Deactivated successfully.
11月 15 06:27:35 kimiblock-archlinux-zenbook audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=clash-core-service@kimiblockzhou comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
11月 15 06:27:35 kimiblock-archlinux-zenbook kernel: audit: type=1131 audit(1668464855.356:787): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=clash-core-service@kimiblockzhou comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
11月 15 06:27:37 kimiblock-archlinux-zenbook CROND[2038]: (root) CMDEND (sleep 10m && timeshift --create --scripted --tags B)
11月 15 06:27:40 kimiblock-archlinux-zenbook systemd[1]: clash-core-service@kimiblockzhou.service: Scheduled restart job, restart counter is at 165.
11月 15 06:27:40 kimiblock-archlinux-zenbook kernel: audit: type=1130 audit(1668464860.549:788): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=clash-core-service@kimiblockzhou comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
11月 15 06:27:40 kimiblock-archlinux-zenbook kernel: audit: type=1131 audit(1668464860.549:789): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=clash-core-service@kimiblockzhou comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
11月 15 06:27:40 kimiblock-archlinux-zenbook audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=clash-core-service@kimiblockzhou comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
11月 15 06:27:40 kimiblock-archlinux-zenbook audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=clash-core-service@kimiblockzhou comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
11月 15 06:27:40 kimiblock-archlinux-zenbook systemd[1]: Stopped Clash core service created by Clash for Windows for normal user..
11月 15 06:27:40 kimiblock-archlinux-zenbook systemd[1]: Starting Clash core service created by Clash for Windows for normal user....
11月 15 06:27:40 kimiblock-archlinux-zenbook systemd[1]: Started Clash core service created by Clash for Windows for normal user..
11月 15 06:27:40 kimiblock-archlinux-zenbook audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=clash-core-service@kimiblockzhou comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
11月 15 06:27:40 kimiblock-archlinux-zenbook clash-core-service[6632]: listen fail with error: listen tcp 127.0.0.1:53000: bind: address already in use
11月 15 06:27:40 kimiblock-archlinux-zenbook kernel: audit: type=1130 audit(1668464860.609:790): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=clash-core-service@kimiblockzhou comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
11月 15 06:27:40 kimiblock-archlinux-zenbook systemd[1]: clash-core-service@kimiblockzhou.service: Deactivated successfully.
11月 15 06:27:40 kimiblock-archlinux-zenbook audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=clash-core-service@kimiblockzhou comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
11月 15 06:27:40 kimiblock-archlinux-zenbook kernel: audit: type=1131 audit(1668464860.613:791): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=clash-core-service@kimiblockzhou comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
11月 15 06:27:45 kimiblock-archlinux-zenbook systemd[1]: clash-core-service@kimiblockzhou.service: Scheduled restart job, restart counter is at 166.
11月 15 06:27:45 kimiblock-archlinux-zenbook systemd[1]: Stopped Clash core service created by Clash for Windows for normal user..
11月 15 06:27:45 kimiblock-archlinux-zenbook audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=clash-core-service@kimiblockzhou comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
11月 15 06:27:45 kimiblock-archlinux-zenbook kernel: audit: type=1130 audit(1668464865.799:792): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=clash-core-service@kimiblockzhou comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
11月 15 06:27:45 kimiblock-archlinux-zenbook kernel: audit: type=1131 audit(1668464865.799:793): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=clash-core-service@kimiblockzhou comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
11月 15 06:27:45 kimiblock-archlinux-zenbook audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=clash-core-service@kimiblockzhou comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
11月 15 06:27:45 kimiblock-archlinux-zenbook systemd[1]: Starting Clash core service created by Clash for Windows for normal user....
11月 15 06:27:45 kimiblock-archlinux-zenbook systemd[1]: Starting Cleanup of Temporary Directories...
11月 15 06:27:45 kimiblock-archlinux-zenbook systemd[1]: Started Clash core service created by Clash for Windows for normal user..
11月 15 06:27:45 kimiblock-archlinux-zenbook audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=clash-core-service@kimiblockzhou comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
11月 15 06:27:45 kimiblock-archlinux-zenbook kernel: audit: type=1130 audit(1668464865.846:794): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=clash-core-service@kimiblockzhou comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
11月 15 06:27:45 kimiblock-archlinux-zenbook clash-core-service[6653]: listen fail with error: listen tcp 127.0.0.1:53000: bind: address already in use
11月 15 06:27:45 kimiblock-archlinux-zenbook systemd[1]: clash-core-service@kimiblockzhou.service: Deactivated successfully.
11月 15 06:27:45 kimiblock-archlinux-zenbook audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=clash-core-service@kimiblockzhou comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'

disable 并 mask 掉自带服务

sudo bash -c 'systemctl disable --now clash-core-service.service && systemctl mask clash-core-service.service'

之后似乎没有再复发, 日志也不再刷上面那种信息了, 很奇怪.

otakutyrant commented on 2022-11-08 10:09 (UTC)

This clash-for-windows-electron-bin is not out-of-the-box, so I use clash-for-windows-bin instead.

behrad commented on 2022-11-05 18:13 (UTC)

Thanks for your help, it is working!

sukanka commented on 2022-11-05 10:31 (UTC) (edited on 2022-11-05 10:36 (UTC) by sukanka)

@behrad, the app always shows that the service mode is not activated, even after you started clash-core-service@$USER.

But you can use all tun features normally as long as clash-core-service@$USER runs(for more info, see this issue), so just ignore the message.

You may need to check the status of clash-core-service@$USER if it does not work.

As for clash-core-service.service, it is not provided by this package, this package only provides clash-core-service@.service. So I don't know anything about that.

And DO NOT USE the in-app way to install service mode for this pkg (or you may want to try clash-for-windows-bin)