Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failed to fetch? #20

Closed
a523 opened this issue Jan 17, 2019 · 9 comments
Closed

Failed to fetch? #20

a523 opened this issue Jan 17, 2019 · 9 comments

Comments

@a523
Copy link

a523 commented Jan 17, 2019

我在fedora29 下安装最新版本, 无法添加下载任务:提示Failed to fetch。
???

@agalwood
Copy link
Owner

fedora29 我没测试过,请 ps 看下本地是否有 aria2 进程

@a523
Copy link
Author

a523 commented Jan 17, 2019

[xin@xin-thinkpad ~]$ ps aux | grep aria2
xin       5101  0.0  0.0 221424  6052 tty2     S+   13:07   0:00 /tmp/.mount_MotrixlyqlDx/resources/engine/aria2c --conf-path=/tmp/.mount_MotrixlyqlDx/resources/engine/aria2.conf --save-session=/home/xin/.config/Motrix/download.session --input-file=/home/xin/.config/Motrix/download.session --dir=/home/xin/下载 --continue=true --pause=true --split=16 --rpc-listen-port=16800 --auto-file-renaming=true --allow-overwrite=true --max-concurrent-downloads=5 --max-connection-per-server=16 --min-split-size=1M --max-overall-download-limit=0 --max-overall-upload-limit=0 --max-download-limit=0 --user-agent=Transmission/2.94

看起来是有这个进程。有哪些地方可以看日志么?
@agalwood

@agalwood
Copy link
Owner

Linux日志在:
~/.config/Motrix/log.log
为啥看起来你是运行在临时目录?

@a523
Copy link
Author

a523 commented Jan 17, 2019

我是用appimage 安装的, 不确定为什么运行在临时目录。日志没有其他内容, 只是退出的时候会打印一个

[2019-01-17 17:51:28.255] [warn] will-quit

@TanghaohanSC
Copy link

manjaro 也遇到了这个问题

@helundong
Copy link

manjaro 同样的问题,不能使用

@Jisxu
Copy link

Jisxu commented Mar 2, 2019

manjaro 也遇到了这个问题

我是arch遇到这个问题,命令行里用sudo启动下就可以用了。
原因是创建文件/var/cache/aria2.session时没有权限

@TanghaohanSC
Copy link

manjaro 也遇到了这个问题

我是arch遇到这个问题,命令行里用sudo启动下就可以用了。
原因是创建文件/var/cache/aria2.session时没有权限

感谢

@lock
Copy link

lock bot commented Apr 9, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Apr 9, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants