OpenListTeam / OpenListTeam/OpenList-Desktop
[错误] 开机自动挂载失效/延迟高:autoMount=true 但日志提示 "No Rclone remotes configured for auto-mount on login",挂载启动滞后于 GitHub 版本检查约 30–40 秒
Nobody has claimed this yet.
- Dominant language
- Vue
- Stars
- 1.5k
- Forks
- 69
- PR merge metrics
- No merged PRs in 30d
Description
错误描述
环境信息
Windows 11 专业版 25H2(10.0.26200)
OpenList Desktop v0.9.1;OpenList core v4.2.5(config.json 中 last_launched_version)
rclone v1.75.0
远程类型:115 Open WebDAV(http://127.0.0.1:5244/dav),network-mode 挂载到 Z:
"115Pan": {
"name": "115Pan",
"type": "webdav",
"url": "http://127.0.0.1:5244/dav",
"vendor": "115 Open",
"user": "webdav",
"pass": "1",
"mountPoint": "Z:",
"volumeName": null,
"extraFlags": ["--buffer-size=32M", "--vfs-cache-max-age=24h", "--vfs-cache-max-size=10G", "--vfs-cache-mode=minimal", "--bwlimit=10M:100M", "--checkers=8", "--transfers=8", "--vfs-read-chunk-size=128M", "--allow-root"],
"autoMount": true,
"networkMode": true
}
现象
登录后 Z: 长时间不可用,约 40–45 秒后才完成挂载;依赖该盘符的第三方程序启动被明显拖慢。
部分登录场景下,自动挂载未在合理时间窗口内发生,表现为“挂载失败/超时”,只能手动挂载。
日志中存在矛盾信息:autoMount=true,但启动日志明确输出 No Rclone remotes configured for auto-mount on login,说明登录自动挂载路径实际被跳过。
时间线(app.log,典型一次登录)
时间 | 事件 -- | -- 23:02:55 | openlist-desktop 启动 23:02:56 | Settings loaded;Auto-start on login is enabled 23:02:59 | openlist_core 启动完成 23:02:59 | No Rclone remotes configured for auto-mount on login(与 autoMount=true 矛盾) 23:03:02 | Fetching openlist/rclone versions from https://api.github.com/... 23:03:34 | rclone_mount_115Pan_process 才被注册并启动(+32 秒) (手动执行rclone挂载命令) ~23:03:40 | Z: 可访问,挂载完成 ## 日志摘录 ```LOG 2026-08-10 23:02:59.983906800 [openlist_desktop_lib] INFO No Rclone remotes configured for auto-mount on login 2026-08-10 23:03:02.864504600 [openlist_desktop_lib::cmd::os_operate] INFO Fetching rclone versions from: https://api.github.com/repos/rclone/rclone/releases 2026-08-10 23:03:34.283016400 [openlist_desktop_lib::core::process_manager] INFO Registering process 'rclone_mount_115Pan_process' 2026-08-10 23:03:34.335293400 [openlist_desktop_lib::core::process_manager] INFO Started process 'rclone_mount_115Pan_process' (pid: 25272) with command: D:\Program Files (x86)\OpenList-Desktop\rclone.exe mount --config ... 115Pan: Z: --network-mode=true ... ```重现步骤
在 OpenList Desktop 中配置 115(或任意 WebDAV)remote,勾选自动挂载(autoMount=true、networkMode=true、volumeName 留空)。
重启/重新登录 Windows。
观察 Z: 出现时间,并查看 %APPDATA%\OpenList Desktop\logs\app.log。
预期行为
autoMount=true 的 remote 应在 openlist core 就绪后立即自动挂载,不依赖 GitHub 版本检查。
volumeName 为 null 不应使 autoMount 失效;network-mode 挂载应自动生成 volume_name 或允许为空。
日志应逐个 remote 输出自动挂载决策,而非笼统输出 No Rclone remotes configured。
实际行为
自挂载失败
操作系统
Windows 11
系统架构
x64 (64位)
OpenList Desktop 版本
OpenList Desktop v0.9.
应用程序日志
2026-08-10 23:02:59.983906800 [openlist_desktop_lib] INFO No Rclone remotes configured for auto-mount on login
2026-08-10 23:03:02.864504600 [openlist_desktop_lib::cmd::os_operate] INFO Fetching rclone versions from: https://api.github.com/repos/rclone/rclone/releases
2026-08-10 23:03:34.283016400 [openlist_desktop_lib::core::process_manager] INFO Registering process 'rclone_mount_115Pan_process'
2026-08-10 23:03:34.335293400 [openlist_desktop_lib::core::process_manager] INFO Started process 'rclone_mount_115Pan_process' (pid: 25272) with command: D:\Program Files (x86)\OpenList-Desktop\rclone.exe mount --config ... 115Pan: Z: --network-mode=true ...
其他信息
疑似根因
登录自动挂载的过滤条件为 auto_mount && mount_point 非空 && volume_name 非空(见 auto_mount_rclone_remotes_on_login)。当前 network-mode 配置下 volumeName 为 null,导致该 remote 被登录自动挂载逻辑静默跳过——这正是 No Rclone remotes configured for auto-mount on login 的来源。后续实际发生的挂载疑似由其他路径(前端 UI 自动挂载)触发,而非登录自动挂载。
即使挂载最终被触发,其启动明显等待 Fetching ... versions from api.github.com 完成;在 GitHub 不可达或响应慢的网络环境(如中国大陆)下,该检查会显著阻塞挂载启动,甚至导致挂载迟迟不发生。
检查清单
- 我已搜索现有问题以确保这不是重复问题
- 我已提供所有必需的环境信息
- 我可以稳定地重现此问题
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the auto_mount_rclone_remotes_on_login entry point and trace how the remote configuration filters autoMount, mountPoint, and volumeName. Then inspect the startup path around the GitHub rclone version fetch and compare it with the supplied app.log timeline. Done means eligible network-mode remotes mount after core readiness without waiting for version checks, with per-remote decisions logged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- tauri
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100