SeaDrive + Win11 = failed to read request from shell extension: The pipe has been ended.

[working-name]

Hello!

First off: really messy install. You're asking for a cache directory but still create %userprofile%\seafile and dump stuff in there like logs. Could be much cleaner if you put everything in the path you asked me to define. That way the path I expect to contain everything about seafile actually does.

Secondly, seadrive will not download a single thing. It updates windows explorer icons to the blue syncing icon but nothing moves. No status reported in the GUI, no error displayed. You have to go dig through the log to get to the issue. Not a user-friendly approach if we're going to call something GUI. Is it ready for windows 11 or did I jump the gun? Is SeaDrive abandonware? Should I actually use the standalone sync client instead? Not very clear on your site.

Here's the seadrive-gui.log:

[10/22/23 13:29:29] starting applet rpc service
[10/22/23 13:29:29] applet rpc service started
[10/22/23 13:29:29] seadrive gui started
[10/22/23 13:29:29] loaded 0 accounts
[10/22/23 13:29:29] Using cache directory: C:\Users\me\Documents\seadrive_cache
[10/22/23 13:29:29] starting seadrive daemon: seadrive.exe "-d" "C:/Users/me/seadrive/data" "-l" "C:/Users/me/seadrive/logs/seadrive.log" "C:\\Users\\me\\Documents\\seadrive_cache"
[10/22/23 13:29:32] [ext listener] listening on \\.\pipe\seadrive_ext_pipe_bWU=
[10/22/23 13:30:47] Unable to get config value download_limit: Config not exists
[10/22/23 13:30:47] Unable to get config value upload_limit: Config not exists
[10/22/23 13:30:47] Unable to get config value delete_confirm_threshold: Config not exists
[10/22/23 13:33:23] failed to parse file path: "C:/Users/me/Documents/seadrive_cache/admin/My Libraries/Folder/S1/Some.pdf"
[10/22/23 13:33:23] [ext] invalid path C:/Users/me/Documents/seadrive_cache/admin/My Libraries/Folder/S1/Some.pdf
[10/22/23 13:33:26] failed to parse file path: "C:/Users/me/Documents/seadrive_cache/admin/My Libraries/Folder/S1/Some.pdf"
[10/22/23 13:33:26] [ext] invalid path C:/Users/me/Documents/seadrive_cache/admin/My Libraries/Folder/S1/Some.pdf
[10/22/23 13:33:28] failed to parse file path: "C:/Users/me/Documents/seadrive_cache/admin/My Libraries/Folder/S1/Some.pdf"
[10/22/23 13:33:28] [ext] invalid path C:/Users/me/Documents/seadrive_cache/admin/My Libraries/Folder/S1/Some.pdf
[10/22/23 13:33:29] failed to parse file path: "C:/Users/me/Documents/seadrive_cache/admin/My Libraries/Folder/S1/Some.pdf"
[10/22/23 13:33:29] [ext] invalid path C:/Users/me/Documents/seadrive_cache/admin/My Libraries/Folder/S1/Some.pdf
[10/22/23 13:33:34] failed to read request from shell extension: The pipe has been ended.

[10/22/23 13:33:40] failed to parse file path: "C:/Users/me/Documents/seadrive_cache/admin/My Libraries/Folder/S1/Some.pdf"
[10/22/23 13:33:40] [ext] invalid path C:/Users/me/Documents/seadrive_cache/admin/My Libraries/Folder/S1/Some.pdf
[10/22/23 13:33:45] failed to read request from shell extension: The pipe has been ended.

[10/22/23 13:33:54] failed to parse file path: "C:/Users/me/Documents/seadrive_cache/admin/My Libraries/Folder/S1/Week 13/AS/Lec/1-Upper Limb Osteo ILA_McNary_Thomas McNary.docx"
[10/22/23 13:33:54] [ext] invalid path C:/Users/me/Documents/seadrive_cache/admin/My Libraries/Folder/S1/Week 13/AS/Lec/1-Upper Limb Osteo ILA_McNary_Thomas McNary.docx
[10/22/23 13:33:55] failed to parse file path: "C:/Users/me/Documents/seadrive_cache/admin/My Libraries/Folder/S1/Week 13/AS/Lec/1-Upper Limb Osteo ILA_McNary_Thomas McNary.docx"
[10/22/23 13:33:55] [ext] invalid path C:/Users/me/Documents/seadrive_cache/admin/My Libraries/Folder/S1/Week 13/AS/Lec/1-Upper Limb Osteo ILA_McNary_Thomas McNary.docx
[10/22/23 13:34:00] failed to read request from shell extension: The pipe has been ended.

[10/22/23 13:34:07] failed to parse file path: "C:/Users/me/Documents/seadrive_cache/admin/My Libraries/Folder/S1/Week 13/AS/Lec/1-Upper Limb Osteo ILA_McNary_Thomas McNary.docx"
[10/22/23 13:34:07] [ext] invalid path C:/Users/me/Documents/seadrive_cache/admin/My Libraries/Folder/S1/Week 13/AS/Lec/1-Upper Limb Osteo ILA_McNary_Thomas McNary.docx
[10/22/23 13:34:12] failed to read request from shell extension: The pipe has been ended.

[10/22/23 13:34:59] failed to parse file path: "C:/Users/me/Documents/seadrive_cache/admin/My Libraries/Folder/S1/Some.pdf"
[10/22/23 13:34:59] [ext] invalid path C:/Users/me/Documents/seadrive_cache/admin/My Libraries/Folder/S1/Some.pdf
[10/22/23 13:35:00] failed to parse file path: "C:/Users/me/Documents/seadrive_cache/admin/My Libraries/Folder/S1/Some.pdf"
[10/22/23 13:35:00] [ext] invalid path C:/Users/me/Documents/seadrive_cache/admin/My Libraries/Folder/S1/Some.pdf
[10/22/23 13:35:02] failed to parse file path: "C:/Users/me/Documents/seadrive_cache/admin/My Libraries/Folder/S1/Some.pdf"
[10/22/23 13:35:02] [ext] invalid path C:/Users/me/Documents/seadrive_cache/admin/My Libraries/Folder/S1/Some.pdf
[10/22/23 13:35:07] failed to read request from shell extension: The pipe has been ended.

[10/22/23 13:35:51] failed to parse file path: "C:/Users/me/Documents/seadrive_cache/admin/My Libraries/Folder/S1/Some.pdf"
[10/22/23 13:35:51] [ext] invalid path C:/Users/me/Documents/seadrive_cache/admin/My Libraries/Folder/S1/Some.pdf
[10/22/23 13:35:53] failed to parse file path: "C:/Users/me/Documents/seadrive_cache/admin/My Libraries/Folder/S1/Some.pdf"
[10/22/23 13:35:53] [ext] invalid path C:/Users/me/Documents/seadrive_cache/admin/My Libraries/Folder/S1/Some.pdf
[10/22/23 13:35:54] failed to parse file path: "C:/Users/me/Documents/seadrive_cache/admin/My Libraries/Folder/S1/Some.pdf"
[10/22/23 13:35:54] [ext] invalid path C:/Users/me/Documents/seadrive_cache/admin/My Libraries/Folder/S1/Some.pdf
[10/22/23 13:35:59] failed to parse file path: "C:/Users/me/Documents/seadrive_cache/admin/My Libraries/Folder/S1/Some.pdf"
[10/22/23 13:35:59] [ext] invalid path C:/Users/me/Documents/seadrive_cache/admin/My Libraries/Folder/S1/Some.pdf
[10/22/23 13:36:04] failed to read request from shell extension: The pipe has been ended.

[10/22/23 13:45:34] failed to parse file path: "C:/Users/me/Documents/seadrive_cache/admin/My Libraries/Folder/S1/Some.pdf"
[10/22/23 13:45:34] [ext] invalid path C:/Users/me/Documents/seadrive_cache/admin/My Libraries/Folder/S1/Some.pdf
[10/22/23 13:45:36] failed to parse file path: "C:/Users/me/Documents/seadrive_cache/admin/My Libraries/Folder/S1/Some.pdf"
[10/22/23 13:45:36] [ext] invalid path C:/Users/me/Documents/seadrive_cache/admin/My Libraries/Folder/S1/Some.pdf
[10/22/23 13:45:37] failed to parse file path: "C:/Users/me/Documents/seadrive_cache/admin/My Libraries/Folder/S1/Some.pdf"
[10/22/23 13:45:37] [ext] invalid path C:/Users/me/Documents/seadrive_cache/admin/My Libraries/Folder/S1/Some.pdf
[10/22/23 13:45:42] failed to read request from shell extension: The pipe has been ended.

Other than that I'm just testing out your software. I'm not sure why but you chose to go the scattered documentation way. Maybe because you don't have someone to maintain them? Not sure. But finding how to get a full suite of seafile going via docker for example is 50% manual labor. And there's no penetrance for your features. For example what the heck is SeaDoc? How do I read about it? Its features? What does it look like? Is it useful to me? How do I know? And if I decide to try it out I have manually update files which apparently get overwritten with the next version of the docker container?! 🤷‍♂️ Very odd choices. Lots to clean up.

Also, "documentation moved here" is 1990. Just redirect.

[killing]

It should be some issues with your client or server environment. You can check seadrive.log for more useful information. The client works on most of our users' computers.

[working-name]

I wiped seadrive and switched to the basic system tray client because it wasn't syncing. I do remember perusing the logs and the seadrive.log had basic stuff like some service started or listening or similar. Nothing interesting there. In fact I couldn't get to the bottom of it on my own which is why I reached out. Doesn't seem like you have come across this much either, so it could be an isolated thing. If you want me to run a debug version or something similar I'd be happy to help.

[rorschach-py]

almost the same problem on Windows Server2019 Desktop, Seadrive 3.0.7
Explorer warn when deleting file: invalid file handle. (create/copy/move a file works well)

seadrive-gui.log:
failed to read request from shell extension: ????????