Skip to content

win10系统上,当用户目录使用相对路径时,重启系统后小狼毫服务读取用户目录异常 #563

@mokapsing

Description

@mokapsing

@lotem @Prcuvu @nameoverflow
win10系统下,当设置用户目录路径为相对路径(e.g. ..\UserData)时,在系统重启后,小狼毫服务进程读取用户目录会产生异常,导致输入功能不可用
image

当前本人注册表启动项为计算机\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Run
image
rime日志如下

Log file created at: 2020/09/22 22:27:08
Running on machine: DESKTOP-7DUJJ5V
Log line format: [IWEF]mmdd hh:mm:ss.uuuuuu threadid file:line] msg
E0922 22:27:08.742835 11180 deployment_tasks.cc:87] Error creating user data dir: ..\UserData
W0922 22:27:08.742835 11180 config_data.cc:62] nonexistent config file '..\UserData\installation.yaml'.
E0922 22:27:08.742835 11180 config_data.cc:41] failed to save config to stream.
W0922 22:27:08.742835 11180 config_data.cc:62] nonexistent config file 'C:\WINDOWS\SysWOW64\..\UserData\build/weasel.yaml'.
W0922 22:27:23.376289  4200 config_data.cc:62] nonexistent config file 'C:\WINDOWS\SysWOW64\..\UserData\build/default.yaml'.
W0922 22:27:23.376289  4200 config_data.cc:62] nonexistent config file 'C:\WINDOWS\SysWOW64\..\UserData\user.yaml'.
W0922 22:27:23.407532  4200 config_data.cc:62] nonexistent config file 'C:\WINDOWS\SysWOW64\..\UserData\build/.default.schema.yaml'.

当注册表信息在WOW6432Node下时,会读取 C:\WINDOWS\SysWOW64..\UserData\ 下的文件
另外本人也验证过,将启动项手动改为计算机\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run 时,日志中则显示会读取 C:\WINDOWS\System32..\UserData\下的文件
怀疑是win10注册表特性变化, 因为本人从win7时就一直习惯以相对路径(..\UserData)设置用户目录
希望本人提供的信息会方便你们开发人员修复此问题
以下为日志文件,希望能有所帮助
rime.weasel.DESKTOP.zip

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      pFad - Phonifier reborn

      Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

      Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


      Alternative Proxies:

      Alternative Proxy

      pFad Proxy

      pFad v3 Proxy

      pFad v4 Proxy